FE

About the Failure Elimination Work
Process
The Failure Elimination Work Process is focused on identifying past failures and
eliminating future failures. The Failure Elimination Work Process consists of the steps
that are outlined in the following table.
Step Description
Details
Understand asset Allows you to use the APM Foundation work process to classify
performance.
your assets and evaluate event history and production losses.
Identify
opportunities.
Allows you to identify chronic events and bad actors based upon
information such as number of work orders, work order cost, and
lost production.
Perform an
investigation.
Allows you to identify how a given failure occurs and take the
appropriate corrective measures to eliminate the identified causes.
Determine
solutions.
Allows you to recommend changes to improve overall asset

performance and communicate your findings and those
recommendations to decision makers.
Implement
solutions.
Allows you to use the APM Foundation work process to track

recommendations through Recommendation Management.
Track
performance.
Allows you to measure the effectiveness of your strategy

implementation, which can transform your corporate visions into
strategies and measures, aligning your key performance indicators
to your company's objectives and strategies.
The following image shows an illustration of how all the steps in the Failure Elimination
Work Process relate to one another. Each step in the work process is represented by a blue
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:
Production Loss Accounting
Generation Management
Metrics and Scorecards
Root Cause Analysis
Reliability Analytics
Asset Answers Integration
V3.6.0.0.0 - Copyright 1993-2014 Meridium, Inc. All rights reserved.
Failure Elimination System

Requirements
Multiple licenses are required to take advantage of Failure Elimination modules. In
addition to the following licenses, your system must contain the Meridium APM system
architecture:

Root Cause Analysis
Asset Answers Integration
After you have configured the basic system architecture and licensed these modules, you
will need to perform configuration steps for each module.
First-Time Deployment Workflow
Deploying and configuring the Failure Elimination Work Process for the first time
includes completing multiple steps, which are outlined in the table in this topic. All of the
steps are required to fully implement the Failure Elimination Work Process. These steps
provide all the information that you need to deploy Failure Elimination with the basic
Meridium APM architecture.
Step Task
1
Configure the Production Loss

Accounting module.
Configure the Generation Management

module.
Configure the Metrics and Scorecards

module.
Configure the Root Cause Analysis

module.
Configure the Reliability Analytics

module.
Configure the Asset Answers

integration.
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 Failure Elimination module/feature:

Root Cause Analysis
Failure Elimination User Instructions

The user instructions for Failure Elimination modules are provided in the documentation
for the related module. Documentation for the Failure Elimination dashboard is provided
in the Failure Elimination Reference Information documentation.
Accessing the Failure Elimination

Dashboard
You can access the Failure Elimination dashboard to view information about pieces of
equipment and locations that you analyze using Failure Elimination modules.
To access the Failure Elimination dashboard:
On the Meridium APM Framework main menu, click Go To, point to Failure
Elimination, and then click Dashboard.
The Dashboard page appears, displaying the Failure Elimination dashboard.
Aspects of the Failure Elimination

Dashboard
The Failure Elimination dashboard contains sections that display information about the
pieces of equipment and locations that you analyze using Failure Elimination modules.
The Failure Elimination dashboard contains the following sections:
Content Filter
Yearly Cost Trend
Top 10 Bad Actors
Completed RCAs
# of FE Recommendations Implemented
Track Results by Recommendation Implementation Year
Outstanding FE Recommendations
The Failure Elimination dashboard also contains additional sections that are hidden by
default.
Note: Your use of the Failure Elimination dashboard will depend upon your role in your
organization and the Failure Elimination modules that are associated with your role. For
example, you might choose to display certain sections and hide others depending on the
type of data that you want to view on the dashboard. This documentation does not assume
a workflow for using the Failure Elimination dashboard. Instead, details on working with
dashboards in general and information on the sections that are displayed on the dashboard
and their supporting Catalog items are provided.
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
Area
Unit
Yearly Cost Trend

The Yearly Cost Trend is a configured Chart - Series section that displays a bar graph that
plots on a yearly basis, for the past 10 years, the sum of:
The Maintenance Cost value in Work History records in your database.
-and
Values in Production Loss records and Production Event records in your database.
The following image shows an example of the Yearly Cost Trend section.
Top 10 Bad Actors

The Top 10 Bad Actors section is a configured Chart - Series section that displays a bar
graph that plots one bar for each of the 10 Equipment records in the database that are
associated with the highest combined:
Maintenance cost (sum of Maintenance Cost values in associated Work History

records).
-and
Lost production cost (sum of values in associated Production Loss records and
Production Event records).
The following image shows an example of the Top 10 Bad Actors section.
Completed RCAs
The Completed RCAs section is a configured Chart - Series section that displays a bar
graph that plots on a yearly basis, for the past five years, the number of RCA Analysis
records that were set to the Published state.
The following image shows an example of the Completed RCAs section.
# of FE Recommendations Implemented
The # of FE Recommendations Implemented section is a configured Chart - Series
section that displays a bar graph that plots on a yearly basis, for the past five years, the
number of Reliability Recommendation records and RCA Recommendation records that
were set to the Implemented state.
Track Results by Recommendation

Implementation Year
The Track Results by Recommendation Implementation Year section is a configured
Chart - Series section that displays a line graph that plots on a yearly basis, for the past
five years, the trend of the combined maintenance cost (sum of Maintenance Cost values
in associated Work History records) and lost production cost (sum of values in associated
Production Loss records and Production Event records) for Equipment record whose
associated Reliability Recommendation or RCA Recommendation record was set to the
Implemented state in one of the last five years. Each line that is displayed on this graph
represents one of these years, as indicated by the legend at the bottom of this section.
Outstanding FE Recommendations
The Outstanding FE Recommendations section is a configured List - Query Result section
that displays the Headline list, which contains one hyperlink for each RCA
Recommendation record and Reliability Recommendation record in your database that
meet the following criteria:
The Completed Date field (in the Reliability Recommendation record) or

Implemented Date field (in RCA Recommendation record) does not contain a
value.
Note: The datasheet caption for the Completed Date field in Reliability Recommendation
records is Implemented Date.
The Target Completion Date field contains a date that is equal to or before 30
days after the current date.
The hyperlink text corresponds with the value in the Recommendation Headline field in
the RCA Recommendation record or Reliability Recommendation record. When you
click a hyperlink in the Headline list, the RCA Recommendation record or Reliability
Recommendation record is displayed in Record Manager.
The following image shows an example of the Outstanding FE Recommendations
section.
Hidden Sections on the Failure

Elimination Dashboard
The Failure Elimination dashboard contains the following sections that are hidden by
default:
Top 10 Bad Actors (w/o PLA)

Yearly Cost Trend (w/o PLA)
Track Results by Recommendation Implementation Year (w/o PLA)
These sections should be redisplayed only if the Production Loss Accounting license is
not active. This documentation assumes that the licenses for all Failure Elimination
modules are active. As such, no additional documentation is provided for these sections.
About the Failure Elimination Catalog

Folder Structure
The main Failure Elimination Catalog folder is \\Public\Meridium\Modules\Failure
Elimination. 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 Failure Elimination 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\Failure Elimination\Dashboards. The dashboard is listed by
name in the table. The dashboard name and caption are the same.
Dashboard
Behavior and Usage
Failure Elimination
Dashboard
Displays the Failure Elimination dashboard on the

Dashboard page.
Dashboard Queries Folder

The following table lists the queries that are stored in the Catalog location
\\Public\Meridium\Modules\Failure Elimination\Queries\Dashboard Queries. The queries
are listed by name in the table. The query name and caption are the same.
Query
Behavior and Usage
FE Dashboard Query - Completed Used by one or more source queries to the Failure
RCAs by Year
Elimination dashboard.
Used to return results that are displayed in the
FE Dashboard Query - Completed
Completed RCAs section on the Failure Elimination
RCAs by Year for Graph
dashboard.
FE Dashboard Query - Costs from Used by one or more source queries to the Failure
Work History by Year
FE Dashboard Query - Equipment
Used by one or more source queries to the Failure
with FE Recommendations
Implemented
FE Dashboard Query - Equipment Used by one or more source queries to the Failure
with FE Recommendations
Implemented - All Years

FE Dashboard Query - FE
Recommendations Implemented

FE Dashboard Query - FE
Used to return results that are displayed in the # of FE
Recommendations Implemented for Recommendations Implemented section on the
Graph
Failure Elimination dashboard.
FE Dashboard Query - Filter
Widget

Content Filter section on the Failure Elimination
dashboard.
FE Dashboard Query - Last 10

Years

FE Dashboard Query - Last 12

Months

FE Dashboard Query - Last 5 Years

FE Dashboard Query - Lost

Productions Costs

FE Dashboard Query - Lost

Production Costs by Year

FE Dashboard Query Maintenance Costs by Year

FE Dashboard Query - Outstanding Used by one or more source queries to the Failure
FE Recommendations
FE Dashboard Query - Outstanding
Outstanding FE Recommendations section on the
FE Recommendations for Graph
Failure Elimination dashboard.
FE Dashboard Query Recommendation States

Used to return results that are displayed in the Top 10

FE Dashboard Query - Total Costs
Bad Actors section on the Failure Elimination
by Equipment - Top 10
dashboard.
Used to return results that are displayed in the Top 10

Bad Actors (w/o PLA) section on the Failure
FE Dashboard Query - Total Costs
from Work History - Top 10
Note: This section is hidden by default. You should
redisplay this section only if the Production Loss
Accounting license is not active.
FE Dashboard Query - Total Costs Used by one or more source queries to the Failure
from Work History by Equipment Elimination dashboard.
FE Dashboard Query - Total Lost
Production Costs by Equipment

FE Dashboard Query - Total Lost

Production Costs by Equipment Sub Query

FE Dashboard Query - Total

Maintenance Costs by Equipment

FE Dashboard Query - Track result Used by one or more source queries to the Failure
- Costs from Work History
FE Dashboard Query - Track Result Used by one or more source queries to the Failure
- Maintenance Costs
- Production Loss Costs
FE Dashboard Query - Track Result
- Production Loss Costs - Sub
Query
- Total
Used to return results that are displayed in the Track
FE Dashboard Query - Track Result
Results by Recommendation Implementation Year
- Total for Graph
section on the Failure Elimination dashboard.
- Total from Work History
Used to return results that are displayed in the Track
FE Dashboard Query - Track Result Results by Recommendation Implementation Year
(w/o PLA) section on the Failure Elimination

dashboard.
- Total from Work History for
Graph

Used to return results that are displayed in the Yearly

FE Dashboard Query - Yearly Cost
Cost Trend section on the Failure Elimination
Trend for Graph
dashboard.
Used to return results that are displayed in the Yearly
Cost Trend (w/o PLA) section on the Failure
FE Dashboard Query - Yearly Cost
Trend from Work History
Overview of Production Loss

Accounting
The goal of all companies is to lower risk, reduce expenses, and produce a quality
product at a predictable rate and cost while maintaining reliability. While owners and
managers know the maximum amount they can produce during optimal operating and
financial conditions, most companies rarely produce this amount on a regular basis.
Inevitably, unplanned events occur that cause them to produce less than the desired
amount. For example, a machine might stop working, causing workers to stop production
while they wait for the machine to be repaired. In other cases, planned events cause
production to slow down or stop. For example, planned shutdowns and predictable
decreases in demand based on historical patterns can lead to production losses.
As a result of decreased production, companies incur costs and are unable to earn
maximum profit.
Meridium APM Production Loss Accounting (PLA) allows you to:
Enter production data.

Identify production losses and associate them with the events that caused them.
Determine what types or categories of events cause your company to lose the
most production.
By entering and evaluating production data, you can more easily identify ways in which
you can reduce unplanned downtime and increase production in the future, which will
result in reduced cost and increased profit.
Consider the following graph, which represents a company's optimal, planned, and actual
production percentage for a year.
In this graph, you can see from the blue line that the maximum demonstrate rate, or the
percentage of output the company can produce during optimal operating conditions, is
100%.
The yellow area displays the planned production percentage for each month. Because the
managers know that they cannot produce 100% of this maximum output each month, the
planned production rate is lower than 100% during some months. In March, the planned
production rate is 0% because the company plans to shut down that month to perform
maintenance, install new equipment, and so on.
The red bars indicate the actual production rate each month. You can see that in some
months, the company produced the amount they planned, and in other months, they
produced less than they had planned.
From this graph, managers might conclude that more than half of their lost production for
the year was due to the shutdown in March. If they could find a way to reduce this
shutdown time or eliminate it completely, they would see a great increase in overall
production.
Based on other data entered using PLA, managers would also be able to determine
exactly how much money they lost during the March shutdown and how much money
they lost during other months in which they did not reach the 100% production rate. They
could then categorize these losses into planned and unplanned losses. D
PLA System Requirements

The Production Loss Accounting license is required to take advantage of PLA
functionality. In addition, your system must contain the basic Meridium APM system
architecture.
Hint: Details on the system requirements for the basic architecture and activating
licenses can be found in the Installation, Upgrade, and System Administration section of
the Meridium APM Help system.
After you have installed and configured the basic architecture, you will need to perform
some configuration tasks specifically for the PLA feature.
Additionally, if you want to view Metric Views that are provided as baseline PLA
content, you will need to deploy the Metrics and Scorecards module. This module
requires additional hardware and software.
PLA Data Model
The following image provides a diagram of the entity families and relationship families
involved in the PLA data model. In the image, boxes represent entity families, and arrows
represent relationship definitions.
Notice that in the baseline PLA data model, you can link:
A Production Unit record (predecessor) to a Functional Location record

(successor) that stores additional information about that production unit.
A Production Event record (successor) to an Equipment record (predecessor) to
represent the piece of equipment that caused the production event.
A Production Event Template record (successor) to an Equipment record
(predecessor) to represent the piece of equipment that caused the production
events that will be created from the Production Event Template record.
Note: The Production Long Range Plan family is activated with the Production Loss
Accounting license, but it is not used in the PLA workflow. It is excluded, therefore, from
the data model image.
Example Used Throughout the PLA

Documentation
Throughout this documentation, we explain PLA terminology and concepts using the
example of a facility that produces the following products:
Bottles
Labels
Caps
We assume that these products are shipped to another facility that is responsible for
processes that you might analyze using a Production Analysis, such as filling the bottles
with water, attaching the labels and caps, and distributing the finished water bottles to
customers such as grocery stores and vending machine companies.
Accessing the PLA Start Page

To access the PLA Start Page:
On the Meridium APM Framework menu bar, click Go To, point to Failure
Elimination, and then click Production Loss Accounting.
The PLA Start Page appears.
Aspects of the PLA Start Page

The PLA Start Page serves as the starting point for the tasks that you can perform in
Production Loss Accounting (PLA). 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 production
data. The PLA Start Page is shown in the following image.
The following links are available:
Production Data Management: Displays the Find Production Plan window,

where you can search for the Production Plan record that you want to open on the
Production Data Entry page.
Production Plan Management: Displays the Find Production Unit window, where
you can search for the Production Unit record that you want to open on the
Manage Production Plans page.
Production Event Management: Displays the Production Event Management
page, where you can manage Production Event records.
Metrics and Analysis: Displays the Metric & Analyses page, where you can create
and open Production Analyses and open Metric Views that display data about a
specific production unit.
Note: The Metrics and Analysis link appears on the PLA Start page only if the Metrics
and Scorecards and/or Reliability Analytics module is active. If neither is active, the link
does not appear and you will not be able to access the Metric Views and Production
Analyses page.
Administration: Displays the Products page, where you can add, modify, and
delete Product records. From this page, you can access other pages that allow you
to perform administrative tasks.
Note: The Administration link appears on the PLA Start page only if you are a member of
the MI Production Loss Accounting Administrator Security Group.

Deploying and configuring the Production Loss Accounting (PLA) module 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 PLA 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 PLA
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
2
Deploy the Metrics and

Scorecards module.
Required/Optional Notes
Required
Review the PLA data model Optional

to determine which
This step is required if you want to

view Metric Views that are provided
as baseline PLA content.
This step is necessary only if you
store equipment and location
relationship definitions you

will need to modify to
include your custom
equipment and location
families. Modify any
relationship definitions as
needed via Configuration
Manager.
information in families other than

the baseline Equipment and
Functional Location families.
Required
3
Assign the desired Security

Users to one or more PLA
Security Groups in
Configuration Manager.
User must have permissions to the

PLA families in order to use the PLA
functionality.
Optional
Change the default currency

symbol.
The currency symbol is set by

default to $ and displayed in the
following places:
Default Margin field on the

Production Profile datasheet.
Production Summary tab of

the Production Data Entry
page.
Required
5
Define all products.

Required
Define production units.
Required
7
Define production profiles.
You will need to define all products

whose production you plan to track
using PLA. Each product is stored in
a Product record.
You will need to identify the
production units that produce the
products you defined in the previous
task. Note that a single product can
be produced by more than one
production unit. A single production
unit can also produce more than one
product.
Each production unit is stored in a
Production Unit record, which can
be linked to an existing Functional
Location record that contains more
detailed information about the
production unit.
For each production unit that you
defined in the previous task, you will
need to identify all the products they

produce and information about those
products, such as the maximum
demonstrated rate of production and
the amount of profit one of those
products yields. The combination of
data about a product and the
corresponding production unit is the
production profile for that
production unit. A production unit
will have one production profile for
each product it produces.
Required
Define production event

codes.
Each production profile is stored in a

Production Profile record, which is
linked to the corresponding Product
record and Production Unit record.
You will need to use production
event codes to categorize the types
of events that can cause you to
produce less than the maximum
sustained capacity amount.
Production event codes define the
cause of lost production and answer
the question: Why are we losing
production? You can also group the
types of events by structuring them
in a hierarchy. For example, you
might group event types into planned
and unplanned, where planned
events are events such as
maintenance down days or employee
holidays, and unplanned events are
events such as equipment failures or
natural disasters (e.g., floods or
hurricanes).
Each event type will be stored in a
separate Production Event Code
record.
Optional
9
Define impact codes.
The baseline Meridium APM

database contains Impact Code
records that define a set of basic
impact codes. Therefore, this step is
required only if you do not want to
use the baseline impact codes or if

you want to use codes in addition to
those that are provided.
10
11
Define OEE codes.
Define values that will be

mapped to a Production
Analysis.
Optional
The baseline Meridium APM

database contains OEE Code records
that define a set of basic OEE codes.
Therefore, this step is required only
if you do not want to use the baseline
OEE codes or if you want to use
codes in addition to those that are
provided. For non-baseline codes to
be included in the OEE Metric View,
however, they must be children of
the baseline parent codes.
Optional
By default, certain PLA values are

mapped to the production data in a
Production Analysis. If you want to
map different or additional PLA
values, you can do so by modifying
the All Production Data query.
Required
12
Deploy the Production Data

cube and Equipment Costs
Data cube on the SQL
Server Analysis Server.
Configure PLA for PDI
Optional
Integration:
Define production
event templates.
Link Production
Profile records to Xi
Tag records.
13
You will need to deploy the cubes so

that users can access Metric Views
that display a graphical
representation of production data.
This step is required only if you

want to use the integration between
PLA and the Process Data
Integration feature where Production
Event records are created
automatically.
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 Production Loss Accounting

from V3.5.1 to V3.6.0.0.0
The following table lists the steps that are required to upgrade and configure PLA for
V3.6.0.0.0. These steps assume that you have completed the steps for upgrading the
components in the basic Meridium APM system architecture.
Step Task
1
Required
Deploy the Production Data cube and Equipment Costs

Data cube on the SQL Server Analysis Server.
None

from V3.5.0 SP1 LP to V3.6.0.0.0
Step Task
Required
1

None

from V3.5.0 to V3.6.0.0.0
Step Task
1
Required

None

from V3.4.5 to V3.6.0.0.0
Step Task
Optional
Define OEE codes.
You can use the baseline OEE Code records

that are provided in the Meridium APM
database. If you do not want to use the OEE
Code records that are provided, you will
need to create custom OEE codes to
identify the types of losses you can incur.
Each OEE code will be stored in an OEE
Code record.
Define values that

will be mapped to a Optional
Production Analysis.
Deploy the
Production Data
cube and Equipment
Costs Data cube on
the SQL Server
Analysis Server.
By default, certain PLA values are mapped

to the production data in a Production
Analysis. If you want to map different or
additional PLA values, you can do so by
modifying the All Production Data query.
Required
None
PLA Security Groups

The baseline Production Loss Accounting (PLA) module contains the following Security
Groups:
MI Production Loss Accounting Administrator

MI Production Loss Accounting Manager
MI Production Loss Accounting Service
MI Production Loss Accounting User
The following table lists the default privileges that members of each group have to the
PLA entity and relationship families.
Family
Entity Families
MI Production Loss MI Production MI Production MI Production

Accounting
Loss Accounting Loss Accounting Loss Accounting
Administrator
Manager
Service
User
Equipment
View, Update,
Insert, Delete
View
View
None
Functional
Location
View
View
View
None
Impact Code
View, Update,
Insert, Delete
View
View
View
Interface Log
View, Update,
Insert, Delete
View
View
View
OEE Code
View, Update,
Insert, Delete
View
View
View
Product
View, Update,
Insert, Delete
View
View
View
Production
Analysis
View, Update,
Insert, Delete
None
View
View, Update,
Insert, Delete
Production Data
View, Update,
Insert, Delete
View
View, Update,
Insert, Delete
View, Update,
Insert, Delete
Production
Event
View, Update,
Insert, Delete
View
View, Update,
Insert, Delete
View, Update,
Insert, Delete
Production
Event Code
View, Update,
Insert, Delete
View
View
View
Production
View, Update,
Event Template Insert, Delete
View
View
View, Update,
Insert, Delete
Production Long View, Update,

Range Plan
Insert, Delete
View
View, Update,
Insert, Delete
View, Update,
Insert, Delete
Production Loss
View, Update,
Insert, Delete
View
View, Update,
Insert, Delete
View, Update,
Insert, Delete
Production
Losses
View, Update,
Insert, Delete
None
View, Update,
Insert, Delete
View, Update,
Insert, Delete
Production Plan
View, Update,
Insert, Delete
View
View
View, Update,
Insert, Delete
Production
Target
View, Update,
Insert, Delete
View
View
View, Update,
Insert, Delete
SSAS Server
View
View
None
View
Xi Reading
None
None
View
None
Xi Tag
View
None
View
None
Relationship Families
Analysis Link
View, Update,
Insert, Delete
None
View
View, Update,
Insert, Delete
Caused by
Production
Event
View, Update,
Insert, Delete
View
View, Update,
Insert, Delete
View, Update,
Insert, Delete
Has Base
Production
Event Code
View, Update,
Insert, Delete
View
View, Update,
Insert, Delete
View, Update,
Insert, Delete
Has Child
Production
Event Code
View, Update,
Insert, Delete
View
View, Update,
Insert, Delete
View
Has Impact
Code
View, Update,
Insert, Delete
View
View, Update,
Insert, Delete
View, Update,
Insert, Delete
Has Losses
View, Update,
Insert, Delete
View
View, Update,
Insert, Delete
View, Update,
Insert, Delete
Has OEE Code
View, Update,
Insert, Delete
View
View, Update,
Insert, Delete
View, Update,
Insert, Delete
Has Product
View, Update,
Insert, Delete
View
View, Update,
Insert, Delete
View
Has Production View, Update,

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

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

Event Code
Insert, Delete
View
View, Update,
Insert, Delete
View, Update,
Insert, Delete

Event Template Insert, Delete
View
View, Update,
Insert, Delete
View, Update,
Insert, Delete
Has Production
View, Update,
Long Range
Insert, Delete
Plan
View
View, Update,
Insert, Delete
View, Update,
Insert, Delete

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

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

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

Unit
Insert, Delete
View
View, Update,
Insert, Delete
View, Update,
Insert, Delete
Has Reference
Documents
View, Update,
Insert, Delete
View
View
View, Update,
Insert, Delete
Has Reliability
View, Update,
Insert, Delete
None
View
View, Update,
Insert, Delete
Has Unit Profile
View, Update,
Insert, Delete
View
View, Update,
Insert, Delete
View
Has Work
History
View, Update,
Insert, Delete
View
View, Update,
Insert, Delete
View, Update,
Insert, Delete
Production
View, Update,
Event Has RCA
Insert, Delete
Analysis
View
View, Update,
Insert, Delete
View, Update,
Insert, Delete
Is Production
Unit
View, Update,
Insert, Delete
View
View, Update,
Insert, Delete
View
Xi Tag Has
View, Update,
Production
Insert, Delete
Event Template
View
View, Update,
Insert, Delete
View, Update,
Insert, Delete
Changing the Currency Symbol

When you define a production profile for a product, you specify the default margin, or the
profit associated with a single unit of that product. When you enter production losses, the
total cost of those losses is displayed on the Production Summary tab. In each case, the
cost is displayed using the currency symbol that is defined in the Currency dialog box.
The default currency symbol is $. If desired, you can change the currency symbol using
these instructions.
Note: You can change the currency on any page that is accessible via the Administration
link. The following instructions show how to change the currency using the
Administration link on the Products page. If you want to change the currency from a
different page, you can skip step 1 and start with step 2 of these instructions.
To change the currency:
1. In the Meridium APM Framework application, on the PLA Start Page, click the
Administration link.
The Products page appears.
2. On the Settings menu, click the Currency link.

The Currency dialog box appears.
3. In the Currency text box, type the desired currency symbol.

4. Click OK.
The currency symbol is saved and will be displayed anywhere that a cost value appears in
PLA.
Setting the Precision of Calculated

Values
On the Production Data Entry page, the following values are calculated in the Meridium
APM system:
Cost of Losses
Unaccounted Loss
In each case, the resulting calculated value will be displayed using the number of
decimals defined by the Display Precision setting. The default precision value, or number
of decimal places that will be displayed, is two. If desired, you can change the number of
decimal places that appear for the Cost of Losses and Unaccounted Loss values using the
following instructions.
Note: You can change this setting from any page where the Display Precision link
appears. The following instructions show how to change the precision using the Display
Precision link on the Products page. If you want to change the precision from a different
page, you can skip step 1 and start with step 2 of these instructions.
To set the precision of calculated values:
2. On the Settings menu, click the Display Precision link.

The Display Precision dialog box appears.
3. In the Cost of Losses text box, type the desired number of decimal places for the
Cost of Losses value on the Production Summary tab. This value must be greater
than or equal to 0 (zero) and less than or equal to 9.
4. In the Unaccounted Loss text box, type the desired number of decimal places for
the values in the Unaccounted Loss column in the grid on the Production Data
tab. This value must be greater than or equal to 0 (zero) and less than or equal to
9.
5. Click OK.
The precision values are saved.
Accessing the Products Page

To access the Products page:
In the Meridium APM Framework application, on the PLA Start Page, click the
Aspects of the Products Page

The Products page contains the following items:
Task menu pane: Contains the following task menus:
Administrative Tasks menu
Settings menu
Common Tasks menu
Associated Pages menu
Products pane: Contains the following items:
A tree that displays all the Product records that exist in the database.
The Add Products button.
The Delete Products button.
Datasheet area: Displays the datasheet for the Product record that is selected in
the tree in the Products pane.
Administrative Tasks Menu

The Administrative Tasks menu on the Products page contains the following links:
Products: Displays the Products page. A green arrow appears to the left of this
link when you are viewing this page.
Production Units: Displays the Production Units and Profiles page.
Production Event Coding: Displays the Production Event Coding page.
Impact Coding: Displays the Impact Coding page.
OEE Coding: Displays the OEE Coding page.
Production Event Templates: Displays the Event Templates page.
Settings Menu
The Settings menu on the Products page contains the following link:
Currency: Displays the Currency dialog box, where you can specify the currency
symbol that will be used throughout PLA.
Display Precision: Displays the Display Precision dialog box, where you can
specify the number of decimal places that will be used for displaying calculated
values on the Production Data Entry page.
Common Tasks Menu
The Common Tasks menu on the Products page contains the following links:
Print: Displays the Preview window, which shows a preview of how the datasheet
that appears in the datasheet area will be printed. From the Preview window, you
can select print options and print the record. This link is enabled only when a
record is selected in the tree.
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. This link is enabled only when a record is selected in the tree.
Documents: Displays the Reference Documents window, where you can manage
Reference Document records for the Product record that is currently selected in
the Products pane. This link is enabled only when a record is selected in the tree.
Help: Displays the context-sensitive Help topic for the Products page.
Associated Pages Menu
The Associated Pages menu on the Products page displays links only if Associated Pages
have been configured for the Product family. If no Associated Pages have been
configured for the Product family, the Associated Pages menu will be empty.
Products Pane
The Products pane on the Products page contains a tree that displays all Product records
that exist in the database. The root level of the tree displays the family grouping Products,
which is represented by the
icon. Directly below the family node are nodes
representing Product records. Each record is represented by the icon. To the right of
each icon is the Record ID.
For example, suppose the following Product records exist in the database: Bottles, Caps,
and Labels. In this case, the tree would look like this:
Below the tree are the following buttons:
Add Product: Displays a blank Product datasheet in the datasheet area, where you
can create a new Product record.
Delete Product: After asking for confirmation, deletes the selected Product
record.
Creating a Product Record

To create a Product record:
1. In the Meridium APM Framework application, on the Products page, below the
tree, click the Add Product button.
A new blank datasheet appears to the right of the Products pane.
2. Enter data into the fields as desired.

3. When you are finished completing the fields, on the datasheet toolbar, click the
Save current record button.
The Product record is saved.
Deleting a Product Record

To delete a Product record:
1. In the Meridium APM Framework application, on the Products page, in the tree,
select the Product record that you want to delete.
2. Below the tree, click the Delete Product button.
A message appears, asking if you are sure you want to delete the record.
3. Click the Yes button.
The Product record is deleted.
Accessing the Production Units and

Profiles Page
To access the Production Units and Profiles page:
2. On the Administrative Tasks menu, click the Production Units link.

The Production Units and Profiles page appears.
Aspects of the Production Units and

Profiles Page
The Production Units and Profiles page contains the following items:
Settings Menu
Common Tasks menu
Production Units pane: Contains the following items:
A tree that displays all the Production Unit records that exist in the
database.
The Add Units button.
The Delete Units button.
Datasheet area: Displays the following items:
The Production Unit tab, which displays the datasheet for the Production
Unit record that is selected in the tree in the Units pane.
The Production Profiles tab, which lets you create Production Profile
records that are linked to the Production Unit record that is selected in the
tree.

The Administrative Tasks menu on the Production Units and Profiles page contains the
following links:
Products: Displays the Products page.

Production Units: Displays the Production Units and Profiles page. A green arrow
appears to the left of this link when you are viewing this page.
Settings Menu
The Settings menu on the Production Units and Profiles page contains the following
links:
Common Tasks Menu
The Common Tasks menu on the Production Units and Profiles page contains the
following links:
Reference Document records for the Production Unit record that is currently
selected in the Units pane. This link is enabled only when a record is selected in
the tree.
Help: Displays the context-sensitive Help topic for the Production Units and
Profiles page.

The Associated Pages menu on the Production Units and Profiles page displays links
only if Associated Pages have been configured for the Production Unit family. If no
Associated Pages have been configured for the Production Unit family, the Associated
Pages menu will be empty.
Production Units Pane

The Production Units pane on the Production Units and Profiles page contains a tree that
displays all Production Unit records that exist in the database. The root level of the tree
displays the family grouping Production Units, which is represented by the icon.
Directly below the family node are nodes representing the Production Unit records. Each
record is represented by the icon. To the right of each icon is the Record ID.
For example, suppose the following Production Unit records exist in the database: Unit
A, Unit B, and Unit C. In this case, the tree would look like this:
Add Unit: Displays a blank Production Unit datasheet in the datasheet area, where
you can create a new Production Unit record.
Delete Unit: After asking for confirmation, deletes the selected Production Unit
record.
Creating Production Unit Records

To create a Production Unit record:
1. In the Meridium APM Framework application, on the Production Units and
Profiles page, below the tree, click the Add Unit button.
A new blank datasheet appears to the right of the Units pane.

3. If you want to link the Production Unit record to a Functional Location record
containing more information about the production unit, in the Associated Unit
cell, click the button.
The Find Unit window appears, displaying the Simple Search workspace. The value in
the Search In list is set by default to Functional Location.
4. If desired, refine the search criteria.

5. When you are finished defining the search criteria, click the Find Now button.
6. In the search results list, select the record to which you want to link to the
Production Unit record, and click the Open button.
The selected record is linked to the Production Unit record. The Record ID of the selected
record appears in the Associated Unit cell as a hyperlink, which you can click to open the
datasheet for the record.
button.
The Production Unit record is saved.
Linking Production Unit Records to

Functional Location Records
A production unit is a collection of equipment and locations that are used to facilitate a
process. PLA uses Production Unit records to store the name and description of your
production units.
If you have implemented the Meridium APM product according to the Meridium APM
Best Practice, your database will also contain Functional Location records that store
additional information about production units. If desired, using the Associated Unit field
in Production Unit records, you can link a PLA Production Unit record to a Functional
Location record that contains more information about that production unit. Combined, the
two records contain all the information about the production unit.
Deleting Production Unit Records

Note: You can delete a Production Unit record only if it is not linked to any Production
Profile records.
To delete a Production Unit record:
Profiles page, in the tree, select the Production Unit record that you want to
delete.
2. Below the tree, click the Delete Unit button.
The Production Unit record is deleted.
About Production Profiles

For each production unit for which you have created a Production Unit record, you will
need to identify all the products it produces and information about those products, such as
the maximum sustained rate of production and the amount of profit one of those products
yields. The combination of data about a product and the corresponding production unit is
the production profile for that production unit.
In terms of the PLA data model, one Production Unit record will be linked to one or more
Production Profile records, as shown in the following image. Each Production Profile
record is linked to a single Product record representing the product that the production
unit produces. In addition, each Production Profile record is linked to one or more
Production Plan records representing the planned production for that production unit and
product combination. The image shows these relationships. The arrows represent
relationship families, and the boxes represent entity families. The Production Profile
family is outlined in red.
Each production unit can produce more than one product. For example, in a waterbottling facility, a single production unit might be responsible for producing both bottles
and labels. A production unit will have one production profile for each product it
produces. In other words, if a production unit produces two products, that production unit
will have two production profiles.
Alternatively, multiple production units can produce the same product. For example, in a
facility that produces water bottles, bottle labels, and bottle caps, the water bottles might
be produced by multiple production units. This ensures that if one production unit fails,
some water bottles will continue to be produced by the other production unit.
Example of One Unit Producing

Multiple Products
Consider the following image, where a single production unit, Unit A, produces multiple
products: Bottles and Labels. You can see that each production unit and product
combination has its own production profile (outlined in red).
For Unit A's bottle production, the production profile indicates that Unit A is
capable of producing 5000 bottles per day, where each bottle yields a $5.00 profit.
For Unit A's label production, the production profile indicates that Unit A is
capable of producing 8000 labels per day, where each label yields a $2.00 profit.
You can also see that for each combination of a production unit, production profile, and
product, multiple production plans exist.
Example of Multiple Units Producing

the Same Product
A single product can be produced by more than one production unit. Consider the
following image, which shows the product Bottles being produced by two production
units, Unit A and Unit B. You can see that each production unit and product combination
has its own production profile (outlined in red).
For Unit A, the production profile indicates that Unit A is capable of producing
5000 bottles per day, where each bottle yields a $5.00 profit.
For Unit B, the production profile indicates that Unit B is capable of producing
4000 bottles per day, where each bottle yields a $5.00 profit.
You can also see that for each combination of a production unit, production profile, and
product, multiple production plans exist.
Creating Production Profile Records

To create a Production Profile record:
Profiles page, in the tree, select the Production Unit record to which you want to
link a new Production Profile record.
The datasheet for the selected Production Unit record appears on the Production Unit tab
to the right of the Production Units pane.
2. Click the Production Profiles tab.

The Production Profiles tab appears.
3. Above the Production Profile datasheet, click the Add Profile button.
A new blank Production Profile datasheet appears.
4. In the datasheet, enter data into the fields as desired. The Standard Batch Size
field is required.
button.
The Production Profile record is saved and linked to the:
Production Unit record that is selected in the tree.
Product record that is represented by the product that you selected in the
Product field.
Xi Tag record that is represented by the tag that you selected in the Xi Tag
ID field.
In addition, a row is added to the grid above the datasheet, displaying the Record ID of
the new Production Profile record.
What If the Margin Changes Over

Time?
In some cases, the product margin, or the amount of profit that one unit of that particular
product yields, changes over time. For example, consider a company that produces water
bottles. If consumers start buying more bottled water versus carbonated soft drinks, the
profit that a single bottle yields might increase.
In this case, in any Production Profile record that defines water bottle production from a
particular unit, you would want to change the value in the Default Margin field to
represent the current margin at that time.
The value in the Default Margin field in the Production Profile record is copied to the
Margin field in all new Production Data records. For instance, if on July 1 the value in the
Default Margin field is 5.00, new Production Data records that are created on or after
July 1 will contain the value 5 in the Margin field. If, however, on July 16 you change the
value in the Default Margin field to 6.00, any new Production Data records that are
created on or after July 16 will contain the value 6 in their Margin field.
Keep in mind that Production Data records are created automatically when you access the
Production Data Entry page. The number of records that are created depends upon the
day on which you access the page and the planning period of the Production Plan record
that you selected when you accessed the page.
For example, suppose the planning period in a Production Plan record is July 1 through
July 31. If you were to access the Production Data Entry page for that Production Plan
record for the first time on July 15, fifteen Production Data records would be created (one
for each day between July 1 and July 15). Each of those records would contain the same
value in the Margin field because they were all created at the same time.
If you were to increase the value in the Default Margin field on July 16 and access the
Production Data Entry page again on July 16, one new Production Data record would be
created to represent July 16, and the value in its Margin field would be the updated value
in the Default Margin field in the Production Profile record.
Note: Although the value in the Default Margin field in a Production Profile record is
used to determine the default value in the Margin field in Production Data records, if
desired, users who are responsible for entering production data can modify the margin in
Production Data records using the Production Data Entry page.
Deleting Production Profile Records

Note: You can delete a Production Profile record only if it is not linked to any Production
Plan records.
To delete a Production Profile record:
Profiles page, in the tree, select the Production Unit record that is linked to the
Production Profile record that you want to delete.
The datasheet for the selected Production Unit record appears on the Production Unit tab
to the right of the Units pane.
2. Click the Production Profiles tab.

3. In the grid, select the Production Profile record that you want to delete.
4. Below the grid, click the Delete Profile button.
A message appears, asking if you are sure that you want to delete the Production Profile
record.
Note: If you are attempting to delete a Production Profile record that is linked to one or
more Production Plan records, the message asks you to delete the Production Plan records
before deleting the Production Profile record.
The Production Profile record is deleted and removed from the grid.
Accessing the Production Event Coding

Page
To access the Production Event Coding page:
2. On the Administrative Tasks menu, click the Production Event Coding link.
The Production Event Coding page appears.
Aspects of the Production Event Coding

Page
The Production Event Coding page contains the following items:
Settings menu
Common Tasks menu
Production Event Codes pane: Contains the following items:
A tree that displays all the Production Event Code records that exist in the
database.
The Add Code button.
The Delete Code button.
Datasheet area: Displays the datasheet for the Production Event Code record that
is selected in the tree in the Production Event Codes pane.

The Administrative Tasks menu on the Production Event Coding page contains the
following links:

Production Event Coding: Displays the Production Event Coding page. A green
arrow appears to the left of this link when you are viewing this page.
Settings Menu
The Settings menu on the Production Event Coding page contains the following link:
Common Tasks Menu
The Common Tasks menu on the Production Event Coding page contains the following
links:
Reference Document records for the Production Event Code record that is
currently selected in the Production Event Codes pane. This link is enabled only
when a record is selected in the tree.
Help: Displays the context-sensitive Help topic for the Production Event Coding
page.

The Associated Pages menu on the Production Event Coding page displays links only if
Associated Pages have been configured for the Production Event Code family. If no
Associated Pages have been configured for the Production Event Code family, the
Associated Pages menu will be empty.
Production Event Codes Pane

The Production Event Codes pane on the Production Event Coding page contains a tree
that displays all Production Event Code records that exist in the database. The root level
of the tree displays the family grouping Production Event Codes, which is represented by
the icon. Directly below the family node are nodes representing the Production Event
Code records. Each record is represented by the icon. To the right of each icon is the
Record ID.
Note that you can group Production Event Code records into categories, where each
category is also represented by its own Production Event Code record. For example,
suppose the following Production Event Code records exist in the database to categorize
types of events: Planned Shutdown, Unplanned Shutdown, and Unplanned Slowdown. In
each category, more specific types of events exist. In this case, the tree might look like
this:
Add Code: Displays a blank Production Event Code datasheet in the datasheet
area, where you can create a new Production Event Code record.
Delete Code: After asking for confirmation, deletes the selected Production Event
Code record.
Creating a Production Event Code

Record
To create a Production Event Code record:
1. In the Meridium APM Framework application, on the Production Event Coding
page, in the tree, select the node below which you want the new Production Event
Code record to appear.
2. Click the Add Code button.
A new blank datasheet appears to the right of the Production Event Codes pane.
3. Complete the fields as desired.

The Production Event Code record is saved.
Deleting a Production Event Code

Record
To delete a Production Event Code record:
1. In the Meridium APM Framework application, on the Production Event Coding
page, in the tree, select the Production Event Code record that you want to delete.
2. Below the tree, click the Delete Code button.
The Production Event Code record is deleted.
Accessing the Impact Coding Page

To access the Impact Coding page:
2. On the Administrative Tasks menu in PLA, click the Impact Coding link.
The Impact Coding page appears.
Aspects of the Impact Coding Page

The Impact Coding page contains the following items:
Settings menu
Common Tasks menu
Impact Codes pane: Contains the following items:
A tree that displays all the Impact Code records that exist in the database.
Datasheet area: Displays the datasheet for the Impact Code record that is selected
in the tree in the Impact Codes pane.
Baseline Impact Code Records

The following Impact Code records are provided in the baseline Meridium APM
database:
Code Description
TADD Turnaround Down Days

RMDD Routine Maintenance Down Days
RMSD Routine Maintenance Slowdown Days
RPDD Regulatory-Process Down Days
RPSD Regulatory-Process Slowdown Days
OTDD Other Down Days
OTSD Other Slowdown Days

The Administrative Tasks menu on the Impact Coding page contains the following links:

Impact Coding: Displays the Impact Coding page. A green arrow appears to the
left of this link when you are viewing this page.
Settings Menu
The Settings menu on the Impact Coding page contains the following link:
Common Tasks Menu
The Common Tasks menu on the Impact Coding page contains the following links:
Reference Document records for the Impact Code record that is currently selected
in the Impact Codes pane. This link is enabled only when a record is selected in
the tree.
Help: Displays the context-sensitive Help topic for the Impact Coding page.

The Associated Pages menu on the Impact Coding page displays links only if Associated
Pages have been configured for the Impact Code family. If no Associated Pages have
been configured for the Impact Code family, the Associated Pages menu will be empty.
Impact Codes Pane

The Impact Codes pane on the Impact Coding page contains a tree that displays all
Impact Code records that exist in the database. The root level of the tree displays the
family grouping Impact Codes, which is represented by the icon. Directly below the
family node are nodes representing the Impact Code records. Each record is represented
by the icon. To the right of each icon is the Record ID.
For example, suppose the following Impact Code records exist in the database:
Opportunity Loss, Product Loss, and Outside Loss. In this case, the tree would look like
this:
Add Code: Displays a blank Impact Code datasheet in the datasheet area, where
you can create a new Impact Code record.
Delete Code: After asking for confirmation, deletes the selected Impact Code
record.
Creating an Impact Code Record

Note: If you create new impact codes and would like to use those impact codes instead of
the baseline codes in the Mechanical Availability, On-Stream Factor, or Operational
Availability Metric Views, you will need to modify the corresponding Metric View
calculations for the Production Data cube in SQL Server Analysis Services. Instructions
for completing this task are not provided in the Meridium APM Documentation. For more
information, consult your Microsoft documentation.
To create an Impact Code record:
1. In the Meridium APM Framework application, on the Impact Coding page, below
the tree, click the Add Code button.
A new blank datasheet appears to the right of the Impact Codes pane.

The Impact Code record is saved.
Deleting an Impact Code Record

To delete an Impact Code record:
1. In the Meridium APM Framework application, on the Impact Coding page, in the
tree, select the Impact Code record that you want to delete.
The Impact Code record is deleted.
About OEE Codes

Many companies report how well a manufacturing operation is running overall using
Overall Equipment Effectiveness codes, or OEE codes. These codes categorize
production losses using three specific areas: equipment availability, performance, and
product quality. The losses associated with these categories are then used to calculate an
overall OEE percentage, which indicates the effectiveness of the production process.
The goal is to reach a 100% OEE level, or 100% efficiency. In order to achieve this, each
category must operate at 100% (i.e., 0 losses are assigned to each category). The OEE
level is a standard way to measure efficiency that can be compared across industries (e.g.,
electric and refining).
In the Meridium APM system, you can categorize losses according to OEE codes via the
OEE Code field in Production Loss records. After production losses are categorized using
OEE codes, for each production unit, you can view the overall OEE percentage that is
calculated by the Meridium APM system via the OEE Metric View. To simply view the
production loss amount attributed to each OEE code, you can view the Losses by OEE
Code Metric View.
Baseline OEE Code Records

The baseline Meridium APM database contains a set of baseline OEE code records that
define basic OEE Codes. Each OEE code is either a parent code or a child code. In
general, parent codes are used to categorize high-level losses, and child codes further
divide those categories into more specific areas. Both parent codes and child codes are
stored in OEE Code records.
You can also create custom OEE codes. Only the baseline codes and their children,
however, will be used to calculate the OEE percentage in the OEE Metric View.
Therefore, in order for custom OEE codes to be included in the OEE percentage
calculation, they must be children of the baseline parent OEE codes.
The following OEE Code records are provided in the baseline Meridium APM database.
Parent
Code
Child Codes
Description
Scheduled
Downtime
Availability
Setup/Clean
Indicates that a production loss is due to resources that
Up
are unavailable for use (e.g., scheduled maintenance).
Unscheduled
Downtime
No Demand
Idle Time
No Feedstock or
Raw Material
Not scheduled for
production
Indicates that a production loss is due to available

resources that are currently not in use (e.g., a piece of
equipment is available for use, but there are not enough
employees to operate it). Losses associated with the Idle
Time OEE code are included in the calculations for other
categories (availability, performance, and quality). Idle
Time does not represent its own OEE category.
Minor Stops
Performance
Quality
Reduced Rate
Startup Rejects
Indicates that a production loss is due to resources that

are not performing at 100% capacity.
Indicates that a production loss is due to poor quality

Production Rejects product that could not be used.
Accessing the OEE Coding Page

To access the OEE Coding page:
2. On the Administrative Tasks menu in PLA, click the OEE Coding link.
The OEE Coding page appears.
Overview of the OEE Coding Page

The OEE Coding page contains the following items:
Settings menu
Common Tasks menu
OEE Codes pane: Contains the following items:
A tree that displays all the OEE Code records that exist in the database.
Datasheet area: Displays the datasheet for the OEE Code record that is selected
in the tree in the OEE Codes pane.
The Administrative Tasks menu on the OEE Coding page contains the following links:

OEE Coding: Displays the OEE Coding page. A green arrow appears to the left of
this link when you are viewing this page.
Settings Menu
The Settings menu on the OEE Coding page contains the following link:
Common Tasks Menu
The Common Tasks menu on the OEE Coding page contains the following links:
Reference Document records for the OEE Code record that is currently selected in
the OEE Codes pane. This link is enabled only when a record is selected in the
tree.
Help: Displays the context-sensitive Help topic for the OEE Coding page.

The Associated Pages menu on the OEE Coding page displays links only if Associated
Pages have been configured for the OEE Code family. If no Associated Pages have been
configured for the OEE Code family, the Associated Pages menu will be empty.
OEE Codes Pane
The OEE Codes pane on the OEE Coding page contains a tree that displays all OEE Code
records that exist in the database.
The root level of the tree displays the text OEE Coding, which is represented by the
icon. Directly below the OEE Coding node are nodes representing OEE Code records.
Each record is identified by the icon and the Record ID. Parent OEE codes exist on the
first level of the hierarchy. To see the child codes of each parent OEE code, you can
expand each parent node to view the second level of the hierarchy.
To the left of each node is a check box, which indicates whether or not the code is
enabled. You can clear the check box to disable the code or select the check box to enable
the code. Only enabled codes can be assigned to production losses. Disabling codes
allows you to restrict them from being used without deleting them from the system. For
example, if you wanted to use the code Startup Rejects only during certain times of the
year, you could disable the Startup Rejects code when you are not using it, and enable it
again later.
The following buttons appear below the tree:
Add Code: Displays a blank OEE Code datasheet in the datasheet area, where you
can create a new OEE Code record.
Delete Code: After asking for confirmation, deletes the selected OEE Code
record.
Creating an OEE Code Record

You can create either a parent OEE code or an OEE code that is the child of another OEE
code.
Note: New child OEE Code records can be added to enabled parent OEE Code records
only.
To create an OEE Code record:
1. In the Meridium APM Framework application, access the OEE Coding page.
2. If you want to create a parent code, select the root OEE Coding node, and click
the Add Code button.
-orIf you want to create a child node, in the OEE Codes pane, select the code that you want
to serve as the parent code, and click the Add Code button.
A new blank datasheet appears to the right of the OEE Codes pane.
3. In the OEE Code text box, type a short name for the OEE code.
4. In the Description text box, type a description of the OEE code.
5. Click the
button.
The OEE Code record is saved.
Disabling OEE Codes

If you are a member of the MI Production Loss Accounting Administrator Security Group
or a Super User, you can disable OEE codes on the OEE Coding page. Disabling an OEE
code prevents users from assigning that code to a Production Loss record without
deleting the record. On the Production Data Entry page, when you are assigning an OEE
code to a loss in the Losses section, disabled OEE codes will be gray in the Select OEE
Code window and you will not be able to select them.
If you disable a parent OEE Code record, its child OEE Code records will be disabled
automatically. Likewise, if you enable a parent OEE Code record, its child OEE Code
records will be enabled automatically. You can enable or disable child nodes, however,
without affecting the state of the parent node. You cannot add a child OEE Code record to
a disabled OEE Code record.
To disable an OEE code:
In the Meridium APM Framework application, in the tree on the OEE Coding
page, clear the check box next to the OEE code that you want to disable.
Note: If the check box is already cleared, you can select it to enable the code.
The OEE code is disabled, and the value in the Is Inactive field is set automatically to
True. In the following image, the parent node Performance and its child nodes are
disabled.
Deleting an OEE Code Record

To delete an OEE Code record:
1. In the Meridium APM Framework application, on the OEE Coding page, in the
tree, select the OEE Code record that you want to delete.
Note: When you delete an OEE code record that has children, the message will warn you
that its children will also be deleted.
The OEE Code record is deleted.
Deploying the Production Data and

Equipment Costs Data Cubes
The Production Data cube is used to build the Metric Views that are provided in the
Catalog folder \\Public\Meridium\Modules\PLA\Metrics, with one exception, the Total
Cost of Unreliability Metric View, which is built using the Equipment Costs Data cube.
The following instructions explain how to deploy the Production Data cube and
Equipment Costs Data cube. These instructions are intended to be used only by users who
are familiar with Microsoft SQL Server Analysis Services and Microsoft SQL Server
Business Intelligence Development Studio and the help systems that exist within each
application. These instructions assume that you have already installed both of these
components.
To deploy the Equipment Costs Data cube and the Production Data cube:
1. In Microsoft SQL Server Business Intelligence Development Studio, open the file
Production Loss Analysis.dwproj. This file is located on the Meridium APM
Framework and Server Setup DVD in one of the following folders. You will need
to use the file in the folder that corresponds to the type of database you are using.
1.
For an Oracle database: \\Meridium APM Framework and Server

Setup\Configuration\PLA Analysis Services Project\Oracle
1.
For an SQL Server database: \\Meridium APM Framework and Server

Setup\Configuration\PLA Analysis Services Project\SQL
Note: If you are opening the Production Loss Analysis.dwproj file for the first time, the
first time you try to save changes to the project, you will be prompted to save the project
to your local machine.
2. In Microsoft SQL Server Business Intelligence Development Studio, in the
properties for the Production Loss Analysis project, identify the Analysis Services
Server that you want to use to deploy the cubes.
Note: You must have permission to access the selected Analysis Services Server in order
for the cubes to deploy correctly.
3. In Microsoft SQL Server Business Intelligence Development Studio, in the
properties for the Production Loss Analysis project, check that the Analysis
Services database is set to Production Loss Analysis. This is the database to which
the project will be deployed. The value Production Loss Analysis is populated
automatically and must not be modified in order for the cubes to deploy correctly.
4. In Microsoft SQL Server Business Intelligence Development Studio, open the
data source Meridium.ds, and identify the connection information for the
Meridium data source to which you want to deploy the cubes.
5. In Microsoft SQL Server Business Intelligence Development Studio, process the
cubes. You can process each cube individually or process both cubes at once by
processing the entire Production Loss Analysis project.
6. In the Meridium APM Framework application, using the Record Manager, open
the Analysis Services Cube record Production Data. In the Analysis Services
Server text box, type the name of the Analysis Services Server.
7. In the Meridium APM Framework application, using the Record Manager, open
the Analysis Services Cube record Equipment Costs Data. In the Analysis
Services Server text box, type the name of the Analysis Services Server.
8. In the Meridium APM Framework application, using the Metrics and Scorecards
module, grant permission to the Production Data cube record and the Equipment
Data Costs cube record to all Security Users and Security Groups whose members
should be allowed to view the PLA Metric Views. Note that all baseline PLA
Security Groups have permission to the Production Data cube and the Equipment
Data Costs cube. If you are using Security Groups outside of this Security Group,
you will need to determine if they will also need permissions to these records.
About Configuring the All Production

Data Query
The All Production Data query, which is located in the Catalog folder
\\Public\Meridium\Modules\Reliability Manager\Analyses, determines which values from
records in the Production Loss Accounting module are mapped to the Production Data
field in Production Analysis records. The Production Data field stores code, which
represents the production data that, along with the mapping supplied through this query,
is used to create the Production Analysis plot. If you want to map values from custom
fields to the Production Data field, you will need to modify the All Production Data
query.
The baseline All Production Data query returns values from fields in Production Data and
Production Loss records, which are then mapped to the Production Data field in a
Production Analysis record. You can map values from a custom field in any record in the
Production Loss Accounting module by adding the field to the All Production Data query.
The baseline All Production Data query returns the following fields from the Production
Data family:
Period
Actual
MSCR
In a Production Analysis:
Values that are mapped from the Period field represent dates.
Values that are mapped from the Actual field represent production data.
Values that are mapped from the MSCR field represent the values against which
the Actual value is compared to determine if a loss occurred.
These values represent the underlying production data for the Production Analysis, which
you can view on the Edit Production Data window in the Production Analysis module.
If you are using fields other than the baseline fields to represent these values, you should
replace the baseline fields with your custom fields accordingly in the All Production Data
query. If you are using fields that contain values other than the values defined in the
baseline fields, you can add the custom fields to the All Production Data query in addition
to the baseline fields.
The baseline All Production Data query also returns the results of the Combined
Production Data Codes query, which returns the following fields from the Production
Loss family:
Impact Code
Event Code
OEE Code
You do not need to modify the Combined Production Data Codes query in order to map
values from custom fields to the Production Data field in a Production Analysis record.
You only need to add your custom field to the All Production Data query.
About Integration with Process Data

Integration
If the Process Data Integration feature has been configured correctly and an
administrative user has completed the necessary system administration steps for PLA, the
following PLA records will be created automatically as a result of the integration:
Production Data records. To enable this integration, you will need to link
Production Profile records to Xi Tag records. As a result, any readings that are
recorded in the associated Xi Reading records will be used to create Production
Data records automatically.
Production Event records. To enable this integration, you will need to create
Production Event Template records and link them to Xi Tag records. As a result,
any readings that are recorded in the associated Xi Reading records will be used
to create or update Production Event records automatically.
An Example of Creating Production

Data Records Automatically
Note: The following example assumes that you are using a daily production plan (i.e., one
Production Data record exists per day during the planning period). The same concept
applies to production plans on other schedules (e.g., weekly, per shift, and so on). In all
cases, dates and times in Xi Reading records are compared to the production planning
schedule to determine if a Production Data record should be created automatically (and
what its start and end dates should be).
Suppose that when your production process finishes filling, labeling, and capping a bottle
of water, the bottle is placed on a pallet. Each filled bottle weighs 40 pounds, and a single
pallet can hold up to 20 water bottles (800 pounds). Also, in a given day, the maximum
amount of product that you can produce is 5,000 bottles. In other words, at the end of the
day, you can fully stock 250 pallets, where the weight on each pallet is 800 pounds, and
the total weight on all pallets is 200,000 pounds.
These numbers are illustrated in the following image.
Given this scenario, you might want to track the amount of product that you produced
each day by measuring the weight on all pallets at the end of the day. To do so, you might
stack each pallet and then use a weight sensor to measure the total weight of the stack. If
the weight sensor records a value of 200,000 pounds, you know that you have met your
maximum production for the day.
In this case, you could use the Process Data Integration feature to create an Xi Tag record
for the weight sensor. The Xi Tag datasheet might look like this:
At the end of the day, the sensor would record the total weight on all pallets in the stack
that day, and the value would be transferred to an Xi Reading record. If the total weight
on 10/1/2011 and 10/2/2011 were 200,000 and 195,000, respectively, at the end of the
day on 10/2/2011, the database would contain Xi Reading records with the following
values.
If you have associated a Production Profile record with this Xi Tag record and that
Production Profile record is linked to a Production Plan record whose date range contains
the days on which the Xi Reading records were created (10/1/2011 and 10/2/2011), a
Production Data record would be created automatically for each reading. The value in the
Actual field in each Production Data record would identify the total weight on all pallets
for that day, where the total weight was originally recorded in the Xi Reading record.
The following image shows the datasheet for the Production Profile record that is linked
to this Xi Tag record. You can see the value Weight Sensor in the Xi Tag ID field.
In addition, the following image shows the production plan details for the Production
Plan record to which this Production Profile record is linked. You can see that the
planning period starts on 10/1/2011 (in the Plan Start Time field) and ends on 10/31/2011
(in the Plan End Time field).
Because these records and values exist, at the end of the day on 10/2/2011, two
Production Data records will have been created automatically to store the values that
were recorded by the weight sensor on those days. The following image shows what
those two Production Data records would look like on the Production Data Entry page.
The dates and actual values have been outlined in red.
Linking a Production Profile Record to

an Xi Tag Record
To link a Production Profile record to an Xi Tag record:
1. On the Production Units and Profiles page, in the tree, select the Production Unit
record that is linked to the Production Profile record to which you want to link an
Xi Tag record.
2. In the datasheet area, click the Production Profiles tab.
3. In the grid at the top of the tab, select the row representing the Production Profile
record that you want to link to an Xi Tag record.
The datasheet for the selected Production Profile record appears below the grid.
4. On the datasheet, in the Xi Tag ID cell, click the
button.
The Find Tag window appears, displaying the Simple Search workspace. The value in the
Search In list is set by default to Xi Tag. You cannot select a different value.

The search results appear below the search criteria.
7. In the search results list, select the Xi Tag record to which you want to link the
Production Profile record, and click the Open button.
The selected Xi Tag record is linked to the Production Profile record. The Record ID of
the selected Xi Tag record appears in the Xi Tag ID cell.
8. On the datasheet toolbar, click the
button.
The Production Profile record is saved.
An Example of Creating Production

Event Records Automatically
Suppose that as part of your company's water bottling process, you are required by state
regulation to remove 97% of all chemicals from the water during the purification process.
In this case, you might use a monitoring system that checks the percentage of remaining
chemicals in the purified water before it flows into the filling machine.
If the system detects that less than 97% of chemicals have been removed from the water,
a control valve closes to stop the water from entering the filling machine. In other words,
when the control valve is open, you know that at least 97% of chemicals have been
removed from the water, and it is safe to continue filling bottles with it. Likewise, when
the control valve is closed, less than 97% of chemicals have been removed, and no bottles
should be filled with that water until the problem is repaired. Throughout the day, the
control value would either be open or closed. If the valve were to close, it would indicate
the start of a production event, and when the valve reopened, it would indicate the end of
that production event.
In this case, you could use the Process Data Integration feature to create an Xi Tag record
for the control valve. The Xi Tag datasheet might look like this:
If the control valve were to close on 10/1/2011 at 10:53:00 A.M. and reopen on 10/1/2011
at 11:25:00 A.M., the database would contain Xi Reading records with the following
values.
If you have created a Production Event Template record that is linked to this Xi Tag
record and contains the values Open and Closed in the Normal State and Abnormal State
fields, respectively, one Production Event record would be created automatically when
the first reading is recorded (start of production event), and that same record would be
updated automatically when the second reading is recorded (end of production event).
The following image shows the datasheet for the Production Event Template record that
is linked to this Xi Tag record. You can see the value Control Valve in the Xi Tag ID field.
You can also see the value Open in the Normal State field and the value Closed in the
Abnormal State field.
Because this record and its values exist, at 10:53:00 A.M. on 10/1/2011, a Production
Event record would be created automatically to track the beginning of the production
event (i.e., the time at which the control valve closed). As shown in the following image,
the value in the Start Date field would be set to 10/1/2011 10:53:00 A.M. All other values
in the Production Event Template record would also be used to populate the
corresponding fields in the Production Event record.
At 11:25:00 A.M. on 10/1/2011, that same Production Event record would be updated
with the end date of 10/1/2011 11:25:00 A.M., as shown with the red outline in the
following image.
Accessing the Event Templates Page

To access the Event Templates page:
1. On the PLA Start Page, click the Administration link.
2. On the Administrative Tasks menu in PLA, click the Production Event Templates
link.
The Event Templates page appears.
Aspects of the Event Templates Page

The Event Templates page contains the following items:
Settings menu
Common Tasks menu
Event Templates pane: Contains the following items:
A tree that displays all the Production Event Template records that exist in
the database.
The Add Template button.
The Delete Template button.
Datasheet area: Displays the datasheet for the Production Event Template record
that is selected in the tree in the Event Templates pane.

The Administrative Tasks menu on the Event Templates page contains the following links:

Production Event Templates: Displays the Event Templates page. A green arrow
Settings Menu
The Settings menu on the Event Templates page contains the following link:
Common Tasks Menu
The Common Tasks menu on the Event Templates page contains the following links:
Documents: This link is always disabled.
Help: Displays the context-sensitive Help topic for the Event Templates page.

The Associated Pages menu on the Event Templates page displays links only if
Associated Pages have been configured for the Production Event Template family. If no
Associated Pages have been configured for the Production Event Template family, the
Associated Pages menu will be empty.
Event Templates Pane

The Event Templates pane on the Event Templates page contains a tree that displays all
Production Event Template records that exist in the database. The root level of the tree
displays the family grouping Production Event Templates, which is represented by the
icon. Directly below the family node are nodes representing the Production Event
Templates records. Each record is represented by the icon. To the right of each icon is
the Record ID.
For example, suppose a Production Event Template record with the Record ID Unit 21 ~
Control Valve exists in the database. In this case, the tree would look like this:
Add Template: Displays a blank Production Event Template datasheet in the

datasheet area, where you can create a new Production Event Template record.
Delete Template: After asking for confirmation, deletes the selected Production
Event Template record.
Creating a Production Event Template

Record
To create a Production Event Template record:
1. On the Event Templates page, below the tree, click the Add Template button.
A new blank datasheet appears to the right of the Event Templates pane.
2. Complete the fields as desired.

button.
The Production Event Template record is saved.
Deleting a Production Event Template

Record
To delete a Production Event Template record:
1. On the Event Templates page, in the tree, select the Production Event Template
record that you want to delete.
2. Below the tree, click the Delete Template button.
The Production Event Template record is deleted.
About Navigating the PLA Module

With the Meridium APM Framework application, the PLA module provides the following
navigational tools:
A start page with links that provide access to the main features of PLA. You can
use these links to complete the PLA workflow.
A Site Map that you can use to navigate within the PLA module. The Site Map
indicates your current location and shows the typical path for arriving there. To
access a previous page, you can click its hyperlinked name in the Site Map.
Using the PLA Site Map

The Site Map in PLA allows you to navigate from the current page to other pages in PLA.
The Production Loss Accounting link, which provides access to the PLA Start Page, will
always be available. Links to other pages may also be available, depending upon your
location in the application. You can click any link that is available to access the
corresponding page.
The following image shows an example of what the Site Map looks like on the
Production Data Entry page. A red outline has been added to the image to highlight the
Site Map.
PLA Workflow
The following workflow describes the basic tasks that you will perform in PLA:
1. For each production unit, create a production plan to specify the amount of
product you plan to produce during a set time period. You can create the plan on
any schedule, such as yearly, quarterly, monthly, and so on.
2. If an event such as an equipment failure or a planned shutdown occurs and causes
you to incur a production loss, document the event.
3. Enter production data on a daily basis. This includes entering the amount of
product you produced and accounting for any losses that you incurred each day.
About Production Plans

Each production unit can generate one or more products. For each product that it
generates, a production profile will exist to identify information about that product, such
as the maximum demonstrated rate of production and the amount of profit one of those
products yields.
For each production unit, a production plan will also exist to define several criteria, as
outlined in the following table.
Plan
Details
What
When
Description
Example
The products that you plan to produce. Each plan You plan to produce water
can include one or more products.
bottles and labels.
When: The time period for which you want to track When: You plan to produce
the production. In this case, you will provide the

start and end dates, and the planned product
bottles and labels from
quantity will be determined automatically based
January 1, 2010 through
upon the production profile. This option is called a
April 30, 2010.
time-based plan.
-orHow
Much
-or-
-or-
How Much: You plan to

How Much: The amount of each product that you
produce 50,000 bottles and
plan to produce. In this case, you will provide the
100,000 labels, starting
start time and the planned product quantity, and the
January 1, 2010.
end time will be determined automatically. This
option is called a quantity-based plan.
You have one shift running
8:00 A.M. to 5:00 P.M.
-or-
During
Which
Hours
The hours each day that you produce the specified

products.
You have two shifts:
8:00 A.M. to 8:00

P.M.
8:00 P.M. to 8:00

A.M.
You enter production data
daily.
How
Often You The frequency by which you enter production data -orEnter
and production losses.
Data
You enter production data
once per shift.
Each production plan is represented by a Production Plan record.
Simple Time-Based Plan

Plan Summary
The following example of a time-based plan assumes that your production plan meets the
following criteria:
Criteria
Data Used in This Example
How Much
One product (bottles)
When
January 1, 2010 through April 30, 2010
During Which Hours
Monday through Friday, 24 hours per day (8:00 A.M. to 8:00

A.M.)
How Often You Enter

Data
Daily
Plan Details
In this example, Production Unit A produces bottles in a water-bottling facility. Unit A's
production profile indicates that:
Unit A can generate 5,000 bottles per day.
One bottle yields a $5.00 profit.
For Unit A, you want to track production for four months, from January 2010 through
April 2010. For each month, you plan to produce the following number of bottles per day.
Month Planned Production (per day)

January 3,000 bottles
February 3,000 bottles
March
4,000 bottles
April
5,000 bottles
You can see that within each individual month, the company plans to produce the same
number of bottles each day of that month. The company does not, however, plan to
produce the same number of bottles per day across months.
In other words:
In the first two months, they plan to produce 3,000 bottles per day, every day.
In the third month, they plan to produce 4,000 bottles per day, every day.
In the fourth month, they plan to produce the maximum amount of bottles per day,
every day: 5,000.
This variation in planned production might be a result of increased demand for water
bottles as the months pass. For example, if the water bottle consumers are in a location
that experiences cold weather in January and February and an increased warming trend
starting in March, there is probably less demand for water bottles in January. Likewise,
starting in March and continuing in April, when the temperature is gradually getting
warmer, demand for water bottles increases, which causes the planned production for
those months to reach the maximum amount that the production unit can produce.
Production Plan Builder Selections

To produce this plan, you would select the following options in the Production Plan
Builder:
Select Products screen:
Plan Basis screen:
Time-Based Plan screen:
Useful Production Time screen:
Data Entry Frequency screen:
Plan Results
You can see that the calculated planned production each day (except Saturdays and
Sundays) is 5,000 bottles per day. This value is calculated automatically using the
standard batch size (5,000 bottles) and cycle time (1 day) in the associated production
profile for Unit A.
If you remember from the plan details explained earlier in this topic, you do not actually
plan to produce 5,000 bottles from January through April. Instead:
In January and February, you plan to produce 3,000 bottles per day.
In March, you plan to produce 4,000 bottles per day.
In April, you plan to produce the maximum amount of bottles per day, every day:
5,000.
To represent this plan in PLA, you would need to modify the plan details manually, so the
final result would look like this:
As you change the plan details, the total quantity, which is calculated automatically,
would be updated accordingly:
Complex Time-Based Plan

Plan Summary
The following example of a time-based plan assumes that your production plan meets the
following criteria:
Criteria
How Much
Two products (bottles and labels)
When
January 1, 2010 through April 30, 2010

Monday through Friday, 24 hours per day, two shifts:
During Which Hours
8:00 A.M. to 8:00 P.M.
8:00 P.M. to 8:00 A.M.
How Often You Enter Data Per Shift (i.e., twice a day)
Plan Details
In this example, Production Unit A produces bottles and labels in a water-bottling facility.
Unit A's production profiles indicate that:
Unit A can generate 5,000 bottles per day and 8,000 labels per day.
One label yields a $1.00 profit.
For Unit A, you want to track production for four months, from January 2010 through
April 2010. For each month, you plan to produce the following number of bottles and
labels per day.
Month Planned Bottle Production (per day) Planned Label Production (per day)
January 3,000 bottles
6,000 labels
February 3,000 bottles
6,000 labels
March
4,000 bottles
7,000 labels
April
5,000 bottles
8,000 labels
You can see that within each individual month, the company plans to produce the same
number of bottles and labels each day of that month. The company does not, however,
plan to produce the same number of bottles and labels per day across months.
In other words:
In the first two months, they plan to produce 3,000 bottles and 6,000 labels per
day, every day.
In the third month, they plan to produce 4,000 bottles and 7,000 labels per day,
every day.
In the fourth month, they plan to produce the maximum amount of bottles and
labels per day, every day: 5,000 bottle and 8,000 labels.
This variation in planned production might be a result of increased demand for water
bottles as the months pass. For example, if the water bottle consumers are in a location
that experiences cold weather in January and February and an increased warming trend
starting in March, there is probably less demand for water bottles in January. Likewise,
starting in March and continuing in April, when the temperature is gradually getting
warmer, demand for water bottles increases, which causes the planned production for
those months to reach the maximum amount that the production unit can produce.

Builder:
Plan Basis screen:
Plan Results
Sundays) is 2,500 bottles and 4,000 labels per shift. This value is calculated automatically
using the standard batch size (5,000 bottles and 8,000 labels) and cycle time (1 day) in
the associated production profiles for Unit A.
Bottles - Production Profile
Labels - Production Profile
If you remember from the plan details explained earlier in this topic, you do not actually
plan to produce 5,000 bottles and 8,000 labels from January through April. Instead:
In January and February, you plan to produce 3,000 bottles and 6,000 labels per
day.
In March, you plan to produce 4,000 bottles and 7,000 labels per day.
In April, you plan to produce the maximum amount of bottles and labels per day,
every day: 5,000 bottles and 8,000 labels.
To represent this plan in PLA, you would need to modify the plan details manually, so the
final result would look like this (remember that each row represents a shift and not an
entire day):
As you change the plan details, the total quantity, which is calculated automatically,
would be updated accordingly:
Simple Quantity-Based Plan

Plan Summary
The following example of a quantity-based plan assumes that your production plan meets
the following criteria:
Criteria
What
One product (bottles)
How Much
50,000 bottles, starting January 1, 2010
During Which Hours
Monday through Friday, 24 hours per day (8:00 A.M. to 8:00

A.M.)
How Often You Enter

Data
Daily
Plan Details
In this example, Production Unit A produces bottles in a water-bottling facility. Unit A's
production profile indicates that:
Unit A can generate 5,000 bottles per day.
For Unit A, you want to track production for 50,000 bottles, starting January 1, 2010. You
do not have a determined end date. Instead, you want the production plan to determine
the end date automatically based upon how long it takes to produce 50,000 bottles.

Builder:
Plan Basis screen:
Quantity-Based Plan screen:
Plan Results
You can see that the planned production each day (except Saturdays and Sundays) is
5,000 bottles per day. This value is determined automatically using the standard batch
size (5,000 bottles) and cycle time (1 day) in the associated production profile for Unit A.
If the plan changes and you need to adjust the planned production per day for any reason,
you can change the details accordingly. As you do so, the quantity will be updated
automatically. For example, if you decide to close the plant on January 1 to account for a
holiday, you could change the planned production for that day to 0. Doing so would cause
the quantity to be recalculated and updated automatically.
Complex Quantity-Based Plan

Plan Summary
The following example of a quantity-based plan assumes that your production plan meets
the following criteria:
Criteria
What
Two products (bottles and labels)
How Much
50,000 bottles and 100,000 labels, starting January 1, 2010

Monday through Friday, 24 hours per day, two shifts:
During Which Hours
8:00 A.M. to 8:00 P.M.
8:00 P.M. to 8:00 A.M.
How Often You Enter Data Per Shift (i.e., twice a day)
Plan Details
In this example, Production Unit A produces bottles and labels in a water-bottling facility.
Unit A's production profiles indicate that:
Unit A can generate 5,000 bottles per day and 8,000 labels per day.
One label yields a $1.00 profit.
For Unit A, you want to track production for 50,000 bottles and 80,000 labels, starting
January 1, 2010. You do not have a determined end date. Instead, you want the
production plan to determine the end date automatically based upon how long it takes to
produce 50,000 bottles and 80,000 labels.
Builder:
Plan Basis screen:
Plan Results
Sundays) is 2,500 bottles and 4,000 labels per shift. This value is calculated automatically
using the standard batch size (5,000 bottles and 80,000 labels) and cycle time (1 day) in
the associated production profiles for Unit A.
Bottles - Production Profile
Labels - Production Profile
If the plan changes and you need to adjust the planned production per day for any reason,
you can change the details accordingly. As you do so, the quantity will be updated
automatically. For example, if you decide to close the plant on January 1 to account for a
holiday, you could change the planned production for that day to 0. Doing so would cause
the quantity to be recalculated and updated automatically.
How are the Planned Production Values

Used?
After you create a production plan, the plan will contain a row for each period for which
you plan to produce a given product (e.g., an entire day or a specific shift within a day).
Each row will contain a planned production value, where the product associated with
those values is specified in the column header. The following image illustrates planned
production values for bottles.
When you access the Production Data Entry page for a production plan, on each
production tab, you will see a similar row for each period in the plan. Each row on the tab
represents a separate Production Data record. In each row, the value in the Short Range
Plan column is a copy of the planned production value.
Note: On the Production Data tab, the short range value can be changed manually if
needed.
In addition, if you click the hyperlink in the Period cell in any row, you will see the
Production Data datasheet, which also displays the Long Range Plan field that belongs to
the Production Data family. The value in the Long Range Plan field is derived the same
way that the Short Range Plan value is derived. Consider the following image, which
shows the value 15610 in the Long Range Plan and Short Range Plan cells on the
Production Data datasheet. A red outline has been added to the image to highlight these
values.
If you were to change the Short Range Plan value on the production tab, the value in the
Short Range Plan field in the Production Data record would be updated accordingly.
Accessing the Manage Production Plans

Page
To access the Manage Production Plans page:
1. On the PLA Start Page, click the Production Plan Management link.
-orOn any Tools menu, click the Manage Plans link.
The Find Production Unit window appears, displaying the Simple Search workspace. The
value in the Search In list is set to Production Unit. You cannot select a different value.

4. In the search results list, select the Production Unit record for which you want to
build a production plan, and click the Open button.
Note: The Production Unit record must be linked to at least one Production Profile
record.
The Manage Production Plans page appears.
Aspects of the Manage Production Plans

Page
The Manage Production Plans page contains the following items:
Tools menu
Common Tasks menu
Production Plans for <Unit Name> pane, where <Unit Name> is the value in the
Name field in the Production Unit record for which you accessed the page. The
pane contains the following items:
A list that displays production plans for the current production unit.
The Add Plan button.
The Copy Existing Plan button.
The Regenerate Selected Plan button.
The Delete Selected Plan button.
Throughout the documentation, this pane is referred to simply as the Production Plans
pane.
Production plan details area: Displays the details of the production plan that is
selected in the Production Plans pane.
Tools Menu
The Tools menu on the Manage Productions Plans page contains the following links:
Manage Plans: Displays the Find Production Unit window, where you can search
for the Production Unit record whose production plans you want to manage on the
current page. A green arrow appears to the left of this link when you are viewing
this page.
Enter Production Data: Displays the Find Production Plan window, where you
can search for the Production Plan record that you want to use to build the data
that will appear on the Production Data Entry page.
Manage Events: Displays the Production Event Management page.
Metrics and Analyses: Displays the Production Analysis page.
Common Tasks Menu
The Common Tasks menu on the Manage Production Plans page contains the following
links:
Print: Displays the Preview window, which shows a preview of how the grid will
be printed. From the Preview window, you can select print options and print the
record.
Page.
Reference Document records for the Production Plan record that is selected in the
tree. This link is enabled only when a Production Plan record is selected in the
tree.
Help: Displays the context-sensitive Help topic for the Manage Production Plans
page.
Select Another Unit: Displays the Find Production Unit window, where you can
search for the Production Unit record whose production plans you want to manage
on the current page.

The Associated Pages menu on the Manage Production Plans page displays links only if
Associated Pages have been configured for the Production Plan family. If no Associated
Pages have been configured for the Production Plan family, the Associated Pages menu
will be empty.
Production Plans Pane

The Production Plans pane on the Manage Production Plans page contains a list that
displays all Production Plans that exist for the Production Unit for which you accessed
the page.
Below the pane are the following buttons:
Add Plan: Displays the Production Plan Builder, where you can create a new
production plan.
Copy Existing Plan: Displays the Find Production Plan window, where you can
select the production plan that you want to copy to create a new production plan.
Regenerate Selected Plan: After displaying a confirmation message confirming

that you want to delete the current production plan and create a new one, displays
the Production Plan Builder, where you can modify the details of the selected
production plan.
Delete Selected Plan: After asking for confirmation, deletes the selected
production plan.
Production Plan Details Area

The production plan details area displays the details of the production plan and the
planned production values per period.
The production plan details area contains the following items:
Plan ID: The record ID of the Production Plan record. This value is read-only.
Plan Start Time: The start date and time of the production plan. This value is readonly.
Plan End Time: The end date and time of the production plan. If this is a timebased plan, you specified this value manually in the Production Plan Builder.
Alternatively, if this is a quantity-based plan, this value is determined
automatically based upon the product quantity and start date that you specified.
This value is read-only.
Products section: Contains a grid, where each row in the grid represents a separate
product that is being produced during the plan. All values in the grid are readonly. The grid contains the following columns:
o
Product Name: The name of the product.
Quantity: How much of the product will be produced during the entire
plan. If this is a time-based plan, this value is determined automatically
based upon the start and end dates that you specified in the Production
Plan Builder and the batch production values that you specified in the
associated Production Profile record. Alternatively, if this is a quantitybased plan, you specified this value manually in the Production Plan
Builder. As you modify individual production values in the Plan Detail
section, this value is updated automatically.
Original Quantity: How much of the product you originally planned to

produce during the entire plan (before you made changes to individual
production values in the Plan Detail section). This column is shown only
for quantity-based plans.
UOM: The unit of measure that is associated with the product.
Start Time: The date and time at which that product will start being
produced. If multiple products are being produced, the start time for each
product is determined based upon your production model selection in the
Production Plan Builder. For example, if multiple products are being
produced sequentially, for each product after the first one, production will
start after production ends for the previous product.
End Time: The date and time at which that product will stop being
produced.
Settings section: Displays the following read-only information:

o
Plan Basis: The type of plan: Time-based or Quantity-based.
Production Model: The order in which the products will be produced (at
the same time or one after the other).
Data Entry Type: How often you plan to enter production data and losses.
Note: The Settings section is collapsed by default.
Plan Detail section: Contains a grid, where each row in the grid represents a
separate period in the plan (e.g., a separate day or a separate shift within the same
day). The grid contains the following columns:
o Start Time: The start date and time of the period. In each row, you can
modify the start time (within certain limits) but not the start date. If you
attempt to modify the start time in a way that is prohibited, a message will
appear to identify the range within which the time must fall.
End Time: The end date and time of the period. In each row, you can
modify the end time (within certain limits) but not the end date. If you
attempt to modify the end time in a way that is prohibited, a message will
appear to identify the range within which the time must fall.
<Product Name (<UOM>)>: The planned production amount for that

period. You can modify the value as long as it does not exceed the
maximum demonstrated capacity that is defined in the associated
production profile.
Below the grid, the following buttons are available:

o
Add Row: Adds a new row to the end of the grid. The start time, end time,
and planned production value for the new row will be determined
automatically.
Remove Last Row: Removes the last row from the grid.
You can modify values in the Plan Detail section. Doing so will update the value in the
Quantity column in the Products section and the plan start and end time above the
Products section.
Creating Production Plans

To create a Production Plan:
1. On the Manage Production Plans page, below the tree, click the Add Plan button.
The Production Plan Builder appears, displaying the Welcome screen.
2. Proceed through the Production Plan Builder to define the details of the
production plan.
The production plan is created, and the details are displayed on the Manage Production
Plans page.
Copying Existing Production Plans

When you create a copy of an existing production plan, a new production plan is created.
You can copy an existing production plan to create a production plan for the same
production unit for which the source plan was created or for a different production unit.
For example, suppose Unit A and Unit B can both produce bottles. If a production plan
already exists for Unit A, you can copy it to create a new production plan for Unit A, or
you can copy it to create a new production plan for Unit B. The Production Unit that you
are currently viewing on the Manage Production Plans page is the target Production Unit
for which the new plan will be created.
To copy an existing Production Plan:
1. On the Manage Production Plans page, below the tree, click the Copy Existing
Plan button.
The Find Production Plan window appears, displaying the Advanced Search workspace.
The value in the Search In list is set to Production Plan. You cannot select a different
value.

4. In the search results list, select the production plan that you want to copy to create
a new production plan, and click the Open button.
Note: You must select a production plan that includes products that can be produced by
the production unit to which you are copying it. For example, if you are copying a
production plan to a unit that can produce only bottles, you cannot copy a production plan
that includes labels.
A new production plan is created based upon the selected production plan, and the new
production plan appears in the Production Plans pane.
Regenerating Existing Production Plans

After a production plan is created (either as a copy of an existing production plan or from
scratch), you can change only the planned production values. You cannot change
production plan details such as start date, end date, and products. Instead, if you want to
modify the details of a production plan, you will need to regenerate the production plan.
Doing so will delete the current production plan and create a new one. You will use the
Production Plan Builder to regenerate the plan, but instead of entering all details from
scratch, the details of the previous plan will be retained in the builder. You can keep the
details that you want to keep and modify the details that are no longer valid.
To regenerate an existing production plan:
1. On the Manage Production Plans page, in the Production Plans pane, select the
production plan that you want to regenerate.
2. Below the pane, click the Regenerate Existing Plan button.
The Production Plan Builder appears, displaying the Welcome screen.
3. Proceed through the Production Plan Builder to define the details of the
production plan.
The previous production plan is deleted, the new production plan is created, and the
details are displayed on the Manage Production Plans page.
Using the Production Plan Builder

The Production Plan Builder appears when you click the Add Plan button or Regenerate
Selected Plan button on the Manage Production Plans page. You can use this builder to
create a new Production Plan or modify the details of an existing production plan.
To use the Production Plan Builder to create or modify a Production Plan:
1. On the Welcome screen, click the Next button. If you do not want to view this
screen in the future, click the Don't show this page again check box.
The Select Products screen appears.
You can use this screen to define the products that you plan to produce. Each plan can
include one or more products.
2. To add a product to the plan, in the left pane, select the product, and then click the
button. If the list of products that you can add is long and you are having
trouble finding the product that you want to add, you can search for a specific
product using the Filter text box.
3. When you are finished adding products to the plan, click the Next button.
The Plan Basis screen appears.
You can use this screen to determine whether the plan will be time-based (i.e., you will
define the time period for which you want to track production) or quantity-based (i.e.,
you will define the amount of each product that you plan to produce).
4. If you want to generate a time-based plan, accept the default selection.
-orIf you want to generate a quantity-based plan, select the Plan is quantity-based option.
5. Click the Next button.
The Time-based Plan screen or Quantity-based Plan screen appears, depending upon
your selection in step 4.
6. If you are creating a time-based plan:

1. In the Start Time cell, type or select the date on which the plan begins.
2. In the End Time cell, type or select the date on which the plan ends.
3. In the Production Model list, select the option that describes how the unit
produces the products that you selected on the Select Products screen. You
can select either of the following options:
Concurrent: The unit produces the products at the same time.
Sequential: The unit produces the first product first, and it begins
producing the second product after production of the first product
is complete.
Note: The Production Model list is disabled if you are producing only one product during
this plan.
-orIf you are creating a quantity-based plan:
1. In the Start Time cell, type or select the date on which the plan begins.
2. In the Production Model list, select the option that describes how the unit
produces the products that you selected on the Select Products screen. You
can select either of the following options:
Concurrent: The unit produces the products at the same time.
Sequential: The unit produces the first product first, and it begins
producing the second product after production of the first product
is complete.
Note: The Production Model list is disabled if you are producing only one product during
this plan.
3. In the Quantity grid, in the Quantity cell for each row, type the amount of
that product that you plan to produce. If the unit produces multiple
products, you can also sort them using the Product column to change the
order in which each product will be produced.
7. When you are finished defining the plan details, click the Next button.
The Useful Production Time screen appears.
You can use this screen to define the hours each day that you produce the specified
products. By default, the builder assumes that Monday through Friday, your production
hours are the same (9:00:00 A.M. to 5:00:00 P.M.). It also assumes that you do not
produce anything on Saturdays or Sundays.
8. To refine the hours each day that you produce the specified products, on each tab,
define your shifts as appropriate. If your shifts are the same Monday through
Friday, you can leave the default check box selected and define the shift only for
Monday. It will then be copied to Tuesday through Friday automatically. If,
however, your shifts are the same every day of the week (including weekends),
you can select the I have the same useful production time for the whole week
check box. You can then define the shift only for Monday, and it will be copied to
Tuesday through Sunday automatically.
When defining shifts, note that:
o
If you run only one shift all day (24 hours a day), make the start time and
end time the same, like this:
If you run multiple shifts per day, back to back, make the start date and
time of the second shift match the end date and time of the previous shift,
like this:
9. When you are finished defining your shifts, click the Next button.
The Data Entry Frequency screen appears.
You can use this screen to define how often you enter production data and production loss
information.
10. In the Data Entry Frequency list, select the frequency by which you enter
production data and loss information.
Note: If you want to enter production data only once over the course of the entire plan
period, select Campaign.
11. Click the Finish button.
The plan is generated and appears on the Manage Production Plans page.
Deleting Production Plans

To delete a Production Plan:
1. On the Manage Production Plans page, in the Production Plans pane, select the
production plan that you want to delete.
2. Below the pane, click the Delete Selected Plan button.
A message appears, asking if you are sure you want to delete the production plan.
The production plan is deleted.
About Production Events

A production event is any event that results in reduced production output, such as:
An equipment failure.
An intentional reduction in production output as the result of some condition (e.g.,
lack of demand for the product).
User error in operating the piece of equipment.
Holidays requiring a facility shutdown.
Loss of employees (i.e., due to vacation days or employee termination).
When an event occurs that causes you to produce less output than you had planned, you
can record the event in a Production Event record. In the Production Event record, you
can identify:
The piece of equipment that caused the event.
To do so, you will use the Causing Asset field. The Production Event record will be
linked to an Equipment record that represents the piece of equipment that caused the
event. Not all production events will be associated with a piece of equipment. For
example, if several employees take a vacation day on the same day and you are,
therefore, unable to produce the maximum amount of product, the production event is not
associated with any specific piece of equipment.
The production unit in which the event occurred.
To do so, you will use the Source Unit field. The Production Event record will be linked
to the selected Production Unit record.
The type of event.
To do so, you will use the Production Event Code field. The Production Event record will
be linked to the selected Production Event Code record.
Work History records that include details about work that was performed as
a result of the event.
To do so, you will use the Work History Link field. The Production Event record will be
linked to the selected Work History records. Not all production events will be associated
with a Work History record. For example, if the event has not resulted in a work order
yet, no Work History records will exist to define the work that was performed as a result
of the event.
You can view a list of all Production Event records that exist in the database on the
Production Event Management page.
As you enter production data on a daily basis, if any day results in reduced production
output, you can enter the amount of production that was lost and identify the production
event that caused the loss.
Accessing the Production Event

Management Page
To access the Production Event Management page:
On the PLA Start Page, click the Production Event Management link.
The Production Event Management page appears.
Aspects of the Production Event

Management Page
The Production Event Management page contains the following items:
Tools menu
Common Tasks menu
PLA - Production Event Management workspace: Contains the following items:
A grid that displays a row for each Production Event record that exists in
the database.
The Add Event button.
The Delete Event button.
Tools
The Tools menu on the Production Event Management page contains the following links:
Manage Events: Displays the Production Event Management page. A green arrow
Metrics and Analyses: Displays the Production Analysis page.
Common Tasks Menu
The Common Tasks menu on the Production Event Management page contains the
following links:
Print: Displays the Preview window, which shows a preview of how the grid will
record.
Page.
Reference Document records for the Production Event record that is currently
selected in the grid.
Help: Displays the context-sensitive Help topic for the Production Event
Management page.

The Associated Pages menu on the Production Event Management page displays links
only if Associated Pages have been configured for the Production Event family. If no
Associated Pages have been configured for the Production Event family, the Associated
Pages menu will be empty.
In the baseline database, the RCA Analysis link appears by default.
Note: If the Root Cause Analysis module is not active, the following error appears when
you click the link: Named resource (RCA/AnalysisBuilder) not found.
PLA - Production Event Management

Workspace
The Production Event Management workspace displays the results of the
AllProductionEvents query, which is stored in the following Catalog folder:
\\Public\Meridium\Modules\PLA\Queries.
The PLA - Production Event Management workspace contains a grid that displays a row
for each Production Event record that exists in the databases. In the baseline database, the
grid contains the following columns:
Event ID
Start Date
End Date
Production Event Code
Source Production Unit
Below the grid are the following buttons:
Add Event: Displays the ~ ~ (new Production Event) window, which displays a
blank Production Event datasheet.
Delete Event: After asking for confirmation, deletes the selected Production Event
record.
About Creating Production Event

Records
You can create a Production Event record from the following pages:
The Production Event Management page. This option is useful if you want to
record a production event for historical record-keeping purposes. After the
Production Event record exists, it can be associated with daily production losses
via the Production Data Entry page.
The Production Data Entry page. This option is useful if you want to associate a
daily production loss with a production event that does not have a corresponding
Production Event record yet. Instead of navigating back to the Production Event
Management page to create the corresponding record, you can create the
Production Event record directly from the Production Data Entry page.
Creating a Production Event Record

from the Production Event
Management Page
To create a Production Event record from the Production Event Management page:
1. On the Production Event Management page, below the grid, click the Add Event
button.
The ~ ~ (new Production Event) window appears.

3. When you are finished completing the fields, click OK.
The Production Event record is saved.
Creating a Production Event Record

from the Production Data Entry Page
To create a Production Event record from the Production Data Entry page:
1. Access the Production Data tab of the Production Data Entry page.
2. In the grid in the Production Data section, select the row representing the day
whose loss you want to associate with a new production event.
3. Below the grid, in the Losses section, select the row containing the loss that you
want to associate with a new production event.
4. In the selected row, in the Production Event cell, expand the list, and select
Create Production Event, as shown in the following image.
The ~ ~ (new Production Event) window appears.

6. When you are finished completing the fields, click OK.
The Production Event record is saved, and its Record ID appears in the Production Event
list.
Note: If you specified a date range that does not include the day that is represented by the
selected row in the Production Data section, when you click OK, a message will appear,
indicating that the date range is not valid for that day. You can click OK on the message
box to continue creating the Production Event record, but it will not be associated with
the selected loss. It will appear, however, on the Production Event Management page.
About Relationships Involving

Production Event Code Records
When you create a Production Event record, on the datasheet, you can click the
button in the Production Event Code cell to select the Production Event Code record that
most accurately represents the type of event that the Production Event record represents.
Likewise, when you create a Production Event Template record, you can click the
button in the Production Event Code cell to select the Production Event Code record that
most accurately represents the type of events that will be created automatically from that
Production Event Template record.
When you save the Production Event or Production Event Template record, it will be
linked automatically to:
The selected Production Event Code record, using the Has Base Production Event
Code relationship.
The selected Production Event Code record, using the Has Production Event Code
relationship.
All Production Event Code records that categorize the selected Production Event
Code record, using the Has Production Event Code relationship.
In other words, the new Production Event or Production Event Template record will
always be linked to one and only one Production Event Code record through the Has
Base Production Event Code relationship and the Has Production Event Code
relationship. Depending upon how that Production Event Code record is categorized, the
new Production Event or Production Event Template record might also be linked to
multiple additional Production Event Code records through the Has Production Event
Code relationship.
For instance, consider the following Production Event Code records, as they appear in the
Production Event Codes pane on the Production Event Coding page:
In this image, you can see that the Production Event Code record Planned Shutdown is a
category that contains two subcategories: Holiday and Scheduled Maintenance. Likewise,
the Production Event Code record Holiday is also a category containing a subset of
categories: United States and France.
Suppose that you create a Production Event record to track a planned shutdown due to the
United States holiday of Thanksgiving Day. In this case, when you create the Production
Event record, in the Production Event Code cell, you would click the
button and
select United States as the type of event, as shown in the following image.
You would probably use the Headline and Description fields to indicate that the holiday is
Thanksgiving Day, so the Production Event record would look something like this:
Based upon this example, the following records and links would be created, where the
Has Base Production Event Code relationship is colored blue to help you easily identify
it.
Deleting a Production Event Record

To delete a Production Event record:
1. On the Production Event Management page, in the grid, select the Production
Event record that you want to delete.
2. Below the gird, click the Delete Event button.
A message appears, asking if you are sure that you want to delete the record.
The Production Event record is deleted.
Creating an RCA Analysis from PLA

To create an RCA Analysis from PLA:
1. Access the Production Event Management page.
2. In the grid, select the row containing the Production Event record that you want to
use to create an RCA Analysis.
3. On the Associated Pages menu, click the RCA Analysis link.
Note: The RCA Analysis link will appear on the Associated Pages menu only if the Root
Cause Analysis (RCA) module is active.
The New Analysis Builder appears, displaying the RCA Analysis Datasheet screen.
4. Use the New Analysis Builder to complete the RCA Analysis.

The Production Event record and the RCA Analysis record are linked automatically. Note
that several fields in the RCA Analysis record are populated automatically based on the
values in the selected Production Event record.
Opening an RCA Analysis from PLA

A production event can be associated with only one RCA Analysis. After an RCA
Analysis record is linked to a Production Event record, you can open the corresponding
RCA Analysis from the Production Event Management page.
To open an RCA Analysis from the Production Event Management page:
1. On the Production Event Management page, in the grid, select the row containing
the Production Event record that is linked to the RCA Analysis record whose
corresponding RCA Analysis you want to open.
2. On the Associated Pages menu, click the RCA Analysis link.
The Analysis page appears, displaying the datasheet for the RCA Analysis record to
which the selected Production Event record is linked.
What Happens When you Create an

RCA Analysis from PLA?
When you create an RCA Analysis from a Production Event record, several fields in the
RCA Analysis record are populated automatically with the corresponding value in the
Production Event record. The field mappings are listed in the following table.
Production Event Field
RCA Analysis Field
Headline
Analysis Name
Description
Analysis Description
Start Date
Start Date
Comments
Comments
Note: Each RCA Analysis record must have a unique value in the Analysis Name field. If
there are multiple Production Event records that have the same value in the Headline
field, in the first RCA Analysis record that is created from one of these Production Event
records, the value in the Analysis Name field will be populated automatically as
<Production Event Headline>. In the second RCA Analysis record that is created, the
value in the Analysis Name will be field populated automatically as <Production Event
Headline> - 1, and so on.
In addition, if the Production Event record is linked to an Equipment record and the
Equipment and Location queries have been configured appropriately in the Root Cause
Analysis module, the RCA Analysis record will be linked to that Equipment record. The
Record ID of the Equipment record will appear in the Asset or Location text box,
whichever appears, on the Select an Asset screen of the New Analysis Builder.
When you open the Logic Tree in an RCA Analysis you created from a Production Event
record, several fields in the RCA Event record will be populated automatically with the
corresponding value in the Production Event record. You can modify these fields
manually if needed. The field mappings are listed in the following table.
Production Event Field
RCA Event Field
Headline
Label
Description
Long Description
Start Date
Event Start Date
End Date
Event End Date
About Production Data

After you establish a production profile and create production plans against it, you are
ready to start recording production data and accounting for any production losses. Using
the Production Data Entry page, you can:
Record production values.

Record production losses.
Associate any production losses with specific production events, impact codes,
and OEE codes.
As you record the data, the information will be summarized automatically and displayed
on the Production Summary tab of the Production Data Entry page.
Remember from the PLA data model that each Production Data record must be linked to
a single predecessor Production Plan record and can be linked to multiple successor
Production Loss records. The following image shows these relationships, where the
arrows represent relationship families, and boxes represent entity families. The
Production Data family is outlined in red.
As you begin recording production data, the data is recorded in Production Data records.
If you do not produce the planned amount in a given period, the Production Data record
for that day can be linked to multiple Production Loss records that indicate the amount of
lost production, the production event that caused the loss, and the impact of the loss.
For example, suppose a production plan spans three months: January 2010 through
March 2010. The planned production for each day is 3,000 bottles per day. On January 1
and January 2, you produce all 3,000 bottles, meeting the planned production. On January
3, however, you produce only 2,000 bottles. To account for the loss, you would create a
Production Loss record and record the 1,000 bottles that were not produced. Now,
suppose that on January 4, you again fail to meet the planned production. This time, you
produce only 1,000 bottles due to an equipment failure and a scheduled maintenance
activity. In this case, you would create two Production Loss records, where one
documents 1,000 bottles that were not produced due to a maintenance activity, and the
other documents 1,000 bottles that were not produced due to an equipment failure.
The following image illustrates the records and links that would be created in this
scenario, where the arrows represent links and the boxes represent records.
Accessing the Production Data Entry

Page
To access the Production Data Entry page:
1. On the PLA Start Page, click the Production Data Management link.
-orOn the Tools menu, click the Enter Production Data link.
The Find Production Plan window appears, displaying the Simple Search workspace. The
value in the Search In list is set to Production Plan by default. You cannot select a
different value.

4. In the search results list, select the Production Plan record that represents the plan
for which you want to record production data, and click the Open button.
The Production Data Entry page appears.
Aspects of the Production Data Entry

Page
The Production Data Entry page contains the following items:
Tools menu
Common Tasks menu
Production Summary tab: Displays summary information about the data

that appears on the production data tabs.
Production data tabs: Allow you to enter production data and record losses.
Tools Menu
The Tools menu on the Production Data Entry page contains the following links:
that will appear on the Production Data Entry page. A green arrow appears to the
left of this link when you are viewing this page.
Manage Events: Displays the Production Event Management page.
Metrics and Analyses: Displays the Metrics & Analysis page.
Common Tasks Menu
The Common Tasks menu on the Production Data Entry page contains the following
links:
Print: Displays the Preview window, which shows a preview of how the page will
record.
Page.
Help: Displays the context-sensitive Help topic for the Production Data Entry
page.
Select Another Plan: Displays the Find Production Plan window, where you can
search for the Production Plan record that you want to use to build the data that
will appear on the current page.

The Associated Pages menu on the Production Data Entry page displays links only if
Associated Pages have been configured for the Production Data family. If no Associated
Pages have been configured for the Production Data family, the Associated Pages menu
will be empty.
Aspects of the Production Data Tabs
On the Production Data Entry page, for each product that is associated with the
production plan whose production data you are viewing, you will see a separate
production data tab. For example, if you are viewing production data for a production
plan that is responsible for producing bottles and labels, you will see two production data
tabs:
One for bottles

One for labels
Each production data tab will be labeled according to the product name (e.g., Bottles).
The following image shows an example of a production data tab for bottles.
Each production data tab contains the following sections:
Production Data: Contains a grid that allows you to enter actual production
values and change the short range plan. Each row in the grid represents a
Production Data record.
Losses for <Period>: Contains a grid containing a row for each Production Loss
record that is linked to the currently selected Production Data record. Each row in
the grid represents a Production Loss record. Note that in the section label,
<Period> is the value in the Period field in the Production Data record that is
selected in the Production Data section. Throughout this documentation,
however, this section is referred to as the Losses section.
As you make changes on a production data tab, the changes are saved automatically and
are reflected on the Production Summary tab.
Production Data Section

The Production Data section on each production data tab contains a grid that allows you
to enter actual production values and change the short range plan, if needed. Each row in
the grid represents a Production Data record. Each time you access a production data tab,
the number of rows will correspond to the number of periods (i.e., days or shifts) in the
production plan, up to and including the current period. The grid does not show periods
in the future. The grid contains the following columns, which display values from fields
in the Production Data records:
Period
Note: The text in each Period cell is a hyperlink, which you can click to access the
Production Data datasheet for that Production Data record.
Actual
Losses
Maximum Sustained Capacity
Short Range Plan
You can modify the default display of the grid using the standard grid-customization
options, with the exception of the data grouping options (i.e., Group By This Field and
Group By Box), which are not available.
In addition, the grid displays the Unaccounted Loss column. The value in this column is
not stored in the Production Data record and is for display purposes only. The number
that appears in each cell in this column is calculated using the following equation:
Unaccounted Loss = Short Range Plan - Losses - Actual
Where Short Range Plan, Losses, and Actual are displayed in the same row as the
Unaccounted Loss value.
For example, assume that the following values appear in a single row on the Production
Data tab:
Short Range Plan = 5,000

Losses = 0
Actual = 3,000
In this case, the value in the Unaccounted Loss column in that row will be calculated
using the following equation:
Unaccounted Loss = 5,000 - 0 - 3,000
Unaccounted Loss = 2,000
Note: The calculated unaccounted loss is displayed using the number of decimal places
defined for the Display Precision setting, regardless of the number of decimal places in
the underlying Short Range, Losses, and Actual values.
At the bottom of the grid below all columns except for Short Range Plan, you will see the
sum of all values in that column, as shown in the following image.
Below the summary values, the following text appears, preceded by the
icon:
n not accounted for

Where n is the sum of unaccounted losses.
For example, using the preceding image, you can see that sum of all unaccounted losses
is 2,000. In this case, below the grid, you would see the following text:
When all losses for all period have been accounted for, the text n not accounted for is
replaced with All losses accounted for, as shown in the following image.
Losses Section
The Losses section on each production data tab contains a grid containing a row for each
Production Loss record that is linked to the currently selected Production Data record.
The grid displays the following columns of information, which display values from fields
in the Production Loss records:
Loss Amount
Production Event
Impact Code
OEE Code
Comment
You can modify the default appearance of the grid using the standard grid-customization
options, with the exception of the data grouping options (i.e., Group By This Field and
Group By Box), which are not available.
The following buttons appear below the grid:
Add Loss: Adds a new row to the grid, where you can account for a loss that
occurred that period.
Delete Loss: After asking for confirmation, deletes the selected Production Loss
record.
About the Production Event List

On each production data tab, in the Losses section, the Production Event list displays the
Record IDs of all the Production Event records that are returned by the EventList query,
which is stored in the Catalog folder \\Public\Meridium\Modules\PLA\Queries.
The EventList query returns the Record ID of all Production Event records whose date
range includes the date in the Period field in the selected Production Data record (in the
Production Data section). A Production Event record's date range is determined from the
values in its Start Date and End Date fields.
For example, consider a Production Event record with a date range of 10/1/2010 to
10/15/2010. The following image shows the datasheet for this Production Event record.
You can see that the date range is determined from the values in the Start Date and End
Date fields.
If you were recording a loss for 10/17/2010, you would not be able to associate the loss
with this Production Event record because the date range of the production event (10/1
through 10/15) does not include 10/17/2010.
In the following image, you can see that the Production Event list for a loss associated
with 10/18/2010 does not include the Record ID of this Production Event record.
Likewise, if you were recording a loss for 10/8/2010, you would be able to associate the
loss with this Production Event record because the date range of the production event
(10/1 through 10/15) does include 10/8/2010.
In the following image, you can see that the Production Event list associated with
10/10/2010 does include the Record ID of this Production Event record.
Note: If the Production Event record does not have a start date, its Record ID will appear
in the Production Event list for losses that are associated with any day before the end
date. Likewise, if the Production Event record does not have an end date, its Record ID
will appear in the Production Event list for losses that are associated with any day after
the start date.
About the Short Range Plan

When you create a Production Profile record, you define the amount of product that can
be consistently produced by a production unit without having any adverse effects on the
piece of equipment or location or the quality of the product. This value is stored in the
Maximum Sustained Capacity Rate field in the Production Profile record.
When you create a production plan, with this value in mind, you can define the amount of
product that you plan for that production unit to produce during a given time period. This
value might be the same as the maximum sustained capacity rate, or it might be different
based on your knowledge of planned events within the facility. For example, if you plan
to shut down a production unit for maintenance, the planned production output for that
production unit will be less than the maximum sustained capacity rate during the
downtime.
When you access the Production Data Entry page for a production plan, on each
production data tab, a row will be available for each period in the plan. Each row
represents a separate Production Data record. In each row, the value in the Short Range
Plan column is a copy of the planned production value.
As you enter production values for a specific day, if needed, you can enter an adjusted
planned production value based on significant events that occurred that day and could not
have been predicted when the plan was created. For example, while a production plan
might call for 15,610 barrels to be produced on June 1, if a hurricane occurs and the
facility is shut down for several weeks for cleaning and repairs, you might want to
indicate that the planned production during those days decreased significantly. The
adjusted value will be stored in the Short Range Plan field in the Production Data record.
Typing Production Values Manually

The following instructions explain how to type production values manually for a given
period in the production plan. If desired, you can also copy a production value from one
period to another.
To type production values manually:
1. Access the appropriate production data tab of the Production Data Entry page.
2. In the row representing the period whose production values you want to record, in
the Actual cell, type the amount of product that you produced that period.
The value is stored in the Actual field in that Production Data record.
If the value is less than the value in the Short Range Plan cell in the same
row, the icon appears in that row to the left of the Period cell. This icon
indicates that you did not produce the planned amount. You will need to
account for the loss to remove the icon.
If the value is greater than the value in the Short Range Plan cell in the
same row, the Add Loss button in the Losses section is disabled.
Note: After you type a value in the Actual cell, you will need to click in a cell in a
different row in order to see the updated sum of all actual values below the grid.
Copying a Production Value
To copy a production value from one day to another:

1. Access the appropriate production data tab on the Production Data Entry page.
2. In the row representing the period whose production value you want to copy,
select the cell in the Actual column.
3. Press and hold the left mouse button.
4. Drag your pointer to the cells in the Actual column to which you want to paste the
copied value.
The pointer changes to a
icon, as shown in the following image. In this image, the
value 5000 is being copied from the first row to the four subsequent rows.
5. Pause on the last cell to which you want to copy the value, and release the mouse
button.
The value is copied to the selected cells.
Typing a Different Short Range Plan

Manually
The following instructions explain how to type a short range plan manually for a given
period. If desired, you can also copy a short range plan value from one day to another.
To change the value in the Short Range Plan field by typing a new value:
2. In the row representing the period for which you want to enter an adjusted
planned production value, in the Short Range Plan cell, delete the existing value,
and type the amount of product that you planned to produce that period based on
the new events and information.
The value is saved automatically and stored in the Short Range Plan field in that
Production Data record.
Copying a Short Range Plan

To copy a short range plan value from one period to another:
2. In the row representing the period whose short range plan value you want to copy,
select the cell in the Short Range Plan column.
4. Drag your pointer to the cells in the Short Range Plan column to which you want
to paste the copied value.
5. Pause on the last cell to which you want to copy the value, and release the mouse
button.
The value is copied to the selected cells.
About Changing the Margin

When you access the Production Data Entry page, the value in the Margin field in all
new Production Data records is set by default to the value in the Default Margin field in
the associated Production Profile record (i.e., the Production Profile record that is linked
to the Production Plan record that you selected when you accessed the page).
For instance, suppose that on July 1, the value in the Default Margin field in a Production
Profile record is 5.00. In this case, new Production Data records that are created on or
after July 1 for the Production Plan record to which that Production Profile record is
linked will contain the value 5 in the Margin field. If, however, on July 16 the value in
the Default Margin field is changed to 6.00, any new Production Data records that are
created on or after July 16 for the same Production Plan record will contain the value 6 in
their Margin field.
Keep in mind that Production Data records are created automatically when you access the
Production Data Entry page. The number of records that are created depends upon the
day on which you access the page and the planning period of the Production Plan record
that you selected when you accessed the page.
For example, suppose the planning period in a Production Plan record is July 1 through
July 31. If you were to access the Production Data Entry page for that Production Plan
record for the first time on July 15, fifteen Production Data records would be created (one
for each day between July 1 and July 15). Each of those records would contain the same
value in the Margin field because they were all created at the same time.
So, using the same example, if you were to increase the value in the Default Margin field
on July 16 and access the Production Data Entry page again on July 16, one new
Production Data record would be created to represent July 16, and the value in its Margin
field would be the updated value in the Default Margin field in the Production Profile
record.
If needed, you can modify the default value in the Margin field in a Production Data
record. You might want to do so, for example, if you access the Production Data Entry
page for a month-long plan for the first time on the last day of the month. In this case,
Production Data records would be created automatically for all days in that month using
the current value in the Default Margin field in the associated Production Profile record.
If you know that at some point during that month the margin was different from the
current margin, you can modify the value in the Margin field in the Production Data
records representing those days.
The value in the Margin field in Production Data records is used to calculate the:
Cost of losses, which appears on the Production Summary tab.

Lost profit opportunity, which is used in the Total Cost of Unreliability Metric
View.
Entering Losses Manually

If you enter an Actual value that is less than the Short Range Value for that period, you
can account for the loss by creating a Production Loss record. Each Production Loss
record contains values that indicate the amount of lost production, the event that caused
the loss, and the impact of the loss. If multiple events lead to a production loss, you can
create multiple Production Loss records, which will be linked to the same Production
Data record.
The following instructions explain how to enter a loss manually for a given period. You
can also copy losses from one period to another.
Note: After you link a Production Loss record to a Production Event record, you cannot
change the start date or end date of the Production Event record.
To create a Production Loss record:
2. In the grid in the Production Data section, select the row representing the period
for which a loss occurred.
3. Below the grid in the Losses section, click the Add Loss button.
4. A new row is added to the grid in the Losses section.
5. In the new row:

1. In the Loss Amount cell, type a number indicating the amount of lost
production.
2. In the Production Event cell, expand the list, and select the event that
caused the loss. The list displays the Record IDs of all Production Event
records that are returned by the EventList query, which is stored in the
Catalog in the folder \\Public\Meridium\Modules\PLA\Queries. If no
applicable events appear in the list, you can create a Production Event
record by clicking Create Production Event.
3. In the Impact Code cell, expand the list, and select the impact of the loss.
Each item in the list represents an Impact Code record that is returned by
the ImpactCodeList query, which is stored in the Catalog in the folder
\\Public\Meridium\Modules\PLA\Queries. Each item in the list is
displayed in the following format:
<Code> - <Description>
...where:
1.
4.
<Code> is the value in the Code field in the Impact Code record.
<Description> is the value in the Description field in the Impact

Code record.
4. In the OEE Code cell, click the

appears.
button. The Select OEE Code window
Select the OEE code that is associated with the production loss. Each item in the tree
represents an OEE Code record that is returned by the OEECodeListProdLoss query,
which is stored in the Catalog in the folder \\Public\Meridium\Modules\PLA\Queries.
Only enabled OEE Code records (i.e., OEE Code records whose Is Inactive field contains
the value False) can be selected from the list. Disabled OEE Code records will be gray
and cannot be selected.
1.
5. In the Comment cell, type any additional comments about the loss.
The values are stored in the Production Loss record.
About Copying Losses

The total number of losses for a given period is calculated as the sum of the individual
loss values in the Production Loss records that are linked to the Production Data record
representing that period. If a Production Data record is linked to only one Production
Loss record, the total loss value in the Production Data record will be equal to the loss
amount in that Production Loss record.
For example, suppose the Production Data record for 1/1/2008 is linked to three
Production Loss records whose individual loss values are 100, 50, and 200. In this case,
the total number of losses for that day will be 350 (100 + 50 + 200). This scenario is
illustrated in the following image, where the total number of losses, 350, is outlined in
red in the Production Data section, and the individual losses are outlined in red in the
Losses section.
If you copy all losses from one period to another, the individual Production Loss
record(s) that are used to determine the total loss value for that period are used to create
new Production Loss records, which are linked automatically to the Production Data
records representing the target days.
For example, using the previous example, suppose you copied all losses from the source
day, 1/1/2008, to the target days 1/2/2008 and 1/3/2008. In this case:
The total loss value of 350 would be copied to the Production Data records
representing 1/2/2011 and 1/3/2011. In the following image, you can see the value
350 outlined in red in the Production Data record for 1/2/2008.
The three individual Production Loss records that were linked to the Production
Data record for 1/1/2008 would be used to create six new Production Loss
records, where...
Three of those records are linked to the Production Data record for
1/2/2011.
Three of those records are linked to the Production Data record for
1/3/2011.
In the following image, you can see that the Production Data record for 1/2/2008 is linked
to three Production Loss records, which are outlined in red.
In addition, you can see in the following image that the Production Data record for
1/3/2008 is also linked to three Production Loss records, which are outlined in red.
Although you cannot determine it from the image, these three Production Loss records
are different records (i.e., with different Entity Keys) from the three records that are
outlined in the preceding image.
Note: If you try to copy a Production Loss record whose Production Event field contains
a value that is invalid for the target period, an error message appears, and the copy
operation is stopped automatically.
Copying Losses
To copy losses from one period to another:
2. In the row representing the period whose losses you want to copy, select the cell
in the Losses column.
4. Drag your pointer to the cells in the Losses column to which you want to paste the
copied value.
5. Pause on the last cell to which you want to copy the losses, and release the mouse
button.
The Copy Losses window appears.
Note: If you copied the losses from a period for which no Production Loss records
actually exist, instead of seeing the Copy Losses window, you will see a message
indicating that no Production Loss records are available to be copied.
Each row in the grid represents a Production Loss record that is linked to the Production
Data record that is represented in the row whose losses you copied in step 2. In the
preceding image, only one Production Loss record appears in the grid, so the Copy check
box is selected automatically. If more than one Production Loss record is displayed in the
grid, none of the Copy check boxes are selected automatically.
6. In the rows representing the Production Loss records that you want to copy to the
Production Data records that are represented by the rows to which you dragged
the pointer, select the Copy check box.
7. Click the Copy button.
The selected Production Loss records are used to create new Production Loss records,
which are linked automatically to the Production Data records that are represented by the
rows to which you dragged the pointer. In addition, for each Production Data record to
which you copied the losses, the value in the Losses field in the Production Data record is
updated to match the value in the Losses field in the Production Data record whose total
loss value you copied.
Deleting a Production Loss Record

To delete a Production Loss record:
2. In the grid in the Losses section, select the row containing the Production Loss
record that you want to delete.
3. Below the grid, click the Delete Loss button.
A confirmation message appears, asking if you are sure that you want to delete the
record.
The Production Loss record is deleted.
About the Production Summary Tab
The Production Summary tab appears on the Production Data Entry page, as shown in
the following image.
The Production Summary tab contains the following items:
Production Data Details pane: Displays the following information:
Plan Date: The time period associated with the production data that
appears on the production data tabs. The plan date is displayed in the
format <Start Date> - <End Date>, where <Start Date> is the value in the
Start Date field and <End Date> is the value in the End Date field in the
Production Plan record that you selected when you accessed the
Production Data Entry page.
Production grid: Displays a row for each product that is associated with
this production plan. The grid contains the following columns:
o
Product: The name of the product.
MSC: The value in the Maximum Sustained Capacity Rate field in

the Production Profile record that is associated with this production
plan.
Planned: The sum of all values in the Short Range Plan column on
the corresponding production data tab.
Actual: The sum of all values in the Actual column on the

corresponding production data tab.
Losses: The sum of all values in the Losses column on the

corresponding production data tab.
Cost of Losses: The cost of all losses, where the value is calculated
using the following equation:
The currency symbol that appears is defined via the Currency dialog box.
o
Long Range Plan: A hyperlink that displays the Long Range Plan Profile
dialog box, where you can see the planned production numbers for each
period.
OEE: The overall OEE percentage for the products that are selected in the
production grid. OEE is calculated using the following equation:
OEE = (Availability x Performance x Quality) x 100

o
Availability: The availability percentage for the products that are selected
in the production grid. Availability is calculated using the following
equation:
Availability = [(Good Production + Performance Loss + Quality Loss) /

(Good Production + Availability Loss + Performance Loss + Quality Loss)] x
100
o
Performance: The performance percentage for the products that are

selected in the production grid. Performance is calculated using the
following equation:
Performance = [(Good Production + Quality Loss) / (Good Production +

Performance Loss + Quality Loss)] x 100
o
Quality: The quality percentage for the products that are selected in the
production grid. Quality is calculated using the following equation:
Quality = [Good Production / (Good Production + Quality Loss)] x 100
Production Data Summary pane: Displays the following information:
Total Production: The sum of all values in the Actual column on the
corresponding production data tab, appended with the value in the Product
UOM field in the Production Profile record that is associated with this
production data. If the production plan includes more than one product,
however, the total production value is appended with Units.
Total Losses: The sum of all values in the Losses column on the
corresponding production data tab, appended with the value in the Product
UOM field in the Production Profile record that is linked to the Production
Plan record that you selected when you accessed the Production Data
Entry page (e.g., Barrels). If the production plan includes more than one
product with different units of measure, however, the total losses value is
appended with Units.
Cost Of Losses: The cost of all losses across all products that are included
in this plan, where the value is calculated using the following equation:
The currency symbol that appears is defined via the Currency dialog box, and the number
of decimal places that appear in the Cost of Losses value is defined via the Display
Precision dialog box.
Production Data Summary Graph pane: Displays the Production Data Summary
graph. The label on the graph is the value that is stored in the Plan ID field in the
Production Plan record that you selected when you accessed the Production Data
Entry page.
Cost of Losses Calculation

On the Production Data Summary pane on the Production Data Entry page, you will see
the Cost Of Losses value. This value is calculated using the values in the following fields
in the Production Data records that are displayed on the corresponding production data
tabs:
Losses
Note: The Losses value is displayed in the Losses column on the production data tabs.
Margin
Note: The Margin value is not displayed on the production data tab. You can, however,
see it on the Production Data datasheet, which you can access by clicking the hyperlink in
the Period column on the production data tabs.
For example, consider the following table, which indicates the values that exist in the
Period, Losses, and Margin fields in Production Data records. You can see that all of the
records contain the same value in the Losses field. Also, half of the records contain the
value 5 in the Margin field (shown in blue in the table), and the other half of the records
contain the value 6 in the Margin field (shown in green in the table).
Period
Losses Margin
7/1/2011 10
7/2/2011 10
7/3/2011 10
7/4/2011 10
7/5/2011 10
7/6/2011 10
7/7/2011 10
7/8/2011 10
7/9/2011 10
7/10/2011 10
The cost of losses for each day is calculated using the following formula:
Cost of Losses Per Day = Losses x Margin
Based on this formula, for the records displayed in the previous table, the cost of losses
per day for each record is shown in the Cost of Losses column in the following table.
Period
Losses Margin Cost of Losses Equation Cost of Losses
7/1/2011 10
(10 x 5)
50
7/2/2011 10
(10 x 5)
50
7/3/2011 10
(10 x 5)
50
7/4/2011 10
(10 x 5)
50
7/5/2011 10
(10 x 5)
50
7/6/2011 10
(10 x 6)
60
7/7/2011 10
(10 x 6)
60
7/8/2011 10
(10 x 6)
60
7/9/2011 10
(10 x 6)
60
7/10/2011 10
(10 x 6)
60
On the Production Data Summary pane, the Cost Of Losses value is the sum of the cost
of losses for all days in the plan. Continuing with the example, in the following table, you
can see the total cost of losses in the last row (shaded orange):
Period
Losses Margin Cost of Losses
7/1/2011 10
50
7/2/2011 10
50
7/3/2011 10
50
7/4/2011 10
50
7/5/2011 10
50
7/6/2011 10
60
7/7/2011 10
60
7/8/2011 10
60
7/9/2011 10
60
7/10/2011 10
60
Total Cost of Losses
550
Based on this data, you would see $550 next to the Cost Of Losses label on the
Production Data Summary tab, as shown in the following image (a red outline has been
added to the image to highlight the value).
Note: The calculated Cost of Losses value is displayed using the number of decimal
places defined for the Display Precision setting, regardless of the number of decimal
places in the underlying Losses and Margin values.
About the Production Data Summary

Graph
Note: The standard toolbar is not displayed on the graph by default. You can display it
manually by right-clicking the graph and clicking Toolbar.
The Production Data Summary graph appears on the Production Summary tab of the
Production Data Entry page. The Production Data Summary graph displays a graphical
representation of the data that exists on the production data tabs. The graph is built
dynamically and is not stored in the Meridium Catalog.
By default, the graph is configured as a pie graph. When you first access the Production
Data Entry page and before you have entered any values on the Production Data tab, the
graph looks like this:
Note: We recommend that you not change the graph type. If you do, it may not work as
expected.
When you enter values on the production data tabs, the graph will be updated
automatically to include additional categories.
You can see different production data details on the graph using the following categories
at the top of the graph:
Production Event Code: Displays information about the production events that are
selected on the production data tabs.
Impact Code: Displays information about the impact codes that are selected on
the production data tabs.
OEE Code: Displays information about all OEE codes that are selected on the
production data tabs.
OEE Code (Availability): Displays information about the availability OEE codes
that are selected on the production data tabs.
OEE Code (Performance): Displays information about the performance OEE

codes that are selected on the production data tabs.
OEE Code (Quality): Displays information about the quality OEE codes that are
selected on the production data tabs.
Production Data Summary Graph

Details
The following table provides details about the categories (above the graph) and
subcategories (below the graph) that appear on the Production Data Summary graph. The
calculations used in each subcategory are colored blue to help them stand out from the
rest of the text.
Subcategory
Good
Production
Main
Category
Production
Event Code
Question
What
percentage of
Impact Code periods
contains an
Actual value
OEE Code
that is greater
than or equal
Calculation
Example
Good
Production =
( All Actual
Values / All
MSC Values)
x 100
The sum of all Actual

values is 45,000.
The sum of all MSC values
is 65,000.
Therefore:
to the Planned
Production
value?
Good Production =
(45,000 / 65,000) x
100
Good Production = .
6923 x 100
Good Production =
69.23%
is 80,000.
The sum of all Short Range

Plan values is 65,000.
values is 45,000.
Unaccounted
Loss = [( All The sum of all Loss values
Short Range is 16,000.
Production
What
Values - All
Event Code percentage of
Actual Values Therefore:
available time
- All
Unaccounted
Impact Code was the
Unaccounted Losses
Losses) /
Loss
production unit
= [(65,000 - 45,000
All MSC
not scheduled
OEE Code
- 16,000) / 80,000]
Values] x 100
for production?
x 100
Unaccounted Losses
= (4000 / 80,000) x
100
Unaccounted Losses
= .05 x 100
Unaccounted Losses
= 5%
is 150,000.
No Planned
Production
Production
Event Code
In what
percentage of
Impact Code periods did I
reduce the
Short Range
OEE Code
Value?
No Planned
Production =
[( All MSC One day, the MSC value is
Values - All 5,000, and the Short Range
Short Range Plan value is 4,000. So, the
Values) / All No Planned Production
MSC Values] Value is 1,000 (5,000 x 100
4,000).
Another day, the MSC

value is 5,000, and the
Short Range Plan value is
3,000. So, the No Planned
Production Value is 2,000
(5,000 - 3,000).
Therefore:
No Planned
Production =
[(1,000 + 2,000) /
150,000] x 100
No Planned
Production = (3,000
/ 150,000) x 100
No Planned
Production = .02 x
100
No Planned
Production = 2%
The sum of losses in all
Production Loss records
where the Production Event
value is null is 31,220.
NPED = (
Losses where
is 483,910.
the
Production
Therefore:
Event value is
null / All
NPED = (31,220 /
MSC Values)
483,910) x 100
x 100
NPED = .00546 x
100
No Production Production
Event Defined Event Code
What
percentage of
losses are
missing a
Production
Event?
No Production Production
Event Code Event Code
Defined
NPED = 0.55%
The sum of losses where
What
NPECD = ( the Production Event comes
percentage of Losses where from a Production Event
record whose Production
losses contain a the
Event Code field is null is
value in the
Production
Production
Event value is
31,220.
Event field but
the
corresponding
Production
Event record
does not have a
value in the
Production
Event Code
field?

populated but
is 483,910.
the associated
Production
Therefore:
Event record
contains no
NPECD = (31,220 /
Production
483,910) x 100
Event Code /
NPECD = .0645 x
All MSC
100
Values) x 100
NPECD = 6.45%
<Production
Event Code
Name> = (
All Losses
where the
the value in the Production
Production
Event Code Event field is
Weekends/Holidays is
value is
<Production 23,000.
Event Code
Name> / All The sum of all MSC values
MSC Values) is 713,000.
x 100
Therefore:
What
percentage of
<Production
loss is not
Production
Event Code
associated with
Event Code
Name>
a given
Weekends/Holidays
<Production
= (23,000 / 713,000)
Note: The
Event Code>?
x 100
colors that are
Weekends/Holidays
used to
represent the
= .03225 x 100
Production
Event Codes
Weekends/Holidays
come from the
= 3.23%
Color field in
Production
Event Code
records.
<Impact Code The sum of losses where
Name> = ( the Impact Code value is
<Impact Code Impact Code What
TADD is 10,000.
Name>
percentage of All Losses
where the
loss is
associated with Impact Code The sum of all MSC values
value is
a given
<Impact Code
Name> / All
MSC Values)
x 100
is 65,000.
Therefore:
<Impact
Code>?
Note: The
colors that are
used to
represent the
Impact Codes
come from the
Color field in
Impact Code
records.
TADD = (10,000 /
65,000) x 100
TADD = .1538 x
100
TADD = 15.38%

the Impact Code value is
null is 2,000.
NICD = (
Losses where
the Impact
is 65,000.
What
Code value is
percentage of
null / All
No Impact
Therefore:
Impact Code losses are
MSC Values)
Code Defined
missing an
x 100
NICD = (2,000 /
Impact Code?
65,000) x 100
NICD = .0308 x 100
NICD = 3.08%
the OEE Code is
Unscheduled Downtime is
10,000.
<OEE Code
Name>
OEE Code
<OEE Code
Name> = (
All Losses
where the
OEE Code
value is <OEE is 65,000.
Code Name>
x All MSC Therefore:
Values) x 100
Unscheduled
Downtime =
(10,000 / 65,000) x
100
Unscheduled
Downtime = .1538
x 100
Unscheduled
Downtime =
15.38%
the OEE Code value is null
is 4,000.
No OEE Code
OEE Code
Defined
What
percentage of
losses are
missing an
OEE Code?

is 65,000.
NOCD = (
Losses where
the OEE Code Therefore:
value is null /
NOCD = (4,000 /
All MSC
Values) x 100
65,000) x 100
NOCD = .0615 x
100
NOCD = 6.15%
the OEE Code value is
under Idle Time is 4,000.
Idle Time
Loss
OEE Code

is 65,000.
Idle Time
Loss = ( All
What the
Losses where Therefore:
percentage of
the OEE Code
time is the
Idle Time Loss =
value is under
production unit
(4,000 / 65,000) x
Idle Time /
Idle?
100
All MSC
Idle Time Loss = .

Values) x 100
0615 x 100
Idle Time Loss =
6.15%
What
Availability the OEE Code value is
percentage of Loss = ( All under Availability is 4,000.
scheduled
Losses where
production time the OEE Code The sum of all MSC values
is the
value is under is 65,000.
production unit Availability /
mechanically All MSC
Therefore:
available? Values) x 100
Availability
Loss
OEE Code
Availability Loss =
(4,000 / 65,000) x
100
Availability Loss = .
0615 x 100
Availability Loss =
6.15%
under Performance is
4,000.
Performance
OEE Code
Loss

Performance
is 65,000.
Loss = ( All
What is the
Losses where
Therefore:
efficiency of the the OEE Code
production
value is under
Performance Loss =
unit?
Performance /
(4,000 / 65,000) x
All MSC
100
Values) x 100
Performance Loss =
.0615 x 100
Performance Loss =
6.15%
under Quality is 4,000.
Quality Loss OEE Code
Quality Loss
What
percentage of = ( All
is 65,000.
Losses where
scheduled
production time the OEE Code
Therefore:
value is under
is the
production unit Quality / All
Quality Loss =
MSC Values)
producing
(4,000 / 65,000) x
products that x 100
100
met 1st run
Quality Loss = .
quality
0615 x 100
requirements?
Quality Loss =
6.15%
<Availability The sum of losses where
OEE Code
the OEE Code is
<Availability OEE Code
What
OEE Code
Name>
Name> = [ Unscheduled Downtime is

All Losses
10,000.
where the
OEE Code
The sum of (All Actual
value is
Values + All Losses where
<Availability
OEE Code
under Availability + All
Name> / (
Losses where the OEE
All Actual
Code value is under
Values + All
Performance + All Losses
Losses where
where the OEE Code value
percentage of the OEE Code is under Quality is 65,000.
value is under
loss is
associated with Availability +
Therefore:
(Availability)
All Losses
a given
<Availability where the
Unscheduled
OEE Code>? OEE Code
Downtime =
value is under
(10,000 / 65,000) x
Performance
100
+ All Losses
Unscheduled
where the
Downtime = .1538
OEE Code
x 100
value is under
Quality)] x
Unscheduled
100
Downtime =
15.38%

<Performance OEE Code
What
<Performance the OEE Code is Minor
Stops is 10,000.
OEE Code
(Performance) percentage of OEE Code
Name>
loss is
Name> = [
associated with All Losses
The sum of all (All Actual
a given
where the
Values + All Losses where
<Performance OEE Code
OEE Code value is under
OEE Code>? value is
Performance + All Losses
<Performance where OEE code value is
OEE Code
under Quality) is 65,000.
Name>)/(
All Actual
Therefore:
Values + All
Losses where
Minor Stops =
OEE Code
(10,000 / 65,000) x
value is under
100
Performance
Minor Stops = .
+ All Losses
1538 x 100
where OEE
Code value is
under
Quality)] x
100
Minor Stops =
15.38%

the OEE Code is Startup
Rejects is 10,000.
<Quality OEE OEE Code

Code Name> (Quality)
OEE Availability
What
percentage of
loss is
associated with
a given
<Quality OEE
Code>?
OEE Code
What
(Availability) percentage of
time was the
production unit
Mechanically
Available to
produce
products?
<Quality OEE
Code Name>
The sum of all (Actual
= [ All
Values + Losses where the
Losses where
the OEE code
Quality) is 65,000.
value is
<Quality OEE
Therefore:
Code Name>/
( All Actual
Startup Rejects =
Values + All
(10,000 / 65,000) x
Losses where
100
the OEE Code
Startup Rejects = .
value is under
1538 x 100
Quality)] x
100
Startup Rejects =
15.38%
OEE Code - values is 10,000.
Availability =
[( All Actual The sum of all losses where
Values + All the OEE Code is under
Losses where Performance is 2,000.
OEE Code
value is under The sum of all losses where
Performance the OEE Code is under
+ All Losses Quality is 1,000.
where OEE
Code value is The sum of all losses where
under
the OEE Code is under
Quality)/( Availability is 3,000.
All Actual
Values + All Therefore:
Losses where
OEE Code
Availability =
Availability +
[(10,000 + 2,000 +
All Losses
1,000) / (10,000 +
where OEE
3,000 + 2,000 +
Code value is
under
Performance
+ All Losses
where OEE
Code value is
under
Quality)[ x
100
1,000)] x 100
OEE Code Availability =
(13,000 / 16,000) x
100

81.25%
values is 10,000.
OEE Code - The sum of all losses where

Performance the OEE Code is under
Performance is 2,000.
= [( All
Actual Values
+ All Losses The sum of all losses where
where OEE the OEE Code is under
Code value is Quality is 1,000.
under
What is the
Quality)/( Therefore:
efficiency of the
All Actual
OEE OEE Code
production unit
OEE Code Values + All
Performance (Performance) for the time
Losses where
Availability =
that production
OEE Code
[(10,000 + 1,000) /
was scheduled?
value is under
(10,000 + 2,000 +
Performance
1,000)] x 100
+ All Losses
OEE Code where OEE
Availability =
Code value is
(11,000 / 13,000) x
under
100
Quality)] x
100
84.61%
OEE - Quality OEE Code
What
OEE Code - values is 10,000.
(Quality)
percentage of Quality = [
1st run
All Actual
The sum of all losses where
quality
Values / ( All the OEE Code is under
products were Actual Values Quality is 1,000.
produced?
+ All Losses
where OEE Therefore:
Code value is
under
OEE Code -
Quality)] x
100
Availability =
[10,000 / (10,000 +
1,000)] x 100
(10,000 / 11,000) x
100
90.9%
Accessing the Metrics & Analysis Page

To access the Metrics & Analysis page:
On the PLA Start Page, click the Metrics and Analysis link.
Note: The Metrics and Analysis link appears on the PLA Start Page only if the Metrics
and Scorecards and/or Reliability Analytics module is active. If neither is active, the link
does not appear.
The Metrics & Analysis page appears.
Aspects of the Metrics & Analysis Page

The Metrics & Analysis page contains the following items:
Tools menu
Common Tasks menu
Production Units pane: Contains a tree that displays all Production Unit records
that exist in the database.
Metrics pane: Displays a list of Metric Views that you can open to display data
from the Production Unit record that is selected in the Production Units pane.
Note: This section appears only if the Metrics and Scorecards module is active.
Production Analyses pane: Displays a list of Production Analysis records that are
linked to the Production Unit record that is selected in the Production Units pane.
Note: This section appears only if the Reliability Analytics module is active.
Tools
The Tools menu on the Metrics & Analysis page contains the following links:
Manage Events: Displays the Production Event Management page, where you can
manage Production Event records.
Metrics and Analyses: Continues to display the Metrics & Analysis page. A green
arrow appears to the left of this link when you are viewing the Metrics & Analysis
page.
Common Tasks Menu

The Common Tasks menu on the Metrics & Analysis page contains the following links:
Page.
Help: Displays the context-sensitive Help topic for the Metrics & Analysis page.
Create Production Analysis: Displays the Production Analysis Builder, which you
can use to build a new Production Analysis.
Note: The Create Production Analysis link appears only if the Reliability Analytics
module is active.
Production Units Pane

The Production Units pane on the Metric Views and Production Analyses page contains a
tree that displays all Production Unit records that exist in the database. The root level of
the tree displays the family grouping Production Units, which is represented by the
icon. Directly below the family node are nodes representing the Product records. Each
record is represented by the icon. To the right of each icon is the Record ID.
For example, suppose the following Production Units records exist in the database: Unit
A and Unit B. In this case, the tree would look like this:
Metrics Pane
The Metrics pane on the Metric Views and Production Analyses page contains a grid,
which displays a list of all Metric Views that exist in the Catalog folder
\\Public\Meridium\Modules\PLA\Metrics. The Metrics pane is shown in the following
image.
Each row in the grid contains the hyperlinked Catalog caption of one Metric View, which
you can click to open the Metric View. Data from the Production Unit record that is
selected in the Production Units pane will be passed into the Metric View.
Note: If the selected Production Unit record is not linked to any Production Profile
records, when you try to open a Metric View for that Production Unit record, an error
message will appear.
Production Analyses Pane

The Production Analyses pane on the Metric Views and Production Analyses page
contains a grid, which displays a list of all Production Analysis records that are linked to
the Production Unit record that is selected in the Production Units pane. The Production
Analyses pane is shown in the following image.
Each row in the grid contains the hyperlinked ID of one Production Analysis record,
which you can click to open the Production Analysis on the Production Analysis page.
Accessing the Production Analysis

Builder
To access the Production Analysis Builder from within PLA:
1. Access the Metric Views and Production Analyses page.
2. On the Common Tasks menu, click the Create Production Analysis link.
The Production Analysis Builder appears, displaying the Welcome screen.
Using the Production Analysis Builder

to Create a Production Analysis from
PLA
To use the Production Analysis Builder to create a Production Analysis from PLA:
1. In the Production Analysis Builder, on the Welcome screen, click the Next button.
The Select Related Production Profile screen appears.
2. In the list, select the Production Profile record that you want to use to build the
Production Analysis.
The Select Time Period screen appears.
4. In the Start Date list, select the first day whose production data you want to plot in
the Production Analysis.
5. In the End Date list, select the last day whose production data you want to plot in
the Production Analysis.
The Specify Production Analysis Name screen appears, displaying a default Analysis ID.
7. If desired, change the Analysis ID.

The Production Analysis is created and appears on the Production Analysis page. Note
that several fields in the Production Analysis record are populated automatically.
Values Mapped to the Production

Analysis Record
When you create a Production Analysis from Production Profile and Production Data
records, several fields in the Production Analysis record are populated automatically as
shown in the following table.
Production
Analysis Field
Default Value
A value that is constructed using the following format:
Analysis ID
<Production Profile ID> ~ <Start Date> ~ <End Date>
...where:
<Production Profile ID> is the Record ID of the Production

Profile record that you selected in the Production Analysis
Builder.
<Start Date> is the Start Date that you selected in the
Production Analysis Builder.
<End Date> is the End Date that you selected in the Production
Analysis Builder.
Start Date
The Start Date that you selected in the Production Analysis Builder.
End Date
The End Date that you selected in the Production Analysis Builder.
Unit of Measure The value in the Product UOM field in the Production Profile record
that you selected in the Production Analysis Builder.
Margin Value
The value in the Default Margin field in the Production Profile record
that you selected in the Production Analysis Builder.
Analysis Type
The value Production Analysis.
Ignored Points
The value 0.
Min Production The value 0.0001.

Contains code representing a combination of values that make up the
Production Data production data that is displayed on the Production Analysis plot. This
combination of values is mapped from the following fields in PLA:
Production Data records:
Actual
Period
MSCR
Production Loss records:
OEE Code
Event Code
Impact Code
The number of Production Data records that meet the following
criteria:
Total Points
They are associated with the Production Profile record that you
selected in the Production Analysis Builder.
-and-
The date in their Period field is on or after the Start Date and
on or before the End Date that you selected in the Production
Analysis Builder.
Values Mapped to the Production Data

Field
About Values Mapped to the Production Data field

When you create a Production Analysis from records in the Production Loss Accounting
module, several field values are passed from those records to the Production Data field in
the Production Analysis record. The Production Data field stores code representing the
production data that is used to create the Production Analysis plot. You can view the
underlying production data on the Edit Production Data window in the Production
Analysis module.
The All Production Data query, which is located in the Catalog folder
\\Public\Meridium\Modules\Reliability Manager\Analyses, determines which values from
PLA are mapped to the Production Data field.
The following table lists the PLA fields whose values are mapped to the Production Data
field by default, along with the columns in the Edit Production Data window in which
you can see those values.
PLA Family
PLA Field
Edit Production Data Window Column
Production Data
Actual
Production Output
Production Data
Period
Date
Production Data
MSCR
MSCR
Production Loss
OEE Code
OEE
Production Loss
Event Code
Event Code
Production Loss
Impact Code
Impact Code
On the Production Analysis page, you can use the group data feature to display
production data according to the values (e.g., impact codes) that are mapped from PLA.
Note: An administrative user can map values in different fields by modifying the All
Production Data query, which is located in the Catalog folder
\\Public\Meridium\Modules\Reliability Manager\Analyses.
About Mapping OEE, Event, and Impact Code Values
To determine which OEE codes, event codes, and impact codes associated with losses for
a given date get mapped from PLA to the Production Data field in a Production Analysis,
the Meridium APM system looks at all Production Loss records that are associated with
the Production Data record for that date. Those Production Loss records are then grouped
by event code, impact code, and OEE code to determine which event code is associated
with the highest loss, which impact code is associated with the highest loss, and which
OEE code is associated with the highest loss.
For each item (event code, impact code, and OEE code) values from the ones that are
associated with the highest loss are mapped to the Production Data field in the Production
Analysis record.
Note: If there is no value (e.g., impact code) defined for the highest loss, the value No
<Field> Defined will be mapped to the Production Analysis dataset.
For example, consider the following Production Loss records that are linked to the
Production Data record for 12/32/2007.
You can see that:
All losses are associated with the same event code: Operational Losses. The Total
loss amount for this event code is 2,100 (500 + 1,000 + 600).
Two of the losses are associated with the same impact code: OTDD Other
Down Days. The total loss amount for this impact code is 1,100 (500 + 600).
All of the losses are associated with different OEE codes. The individual loss
amounts associated with these OEE codes are 500, 1,000, and 600.
Using this example, for 12/23/2007, the following data would be mapped to the
Production Data field in a Production Analysis:
Production Event: Operational Losses, because it is the only event code that exists
for this date.
Impact Code: OTDD, because the combined loss amount associated with this
impact code is 1,100, which is higher than the loss amount associated with the
remaining Production Loss record (1,000).
OEE Code: Scheduled Downtime, because the loss amount associated with this
OEE code is 1000, which is higher than the loss amount associated with the
remaining two Production Loss records (500 and 600).
Note: The values that are mapped for each field for a given day do not have to be from
the same Production Loss record. In the example, OTDD and Scheduled Downtime are
not in the same Production Loss record.
Example of a Production Analysis

Created from PLA
Note: The purpose of the following example is only to show how data gets mapped from
PLA to a Production Analysis. It is not meant to show how production data can be used to
create a realistic Production Analysis.
Suppose a production plan is for January 1, 2010 through January 31, 2010 and that the
current day is January 13, 2010. In this case, the Production Data tab on the Production
Data Entry page would look something like this:
If you created a Production Analysis from this data, it would look like this, where the
Actual values are plotted on the x-axis:
For example, you can see the two Production Data records that have an Actual value of 0.
If you clicked the Unit of Measure link on the Analysis Settings task menu, you would see
Bottles/Day.
If you opened the Production Profile record that you selected in the Production Analysis
Builder when you created the Production Analysis, you would see the same value in the
Product UOM field, as shown in the following image.
If you clicked the Margin Value link on the Analysis Settings task menu, you would see 5.
If you opened the Production Profile record that you selected in the Production Analysis
Builder when you created the Production Analysis, you would see the same value in the
Default Margin field.
About the Integration Between PLA and

Metric Views
The baseline Meridium APM database contains the following PLA Metric Views, which
are stored in the Catalog folder \\Public\Meridium\Modules\PLA\Metrics:
Actual Versus Planned - Long Range

Actual Versus Planned - Short Range
Losses By Event Code
Losses By Impact Code
Losses By OEE Code
Mechanical Availability
OEE
OEE - Availability
OEE - Performance
OEE - Quality
On-Stream Factor
Operational Availability
Total Cost of Unreliability
After you record production values and account for losses using the Production Data
Entry page, you can access these Metric Views from the Metric Views and Production
Analyses page.
Note: You will be able to access the Metric Views only if an administrative user has
completed the necessary configuration steps.

Using the Long Range Plan field in Production Data records that are associated with that
Production Unit record, the Actual Versus Planned - Long Range Metric View illustrates
for a single production unit how much output it produced versus how much you planned
for it to produce.
Each level of the Metric View displays a percentage of production output values using the
following equation:
For example, assume that for Unit 1, the following values exist as of January 10, 2009.
Product
Date
Actual Value
Long Range Plan
Bottles
1/1/2009
3000
3000
Bottles
1/2/2009
3000
3000
Bottles
1/3/2009
2000
3000
Bottles
1/4/2009
3000
3000
Bottles
1/5/2009
2000
3000
Bottles
1/6/2009
3000
3000
Bottles
1/7/2009
3000
Bottles
1/8/2009
3000
Bottles
1/9/2009
1500
3000
Bottles
1/10/2009
1800
3000
Labels
1/1/2009
5000
6000
Labels
1/2/2009
5000
6000
Labels
1/3/2009
4000
6000
Labels
1/4/2009
4500
6000
Labels
1/5/2009
5000
6000
Labels
1/6/2009
6000
6000
Labels
1/7/2009
6000
Labels
1/8/2009
6000
Labels
1/9/2009
4800
6000
Labels
1/10/2009
5000
6000
From this table, for Unit 1 for January 1 through January 10:
The sum of all Actual values is 58,600.

The sum of all Long Range values is 90,000.
In this case, if you were to view the Actual Versus Planned - Long Range Metric View for
Unit 1, the level that displays Actual Versus Planned Long Range values for January
would use this equation:
Actual Versus Planned (Long Range) = (58,600 / 90,000) x 100
Actual Versus Planned (Long Range) = .6511 x 100
Actual Versus Planned (Long Range) = 65.11%

The graph would look like this, where the month of January is displayed on the x-axis,
and the production output is displayed on the y-axis as a percentage:
In other words, from January 1 through January 10, Unit 1 produced 65.11% of what you
planned for it to produce.
If you were to drill down into the next level of the graph, you would see this:
Here, you can see that for day 3 (January 3), Unit 1 produced 66.67% of the output you
planned for it to produce. This value is calculated using the following values from the
previous table.
Product
Date
Actual Value
Long Range Plan
Bottles
1/3/2009
2000
3000
Labels
1/3/2009
4000
6000
Using these values, for January 3:
The sum of all Long Range values is 9,000.
In this case, Actual Versus Planned (Long Range) is calculated as:

Actual Versus Planned (Long Range) = (6,000 / 9,000) x 100
Actual Versus Planned (Long Range) = .6666 x 100
Actual Versus Planned (Long Range) = 66.67%

Using the Short Range Plan field in Production Data records that are associated with that
Production Unit record, the Actual Versus Planned - Short Range Metric View illustrates
for a single production unit how much output it produced versus how much you planned
for it to produce after you adjusted the planned output amount.
Each level of the Metric View displays a percentage of production output values using the
following equation:
For example, assume that for Unit 1, the following values exist as of January 10, 2009.
Product
Date
Actual Value
Short Range Plan
Bottles
1/1/2009
3000
3000
Bottles
1/2/2009
3000
3000
Bottles
1/3/2009
2000
3000
Bottles
1/4/2009
3000
3000
Bottles
1/5/2009
2000
3000
Bottles
1/6/2009
3000
3000
Bottles
1/7/2009
Bottles
1/8/2009
Bottles
1/9/2009
1500
2000
Bottles
1/10/2009
1800
2000
Labels
1/1/2009
5000
6000
Labels
1/2/2009
5000
6000
Labels
1/3/2009
4000
6000
Labels
1/4/2009
4500
6000
Labels
1/5/2009
5000
6000
Labels
1/6/2009
6000
6000
Labels
1/7/2009
Labels
1/8/2009
Labels
1/9/2009
4800
5000
Labels
1/10/2009
5000
5000
From this table, for Unit 1 for January 1 through January 10:

The sum of all Short Range values is 68,000.
In this case, if you were to view the Actual Versus Planned - Short Range Metric View
for Unit 1, the level that displays Actual Versus Planned Short Range values for January
would use this equation:
Actual Versus Planned (Short Range) = (58,600 / 68,000) x 100
Actual Versus Planned (Short Range) = .86176 x 100
Actual Versus Planned (Short Range) = 86.18%

The graph would look like this, where the month of January is displayed on the x-axis,
and the production output is displayed on the y-axis as a percentage:
In other words, from January 1 through January 10, Unit 1 produced 84.93% of what you
planned for it to produce based on the adjusted planned output values.
Here, you can see that for day 9 (January 9), Unit 1 produced 90% of the output you
planned for it to produce after you adjusted the planned output amount. This value is
calculated using the following values from the previous table.
Product
Date
Actual Value
Short Range Plan
Bottles
1/9/2009
1500
2000
Labels
1/9/2009
4800
5000
The sum of all Short Range values is 7,000.
In this case, Actual Versus Planned (Short Range) is calculated as:

Actual Versus Planned (Short Range) = (6,300 / 7,000) x 100
Actual Versus Planned (Short Range) = .9 x 100
Actual Versus Planned (Short Range) = 90%
Losses By Event Code

The Losses By Event Code Metric View indicates the total amount of production losses
for a single production unit. Each level of the Metric View displays the sum of all values
in the Losses column on the Production Data tab.
The losses are displayed by Production Event Code, which is defined in the Production
Event Code field of the Production Event record that is linked to a Production Loss
record.
If there is no Production Event associated with a Production Loss, the loss will be
labeled No Production Event Defined on the legend.
If there is a Production Event associated with the Production Loss but it does not
have a Production Event Code, the loss will be labeled No Production Event Code
Defined on the legend.
If there is unaccounted loss that is not defined in a Production Loss record (i.e.,
the value in the Unaccounted Loss column on the Production Data tab), the loss
will be labeled Unaccounted Loss on the legend.
For example, assume that Unit 21 experiences the following losses on a monthly basis in
2011.
Production
Loss
Event Code
February
13,000
Forced Speed Reduction
24,000
Capital Improvement
38,000
Unaccounted Loss
March
7,500
Unaccounted Opportunity
Loss
15,000
No Production Event Code

Defined
4,500
No Production Event
Defined
88,500
Unaccounted Loss
April
5,500
Unaccounted Loss
The Losses By Event Code Metric View graph for this dataset is displayed in the
following image, where Time is displayed on the x-axis, Production Loss Amount is
displayed on the y-axis, and the Production Event Code is displayed on the legend.
If you drill down into the next level of the graph, the Metric View is divided into separate
months, as shown in the following image.
Losses By Impact Code
The Losses By Event Code Metric View indicates the total amount of production losses
for a single production unit. Each level of the Metric View displays the sum of all values
in the Losses column on the Production Data tab.
The losses are displayed by Impact Code, which is defined in the Impact Code field of
each Production Loss record.
If there is no value defined in the Impact Code field of a Production Loss record,
the loss will be labeled No Impact Code Defined on the legend.
For example, assume that Unit 21 experiences the following losses on a monthly basis in
2011.
Production Loss Impact Code

February
1,000
RMSD (Routine Maintenance Slowdown Day)
12,000
RMDD (Routine Maintenance Down Day)
24,000
OTDD (Other Type of Down Day)
38,000
Unaccounted Loss
March
3,000
RPSD (Regulatory Process Slowdown Day)
88,500
Unaccounted Loss
24,000
No Impact Code Defined
April
5,500
Unaccounted Loss
The Losses By Impact Code Metric View would look like this, where Time is displayed
on the x-axis, Production Loss Amount is displayed on the y-axis, and the Impact Code is
displayed on the legend:
If you drill down into the next level of the graph, the Metric View is divided into separate
months, as shown in the following image.
Losses By OEE Code

The Losses By OEE Code Metric View indicates the total amount of lost production,
grouped by OEE Code, for a single production unit. Each level of the Metric View
displays the sum of all values in the Losses column on the Production Data tab.
The losses are grouped by OEE Code, which is defined in the OEE Code field of each
Production Loss record.
If there is no value in this field, the loss will be labeled No OEE Code Defined on
the legend.
For example, assume that Unit 16 experiences the following losses in 2011.
Production Loss
OEE Code
January
27,900
(Unaccounted Loss)
31,000
Minor Stops
100
Startup Rejects
February
56,000
(Unaccounted Loss)
28,000
Minor Stops
March
31,000
(Unaccounted Loss)
93,000
Production Rejects
April
20,000
(Unaccounted Loss)
30,000
Production Rejects
10,000
Reduced Rate
20,000
Unscheduled Downtime
May
13,000
(No OEE Code Defined)
15,500
(Unaccounted Loss)
26,000
Scheduled Downtime
28,500
Reduced Rate
5,000
Unscheduled Downtime
June
6,000
(No OEE Code Defined)
6,000
(Unaccounted Loss)
12,000
Scheduled Downtime
12,000
Reduced Rate
Given these numbers, the Losses By OEE Code Metric View would look like this, where
time is displayed on the x-axis, production loss amount is displayed on the y-axis, and the
OEE Code is displayed on the legend:
The Mechanical Availability Metric View illustrates for a single production unit how
much time the unit was available for production and not down for one of the following
reasons:
Turnaround Down Day

Routine Maintenance Down Day
Routine Maintenance Slowdown Day
Each level of the Metric View displays a percentage of available time using the following
equation:
...where:
Time is the number of days for which the production data exists.
Short Range Plan is the Short Range Plan value for any day for which the
production data exists.
Note: If a production unit produces more than one product, where each of those products
has its own Short Range Plan values, the sum of those Short Range Plan values is used in
the equation. This is illustrated in the example following this list.
TADD is the amount of production that was lost due to a Turnaround Down Days
(i.e., the Impact Code is TADD).
RMDD is the amount of production that was lost due to a Routine Maintenance
Down Day (i.e., the Impact Code is RMDD).
RMSD is the amount of production that was lost due to a Routine Maintenance
Slowdown Day (i.e., the Impact Code is RMSD).
Note: If you have created custom impact codes to categorize your data, you will need to
modify the calculation for the Mechanical Availability Metric View in the Production
Data cube in SQL Server Analysis Services. Instructions for completing this task are not
provided in the Meridium APM Documentation. For more information, consult your
Microsoft documentation.
For example, assume that for Unit 1:
Production data exists for January 1 through January 10. So, time is 10 (ten days).
Unit 1 produced both bottles and labels during those ten days.
Unit 1 can produce 5,000 bottles per day and 8,000 labels per day.
Within the ten days, 24,500 bottles and labels were not produced as a result of
Turnaround Down Days.
Routine Maintenance Down Days.
Routine Maintenance Slowdown Days.
Using this data, Mechanical Availability is calculated using the following values:
Time = 10
Short Range Plan = 13,000 (i.e., 5,000 + 8,000)
TADD = 24,500
RMDD = 8,200
RMSD = 19,500
Remember that Mechanical Availability is calculated as:
...so:
Mechanical Availability = (10 x 13,000 - [24,500 + 8,200 + 19,500] / [10 x 13,000]) x

100
Mechanical Availability = ([130,000 - 52,200] / 130,000) x 100
Mechanical Availability = (77,800 / 130,000) x 100
Mechanical Availability = .59846 x 100
Mechanical Availability = 59.85%
In this case, if you were to view the Mechanical Availability Metric View for Unit 1, the
level that displays Mechanical Availability for January would look like this, where the
month of January is displayed on the x-axis, and the mechanical availability is displayed
on the y-axis as a percentage:
In other words, from January 1 through January 10, Unit 1 operated 59.85% of the time
without experiencing a Turnaround Down Day, Routine Maintenance Down Day, or
Routine Maintenance Slowdown Day.
Here, you can see that for day 2 (January 2), Unit 1 was available 84.62% of the day
without experiencing a Turnaround Down Day, Routine Maintenance Down Day, or
Routine Maintenance Slowdown Day. This value is calculated using the following values.
Product
Date
MSCR
Loss
Impact Code
Bottles
1/2/2010
5000
2000
RMSD
Labels
1/2/2010
8000
3000
RPSD
Time = 1 day
Short Range Plan = 13,000 (5,000 + 8,000)
TADD = 0
RMDD = 0
RMSD = 2,000
...Mechanical Availability is calculated as:

Mechanical Availability = ([1 x 13,000 - 2,000] / [1 x 13,000]) x 100
Mechanical Availability = .84615 x 100
Mechanical Availability = 84.62%
OEE Metric Views

The OEE Metric View indicates how well a manufacturing unit is performing by
evaluating the total availability, performance, and quality of that production unit and its
products. Using the OEE Code field in Production Loss records that are associated with a
Production Unit record, the OEE Metric View categorizes the production losses for a
given Production Unit into these three categories.
The results are displayed as an overall OEE percentage. A manufacturer's goal is to
operate at 100% OEE (or as close to it as possible), which can be accomplished only by
achieving 100% availability, 100% performance, and 100% quality. Each production loss
categorized by an availability, performance, idle time, or quality OEE code, or a child
code of these codes, will subtract from each percentage.
Note: If you have created a custom OEE code, it must be a child of a baseline OEE code
(i.e., Availability, Performance, Idle Time, or Quality) in order to be included in the OEE
Metric View calculations.
Each level of the OEE Metric View displays the OEE percentage for a production unit
during a given time frame (year, month, day), where the time frame is displayed along the
x-axis and gets progressively smaller as you drill into the Metric View. The OEE
percentage at each level of the Metric View is calculated using the following equation:
OEE (%) = [OEE (Availability) (%) x OEE (Performance) (%) x OEE (Quality) (%)] x
100
This formula can be further divided into three subformulas, where each subformula is
used to calculate the percentage of availability, performance, or quality.
For example, we want to measure the OEE of a bottling plant during the month of April.
The actual production for the month is 1,000 bottles. The following chart displays the
total production loss associated with each OEE code during that month.
Parent OEE Code Child OEE Code
Production Loss Amount
Availability
Scheduled Downtime
40
Availability
Unscheduled Downtime 150
Performance
Reduced Rate
75
Performance
Minor Stops
77
Quality
Production Rejects
300
Quality
Startup Rejects
To calculate OEE percentage for our bottling process, we must first calculate the
availability, performance, and quality percentages using the OEE codes that are assigned
to production losses. Each of these subformulas within the OEE calculation has its own
corresponding Metric View, which are described below.
OEE (Availability) (%)

OEE (Availability) (%) = (Actual + Performance Losses + Quality Losses) / (Actual +
Performance Losses + Quality Losses + Availability Losses)
...where:
Availability Losses =
Losses due to Availability +
Losses due to
Unscheduled Downtime +
Losses due to Scheduled Downtime +
Losses due to custom child OEE codes with Availability as a parent code
Performance Losses =
Losses due to Performance +
Minor Stops +
Losses due to Reduced Rate +
child OEE codes with Performance as a parent code
Quality Losses =
Losses due to Quality +
Losses due to
Losses due to custom
Losses due to Production
Rejects +
Losses due to Startup Rejects +
OEE codes with Quality as a parent code
Losses due to custom child
For our example, suppose that:
Actual values are 1,000.

Quality Losses are 304 (300 + 4).
Performance Losses are 152 (75 + 77).
Availability Losses are 190 (150 + 40).
In this case, the Availability (%) calculation would look like this:
OEE (Availability) (%) = (1,000 + 152 + 304) / (1,000 + 152 + 304 + 190)
OEE (Availability) (%) = 1,456 / 1,646
OEE (Availability) (%) = 0.88
OEE (Performance) (%)

OEE (Performance) (%) = (Actual + Quality Losses) / (Actual + Quality Losses +
Performance Losses)
Where...
Performance Losses =
Losses due to Performance +
Minor Stops +
Losses due to Reduced Rate +
child OEE codes with Performance as a parent code
Quality Losses =
Rejects +
Losses due to
Losses due to custom

For our example, Performance Losses are 152 (77 + 75) and Quality Losses are 304 (300
+ 4). The Performance (%) calculation would look like this:
OEE (Performance) (%) = (1,000 + 304) / (1,000 + 304 + 152)
OEE (Performance) (%) = 1,304 / 1,456
OEE (Performance) (%) = 0.90
OEE (Quality) (%)

OEE (Quality) (%) = Actual / (Actual + Quality Losses)
Where...
Quality Losses =
Rejects +

For our example, Quality Losses are 304 (300 + 4). The Quality (%) calculation would
look like this:
OEE (Performance) (%) = 1,000 / 1,304
OEE (Performance) (%) = 0.77
OEE (%)
After each subformula has been calculated, we can use those percentages to calculate the
overall OEE percentage.
OEE (%) = [OEE (Availability) (%) x OEE (Performance) (%) x OEE (Quality) (%)] x
100
OEE (%) = [ 0.88 x 0.90 x 0.77 ] x 100
OEE (%) = [ 0.61 ] x 100
OEE (%) = 61%
You can use the OEE Metric View to see how well your manufacturing operation is
performing. For example, perhaps in 2011, this unit had an OEE percentage of 85%
during the month of February. This means that due to a decrease in availability,
performance, or quality, the production unit was not 100% efficient. In April, the month
we used in our example, OEE dropped to 61%. We may conclude that a change in our
production process caused a loss of efficiency, and we should examine the areas of
availability, quality, and performance to determine what changes can be made to improve
OEE. To see which OEE code was associated with the highest amount of production loss,
use the Losses By OEE Code Metric View.
On-Stream Factor
The On-Stream Factor Metric View illustrates for a single production unit how much
time the unit was available for production and not down for any reason indicated in the
baseline Impact Code records.
equation:
...where:
has its own production plan and Short Range Plan values, the sum of those Short Range
Plan values is used in the equation. This is illustrated in the example following this list.
TADD is the amount of product that was lost due to a Turnaround Down Days
RMDD is the amount of product that was lost to a Routine Maintenance Down
Day (i.e., the Impact Code is RMDD).
RMSD is the amount of product that was lost due to a Routine Maintenance
RPDD is the amount of product that was lost due to a Regulatory Process Down
Day (i.e., the Impact Code is RPDD).
RPSD is the amount of product that was lost due to a Regulatory Process
Slowdown Day (i.e., the Impact Code is RPSD).
OTDD is the amount of product that was lost due to another type of Down Day
(i.e., the Impact Code is OTDD).
OTSD is the amount of product that was lost due to another type of Slowdown
Day (i.e., the Impact Code is OTSD).
modify the calculation for the On-Stream Factor Metric View in the Production Data cube
in SQL Server Analysis Services. Instructions for completing this task are not provided in
the Meridium APM Documentation. For more information, consult your Microsoft
documentation.
Within the ten days, no Regulatory Process Down Days occurred.
Regulatory Process Slowdown Days.
Within the ten days, no other type of Down Day occurred.
another type of Slowdown Day.
Time = 10
TADD = 24,500
RMDD = 8,200
RMSD = 19,500
RPDD = 0
RPSD = 14,200
OTDD = 0
OTSD = 5,000
Remember that On-Stream Factor is calculated as:
...so:
On-Stream Factor = (10 x 13,000 - [24,500 + 8,200 + 19,500 + 0 + 14,200 + 0 + 5,000] /
[10 x 13,000]) x 100
On-Stream Factor = ([130,000 - 71,400] / 130,000) x 100
On-Stream Factor = (58,600 / 130,000) x 100
On-Stream Factor = .4507 x 100
On-Stream Factor = 45.07%
In this case, if you were to view the On-Stream Factor Metric View for Unit 1, the level
that displays on-stream factor for January would look like this, where the month of
January is displayed on the x-axis, and the on-stream factor is displayed on the y-axis as a
percentage:
without experiencing a Down Day or Slowdown Day.
without experiencing a Down Day or Slowdown Day. This value is calculated using the
following values.
Product
Date
MSCR
Losses
Impact Code
Bottles
1/6/2010
5000
2000
RPSD
Labels
1/6/2010
8000
2000
OTSD
Time = 1 day
Short Range Plan = 13,000 (5,000 + 8,000)
TADD = 0
RMDD = 0
RMSD = 0
RPDD = 0
RPSD = 2,000
OTDD = 0
OTD = 2,000
...On-Stream Factor is calculated as:

On-Stream Factor = ([1 x 13,000 - 4,000] / [1 x 13,000]) x 100
On-Stream Factor = .6923 x 100
On-Stream Factor = 69.23%
The Operational Availability Metric View illustrates for a single production unit how
much time the unit was available for production and not down for one of the following
reasons:
Turnaround Down Day

Routine Maintenance Down Day
Routine Maintenance Slowdown Day
Regulatory Process Down Day
Regulatory Process Slowdown Day
equation:
...where:
has its own production plan and Short Range Plan values, the sum of those Short Range
Plan values is used in the equation. This is illustrated in the example following this list.
TADD is the amount of product that was lost due to a Turnaround Down Days
RMDD is the amount of product that was lost to a Routine Maintenance Down
Day (i.e., the Impact Code is RMDD).
RMSD is the amount of product that was lost due to a Routine Maintenance
RPDD is the amount of product that was lost due to a Regulatory Process Down
Day (i.e., the Impact Code is RPDD).
RPSD is the amount of product that was lost due to a Regulatory Process
Slowdown Day (i.e., the Impact Code is RPSD).
modify the calculation for the Operational Availability Metric View in the Production
Data cube in SQL Server Analysis Services. Instructions for completing this task are not
provided in the Meridium APM Documentation. For more information, consult your
Microsoft documentation.
Within the ten days, no Regulatory Process Down Days occurred.
Regulatory Process Slowdown Days.
Time = 10
TADD = 24,500
RMDD = 8,200
RMSD = 19,500
RPDD = 0
RPSD = 14,200
Remember that Mechanical Availability is calculated as:
...so:
Operational Availability = (10 x 13,000 - [24,500 + 8,200 + 19,500 + 0 + 14,200] / [10 x
13,000]) x 100
Operational Availability = ([130,000 - 66,400] / 130,000) x 100
Operational Availability = (63,600 / 130,000) x 100
Operational Availability = .4892 x 100
Operational Availability = 48.92%
In this case, if you were to view the Operational Availability Metric View for Unit 1, the
level that displays Operational Availability for January would look like this, where the
month of January is displayed on the x-axis, and the operational availability is displayed
on the y-axis as a percentage:
without experiencing a Turnaround Down Day, Routine Maintenance Down Day, Routine
Maintenance Slowdown Day, Regulatory Process Down Day, or Regulatory Process
Slowdown Day.
without experiencing Turnaround Down Day, Routine Maintenance Down Day, Routine
Maintenance Slowdown Day, Regulatory Process Down Day, or Regulatory Process
Slowdown Day. This value is calculated using the following values.
Product
Date
MSCR
Losses
Impact Code
Bottles
1/3/2010
5000
3000
RMSD
Labels
1/3/2010
8000
4000
RMSD
Time = 1 day
Short Range Plan = 13,000 (5,000 + 8,000)
TADD = 0
RMDD = 0
RMSD = 7,000
RPDD = 0
RPSD = 0
...Operational Availability is calculated as:

Operational Availability = ([1 x 13,000 - 7,000] / [1 x 13,000]) x 100
Operational Availability = .4615 x 100
Operational Availability = 46.15%

The Total Cost of Unreliability Metric View indicates the total cost associated with all
production losses in all plans for a single production unit. Causing Equipment (i.e., the
value in the Causing Asset field of a Production Event record linked to a Production Loss
record) is displayed on the x-axis using the value in the Equipment Technical Number
field of the causing Equipment record. Cost associated with production losses is
displayed on the y-axis. The type of cost is displayed on the legend.
The Metric View displays cost of unreliability using the following equation:
For example, during the month of January, two production events occur for Unit 16.
Event 1 is an equipment breakdown, which is caused by a bottling machine associated
with the Equipment Record A0001-104. The value A0001-104 appears in the Causing
Equipment field of the Production Event record Event 1.
Event 2 is a power outage, which is associated with a Production Loss record but is not
associated with an Equipment Record (i.e., no value appears in the Causing Equipment
field of the Production Event record Event 2).
The following formulas are used to calculate the Total Cost of Unreliability for Unit 16.
Maintenance Cost
Maintenance Cost is the value in the Maintenance Cost field in a Work History record
that is associated with a Production Loss record for a production unit. The following table
displays how Work History records are associated with Production Loss records via other
records.
Record
Relationship
Record
Work History
Has Work History
Equipment
Equipment
Has Production Event
Production Event
Production Event
Caused By Production Event
Production Loss
Note: In order for the Maintenance Cost to appear in the Total Cost of Unreliability
Metric View for a production unit, the Production Unit record must be linked to the same
Functional Location record as the Work History record. In other words, work history
must be associated with a location that is part of the production unit.
For example, consider Event 1, the equipment breakdown event for Unit 16. The causing
equipment for this event, A0001-104, is linked to a Work History record with the value
6,395 in the Maintenance Cost field. In this case:
Maintenance Cost = $6,395
Event 2 does not have any maintenance cost because it is not associated with an
Equipment record.
Lost Profit Opportunity

Lost Profit Opportunity is a value representing the cost of production loss. LPO is
calculated using the following equation:
Lost Profit Opportunity = Losses x Margin
The margin value is located in the Margin field of a Production Profile record that is
linked to a Production Unit record. Losses are located in the Loss Amount field of a
Production Loss record.
For example, due to Event 1, Unit 16 records a loss of 9,000 bottles. The margin is $5.00.
This Lost Profit Opportunity for this example is calculated using the following values:
Losses = 9,000
Margin = $5
In other words, Lost Profit Opportunity is calculated as:

Lost Profit Opportunity = 9,000 x $5
Lost Profit Opportunity = $45,000
In the graph, $45,000 is displayed as LPO associated with A0001-104, the causing
equipment for Event 1.
For Event 2, a power outage causes a loss of 3,100 bottles. The loss is associated with the
same production profile, so the margin is $5. The Lost Profit Opportunity for Event 2 is
calculated as:
Lost Profit Opportunity = 3,100 x $5
This loss was not attributed to a particular piece of equipment. In the graph, $15,500 is
displayed as LPO labeled No Causing Equipment Defined.
Other Event Costs

Other Event Costs are any additional costs that are associated with a production event
that is associated with a production loss. These values are located in the Other Event
Costs field of a Production Event record that is linked to a Production Loss record.
For example, additional replacement parts need to be bought for Unit 16 as a result of
Event 1. The Other Event Costs field in the Production Event record contains a value of
$3,000 to account for additional replacement parts. In this case:
Other Event Costs = $3,000
In the graph, $3,000 is displayed as Other Event Costs associated with A0001-104, the
causing equipment for Event 1.
For Event 2, additional costs were incurred as a result of the storm that caused the power
outage. The Other Event Costs field the in the Production Event record contains a value
of $1,500 to account for those costs. In this case:
This loss was not attributed to a particular piece of equipment. In the graph, $1,500 is
displayed as Other Event Costs labeled No Causing Equipment Defined.
Complete Example
Consider the previous example for Unit 16.
The following totals were associated with the causing equipment A0001-104 (i.e., Event
1):
Maintenance Cost = $6,395

Given these values, Total Cost of Unreliability for A0001-104 for Unit 16 is calculated as:
Total Cost of Unreliability = Maintenance Cost + Lost Profit Opportunity + Other Event
Costs
Total Cost of Unreliability = $6,395 + $45,000 +$3,000
Total Cost of Unreliability = $54,395
The following totals were associated with an Equipment record (i.e., Event 2):

Given these values, Total Cost of Unreliability for No Causing Equipment Defined for
Unit 16 is calculated as:
Total Cost of Unreliability = Lost Profit Opportunity + Other Event Costs
Total Cost of Unreliability = $15,500+$1,500
Total Cost of Unreliability = $17,000
The Total Cost of Unreliability Metric View would look like this, where the Total Cost of
Unreliability is displayed on the y-axis, Causing Equipment is displayed on the x-axis,
and type of cost is displayed on the legend.
PLA Associated Pages

The following Associated Page is configured by default for the Production Event family
to facilitate workflows in PLA:
RCA Analysis: Displays one of the following items:
The New Analysis Builder: Displayed for Production Event records that
are not linked to an RCA Analysis record. You can use the New Analysis
Builder to create a new RCA Analysis from the selected Production Event
record.
The Analysis page: Displayed for Production Event records that ARE
linked to an RCA Analysis record. On the Analysis page, you can view the
details of the RCA Analysis record that is linked to the selected Production
Event record.
Note: To see the underlying URL for this Associated Page, you can use the URL Manager
application.
Metrics Folder
The folder \\Public\Meridium\Modules\PLA\Metrics contains Metric Views with the
following names, which are displayed on the Metric Views and Production Analyses
page:
Losses by Event Code
Losses by Impact Code
Losses by OEE Code
OEE
OEE - Availability
OEE - Performance
OEE - Quality
On-Stream Factor
Queries Folder
The folder \\Public\Meridium\Modules\PLA\Queries contains the following queries:
Query Name
AllProductionEvents
EventList
Behavior and Usage

Returns the Entity ID of all Production Event records. The query
is used to display values in the Production Event list on the
Production Event Management page. If desired, you can modify
the query to further limit the Production Event records that are
displayed in the list.
Returns the Entity ID of all Production Event records whose date
range includes the date in the Period field in a given Production
Data record. This query is used to display values in the

Production Event list on the Production Data Entry page. If
desired, you can modify the query to further limit the Production
Event records that are displayed in the list.
ImpactCodeList
Returns the Entity ID of all Impact Code records. This query is

used to display values in the Impact Code list on the Production
Data Entry page. If desired, you can modify the query to further
limit the Impact Code records that are displayed in the list.
OEECodeList
Returns the Entity ID of all OEE Code records. This query is

used to display values in the OEE Codes pane on the OEE
Coding page. If desired, you can modify the query to further limit
the OEE Code records that are displayed in the list.
Returns the Entity ID of all OEE Code records that contain the
value False in the Is Inactive field. This query is used to display
OEECodeListProdLoss values in the OEE Coding list on the Production Data Entry
page. If desired, you can modify the query to further limit the
OEE Code records that are displayed in the list.
Impact Code
Impact Code records store information about the impact of a production loss. The
following table provides an alphabetical list and description of the fields that exist for the
Impact Code family and appear on the Impact Code datasheet by default. The information
in the table reflects the baseline state and behavior of these fields.
Field
Code
Color
Data
Type
Description
Behavior and Usage
A short code that

This field is required. A list of baseline
Character represents the impact
Impact Code records can be found here.
of the production loss.
Character The color that is used This field contains a list, which displays
to represent the impact all colors that you can assign to the impact
code on the Production code. In the baseline database, colors are
not assigned to the baseline Impact Code

Data Summary graph. records. You will need to assign the
desired colors manually.
Description Character
A description of the
impact.
You can define this field manually.
OEE Code
OEE Code records store information about the overall effectiveness of a piece of
equipment that causes a production loss. The following table provides an alphabetical list
and description of the fields that exist for the OEE Code family and appear on the OEE
Code datasheet by default. The information in the table reflects the baseline state and
behavior of these fields.
Field
Data
Type
Description
Behavior and Usage
A short code that

identifies a reason
for a loss in
OEE Code Character equipment
This field is required.
efficiency that
caused a production
loss.
A description of the You can define this value manually by typing

OEE code.
a description into this field.
If this field contains the value True, the code

is disabled in the OEE codes pane on the
OEE Coding page. If the code is disabled,
Indicates whether you will not be able to add a child code under
Is Inactive Logical the OEE code is
it. Also, you will not be able to assign a
enabled or disabled. disabled code to a production loss. If this
field contains the value False, the code is
enabled and you will be able to use the code
throughout PLA.
Root Code Character
The parent code of

the OEE code.
This field does not appear on the datasheet.

The OEE Metric View uses the value in this
field to determine whether an OEE code is an
Availability, Performance, or Quality code in
the OEE (%) calculation. This field contains
the following values, depending on the type
of OEE code:
For child OEE codes, this field

contains the parent OEE code.
For parent OEE codes, this field

contains the same value as the OEE
code field.
Product
Product records store basic information about a product in the Meridium APM system.
The following table provides an alphabetical list and description of the fields that exist
for the Product family and appear on the Product datasheet by default. The information in
the table reflects the baseline state and behavior of these fields.
Description
Behavior and Usage
Description Text
product.
You can define this field manually
Name
The name of the

product.
This field is required. You can define this

field manually.
Field
Data
Type
Character
Production Data
Production Data records store information about production values. The following table
provides an alphabetical list and description of the fields that exist for the Production
Data family and are appear on the Production Data datasheet. The information in the table
reflects the baseline state and behavior of these fields.
The baseline Production Data fields are displayed in the grid on the Production Data tab
of the Production Data Entry page. You can access the Production Data datasheet for a
Production Data record by clicking any hyperlinked Period in that grid. If, however, you
add fields to the Production Data family and datasheet, those fields will not appear on the
Production Data tab.
Field
Actual
Long
Range
Plan
Data
Type
Description
Behavior and Usage
When the Production Data record is

created, the value is set by default to
The amount of product you zero (0). It is updated automatically
Number produced on the period in the with the Actual value that you enter
Period field.
in the grid on the Production Data
tab on the Production Data Entry
page.
By default, the value is set to the
planned production amount, which
appears in the <Product Name
The amount of product that (<UOM>)> cell on the Production
Number you planned to produce this Plan Management page for the
associated production plan.
period.
This field is disabled.
created, this field does not contain a
value. It is populated automatically
with the sum of the values in the Loss
Amount field in all Production Loss
records to which the Production Data
record is linked. This field is
disabled.
Losses
Margin
The amount of product that

you could have produced but
Number
did not produce during the
Along with the value in the Margin
period in the Period field.
field in the Production Data record,
the value in the Losses field is used to
calculate the cost of losses, which
appears on the Production Data
Summary tab on the Production Data
Entry page.
created, the value in the Margin field
Number The profit associated with
is set by default to the value in the

Default Margin field in the associated
Production Profile record (i.e., the
Production Profile record that is
linked to the Production Plan record
producing one unit of the
product, where the product is to which the Production Data record
defined in the Product field in is linked). The field is disabled.
the Production Profile record
that is linked to the
Along with the value in the Losses
Production Plan record to
field in the Production Data record,
which this Production Data the value in the Margin field is used
record is linked.
to calculate the cost of losses, which
appears on the Production Data
Summary tab on the Production Data
Entry page.
This value is set by default to the
value in the Maximum Sustained
Capacity Rate field in the Production
Max
The value against which the Profile record that is linked to the
Sustained Number Actual value is compared to Production Plan record to which the
Capacity
determine if a loss occurred. Production Data record is linked.
On the Production Data Entry page,
the Period column displays the start
time and end time, separated by a
dash.
The period for which the
production data begins.
Start Time Date
End Time Date
The period for which the

production data begins.
In the baseline database, this field

stores time using the Coordinated
Universal Time (UTC) format (i.e.,
the UTC check box is selected when
you view the field properties in the
Configuration Manager).
On the Production Data Entry page,
the Period column displays the start
time and end time, separated by a
dash.
In the baseline database, this field
stores time using the Coordinated
Universal Time (UTC) format (i.e.,
the UTC check box is selected when
you view the field properties in the
Short
Range
Plan

By default, the value is set to the
planned production amount, which
appears in the <Product Name
(<UOM>)> cell on the Production
Plan Management page for the
associated production plan.
The adjusted planned

production output due to a
circumstance that could not
Number have been predicted at the
time the plan was created
(e.g., natural disaster such as
a flood or a hurricane).
You can modify this value is needed.
Production Event
Production Event records store details about an event that results in reduced production
output. The following table provides an alphabetical list and description of the fields that
exist for the Production Event family and appear on the baseline Production Event
datasheet. The information in the table reflects the baseline state and behavior of these
fields.
Field
Causing
Asset
Comment
Data
Type
Description
Behavior and Usage
This field contains a

button, which you
can
click
to
select
the
Equipment
record that
The piece of
represents the piece of equipment that caused
Character equipment that
caused the event. the event. When you save the Production
Event record, it will be linked automatically to
the selected Equipment record.
Text
Additional
comments about
the event.
This field can be define manually.
Created By Character The User Name of When the record is created, this field is
the Security User populated automatically with the User Name
who created the of the Security User who is currently logged
Production Event in. You cannot modify the value in this field.
record.
Created
Date
Date
Description Text
End Date
Event ID
Date
The date and time

the Production
Event record was
created.
When the record is created, this field is

populated automatically with the current date
and time. You cannot modify the value in this
field.
A detailed
description of the You can define this field manually.
event.
Along with the production event start date, the
end date determines whether or not this
production event will be available in the
Production Event list on the Production Data
Entry page.
If the Production Event record does not have
an end date, the production event will appear
The date that the
in the Production Event list for losses that are
event ended.
associated with any day after the start date.
Character The ID of the

event.
In the baseline database, this field stores time

using the Coordinated Universal Time (UTC)
format (i.e., the UTC check box is selected
when you view the field properties in the
This field is populated automatically with a
value that appears in the following format:
<Source Unit>~<Production Event
Code>~<Start Date>~<Headline>
...where:
<Source Unit> is the value in the

Source Unit field in this Production
Event record.
<Production Event Code> is the value
in the Production Event Code field in
this Production Event record.
<Start Date> is the value in the Start
Date field in this Production Event
record.
<Headline> is the value in the

Headline field in this Production Event
record.
This field does not appear on the datasheet but

it does appear in the grid on the Production
Event Management page.
Headline
A short
Character description of the You can define this field manually.
event.
Costs that are

associated with
Other Event
the event and are
Number
Costs
not recorded in
the selected Work
History record.
This value is preceded by a currency symbol,

which is set by default to $ but can be
changed via the Currency dialog box if
desired.

button, which you
Production Character The type of
Event Code
production event. can click to select the Production Event Code
record that most accurately represents the type
of event. After you select the appropriate
record and click OK, the full path to the
selected Production Event Code record is
displayed on the datasheet, including all
categories into which that Production Event
Code record is grouped.
For example, suppose you selected Equipment
Malfunction, which is grouped under
Operational Losses, as shown in the following
image:
In this case, the Production Event Code cell

on the datasheet would display the value
Operational Losses\Equipment Malfunction,
as shown in the following image:
When you save the Production Event record,

it will be linked automatically to the selected
Production Event Code record. After the two

records are linked, if you change the value in
the Code field in the Production Event Code
record, the value in the Production Event
Code field in the Production Event record will
be updated automatically to reflect the
change.
This field contains a list, which displays the
Record IDs of all Production Unit records.
When you save the Production Event record,
it will be linked automatically to the selected
Source
The production
Production Unit record. After the two records
Production Character unit in which the are linked, if you change the value in the
Unit
event occurred. Production Unit Name field in the Production
Unit record, the value in the Source
Production Unit field in the Production Event
record will be updated automatically to reflect
the change.
Along with the production event end date, the
start date determines whether or not this
production event will be available in the
Production Event list in the Losses section on
the Production Data Entry page.
Start Date
Date
If the Production Event record does not have a

start date, the production event will appear in
The date that the
the Production Event list for losses that are
event started.
associated with any day before the end date.
In the baseline database, this field stores time
using the Coordinated Universal Time (UTC)
format (i.e., the UTC check box is selected
when you view the field properties in the
This field contains the following buttons:
Work
History
Link
Character A reference to the

work that was
performed as a
result of the event.
Link Work History: Lets you select the

Work History records that contain
more information about work that was
performed as a result of the event.
When you save the Production Event
record, it will be linked automatically
to the selected Work History records.
Unlink Work History: Lets you unlink

Work History records that are already
linked to the Production Event record.
The User Name of

This field is populated automatically. If there
the Security User
have been no updates to the record, this field
Updated By Character who last updated
will be empty. You cannot modify the value in
the Production
this field.
Event record.
Updated
Date
Date
The date and time

the Production
Event record was
last updated.
This field is automatically populated. If there

have been no updates to the record, this field
will empty. You cannot modify the value in
this field.

Production Event Code records store details that represent a type of Production Event.
for the Production Event Code family and appear on the baseline Production Event Code
fields.
Field
Code
Color
Data
Type
Description
A short code that

Character represents the type of
event.
Behavior and Usage
This field is required. On the Production

Event datasheet, the Production Event
field contains a
button, which you
can click to select the Production Event
Code record that most accurately
represents the type of event.
On the datasheet, this field contains a
Character The color that is used to list, which displays all colors that you
represent the production
can assign to the impact code.

event code on the
Production Data
Summary graph.
In the baseline database, colors are not

assigned to the baseline Production
Event Code records. You will need to
assign the desired colors manually.
A description of the type

of event.
Production Event Template

A Production Event Template record stores general event information that can be used to
create more specific Production Event records. The following table provides an
alphabetical list and description of the fields that exist for the Production Event Template
family and appear on the baseline Production Event Template datasheet. The information
in the table reflects the baseline state and behavior of these fields.
Field
Abnormal
State
Causing
Asset
Comment
Data
Type
Description
Behavior and Usage
This value in Xi Reading records (that

are linked to the Xi Tag record identified
A name that represents
in the Xi Tag ID field) should trigger a
Character an abnormal state of
Production Event record to be created
operation.
automatically from this Production
button, which
you can click to select the Equipment
The piece of equipment
record that represents the piece of
that caused the events
equipment that caused the events that
Character that will be created
will be created automatically from this
automatically from this
template. When you save the Production
template.
Event Template record, it will be linked
automatically to the selected Equipment
record.
Text
Additional comments
about the events that

will be created
template.
Description Text
A detailed description
of the events that will
be created
template.
This field is populated automatically
with a value that appears in the
following format:
<Source Unit>~<Production Event
Code>~<Start Date>~<Headline>
...where:
Event
Template
ID
The ID of the event

Character
template.
<Source Unit> is the value in the

Source Unit field in this
record.
<Production Event Code> is the
value in the Production Event
Code field in this Production
<Start Date> is the value in the

Start Date field in this Production
<Headline> is the value in the

Headline field in this Production
This field does not appear on the

datasheet.
Headline
A short description of
the events that will be
Character
created automatically
from this template.
Normal
Character A name that represents This value in Xi Reading records (that
State
a normal state of
operation.
Costs that are

associated with the
events that will be
Other Event
Number
Costs
from this template and
are not recorded in the
selected Work History
record.
Production Character The type of production
Event Code
events that will be
from this template.
are linked to the Xi Tag record identified

in the Xi Tag ID field) should trigger a
Production Event record to be updated
automatically from this Production
The value is preceded by a currency

symbol, which is set by default to $ but
can be changed via the Currency dialog
box if desired.

button, which
you can click to select the Production
Event Code record that most accurately
represents the type of events that will be
created automatically from this template.
After you select the appropriate record
and click OK, the full path to the
selected the Production Event Code
record is displayed on the datasheet,
including all categories into which that
Production Event Code record is
grouped.
For example, suppose you selected
Equipment Malfunction, which is
grouped under Operational Losses, as
shown in the following image:
In this case, the Production Event Code

cell on the datasheet would display the
value Operational Losses\Equipment
Malfunction, as shown in the following
image:
When you save the Production Event
Template record, it will be linked

automatically to the selected Production
Event Code record. After the two records
are linked, if you change the value in the
Code field in the Production Event Code
record, the value in the Production Event
Code field in the Production Event
Template record will be updated
automatically to reflect the change.
This field contains a list, which displays
the Record IDs of all Production Unit
records. When you save the Production
The production unit in automatically to the selected Production
Source
which the events that Unit record. After the two records are
Production Character will be created
linked, if you change the value in the
Unit
automatically from this Production Unit Name field in the
template occurred.
Production Unit record, the value in the
Source Production Unit field in the
Production Event Template record will
be updated automatically to reflect the
change.
This field contains the following buttons:
Work
History
Link
Xi Tag ID
Link Work History: Lets you

select the Work History records
that contain more information
about work that is related to the
events that will be created
automatically from this template.
When you save the Production
Event Template record, it will be
linked automatically to the
selected Work History records.
Unlink Work History: Lets you

unlink Work History records that
are already linked to the
record.
A reference to the Work

History records that are
Character related to the
Production Event
Template record.
Character A reference to the Xi

button, which
Tag record representing This field contains a
the tag whose readings you can click to select the desired Xi Tag
will be used to create

Production Event
records automatically
from this Production
record. When you save the Production

automatically to the selected Xi Tag
record.
Production Loss
Production Loss records store information about the loss of production caused be an
event. The following table provides an alphabetical list and description of the fields that
exist for Production Loss family and appear on the Production Loss datasheet. The
information in the table reflects the baseline state and behavior of these fields.
Field
Data
Type
Comment Type
Impact
Code
Description
Behavior and Usage
Additional
comments
about the
production
loss.
This field contains a list that displays all Impact

Character The impact of Code records that are returned by the
ImpactCodeList query, which is stored in the
the
Catalog in the folder
production
\\Public\Meridium\Modules\PLA\Queries. Each
loss.
item in the list is displayed in the following format:
<Code> - <Description>
...where:
<Code> is the value in the Code field in the

Impact Code record.
<Description> is the value in the
Description field in the Impact Code record.
When you select a value in the list, while the Code

and Description are displayed on the datasheet, only
the Code is stored in the field.

This field displays the Select OEE Code window,
which contains a hierarchal tree of OEE
Codes. Each item in the tree represents an OEE
Code record that is returned by the
OEECodeListProdLoss query, which is stored in the
A value that Catalog in the folder
identifies a \\Public\Meridium\Modules\PLA\Queries.
reason for
Only enabled OEE Code records (i.e., OEE Code
equipment
OEE Code Character
records whose Is Inactive field contains the value
efficiency
that led to a False) can be selected from the list. Disabled OEE
Code records will be gray and cannot be selected.
production
loss.
When you select a value from the tree and click
OK, the value in the OEE Code field of the OEE
Code record is displayed in the OEE Code field of
the Production Loss record.
The
production
Production
Character event that
Event
caused the
loss.
This field contains a list that displays the Record

IDs of all Production Event records that are returned
by the EventList query, which is stored in the
Catalog in the folder
\\Public\Meridium\Modules\PLA\Queries. When
you save the Production Loss record, it will be
linked automatically to the selected Production
Event record. After the two records are linked, if
you change any part of the Production Event
record's Record ID, the value in the Production
Event field in the Production Loss record will be
updated automatically to reflect the change.
The amount
Production
Number of production You can define this field manually.
Loss
that was lost.
Production Plan
Production Plan records store information about how much product you plan to produce
within a certain time period. The following table provides an alphabetical list and
description of the fields that exist for the Production Plan family and appear on the
Production Plan datasheet. The information in the table reflects the baseline state and
Note: All fields on the Production Plan datasheet are disabled and populated
automatically based upon your selections in the Production Plan Builder. The Behavior
and Usage column, therefore, is not displayed in this table.
Field
Data
Type
Description
Data Entry
Frequency
How often you plan to

Character enter production data and
losses.
End Date
Date
The date and time on

which the plan ends.
Plan Basis
Character
The type of plan: Timebased or Quantity-based.
Plan ID
Character
A value that identifies the

production plan.
Production
Model
The order in which the

products will be produced
Character
(at the same time or one
after the other).
Start Date
Date
The date and time on

which the plan begins.
Production Profile
Production Profile records store information about a product and its corresponding
production unit. The following table provides an alphabetical list and description of the
fields that exist for the Production Profile family and appear on the Production Profile
fields.
Field
Description
Data
Type
Text
Description
Behavior and Usage
A detailed description
of the production
profile.
This value is preceded by a currency

Default
symbol, which is set by default to $ but
Margin
can be changed via the Currency dialog
box if desired.
On the datasheet, after you navigate
away from the Max Demonstrated Rate
text box, the value that you typed is
appended with the value <Product
UOM>/<Production Rate UOM>,
The highest number of
where:
products the
production unit
<Product UOM> is the value in
produced,
the Product UOM field.
Max
disregarding the
<Production Rate UOM> is the
Demonstrated Number
impact it may have
Rate
value in the Production Rate
had on the equipment
UOM field.
or locations involved
in the process or the
For example, if the Product UOM is
quality of the product.
Tons and the Production Rate UOM is
Hour, if you type 3,000 in the Max
Demonstrated Rate text box, the value
will be displayed as 3,000 Tons/Hour.
This field is disabled, and the value is
set by default based upon the values in
Max Sustained Number The number of
the following fields:
Capacity Rate
products that the
production unit can
produce consistently
Product UOM
without having any
Production Rate UOM
adverse effects on the
assets involved in the
Standard Batch Size
process or the quality
of the product.
Standard Batch Cycle Time
The profit that one
Number unit of the product
yields.
Specifically, the numeric part of the

value is calculated as:
Standard Batch Size / Standard
Batch Cycle Time

So, if the Standard Batch Size is 5,000
and the Standard Batch Cycle Time is 2
days, the numeric part of the Max
Sustained Capacity Rate would be
2,500 (5,000 / 2).
The numeric value is then appended
with the value <Product
UOM>/<Production Rate UOM>,
where:
<Product UOM> is the value in

the Product UOM field.
<Production Rate UOM> is the

value in the Production Rate
UOM field.
For example, consider the complete

example in the following image.
Product
The product
Character associated with the
profile.
Product UOM Character The unit that is

associated with the
product that is stored
in the Product field.
For example, if you
are producing steel,
the unit might be
This field contains a list of all values in

the Name field in all Product records.
When you save the Production Profile
record, it will be linked automatically
to the selected Product record. After the
two records are linked, if you change
the value in the Name field in the
Product record, the value in the Product
field in the Production Profile record
will be updated automatically top
reflect the change.
This field contains a list, which
displays the values that exist in the
Product UOM field in all existing
Production Profile records. You can
select a value from the list or type a
new value.
Tons.
This field contains a list with the
following values, which come from the
System Code Table with the ID
MI_PLA_RATE_UOM:
Production
Rate UOM
How often you

Character measure production
(e.g., Day).
Hour
Day
Week
Month
Quarter
Year
The default value is Day. This field is

required.
Standard
Batch Cycle
Time
Standard
Batch Size
Xi Tag ID
The number that you type will be

The amount of time it
appended automatically with the value
takes you to produce
in the Production Rate UOM field.
Character one batch of the
product that is stored
in the Product field.
The number that you type will be
appended automatically with the value
The amount of
in the Product UOM field.
Character product that you can
produce in one batch.
The tag whose
readings you want to
button, which
Character use to create
you can click to select the desired Xi
Production Data
Tag record.
records automatically.
Production Target
Production Target records store information about planned production values for a given
product within a given production plan. The following table provides an alphabetical list
and description of the fields that exist for the Production Target family and appear on the
Production Target datasheet. The information in the table reflects the baseline state and
Note: All fields on the Production Target datasheet are disabled and populated
automatically based upon your selections in the Production Plan Builder. The Behavior
and Usage column, therefore, is not displayed in this table.
Field
Data
Type
Description
End Time Date
The date and time on which production of the product ends.
Quantity Number
The amount of product that should be produced during the start and
end time.
Sequence Number
The order in which the product will be produced during the

production plan (represented by a number 1 through n).
Start
Time
The date and time on which production of the product begins.
Date
Production Unit
Production Unit records store basic information about a single production unit. The
following table provides an alphabetical list and description of the fields that exist for the
Production Unit family and appear on the Production Unit datasheet. The information in
the table reflects the baseline state and behavior of these fields.
Field
Production
Unit Name
Data
Type
Character
Production
Unit
Text
Description
Description
Behavior and Usage
The name of the

production unit.
production unit.

button, which
you can click to select the Functional
Location record that contains more
information about the production unit.
When you save the Production Unit record,
it will be linked automatically to the
selected Functional Location record.
Associated
Unit
A reference to a
separate record that
Character contains more
information about
the production unit.
Time Zone
This value is associated with dates in

The time zone that
Production Data records that were created
Character is associated with
automatically as part of the integration
the production unit.
with Process Data Integration.
System Code Tables Used by PLA

The following System Code Tables are used by PLA.
Table ID
MI_IMPACT_CODE_COLOR
Table Description Function

Impact Code
Color
Populates the list of values in the

Color list in Impact Code records.
MI_PLA_DATA_FREQ
Populates the Data Entry

PLA Data Entry
Frequency list in Production Plan
Frequency
records.
MI_PLA_PLAN_BASIS
PLA Plan Basis
MI_PLA_PRODUCTION_MODEL
PLA Production Populates the Production Model

Model
list in Production Plan records.
MI_PLA_RATE_UOM
Populates the Production Rate

PLA Production
UOM list in Production Profile
Rate UOM
records.
PEST
Populates the list of values in the

Production Event
Status list in Production Event
Status
records.
Populates the Plan Basis list in

Production Plan records.
Parameters for the Production Loss

Accounting URL
There is one root URL associated with Production Loss Accounting (PLA):
meridium://PLA. A link constructed from the path alone will open the PLA Start Page.
This URL accepts the parameters that are described in the following table. Click here for
examples of using these parameters to customize the PLA URL.
Parameter
Description
Name
Page
Accepted Value(s)
Products
Specifies the
page that you UnitProfiles
want to view.
EventCodes
Notes
Products: Displays the

Products page.
UnitProfiles: Displays the

Production Units and Profiles
page.
ImpactCodes
EventCodes: Displays the
Production Event Coding page.
ImpactCodes: Displays the

Impact Coding page.
Events: Displays the

Production Event Management
page.
Plans: Displays the Find

Production Unit window, where
you can select the Production Unit
record for which you want to
create a production plan. If
Page=Plans, you can also use the
EntyKey and FamilyKey
parameters to specify the
Production Unit record for which
you want to create a production
plan, which will bypass the Find
Production Unit window.
ProductionAnalysis
Entry: Displays the Find

Production Plan window, where
you can select the Production Plan
record that will be used to compile
the data that appears on the
Production Data Entry page. If
Page=Entry, you can also use the
EntyKey and FamilyKey
parameters to specify the
Production Plan record that you
want to see on the Production Data
Entry page, which will bypass the
Find Production Plan window.
Events
Plans
Entry
EntyKey
Specifies the
record that
you want to The Entity Key of
see on the
the desired record.
specified
page.
ProductionAnalysis: Displays
the Production Analysis page.
You can use the EntyKey parameter if

Page=Plans or Page=Entry. If you use
the EntyKey parameter, you must also
use the FamilyKey parameter.
FamilyKey
Specifies the
family of the
record that
The Family Key of
you want to
the desired family.
see on the
specified
page.
You can use the FamilyKey parameter

if Page=Plans or Page=Entry. If you
use the FamilyKey parameter, you
must also use the EntyKey parameter.
Examples of PLA URLs
meridium://PLA
Displays the PLA Start Page.
meridium://PLA?Page=Products
Displays the Products page.
meridium://PLA?Page=Plans
Displays the Find Production Unit window, where you can select the Production Unit
record for which you want to create or open a production plan.
meridium://PLA?Page=Plans&EntyKey=123456&FamilyKey=987654
Displays the Manage Production Plans page, displaying production plans for the
Production Unit record with the Entity Key 123456 in the family with the Family Key
987654.
meridium://PLA?Page=Entry
Displays the Find Production Plan window, where you can select the Production Plan
record that will be used to compile the data that appears on the Production Data Entry
page.
meridium://PLA?Page=Entry&EntyKey=123456&FamilyKey=987654
Displays the Production Data Entry page, where the data on the Production Data tab is
compiled using the values in the Production Plan record with the Entity Key 123456 in
the family with the Family Key 987654.
Impact Code
A short code that represents the impact of the production loss.
Overall Equipment Effectiveness Codes

(OEE)
A short code that categorizes losses according to equipment availability, performance,
and product quality. The losses associated with these categories are used to calculate an
overall OEE percentage, which indicates the effectiveness of the production process.
Production Event
Any event that results in reduced production output.

A short code that represents the type of event that caused production loss.
Production Plan
A plan that defines the time period for which you want to track production and the
amount of product that you plan to produce during that time period.
Overview of Generation Management

Many North American utility companies report generation and loss event data to the
North American Electric Reliability Corporation (NERC) and the Energy Information
Administration (EIA) using applications such as the Generation Availability Database
System (GADS). Meridium APMs Generation Management (GM) module uses the
Meridium APM's core functionality to help you record generation and loss data for each
unit in your company. Using GM, you can easily enter incident and fuel consumption
data into records. You can then generate reports that follow the GADS data-reporting
requirements and send the reports to NERC and the EIA.
In addition, Meridium APM Generation Management allows you to view general
information, such as the unit type and megawatt rating, for other utility companies that
are reporting information to NERC and the EIA. Therefore, not only can you record and
analyze detailed data about your company, but you can also compare your data to that of
other utility companies.
Unlike other GADS-reporting products, Meridium APM Generation Management lets
you go beyond simple data collection and reporting to analyze your power generation
data further using other Meridium APM features. Using Metrics, for example, you can
generate and analyze Metric Views that are specific to your company's units. Metric
Views allow you to view information such as the availability factor per unit over time or
the number of incidents per cause code and location. These types of Metric Views
provide a fast and easy way to evaluate detailed data.
If you see that your data indicates a need for action, you might also use Meridium APM
to create work orders for individual units. If you want to analyze the reliability of your
units, you can use Meridium APM Reliability Analytics to create system models
reflecting the components in your power system. Or, you can use Root Cause Analysis
for Meridium APM to conduct a Root Cause Analysis on a unit's failure to produce the
desired output. D
System Requirements for GM

The Generation Management license is required to take advantage of Generation
Management (GM) functionality. In addition, your system must contain the basic
Meridium APM system architecture.
Hint: Details on the system requirements for the basic Meridium APM system
architecture and activating licenses can be found in the Installation, Upgrade, and System
Administration section of the Meridium APM Help system.
After you have installed and configured the basic system architecture, you will need to
perform some configuration tasks specifically for the GM module.
GM Data Model
Like all Meridium APM modules, the Meridium APM Generation Management module
consists of entity families, relationship families, and business rules. When attempting to
understand and make use of GM functionality, it can be helpful to visualize the GM 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 GM, it
may be useful to remember that GM simply allows you to create, view, and manage
records.
The following diagram shows the GM entity families and the relationships that exist
between them. Note that the following image does not include entity and relationship
families used in GMs role-based security feature. To view the GM entity families and
relationships used in role-based security, see the GM role-based security data model.
This figure shows only one box for the Generation Nameplate family. The Generation
Nameplate family contains the following subfamilies, each of which is related to the
Generation Unit family through the Has Nameplate Data relationship:
Generation Nameplate Combined Cycle

Generation Nameplate Diesel
Generation Nameplate Fluidized Bed
Generation Nameplate Fossil Steam
Generation Nameplate Gas Turbine
Generation Nameplate Hydro
Generation Nameplate Miscellaneous
Generation Nameplate Nuclear
GM Workflow
The following workflow describes the basic tasks that you will perform in GM:
1. Perform administrative tasks before users begin using GM. This includes:
o Configuring GM role-based security. In general, this is a one-time
configuration task that you will need to perform before users can begin
using Generation Management. If you have NOT configured role-based
security for a given Security User, that user will not be able to use GM.
1.
o
Creating Generation Company, Generation Plant, and Generation Unit

records to represent the hierarchy that you want use in GM. Typically, you
will need to complete these tasks when you initially set up your GM
system. You will need to repeat these steps whenever you want to record
data about any company, plant, or unit that has NOT yet been identified
within your system.
2. Record event data as incidents occur. To do so, you will create Primary Capacity
Incident and Contributing Capacity Incident records to represent events in which
units suffer a loss of power generation capacity. You will need to repeat this step
each time an incident occurs.
3. Report data to the EIA, to NERC, or to both. You should run reports after the end
of each reporting period. The reporting periods and the schedule on which you
should report data are defined by the organization to which you are reporting the
data.

Deploying and configuring GM 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 GM on top of the basic
Meridium APM system architecture.
are marked as Required if you must perform the step to take advantage of GM
functionality.
Step Task
Assign Security Users to GM

Security Groups in Configuration Required
Manager.
None
Configure role-based security in

Required
the APM Framework.
None
Create Generation Company,

Generation Plant, and Generation
Unit records to represent the
Required
hierarchy that you want use in
GM.
Generation Company,
Generation Plant, and
Generation Unit records must
exist before users can start
recording incident data.
Upgrade Workflow
You can upgrade to 3.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 GM from V3.5.1 to

V3.6.0.0.0
GM 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 GM from V3.5.0 SP1 LP to

V3.6.0.0.0
GM 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
required.

V3.6.0.0.0
required.
GM Security Groups
The following Security Groups are provided as part of the baseline Meridium APM
database:
MI Generation Management
MI Generation Management Administrator
MI Generation Management Analyst
MI Generation Management Forecast
MI Generation Management Nameplate
MI Generation Management Security
MI Generation Management Trading
Note: Role-based security can be configured only for baseline GM Security Groups. You
must use the baseline GM Security Groups if you plan to implement role-based security.
These Security Groups are intended to support the users who will access the GM system.
The baseline privileges for these Security Groups are summarized in the following table.
Family
MI
MI
MI
MI
MI
MI
Generation Generation Generation Generation Generation
Generation
Management Management Management Management Management
Management
Administrator Analyst
Forecast
Nameplate Security
View
Update
APM Event View
Insert
View
Update,
Insert
None
None
None
None
None
None
None
None
None
View
None
None
None
View
None
None
None
Delete
View
View
Update1,2
Capacity
History
View
Update1
Insert
Insert
Delete
View
View
Update3,4
Capacity
Incident
View
Update3
Insert
Insert
Delete
View
Update
Commodity
View
Pricing
Insert
Delete
View
Generation
Company
View
Update
Insert
Delete
Update
Generation
Forecast
View
None
None
Insert
None
None
None
None
Delete
View
View
Update
Generation
View
Fuel Report
Update
Insert
None
Insert
Delete
View
Update
Generation
Nameplate
View
None
None
None
Insert
None
Delete
View
Generation
NERC
Report
Update
None
Insert
View
None
None
None
View
None
None
None
View
None
None
None
View
None
None
None
Delete
View
Update
EIA Federal
View
Region
Insert
Delete
View
Update
GADS Cause
View
Codes
Insert
Delete
View
Generation
Plant
View
Update
Insert
Delete
Update
Generation
Role
View
None
None
None
None
Delete
Update
Update
Generation
Role
View
Assignment
Insert
None
Generation
Role
Definition
None
View
None
None
None
Delete
Generation
Role Field
View
Configuration
Insert
Insert
Delete
Update
None
None
None
Insert
Delete
Update
None
None
None
Insert
Delete
View
Update
Plant
Reference
View
Insert
None
None
None
None
None
None
None
None
None
None
None
Delete
View
Update
Utilities
Reference
View
Insert
Delete
View
Unit
Reference
View
None
Update
Insert
Delete
GM Macro
None
Update
View
Update
None
None
None
View
None
None
None
Update
Generation
Unit
View
Insert
Delete
View
Generation
Unit Loading View
Profile
Update
None
None
None
Insert
None
Delete
View
Generation
Unit Starting View
Profile
Update
None
None
None
Insert
None
Delete
Update
Daylight
Saving Time View
Reference
Insert
None
None
None
None
View
None
None
None
None
None
None
None
Delete
View
Update
Generation
Pool
View
Insert
Delete
Update
Heating
View
Value Ranges
Insert
Delete
View
Update
Accumulates
Capacity
View
Incident
Associated
with APM
Event
View
Assigned To
View
Plants-Units
Has Capacity
View
History
Update
Insert
Insert
None
None
None
None
None
None
Delete
Delete
View
View
Update
Update
Insert
Insert
Delete
Update
Delete
Insert
Update
None
Delete
View
View
Update
Update
Insert
Insert
Delete
View
Delete
None
None
Insert
Delete
None
None
None
None
None
None
None
None
View
Update
Has Fuel
Report
View
Update
Insert
Insert
Delete
View
Has
Generation
Forecast
Update
View
None
None
Insert
Delete
Update
Has GM Role
View
Assignment
Insert
Delete
Update
None
None
None
Insert
Delete
Update
Has GM
Roles
View
Has Incident View
Insert
Update
None
Delete
View
View
Update
Update
Insert
Insert
Delete
Delete
None
None
Insert
Delete
None
None
None
View
Update
Has Loading
View
Profile
None
None
None
Insert
None
Delete
Update
Has
Nameplate
Data
View
None
None
None
Insert
None
Delete
View
Update
Has Plant
View
Insert
View
None
None
None
None
None
None
None
Delete
Has
Reference
Documents
None
None
Update
Has Role
View
Assignment
Insert
Update
None
None
None
Delete
Insert
Delete
Update
Has Starting
View
Profile
None
None
None
Insert
Delete
None
View
Update
Has Unit
View
Insert
View
None
None
None
None
None
None
None
Delete
View
Update
Has Utility
Reference
None
Insert
Delete
Update
Has Role
Definition
View
None
None
None
None
Insert
Delete
1.
Only members of this Security Group can change the Reporting Status cell on the
Capacity History datasheet to Unit Level Approval.
2.
Only members of this Security Group can change the Reporting Status cell on the
Capacity History datasheet to Corporate Approval.
3.
Only members of this Security Group can change the Incident Reporting Status cell
on the Primary Capacity Incident datasheet or the Contributing Capacity Incident
datasheet to Unit Level Approval.
4.
Only members of this Security Group can change the Incident Reporting Status cell
on the Primary Capacity Incident datasheet or the Contributing Capacity Incident
datasheet to Corporate Approval.
About Role-Based Security

A role represents a users function within an organization. Role-based security is intended
to control the privileges that represent a Meridium APM Security User's function, or role,
within the Generation Management workflow.
Role-based security consists of the following types of privileges, which work together to
determine what a Security User can and cannot do within GM:
1. Family-Level Privileges: Controls a user's ability to interact with records in a
given family.
2. Field-Level Privileges: Controls a user's ability to interact with fields in records
belonging to the families that they have permission to access.
3. Plant-Level and Unit-Level Privileges: Controls a user's ability to interact with
records that are linked to specific Generation Plant and Generation Unit records.
In other words, the combination of family-level, field-level, plant-level, and unit-level
privileges that are associated with a Security User defines that users Generation
Management role.
The role-based security model works together with the standard family-level security
model that you can configure in the Configuration Manager. Role-based security provides
additional levels of security that are not available through the standard Meridium APM
security model. With standard family-level privileges, you can control a Security User's
ability to manage records in a certain family. Role-based security extends to the field
level by allowing you to control a users ability to manage fields in the families to which
that Security User has already been granted family-level privileges. Plant- and unit-level
privileges allow you to control a user's ability to access specific records.
Role-based security is not fully implemented for GM in the baseline product. The
Meridium APM Framework provides some of the components that you must combine to
create a certain role. As part of your administrative configuration of GM, you should
configure role-based security. In order for GM users access to GM records, you will need
to configure their family-level, field-level, and unit-level or plant-level privileges. If you
do not configure role-based security, users will not be able to use GM.
After you have implemented role-based security, if desired, you can modify individual
field-level privileges, plant-level privileges, and unit-level privileges to customize your
implementation.
GM Role-Based Security Model

The following diagram shows the GM entity families that are involved in role-based
security and the relationships that exist between them. To view a diagram of other
families involved in the GM data model, see the GM Data Model.
Note: The Generation Role Field Configuration family does not participate in any GM
relationship definitions.
Baseline Generation Management Roles

The following table lists the baseline Generation Role records, the Security Groups to
which they are linked, and the families to which each Generation Role records has Insert
and Update privileges. Additionally, the following table indicates whether unit-level or
plant-level privileges are initially required. These are the baseline privileges that the
Meridium APM Framework delivers that override any less restrictive family-level
privileges that are assigned to a user via the Configuration Manager. You can either
configure role-based security to use these baseline privileges or customize them to work
specifically for your company.
Generation Security
Role
Group
Generation
Data Entry
Unit Level
Approver
MI
Generation
Management
Analyst
MI
Generation
Management
Analyst
Insert?
Primary
Capacity
Incident
Contributing
Capacity
Incident
Contributing
Capacity
Generation
Incident
Unit
Capacity
History
Capacity
History
Primary
Capacity
Incident
Primary
Capacity
Incident
MI
Generation
Management
Analyst
Fuel
MI
Administrator Generation
Management
Unit/Plant?
Fuel Data
Entry
Update?
Contributing
Capacity
Incident
Capacity
History
Primary
Capacity
Incident
Contributing
Generation
Capacity
Unit
Incident
Capacity
History
Generation
Fuel Monthly
Report
Generation
Fuel Monthly
Report
Generation
Fuel Annual
Report
Generation
Fuel Annual
Report
Generation
Fuel Monthly
Report
Generation
Fuel Monthly
Report
Generation
Plant
Generation
Unit/
Generation
Analyst
Generation
Fuel Annual
Report
Generation
Fuel Annual
Report
Capacity
History
Capacity
History
Generation
Company
Generation
Company
Generation
Forecast1
Generation
Forecast1
Generation
Plant
Generation
Plant
Generation
Unit
Generation
Unit
Primary
Capacity
Incident
Primary
Capacity
Incident
MI
Generation
Generation
Management
Management
Administrator
Administrator
Contributing
Capacity
Incident
Capacity
History
Generation
Fuel Annual
Report
Generation
Fuel Monthly
Report
NERC
Report
Nameplate
MI
Administrator Generation
Management
Generation
Nameplate
Generation
Contributing
Unit/
Capacity
Generation
Incident
Plant
Capacity
History
Generation
Fuel Annual
Report
Generation
Fuel Monthly
Report
Plant
NERC Report
Generation
Nameplate
Generation
Unit
Nameplate
MI
Start-Load
Generation
Profile
Management
Administrator
Nameplate
Generation
Unit Loading
Profile
Generation
Unit Starting
Profile
Generation
Unit
Generation
Unit Loading
Profile
Generation
Unit Starting
Profile
MI
Forecast
Generation
Capacity
Management
Administrator
Forecast
Generation
Forecast
Generation
Forecast
Generation
Unit
MI
Forecast Fuel Generation

Administrator Management
Forecast
Generation
Forecast
Generation
Forecast
Generation
Unit
1. Although Meridium APM provides Generation Role Field Configuration records that
allow the Generation Management Administrator role to insert and update records in the
Generation Forecast family, the MI Generation Management Administrator Security
Group does not have Insert or Update privileges to the Generation Forecast family. This
means that in the baseline GM database, members of the MI Generation Management
Administrator Security Group cannot create or modify Generation Forecast records. To
allow members of the MI Generation Management Administrator Security Group to
create and modify Generation Forecast records, via the Configuration Manager, grant the
Security Group Insert and Update privileges to the Generation Forecast family.
Configuring Family-Level Privileges

Family-level privileges can be configured via the Configuration Manager application and
control each Security User's ability to create, modify, view, delete, and link records that
belong to particular entity families. GM provides a set of baseline Security Groups that
can be used to manage family-level privileges. Each Generation Management Security
Group has a predefined set of baseline family-level privileges associated with it.
Based upon the Meridium APM Framework's standard security model, any Security User
who is assigned to one of the baseline Generation Management Security Groups will
inherit the family-level privileges associated with that Security Group. Those family-level
privileges will then control that Security User's ability to access and modify records in
those families.
To configure family-level privileges for role-based security, you will need to:
Assign the desired Security Users to the appropriate GM Security Groups.

Security Group assignments must be configured in the Configuration Manager
application.
IMPORTANT: Role-based security can be configured only for the baseline GM Security
Groups. Any Security User who should be allowed to access GM records must be
assigned to one of these groups. To ensure that role-based security works properly in GM,
we recommend that you NOT modify the baseline family-level privileges that are
associated with these Security Groups.
Configuring Field-Level Privileges

In addition to security that is established via family-level privileges in the Configuration
Manager, Generation Management also uses role-based security to provide security at the
field level. You can configure field-level privileges using the following records:
Generation Role records

Generation Role Assignment records
Generation Role Field Configuration records
Field-level privileges that are configured for role-based security override any less
restrictive family-level privileges that are assigned to a user. Regardless of the familylevel privileges that are associated with the baseline GM Security Groups in the
Configuration Manager, some actions may be restricted for certain GM users based on
the field-level privileges assigned to that Security User.
For example, the baseline MI Generation Management Analyst Security Group has Insert
privileges on the Primary Capacity Incident family. If a Security User is a member of this
Security Group but is also assigned the Fuel Data Entry role, however, that user will NOT
be able to create a Primary Capacity Incident record because the field-level privileges
that are assigned to the Fuel Data Entry role associated with that role restrict access to the
fields that are required to create Primary Capacity Incident records. Click here to view
the privileges associated with the Generation Role records that GM delivers.
If you wanted the Security User who is assigned the Fuel Data Entry role to be able to
create Primary Capacity Incident records, you could create Generation Role Field
Configuration records associated with the Fuel Data Entry role to enable field-level
privileges on the Primary Capacity Incident family.
To configure field-level privileges for role-based security, you will need to:
1. Create Generation Role records to associate Security Users with Security Groups.
Various baseline Generation Role records are provided and are linked
automatically to the baseline GM Security Groups.
Note: If you are using the baseline Generation Role records that Meridium APM
provides, you can skip this step.
2. Create Generation Role Assignment records to associate Security Users with
Generation Role records. Associating a Security User with a Generation Role
record gives that Security User the specific field-level privileges that are
associated with that Generation Role record via Generation Field Configuration
records.
3. Create Generation Role Field Configuration records. A Generation Role Field
Configuration record grants members of a specific Generation Role insert and/or
update privileges on specific fields in specific families. Note that a set of baseline
Generation Field Configuration records are provided for each Generation Role
record.
Note: If you are using the baseline Generation Role Field Configuration records that
Meridium APM provides, you can skip this step.
Configuring Plant-Level and Unit-Level

Privileges
In addition to security that is established via family-level and field-level privileges,
Generation Management also uses plant-based and unit-based security to provide security
at the plant level and the unit level. Generation Management enforces plant-level and
unit-level privileges via Generation Role Definition records.
By default, the family-level and field-level privileges that you configure for all the
families that serve as successors in the baseline relationship definitions involving the
Generation Unit and Generation Plant families will be enabled only after a link has been
created between the appropriate Generation Role Assignment record and the Generation
Unit or Generation Plant record for which the user will be granted privileges.
Note: If desired, you can choose not to use the plant-level or unit-level security, which
will grant users access to all appropriate successors of ALL Generation Plant and
Generation Unit records.
privileges to the Primary Capacity Incident family. This means that a Security User who
is assigned the Generation Data Entry role can create a new Primary Capacity Incident
record. The creation will not be allowed, however, until the Generation Role Assignment
record associated with that Security User has been linked to the Generation Unit record of
the Primary Capacity Incident record that the user wants to create.
To configure plant-level and unit-level privileges, you will need to:
1. Create Generation Role Definition records to establish whether or not a link is
required between a Generation Role Assignment record and a Generation Plant or
Generation Unit record. The Meridium APM Framework delivers a set of
Generation Role Definition records that are configured for use with the baseline
Generation Role records.
Note: You need to create Generation Role Definition records only if you created a new
Generation Role record. If you are using the baseline Generation Role records that
Meridium APM provides, you can skip this step.
2. Link Generation Role Assignment records to the desired Generation Unit records.
3. Link Generation Role Assignment records to the desired Generation Plant records.
Note: Plant- and unit-level privileges can be configured only after the necessary
Generation Plant and Generation Unit records exist.
Overview of Configuring Role-Based

Security
Generation Management contains a set of baseline Generation Role records, Generation

Role Field Configuration records, and Generation Role Definition records. To implement
role-based security for GM users, you need to:
Follow the baseline workflow.
-OR
Customize the existing baseline role-based security to specify your own fieldlevel privileges.
Note: Only Security Users who are assigned to the MI Generation Management Security
Administrator Security Group can configure role-based security.
Creating a Generation Role Record

To create a Generation Role record:
1. On the Meridium APM Framework toolbar, click the New button.
The Select Family dialog box appears.
2. In the list, select Generation Role.
3. Click OK.
A new Generation Role record appears in the Record Manager.
4. In the Role ID cell, type a unique name for the new role. This field is required.
5. In the Role Description cell, type any additional information about the new role.
6. On the Common Tasks menu, click the Save link.

The Generation Role record is created and saved. Note that the new Generation Role
record is not linked to any other families by default.
Creating a Generation Role Field

Configuration Record
Via Generation Role Field Configuration records, the following field-level privileges can
be granted:
Insert
Update
Insert and Update
If a Generation Role Field Configuration record does not exist for a field, Security Users
assigned to the associated Generation Role will be able to view the field only, provided
that they have the necessary family-level privileges. If users attempt to add a value to a
field or modify an existing value, an error message will be displayed, indicating that rolebased security privileges have not been configured for the field.
By default, Generation Role Field Configuration records are delivered with Generation
Management, and they are enabled automatically for both insert and update privileges.
The following instructions provide details on creating new field-level privileges on a
single field for a single role. For every new role created, you will need to repeat this
procedure for every field to which you want to create field-level privileges. Additionally,
you can update the field-level privileges at any time.
To create a Generation Role Field Configuration record:
2. In the list, select Generation Role Field Configuration.
3. Click OK.
A new Generation Role Field Configuration record appears in the Record Manager.
4. In the Role ID list, select the Generation Role record for which you are creating
this Generation Role Field Configuration record. This field is required.
5. In the Family list, select the GM family for which you are creating this
Generation Role Field Configuration record. This field is required.
6. In the Field list, select the field for which you are creating the Generation Role
Field Configuration record. This list contains all the fields that exist in the family
that you selected in the Family list. This field is required.
7. Clear the Insert Enabled check box if you do NOT want to allow insert privileges
on the selected field for the selected role. Note that this check box is selected by
default, meaning that by default, insert privileges are enable.
8. Clear the Update Enabled check box if you do NOT want to allow update
privileges on the selected field for the selected role. Note that this check box is
selected by default, meaning that by default, update privileges are enabled.
The Generation Role Field Configuration record is created and saved to the database.
Creating a Generation Role Definition

Record
To create a Generation Role Definition record:

2. In the list, select Generation Role Definition.
3. Click OK.
A new Generation Role Definition record appears in the Record Manager.
4. In the Role ID cell, type the name of the Role ID for the Generation Role record
for which you are creating this Generation Role Definition record.
5. In the Role Assignment Family ID cell, type the family ID for a Generation Plant
or a Generation Unit family for which you are creating this Generation Role
Definition record. If you are creating the Generation Role Definition record to
indicate access to successors of a Generation Plant family, type MI_GM_PLANT.
If you are creating the Generation Role Definition record to indicate access to
successors of a Generation Unit record, type MI_GM_UNIT0.
6. In the Entity Assignment Required check box, select the check box if you want to
require a link between the Generation Role Assignment record and the family that
is specified in the Role Assignment Family ID cell. Note that if you do not select
the Entity Assignment Required check box, the link between a Generation Role
Assignment record and a Generation Plant or Generation Unit record is not
required. Users associated with the GM role in the Role ID cell will have their
field-level privileges for the appropriate successors of ALL the Generation Plant
or Generation Unit family (indicated in the Role Assignment Family ID cell),
rather than only Generation Plant or Generation Unit records that are linked to the
appropriate Generation Role Assignment record.
The Generation Role Definition record is created and saved to the database.
Creating a Generation Role Assignment

Record
You will need to create Generation Role Assignment records to associate users with
specific Generation Role records. Any user who is associated with a given Generation
Role record will be given the field-level privileges defined in the Generation Role Field
Configuration records that exist for that Generation Role record.
Note: Users can be assigned a given role only once. Therefore, you cannot create multiple
Generation Role Assignment records with the same User ID and Role ID values as
existing Generation Role Assignment records.
To create a Generation Role Assignment record:
2. In the list, select Generation Role Assignment.
3. Click OK.
A new Generation Role Assignment record appears in the Record Manager.
4. In the User ID list, select the user ID of the Security User that you want to
assigned to a GM role. The list contains the user IDs of all active Security Users
that are assigned to any baseline GM Security Group. This field is required.
5. In the Role ID list, select the ID of the Generation Role record that you want to
associate with this user. The Role ID list displays only the IDs of the Generation
Role record(s) that are linked to the baseline GM Security Group(s) of which the
selected user is a member. The user will be given the field-level privileges that are
defined in the Generation Role Field Configuration records that exist for the
selected Generation Role record. This field is required.
6. Accept the default selections in the User Enabled and Role Enabled check boxes,
which indicate that role-based security is enabled for this user and role. If desired,
you can clear the User Enabled and Role Enabled check boxes to disable rolebased security.
The Generation Role Assignment record is created and saved. A link is created between
the new Generation Role Assignment record, the Security User record you selected in the
User ID field, and the Generation Role record you selected in the Role ID field.
8. If you created the Generation Role Assignment record for a Generation Role that
requires Generation Role Assignment records to be linked to Generation Unit or
Generation Plant records, then link the Generation Role Assignment record to the
Generation Unit record or link the Generation Role Assignment record to the
Generation Plant record.
Linking Generation Role Assignment

Records to Generation Plant Records
When you create a Generation Role Assignment record, the Meridium APM system
creates a link between the selected Security User and the selected Generation Role
record. If you created the Generation Role Assignment record for one of the following
GM roles, you must manually link it to a Generation Plant record:
Fuel Data Entry

Fuel Administrator
Generation Management Administrator
Linking the Generation Role Assignment record to a Generation Plant record will apply
the field-level privileges associated with the selected role to the Generation Fuel Report
records associated with the related Generation Plant record. Users will NOT be granted
field-level privileges to Generation Fuel Report records associated with any other
Generation Plant records.
Note that if a link does not exist between the Generation Role Assignment record and a
Generation Plant record, an error will appear when the Generation Fuel Report record is
saved, indicating the user is not related to the Generation Plant record.
To link Generation Role Assignments records to Generation Plant records:
1. On the Meridium APM Framework toolbar, click the Search button.
The Search page appears.
2. In the Search In list, select Generation Plant, and then click Find Now.
3. From the search results, click the Record ID hyperlink of the desired record.
The record appears in the Record Manager, displaying in the Record Explorer pane the
families whose members can be linked to the root record. Find the Generation Role
Assignment family and right-click the family name.
4. In the hierarchy, locate and right-click the Generation Role Assignment family.
A submenu appears.
4. Click the Find an existing Generation Role Assignment to link to <the root
record> link.
The Find an existing Generation Role Assignment to link to <the root record> window
appears, displaying Generation Role Assignment in the Search In field.
6. Click the Find Now button.
Your search results appear in a list below the search form.
7. Highlight the desired record, and click the Link to Selected Record button.
The search closes, revealing the Record Manager. The Generation Role Assignment
record you selected from the search results has been linked to the Generation Plant
record.
Linking Generation Role Assignment

Records to Generation Unit Records
When you create a Generation Role Assignment record, Meridium APM creates a link
between the selected Security User and the selected Generation Role record. If you
created the Generation Role Assignment record for one of the following GM roles, you
must manually link it to a Generation Unit record:
Generation Data Entry

Unit Level Approver
Fuel Administrator
Generation Management Administrator
Nameplate Administrator
Start-Load Profile Administrator
Forecast Capacity Administrator
Forecast Fuel Administrator
Linking the Generation Role Assignment record to a Generation Unit record will apply
the field-level privileges associated with the selected role to records associated with the
related Generation Unit record. Users will NOT be granted field-level privileges to
records associated with any other Generation Unit records.
Note that if a link does not exist between the Generation Role Assignment record and a
Generation Unit record, an error will appear when the record is saved, indicating the user
is not related to the associated Generation Unit record.
To link Generation Role Assignments records to Generation Unit records:
2. In the Search In list, select Generation Unit, and then click Find Now.
3. From the search results, click the Record ID hyperlink of the desired record.
The record appears in the Record Manager, displaying in the Record Explorer pane the
families whose members can be linked to the root record.
4. In the hierarchy, locate and right-click the Generation Role Assignment.

A submenu appears.
5. Click the Find an existing Generation Role Assignment to link to <the root
record> link.
The Find an existing Generation Role Assignment to link to <the root record> window
appears, displaying Generation Role Assignment in the Search In field.
Your search results appear in a list below the search form.
7. Highlight the desired record, and click the Link to Selected Record button.
The search closes, revealing the Record Manager. The Generation Role Assignment
record you selected from the search results has been linked to the Generation Unit record.
Example of How to Configure Baseline

Role-Based Security
Suppose Bob Smith was recently hired to your company. He will not have access to
Generation Management until role-based security has been configured for his Security
User, BSmith.
To configure baseline role-based security for BSmith, you will need to:
1. Assign BSmith to the MI Generation Management Forecast Security Group since
Bob Smith will be recording fuel data. Through membership to this Security
Group, BSmith will have View, Insert, Update, and Delete privileges on the
Generation Forecast family.
2. Create a Generation Role Assignment record that associates BSmith with the
Forecast Fuel Administrator role to grant him field-level privileges that are
associated with the Forecast Fuel Administrator via the Generation Role Field
Configuration records that the Meridium APM Framework provides.
3. Link this Generation Role Assignment record to the Generation Unit record(s)
that are the predecessors of the Generation Forecast records that you want BSmith
to manage.
After you have completed these steps, when BSmith logs in to Meridium APM, he will be
able to create new Generation Forecast records and update existing Generation Forecast
records.
Allowing Users Access to All Generation

Plant and Generation Unit Records
When the Entity Assignment Required field is set to True in a Generation Role Definition
record that is associated with a Generation Management role, a link is required between a
Generation Role Assignment record and a Generation Plant or Generation Unit record.
This link between a Generation Role Assignment record and a Generation Plant or
Generation Unit record limits family-level and field-level privileges to the successor
families of the linked Generation Plant or Generation Unit record.
privileges in the Primary Capacity Incident family. A Security User who is assigned the
Generation Data Entry role can create a new Primary Capacity Incident record but not
until the Generation Role Assignment record associated with that Security User has been
linked to the Generation Unit record of the Primary Capacity Incident record that the user
wants to create.
If desired, you can configure role-based security so that Security Users associated with
the desired Generation Management roles are NOT limited to the successor families of
Generation Plant or Generation Unit records that are linked to a Generation Role
Assignment record. Users will then have their specific family-level and field-level
privileges to all successor families for ALL Generation Plant or Generation Unit records.
To allow users access to all Generation Plant or Generation Unit records:
2. In the Search In list, select Generation Role Definition.

A list of existing Generation Role Definition records will appear in the search results.
4. Click the Record ID hyperlink of the desired Generation Role Definition record
for which you want to allow users associated with that Generation Management
role to have access to all successor families of either a Generation Plant or
Generation Unit record.
The Generation Role Definition record appears.
5. On the Generation Role Definition datasheet, on the Role Entity Assignment Info
tab, clear the Entity Assignment Required check box.
The modified Generation Role Definition record is saved.
Omitting Role-Based Security

After you assign a user to a Generation Role via a Generation Role Assignment record,
you might later decide that you want to omit the existing privileges. If so, on a
Generation Role Assignment record, you can:
Clear the Role Enable check box to disable all field-level privileges associated
with the Generation Role record identified by the value in the Role ID field.
Field-level privileges will be omitted for ALL Security Users associated with that
Generation Role record.
Clear the User Enable check box to disable all field-level privileges associated
with any Generation Role records to the Security User who is identified by the
value in the User ID field.
About Generation Company, Plant, and

Unit Records
Before you can begin creating Primary Capacity Incident records, Contributing Capacity
Incident records, or Capacity History records, the following records must exist in your
database:
Generation Company: Represents the highest level of organization within your

business: the company under which plants and units operate. In general, a
Generation Company record represents a company that owns the plants and units
for which generation data and fuel consumption data will be collected.
Generation Plant: Represents a plant in which generation units reside. Generation
Plant records can store information about the plant itself and the company that
owns the plant. In addition, Generation Plant records determine:
Whether or not Primary Capacity Incident and Contributing Capacity

Incident records associated with those Generation Plant records will
account for Daylight Saving Time.
The date and time format that will be used in date fields in Primary
Capacity Incident records that are associated with the Generation Plant
record.
Generation Unit: Represents a unit that generates power. A Generation Unit record
can store information about a unit's power-generation capabilities and the fuel that
the unit consumes. In addition, Generation Unit records determine how incident
cost will be calculated in Primary Capacity Incident records that are linked to the
Workflow for Creating Company, Plant,

and Unit Records
Together, Generation Company, Generation Plant, and Generation Unit records create a
hierarchy that serves as the backbone for power-generation data collection in Meridium
APM.
Generation Company records exist at the root level of this hierarchy and should
be created first.
Generation Plant records can then be created and linked to existing Generation
Company records.
Note: A Generation Plant record can be linked to only ONE Generation Company record,
but a Generation Company record can be linked to multiple Generation Plant records.
Generation Unit records can then be created and linked to Generation Plant
records.
Note: A Generation Unit record can be linked to only ONE Generation Plant record, but a
Generation Plant record can be linked to multiple Generation Unit records.
After Generation Unit records have been created, incident data can be recorded in
Primary Capacity Incident records that you create and link to those Generation Unit
records. Therefore, you must create this record hierarchy before you can begin recording
incident data. We recommend that you create records in the order listed above.
In most cases, you will create these records when you first set up your GM system. You
may also need to create additional records on a periodic basis over the life of your system
(e.g., if you add a new unit).
About Generation Company Records

Generation Company records represent the highest level of organization within your
business and represent the root level of the Generation Management business hierarchy.
Before you can begin creating Generation Company and Generation Unit records, you
must first create Generation Plant records. You can create Generation Company records
in two ways:
Using the Record Manager. This represents the primary, recommended workflow
for creating Generation Company records. Throughout this documentation, we
assume that you have created your Generation Company records using this
method.
Using the Create Company Query. This option exists as an alternative to creating
Generation Company records in the Record Manager but is not recommended.
Creating Generation Company Records

These instructions provide details on creating a new Generation Company record using
the baseline Company datasheet.
To create a Generation Company record:
2. In the list, select Generation Company.
A new Generation Company record appears in the Record Manager.
3. In the Company ID cell, type a short name or acronym that identifies the
company.
4. In the Company Name cell, type the company's full name.
5. In the State list, select the state where the company is based.
6. Complete the remaining fields as desired.
The Generation Company record is created and saved to the database.
Using the Create Company Query

The Create Company query is provided in the baseline Meridium APM database and is
stored in the Catalog folder \\Public\Meridium\Modules\Generation
Management\Configuration. It queries the Utilities Reference family and is provided as a
tool that can assist in the creation of Generation Company records by populating fields in
new records automatically.
Note: Utilities Reference records are delivered in the baseline Meridium APM database
and contain information about companies. Because the data that is stored in the baseline
Utilities Reference records may not be current, using the Create Company query is not
presented in this documentation as the primary method for creating Generation Company
records. Instead, the recommended workflow is to create Generation Company records
from scratch.
When you run the Create Company query, the Meridium APM system will run a query
and display a list of records in the Utilities Reference family. You can select a record
from the list and use it to create a new Generation Company record. Many of the values
in the selected Utilities Reference record will be used to populate the corresponding
fields in the new Generation Company record automatically. You can enter information in
the remaining fields and edit the information that is supplied by the Utilities Reference
record as desired.
Note: Fields in a Generation Company record are populated based on values in Utilities
Reference records only when the record is first created. After the Generation Company
record has been saved for the first time, it has no knowledge of the Utilities Reference
record from which its fields were originally populated.
About Generation Plant Records

Generation Plant records represent a plant in which units reside. Generation Plant records
are linked to Generation Company records and should be created after Generation
Company records have been created but before you can create Generation Unit records.
Additionally, before you create Generation Plant records, you must determine:
Whether or not Incident records associated with those Generation Plant records
will account for Daylight Saving Time. If you want Incident records to account
for Daylight Saving Time, you will need to create Daylight Saving Time
Reference records before you create Generation Plant records.
The date and time format that will be used in date fields in Primary Capacity
Incident records that are associated with the Generation Plant record. Before you
create Generation Plant records, you must determine which date and time format
you want to use.
You can create Generation Plant records in two ways:
for creating Generation Plant records. Throughout this documentation, we assume
that you have created your Generation Plant records using this method.
Using the Create Plant Query. This option exists as an alternative to creating
Generation Plant records in the Record Manager but is not recommended.
Creating Generation Plant Records

The following instructions provide details on creating a new Generation Plant record
using the baseline Plant datasheet.
To create a Generation Plant record:
2. In the Search In list, select Generation Company.
A list appears in the results section of the Search page, displaying all the Generation
Company records that exist in the database.
4. Click the hyperlinked Record ID of the Generation Company record for which
you want to create a Generation Plant record.
The selected Generation Company record appears in the Record Manager.
5. In the Record Explorer pane, right-click the Generation Plant node, and then click
Create a new Generation Plant record to link to <Generation Company record>.
The new Generation Plant window appears, displaying an empty datasheet for the
Generation Plant family.
6. In the Plant ID text box, type a short name or acronym that identifies the plant.
7. In the Plant Name text box, type the full name of the plant.
8. If you plan to use Daylight Saving Time...

9. In the Date/Time Alternate Format list, choose the date and time format to use for
records that are associated with the Generation Plant record.
Note: Some fields that are not required to save a Generation Plant record ARE required in
order to create accurate power generation and fuel consumption reports.
The Generation Plant record is created, saved to the database, and linked to the selected
Generation Company record.
Using the Create Plant Query

The Create Plant query is provided in the baseline Meridium APM database and is stored
in the Catalog folder \\Public\Meridium\Modules\Generation Management\Configuration.
It queries the Plant Reference family and is provided as a tool that can assist in the
creation of Generation Plant records by populating fields in new records automatically.
Note: Plant Reference records are delivered in the baseline Meridium APM database and
contain information about plants. Because the data that is stored in the baseline Plant
Reference records may not be current, using the Create Plant query is not presented in
this documentation as the primary method for creating Generation Plant records. Instead,
the recommended workflow is to create Generation Plant records from scratch.
When you run the Create Plant query, the Meridium APM system will run a query and
display a list of records in the Plant Reference family. You can select a record from the
list and use it to create a new Generation Plant record. Many of the values in the selected
Plant Reference record will be used to populate the corresponding fields in the new
Generation Plant record automatically. You can enter information in the remaining fields
and edit the information that is supplied by the Plant Reference record as desired.
Note: Fields in a Generation Plant record are populated based upon values in Plant
Reference records only when the record is first created using the Create Plant query. After
the Generation Plant record has been saved for the first time, it has no knowledge of the
Plant Reference record from which its fields were originally populated.
How Census-Related Fields Are

Populated
EIA Federal Region records exist in the baseline Meridium APM database and contain
information about US Census Regions. These records are provided as a way to ensure
that the federal region values in Generation Plant records are correct by populating them
automatically.
When the State field in any Generation Plant record is populated with a value, the
Meridium APM system finds the EIA Federal Region record with the same value in its
State field and:
Populates the EIA Census Division field in the Generation Plant record with the
value in the Census Division field in the EIA Federal Region record.
Populates the EIA Federal Region field in the Generation Plant record with the
value in the Federal Region field in the EIA Federal Region record.
For example, using the baseline EIA Federal Region records, in a Generation Plant
record, if you populate the State field with the value Virginia (VA) the Meridium APM
system will:
Populate the EIA Census Division field in the Generation Plant record with the
value South Atlantic.
Populate the EIA Federal Region field in the Generation Plant record with the
value 3.
To make sure that Generation Plant records are always populated with accurate
information, we recommend that you:
NOT modify the baseline EIA Federal Region records.

NOT create your own EIA Federal Region records.
About Accounting for Daylight Saving

Time Adjustments
If an event occurs during a time period when Daylight Saving Time (DST) begins or
ends, and your plant exists in a part of the country where DST is observed, you will
probably want to adjust the values in these fields to account for the DST adjustment.
For example, in 2007, DST in the United States started at 2:00 A.M. on March 11. As a
result, observers of DST lost one hour of daylight (e.g., a clock that read 4:00 A.M. on
March 11 would have read 3:00 A.M. on March 10). Because DST started at 2:00 A.M.,
observers were required to set their clocks forward one hour at that time. So at 2:00 A.M.,
you had to set your clock to 3:00 A.M. even though an hour had not actually passed.
With that in mind, suppose an event occurred at 11:00 P.M. on March 10, 2007 and ended
at 4:00 A.M. on March 11, 2007. By the clock, it would appear that the event lasted five
hours. In reality, the event lasted only four hours because DST added an hour to the clock
even though that hour did not actually occur.
If you allow the Meridium APM system to take DST into account, you will pay for power
for the four hours that the event lasted according to real linear time. If you do NOT allow
the Meridium APM system to take DST into account, you could end up paying for power
for the five hours the event lasted according to the clock.
About Daylight Saving Time Reference

Records
Daylight Saving Time Reference records represent a region in which Daylight Saving
Time (DST) is observed and contain information about when DST begins and ends for
that region for a given year. Multiple Daylight Saving Time Reference records may exist
for a given DST region, one for each year in which Daylight Saving Time is observed.
The following fields in Primary Capacity Incident records are affected by the values in
Daylight Saving Time Reference records:
Potential Capacity Incident Cost

Event Duration
Work Duration
If you want to include Daylight Saving Time adjustments when calculating the values in
these fields, you will need to:
Create Daylight Saving Time Reference records to indicate the start and end time
for Daylight Saving Time each year.
Set the Use Daylight Saving Time field to True in Generation Plant records whose
associated Primary Capacity Incidents you want to calculate using Daylight
Saving Time adjustments.
Populate the DST Region field in Generation Plant records whose associated
Primary Capacity Incidents you want to calculate using Daylight Saving Time
adjustments with the appropriate value.
Creating Daylight Saving Time

Reference Records
To create a Daylight Saving Time Reference record:
2. In the list, select Daylight Saving Time Reference.
3. Click OK.
A new Daylight Saving Time Reference record appears in the Record Manager.
4. In the DST Region Code text box, type a value representing a region. You can
type any value. For example, you might type US to indicate that this record
corresponds to the United States. The value that you type will appear in the DST
Region list in all Generation Plant records. If you want to use this Daylight
Saving Time Reference record to calculate values in Primary Capacity Incidents
records linked to a specific Generation Plant record, you will need to select this
value in the DST Region list in those Generation Plant records.
5. In the DST Start cell, specify the date and time that Daylight Saving Time starts.
6. In the DST End cell, specify the date and time that Daylight Saving Time ends.
Note: The value in the DST Adjustment cell is set to one hour and disabled by default.
The Daylight Saving Time Reference record is created and saved to the database.
About Choosing How Dates Will Be

Entered and Displayed
In Generation Management, Primary Capacity Incident records contain fields that store
date and time information. For example, the Event Start Date field identifies the date and
time that an incident began. The Meridium APM Framework provides TWO types of date
fields that provide you with two options for displaying and entering date and time data in
Primary Capacity Incident records:
Standard date fields, which use the Calendar and support the use of a 12-hour
clock.
Alternate date fields, which are character fields that do NOT use the Calendar and
support the use of a 24-hour clock.
Both types of date fields appear by default on the baseline Primary Capacity Incident
datasheet. Before you begin recording incident data, you will need to determine which
time format to use. You can do so by selecting a value in the Date/Time Alternate Format
field in Generation Plant records. You will then want to modify the Primary Capacity
Incident datasheet to remove the fields that you do not want to use (i.e., the standard date
fields or the alternate date fields).
IMPORTANT: The value that you select in the Date/Time alternate Format field of a
Generation Plant record will apply to ALL Primary Capacity Incident records that are
linked to any Generation Unit record that is linked to that Generation Plant record.
Click one of the following links for instructions on configuring GM to use the desired
time format:
12-hour time format.

24-hour time format.
Note: Regardless of which date fields you choose to use for entering data, the Meridium
APM system will use the values in the standard date fields for performing calculations. If
you choose to use the alternate date fields, the standard date fields will be populated
automatically with the same date and time information, even if they are not displayed on
the datasheet.
Using the 12-Hour Time Format

If you want to use the 12-hour time format, you should simply use the standard date
fields. To do so:
In Generation Plant records, select NO value in the Date/Time Alternate Format

field.
Note: This field is populated with a value by default. So if you want to use the 12-hour
time format, you will need to delete the default value.
Using the Configuration Manager application, remove the following fields from
the Primary Capacity Incident datasheet.
Event End Date (Alternate Format)
Event Start Date (Alternate Format)
Work Ended (Alternate Format)
Work Started (Alternate Format)
Note: By default, both the standard and alternate date fields are included on the Primary
Capacity Incident datasheet. If you want to use the 12-hour time format, however, there is
no need to include the alternate date fields on the datasheet.
Using a 24-Hour Time Format

If you want to use a 24-hour time format, you will need to use the alternate date fields. To
do so:
In Generation Plant records, select one of the following values in the Date/Time
Alternate Format field.
YYYY-MM-DD HH:MM
MM/DD/YYYY HH:MM
MM/DD/YYYY HH:MM:SS
The option you select should correspond to the format in which you want users to type
date and time information. Keep in mind that the alternate date fields do NOT provide the
Calendar. Users will need to type date and time information into these fields using the
format specified in the associated Generation Plant record.
Using the Configuration Manager application, remove the following date fields
from the Primary Capacity Incident datasheet:
Event End Date
Event Start Date
Work Ended
Work Started
Note: By default, both the standard and alternate date fields are included on the Primary
Capacity Incident datasheet. If you want to use the 24-hour time format, however, there is
no need to include the standard date fields on the datasheet since they do not fully support
the use of a 24-hour time format.
About Generation Unit Records

A Generation Unit record represents a unit that generates power. You will collect incident
and fuel consumption data for Generation Unit records. Before you can create Generation
Unit records, you must create the Generation Plant records to which they will be linked.
You can create Generation Unit records in two ways:
for creating Generation Unit records. Throughout this documentation, we assume
that you have created your Generation Unit records using this method.
Using the Create Unit Query. This option exists as an alternative to creating
Generation Unit records in the Record Manager but is not recommended.
Creating Generation Unit Records

To create a Generation Unit record:
2. In the Search In list, select Generation Plant.
The search results are displayed in the results section of the Search page.
4. Click the hyperlinked Record ID of the Generation Plant record for which you
want to create a Generation Unit record.
The selected Generation Plant record appears in the Record Manager.
5. In the Record Explorer pane, right-click the Generation Unit node, and then click
Create a new Generation Unit record to link to <Generation Plant record>.
The new Generation Unit window appears, displaying an empty datasheet for the
Generation Unit family.
This image displays the baseline Unit datasheet. These instructions provide details on
creating a new Generation Unit record using this datasheet.
6. On the Unit tab, in the Unit ID text box, type a short name or acronym that
identifies the unit.
7. In the Unit Name text box, type the unit's name.

8. In the Gross Maximum Capacity text box, type the unit's gross maximum
capacity.
-ORIn the Net Maximum Capacity text box, type the unit's net maximum capacity.
9. Click the References tab.
10. In the GADS Unit Type list, select the appropriate GADS unit type of the unit.
11. In the GADS Region list, select the GADS region for which the unit generates
power.
12. Click the Calculation Settings tab.
13. In the Generation Cost Model list, select the value that corresponds to the method
that you want to use for calculating capacity incidents costs.
14. Click the Defaults tab.
15. In the Default Unit Loading list, select the value that indicates the time during
which the unit generates power.
Note: If the Default Unit Loading field is set to Other (6), the Verbal Description field
will be required.
16. In the Primary Fuel Code list, select the value that identifies the primary fuel used
by the unit.
17. Complete the remaining fields as desired. Note that some fields that are NOT
required to save a Generation Unit record ARE required in order to create
accurate power generation and fuel consumption reports.
The Generation Unit record is created, linked to the selected Generation Plant record, and
saved to the database.
Using the Create Unit Query
The Create Unit query is provided in the baseline Meridium APM database and is stored
in the Catalog folder \\Public\Meridium\Modules\Generation Management\Configuration.
It queries the Unit Reference family and is provided as a tool to assist in the creation of
Generation Unit records by populating fields in new records automatically.
Note: Unit Reference records are delivered in the baseline Meridium APM database and
contain information about units. Because Meridium APM cannot guarantee the accuracy
of the data that is stored in the baseline Unit Reference records, using the Create Unit
query is not presented in this documentation as the primary method for creating
Generation Unit records. Instead, the recommended workflow is to create Generation
Unit records from scratch.
When you run the Create Unit query, the Meridium APM system will run a query and
display a list of records in the Unit Reference family. You can select a record from the list
and use it to create a new Generation Unit record. Many of the values in the selected Unit
Reference record will be used to populate the corresponding fields in the new Generation
Unit record automatically. You can enter information in the remaining fields and edit the
information that is supplied by the Unit Reference record as desired.
Note: Fields in a Generation Unit record are populated based on values in Unit Reference
records only when the record is first created via the Create Unit query. After the
Generation Unit record has been saved for the first time, it has no knowledge of the Unit
Reference record from which its fields were originally populated.
Capacity Fields
Generation Unit records contain four fields that define the capacity of the unit:
Gross Dependable Capacity

Gross Maximum Capacity
Net Dependable Capacity
Net Maximum Capacity
When you create a new Generation Unit record, you must specify a value in either the
Gross Maximum Capacity field OR the Net Maximum Capacity field, which will cause
the Meridium APM system to populate the remaining fields using the following
equations:
Gross Dependable Capacity: Equal to the value in the Gross Maximum Capacity
field and greater than the net capacity values by a factor determined by the value
in the GADS Unit Type field.
Gross Maximum Capacity: Equal to the value in the Gross Dependable Capacity
field and greater than the net capacity values by a factor determined by the value
in the GADS Unit Type field.
Net Dependable Capacity: Equal to the value in the Net Maximum Capacity field
and less than the gross capacity values by a factor determined by the value in the
GADS Unit Type field.
Net Maximum Capacity: Equal to the value in the Net Dependable Capacity field
and less than the gross capacity values by a factor determined by the value in the
GADS Unit Type field.
It is important that when you create a new Generation Unit record, you specify an
accurate value in either the Gross Maximum Capacity OR the Net Maximum Capacity
field. If you supply a value in both the Gross Maximum Capacity field and the Net
Maximum Capacity field:
The Meridium APM system will NOT perform the proper calculation using the
value specified for the GADS Unit Type.
After the Generation Unit record exists, if you modify one of the values, the
calculations will NOT be performed again.
GADS Unit Type Field

The value in the GADS Unit Type field in Generation Unit records is used in conjunction
with the value in the Gross Maximum Capacity or Net Maximum Capacity field to
calculate missing capacity values. The value in the GADS Unit Type field can be set to:
Fossil, Nuclear, or Fluidized Bed Units: The Gross Maximum Capacity and Gross
Dependable Capacity values will be 5% greater than the Net Maximum Capacity
and Net Dependable Capacity values.
Gas Turbine/Jet Engine: The Gross Maximum Capacity and Gross Dependable
Capacity values will be 2% greater than the Net Maximum Capacity and Net
Dependable Capacity values.
Diesel Units: The Gross Maximum Capacity and Gross Dependable Capacity
values will be 0% greater than the Net Maximum Capacity and Net Dependable
Capacity values. In other words, all capacity values will be the same.
Hydro/Pumped Storage Units: The Gross Maximum Capacity and Gross

and Net Dependable Capacity values.
Miscellaneous Units: The Gross Maximum Capacity and Gross Dependable

Capacity values will be 4% greater than the Net Maximum Capacity and Net
Dependable Capacity values.
Multi-Boiler/Multi-Turbine: The Gross Maximum Capacity and Gross

and Net Dependable Capacity values. In other words, all capacity values will be
the same.
For example, suppose you created a Generation Unit record that contains the value Gas
Turbine/Jet Engine (300) in the GADS Unit Type field and the value 100 in the Gross
Maximum Capacity field. When you save that Generation Unit record, the remaining
capacity fields will be populated automatically as follows:
Gross Dependable Capacity: 1000

Net Maximum Capacity: 980
Net Dependable Capacity: 980
About Fuel Codes

In Generation Unit records, the fuel code fields store values that identify the types of fuel
used by a given unit. For each unit, the Meridium APM system supports defining up to
four levels of fuel that will be used, depending upon availability:
Primary Fuel: The unit's first choice of fuel types. As long as this type of fuel is
available, it will be used.
Secondary Fuel: The type of fuel that will be used if the primary fuel is not
available.
Tertiary Fuel: The type of fuel that will be used if the primary and secondary fuels
are not available.
Quaternary Fuel: The type of fuel that will be used if the primary, secondary, and
tertiary fuels are not available.
In Generation Unit records, fuel types are identified through codes. The Meridium APM
system supports the use of four different types of fuel code schemes, each of which uses a
slightly different code for classifying the same types of fuel:
NERC fuel codes

EIA energy source codes
AER fuel codes
Common fuel codes
Given the four levels of fuel types and the four fuel code schemes, a Generation Unit
record can have as many as 16 fuel codes defined for it, one for each level and scheme
combination. For example, the following image displays the Defaults tab of the Unit
datasheet for a Generation Unit record.
The columns represent the different fuel code schemes:
NERC Values
EIA Energy Source Values
AER Fuel Code Values
Common Fuel Code Value
The rows represent the fuel type levels:
Primary Fuel Code

Secondary Fuel Code
Tertiary Fuel Code
Quaternary Fuel Code
If you populated each cell, the Generation Unit record would contain 16 fuel codes.
Note: Fuel code values are defined in Heating Value Ranges records. To see a list of these
records, you can run the query Heating Range Values, which is stored in the following
Catalog folder: \\Public\Meridium\Modules\Generation Management\Queries.
Mapping Family Fields to Cells on the

Datasheet
In Generation Unit records, fuel codes are stored within 16 distinct fields. While these
fields appear as 16 separate cells on the Defaults tab of the Unit datasheet, the names of
the cells do not correspond exactly to the names of the field captions (i.e., NOT the
datasheet labels). Throughout this documentation, we use the field captions when
referring to these fields. Therefore, the following table maps the datasheet cell to the field
caption.
Field Caption
Column
Row
AER Fuel Type Code 1
Primary Fuel Code
Secondary Fuel Code
Tertiary Fuel Code
Common Fuel Code 1
Common Fuel Code Values Primary Fuel Code
Common Fuel Code 2
Common Fuel Code Values Secondary Fuel Code
Common Fuel Code 3
Common Fuel Code Values Tertiary Fuel Code
Common Fuel Code 4
Common Fuel Code Values Quaternary Fuel Code
EIA Energy Source 1
Primary Fuel Code
EIA Energy Source 2
Secondary Fuel Code
EIA Energy Source 3
Tertiary Fuel Code
EIA Energy Source 4
Primary Fuel Code
NERC Values
Primary Fuel Code
NERC Values
Secondary Fuel Code
NERC Values
Secondary Fuel Code
Tertiary Fuel Code
NERC Values
Tertiary Fuel Code
How Fuel Code Fields are Populated

Fuel code fields in Generation Unit records are populated using values in Heating Value
Ranges records, which store information about the various fuels that can be used by units.
Each Heating Value Ranges record represents a unique fuel type.
For example, in Generation Unit records, the AER Fuel Type Code 1 field will contain a
list of values from the AER Fuel Code Description fields in Heating Value Ranges
records. The following table shows how the lists in the fuel code fields in Generation
Unit records are populated using values in Heating Value Ranges records.
This Field in Generation Unit

Records:
...Is Populated Using These Fields and Format:
AER Fuel Type Code <1-4>
AER Fuel Description (AER Fuel Code)
Common Fuel Code <1-4>
Common Fuel Description (Common Fuel

Code)
EIA Energy Source <1-4>
Fuel Type Description (Fuel Type)
Primary Fuel Code
NERC Fuel Description (NERC Fuel Code)
Secondary Fuel Code
Tertiary Fuel Code
In a Generation Unit record, when a NERC fuel code field is populated with a value, the
corresponding EIA energy source code, AER fuel code, and common fuel code fields are
restricted to contain only values in fields in Heating Value Ranges records with a value in
the NERC Fuel Code field that matches the NERC Fuel Code value in that NERC fuel
code field.
For example, using the baseline Heating Value Ranges records, if a Generation Unit
record contains the value Water (WA) in the Primary Fuel Code field, the other primary
fuel code fields will be restricted to show the values from Heating Value Ranges records
that contained the value Water in the NERC Fuel Description field and the value WA in
the NERC Fuel Code field. Specifically:
The AER Fuel Type Code 1 field will contain these values:
Hydroelectric Pumped Storage (HPS)
Hydroelectric Conventional (HYC)
The Common Fuel Code 1 field will contain these values:
Water Hydro (HY WAT)
Water Pump Storage (PS WAT)
The EIA Energy Source 1 field will contain these values:
Water (HY WAT)
Water (PS WAT)
If you populate any additional fuel code field after populating the value in the NERC fuel
code field, the remaining fuel code fields will be restricted based upon that value as well.
So in this example, if you select Hydroelectric Pumped Storage (HPS) in the AER Fuel
Type Code 1 field:
The list in the Common Fuel Code 1 field would contain only the value Water
Pump Storage (PS WAT).
The EIA Energy Source 1 field would contain only Water (PS WAT).
Note: When the value in any NERC fuel code field is changed, if any of the fields for the
same fuel level contain a value, that value will be cleared, and the field will contain NO
value.
The baseline Meridium APM database contains Heating Value Ranges records that are
already populated with values that identify fuels as they are defined by NERC and the
EIA. We recommend that you:
NOT modify the baseline Heating Value Ranges records so that they match what
is defined by NERC and the EIA.
NOT create your own Heating Value Ranges records.
Defining How Data Should Be Reported

The value in the Report Capacity Data field is used to specify how data in Incident
records that are linked to a Generation Unit record should be reported and can contain
one of the following options:
NERC: Incident data linked to the Generation Unit record should be included in
NERC reports.
Internal: Incident data linked to the Generation Unit record should be excluded
from NERC reports but included in any internal reports. For example, you may
want to create a monthly report of incident data linked to certain Generation Unit
records to report data to upper management, but NOT to NERC. In this case, you
would select Internal.
NERC and Internal: Incident data linked to the Generation Unit record should be
included both in the NERC reports and in any internal reports. For example, you
may want to create a monthly report of incident data linked to certain Generation
Unit records to report data to upper management and also to NERC. In this case,
you would select NERC and Internal.
Do Not Report: All incident data linked to the Generation Unit record should be
excluded from both NERC reports and any internal reports.
To make use of the values specified in the Report Capacity Data field, you will need to
customize the baseline NERC reports to filter incident data into these categories. If you
do NOT customize the existing queries, then the incident data will NOT be accurate in
NERC or internal reports.
Choosing How To Calculate Incident

Cost
In a Primary Capacity Incident record, the Capacity Incident Cost field can be used to
store the cost of the event represented by that record. How the cost of the event is
calculated is determined by the value in the Generation Cost Model field in the
Generation Unit record to which the Primary Capacity Incident record is linked. Before
you begin creating Primary Capacity Incident records, you need to determine how you
will calculate the cost of incidents by setting the Generation Cost Model field to one of
the following values:
No Cost Calculation: The value in the Capacity Incident Cost field will NOT be
populated (i.e., no cost calculation will be performed).
Price Curve: The value in the Capacity Incident Cost field will be calculated
based upon values in Power Price Curve records.
Reference Value: The value in the Capacity Incident Cost field will be calculated
based on the value specified in the Generation Cost Reference Value field in the
Generation Unit record. If you set the Generation Cost model field to Reference
Value, the Generation Cost Reference Value field becomes required.
IMPORTANT: The capacity incident cost will be calculated based upon the value in the
Generation Cost Model field when the Primary Capacity Incident record is created. If
you select a value, save the Generation Unit record, create Primary Capacity Incident
records associated with the unit, and then modify this value, the new value will NOT be
used in existing Capacity Incident Cost calculations.
Determining When APM Event Records

Are Created
In Generation Unit records, the APM Event Creation field stores a value that determines
whether an APM Event record will be created when a new Primary Capacity Incident
record is created and linked to a given Generation Unit record. The APM Event Creation
field can be set to:
All Primary Capacity Events: An APM Event record will be created each time a
Primary Capacity Incident record is created and linked to the Generation Unit
record. The APM Event record will be linked automatically to the Primary
Capacity Incident record.
MWH Loss Exceeds Reference: An APM Event record will be created when a
Primary Capacity Incident record is created and linked to the Generation Unit
record IF the value in the Total Equivalent Derate MWh w/out Shadowing field of
the Primary Capacity Incident record exceeds the value in the APM Event
Creation Reference Value field in the Generation Unit record. The APM Event
record will be linked automatically to the Primary Capacity Incident record.
Production Loss Exceeds Reference: An APM Event record will be created
when a Primary Capacity Incident record is created and linked to the Generation
Unit record IF the value in the Total Equivalent Derate Hours w/out Shadowing
field in the Primary Capacity Incident record exceeds the value in the APM Event
Creation Reference Value field of the Generation Unit record. The APM Event
record will be linked automatically to the Primary Capacity Incident record.
About Generation Pool Records

Generation Pool records provide you with a way to group multiple Generation Unit
records together into a generation pool, which is a grouping of units that are consistently
reported as a group and is represented in Meridium APM by a single Generation Pool
record. You will create one Generation Pool record for each generation pool and unit
combination. You can associate a Generation Unit record with multiple generation pools
by creating multiple Generation Pool records, one for each pool to which a unit belongs.
Creating a Generation Pool Record

To create a Generation Pool record:

2. In the list, select Generation Pool.
3. Click OK.
A new Generation Pool record appears in the Record Manager.
4. In the Generation Pool Name text box, type a name or select one from the list.
The Unit ID cell will become required after the Generation Pool Name cell has been
populated.
5. In the Unit ID list, select the Generation Unit record to which you want to link
this Generation Pool record. The list will show only the Generation Unit records
that are not linked to the record specified in the Generation Pool Name field.
The Generation Pool record created and saved to the database.
About Creating Loading Profile and

Starting Profile Records
After you have created all desired Generation Company, Generation Plant, and
Generation Unit records, you can create additional records to store data and refer to it as
needed.
For instance, you might want to create:
Generation Unit Loading Profile records.

Generation Unit Starting Profile records.
Creating a Generation Unit Loading

Profile Record
To create a Generation Unit Loading Profile record:
1. In the Meridium APM Framework application, open a Generation Unit record in
the Record Manager.
2. In the Record Explorer pane, right-click the Generation Unit Loading Profile
family node, and click Create a new Generation Unit Loading Profile record to
link to [root record].
A new Generation Unit Loading Profile record appears.
3. In the Unit ID list, select the Generation Unit record to which you want to link the
Generation Unit Loading Profile record. This field is required.
4. Complete the remaining fields as desired. Note that the Loading Profile and Load
Point Number fields are required.
5. Click OK.
The Generation Unit Loading Profile record is saved and linked to the selected
Creating a Generation Unit Starting

Profile Record
To create a Generation Unit Starting Profile record:
1. In the Meridium APM Framework application, open a Generation Unit record in
the Record Manager.
2. In the Record Explorer pane, right-click the Generation Unit Starting Profile
family node, and click Create a new Generation Unit Starting Profile record to
link to [root record].
A new Generation Unit Starting Profile record appears.
Generation Unit Starting Profile record. This field is required.
4. Complete the remaining fields as desired. Note that the Startup Type field is
required.
5. Click OK.
The Generation Unit Starting Profile record is saved and linked to the selected
About Creating Nameplate Records

The Generation Nameplate family includes the following subfamilies:
Generation Nameplate Combined Cycle
Generation Nameplate Diesel
Generation Nameplate Fluidized Bed
Generation Nameplate Fossil Steam
Generation Nameplate Gas Turbine
Generation Nameplate Hydro
Generation Nameplate Miscellaneous
Generation Nameplate Nuclear
By default, no datasheet is defined for the Generation Nameplate family. Datasheets exist
only for the subfamilies. Therefore, by default, you can create Generation Nameplate
records only within the subfamilies.
Creating a Generation Nameplate

Record
You can create a record in any Generation Nameplate subfamily. The following
instructions provide an example for creating a Generation Nameplate Combined Cycle
record.
To create a Generation Nameplate Combined Cycle Record:
2. In the list, select Generation Nameplate Combined Cycle.
3. Click OK.
A new Generation Nameplate Combined Cycle record appears in the Record Manager.
4. On the General Unit Data tab, in the Unit ID list, select the Generation Unit
record to which you want to link the Generation Nameplate Combined Cycle
record. Various fields in the Generation Nameplate Combined Cycle record will
be populated automatically with values from that Generation Unit record. This
field is required.
The Generation Nameplate Combined Cycle record is saved and linked to the Generation
Unit record identified by the value that you selected in the Unit ID list.
About Generation Forecast Records

Generation Forecast records store information that is used to predict the future capacity
of units and plants. This information will not be used when generating reports but can be
used to more accurately estimate the cost of incidents. You should create Generation
Forecast records before the time period for which they exist.
Creating Generation Forecast Records

To create a Generation Forecast record:
2. In the list, select Generation Forecast.
3. Click OK.
A new Generation Forecast record appears in the Record Manager.
4. In the Unit ID list, select the Generation Unit record to which you want to link
this Generation Forecast record. Some fields in the Generation Forecast record
will be populated automatically with values from the selected Generation Unit
record. This field is required.
5. In the Forecast Year list, select the year for which you want to predict future
capacity.
6. In the Forecast Month list, select the month for which you want to predict future
capacity.
Note: You cannot create multiple Generation Forecast records for the same month and
year.
The Generation Forecast record is saved and linked to the Generation Unit record
identified by the value that you selected in the Unit ID list.
About Incident Records

In Generation Management, Incident records store information about events in which a
unit suffers a loss of power generation capacity. GM uses two types of Incident records:
Primary Capacity Incident: Stores information about the primary cause of an

event. When something goes wrong in a unit, you will record information about
the event in a Primary Capacity Incident record. Primary Capacity Incident
records are linked to the Generation Unit record that represents the unit at which
the event occurred.
Contributing Capacity Incident: Stores additional information about the event,
such as a secondary cause. All Contributing Capacity Incident records are linked
to a Primary Capacity Incident record. Therefore, to create a Contributing
Capacity Incident record, you must have already created the Primary Capacity
Incident record to which it will be linked. When you create a Contributing
Capacity Incident record, all required fields will be populated automatically with
values in the Primary Capacity Incident record to which it is linked.
Each event that occurs will be represented by at least a Primary Capacity Incident record.
Depending upon the event, one or more Contributing Capacity Incident records may need
to be created and linked to the Primary Capacity Incident record. Together, the Primary
Capacity Incident record AND all the Contributing Capacity Incident records that are
linked to it represent a single event.
Because Primary Capacity Incident records and Contributing Capacity Incident records
are similar in that they share many of the same fields and behave the same way,
throughout this documentation we refer to them collectively as Incident records. Where
necessary, we make a distinction between the functionality of Primary Capacity Incident
records and Contributing Capacity Incident records. Wherever that distinction is NOT
made, you can assume that all Incident records function the same way.
The Incident Record Workflow

Before you can create Incident records, you must have already created the Generation
Company, Generation Plant, and Generation Unit records with which the Incident records
will be associated. The following workflow represents the steps that you might take to
record information about events in which a unit suffers a loss of power generation
capacity.
1. Create a Primary Capacity Incident record to represent the event. Because each
Primary Capacity Incident record represents a different event, each time a unit
suffers a loss of power generation capacity, you will need to create a new Primary
Note: If you create Primary Capacity Incident records in an order that is different from
the order in which the incidents occurred, you will need to put the Primary Capacity
Incident records in order after they have been created.
2. If needed, create one or more Contributing Capacity Incident records to represent
incidents related to the event, and link them to the Primary Capacity Incident
record.
Creating Primary Capacity Incident

Records
The following instructions provide details on creating a Primary Capacity Incident record
using the baseline Primary Capacity Incident datasheet. Before you can complete these
instructions, you must have already created the Generation Unit record to which the
Primary Capacity Incident record will be linked.
To create a Primary Capacity Incident record:
1. If you plan to use Power Price Curve records to calculate the cost of the event,
create those records before creating the Primary Capacity Incident record.
The Select Family dialog box appears. In the list, select Primary Capacity Incident.
A new Primary Capacity Incident record appears in the Record Manager.
Primary Capacity Incident record. Certain values from the Generation Unit record
will be used to populate various fields in the Primary Capacity Incident record
automatically.
5. In the Capacity Event Type list, select the value that represents the incident type.
6. Specify the start date and time of the event. To do so:
5.
o
In the Event Start cell, change the value to the date and time the incident
occurred. This field is populated automatically with the current date and
time.
-or1.
o
In the Event Start Date (Alternate Format) text box, type a value that
identifies the date and time the incident began using the format specified
in the Date/Time Alternate Format field in the Generation Plant record
associated with the Primary Capacity Incident record. This field is
populated automatically with the current date and time.
Note: While both of these fields appear on the baseline Primary Capacity Incident
datasheet, if you have followed our recommendation for choosing which date and time
format to use, you will see only one of them.
The Reporting Year and Reporting Month cells are disabled and populated automatically
based on the Event Start date.
7. Specify an end date and time for the event. To do so:
In the Event End cell, specify the date and time the incident ended.
-or
In the Event End Date (Alternate Format) text box, type a value the identifies the
date and time the incident ended using the format specified in the Date/Time
Alternate Format field in the Generation Plant record associated with the Primary
Note: While both of these fields appear on the baseline Primary Capacity Incident
datasheet, if you have followed our recommendation for choosing which date and time
format to use, you will see only one of them.
-or
Leave both the Event End and Event End Date (Alternate Format) cells empty. In
this case, when you save the record, these fields will be populated automatically
with the last day of the same month of the event start date at 11:59 P.M., and the
End Date is Estimated? check box will be selected automatically.

The Primary Capacity Incident record is created, saved to the database, and linked to the
Generation Unit record identified by the value that you selected in the Unit ID list. In
addition:
1.
o
If one does not already exist, a Capacity History record will be created
automatically and linked to the Primary Capacity Incident record and to
the Generation Unit record to which the Primary Capacity Incident record
is linked.
An APM Event record may also be created and linked to the Primary
Capacity Incident record, depending on the value in the APM Event
Creation field in the linked Generation Unit record.
Creating Contributing Capacity

Incident Records
The following instructions provide details on creating a Contributing Capacity Incident
record. Before you can create a Contributing Capacity Incident record, you must have
already created the Primary Capacity Incident record to which the Contributing Capacity
Incident record will be linked.
The instructions in this topic represent the only way to create a Contributing Capacity
Incident record successfully using the baseline GM product. This method will cause
fields in the new Contributing Capacity Incident record to be populated with information
from the Primary Capacity Incident record. If you attempt to create a Contributing
Capacity Incident record using a different method (e.g., clicking the New button on the
Meridium APM Framework toolbar), some required fields will NOT be populated but
will be disabled so that you will not able to enter the required information, causing an
error message to appear when you attempt to save the record.
To create a Contributing Capacity Incident record:
1. Open in the Record Manager the Primary Capacity Incident record to which the
Contributing Capacity Incident record will be linked.
2. On the Associated Pages menu, click the Create link, and then click Create
Contributing Incident.
A new Contributing Capacity Incident record appears in a new window.
This image displays the baseline Contributing Capacity Incident datasheet. These
instructions provide details on creating a new Contributing Capacity Incident record
using this datasheet.
3. Complete any optional fields as desired.
Note: All required fields are populated based upon values in the Primary Capacity
Incident record.
4. Click OK.
The Contributing Capacity Incident record is created, saved to the database, and linked to
the Primary Capacity Incident record.
Why Do I Need to Put Primary Capacity

Incidents in Order?
When you create a Primary Capacity Incident record for a unit, an event number is
created and stored in the Event Number field, which is included in the Record ID. The
value in the Event Number field corresponds to the order in which the record was created
for that particular unit for that year, which is determined based on the value in the Event
Start Date field. So, for example, if the record is the third record that you have created for
a unit for 2008, the event number will be 3 (three).
In the following image, the formatted values from the Event Number field in both
Primary Capacity Incident records are circled.
Note: If the value in the Event Number field is fewer that four digits, zeros will be added
in front of the value so that the formatted event number will be four digits.
Throughout the year, however, Primary Capacity Incident records may be created in an
order that does NOT reflect the order in which the incidents occurred. For example, an
incident might occur on January 12, 2008, but you might not create the record to capture
the incident data until January 15, 2008. When incidents are not recorded immediately
after they occur, the values in the Event Number field in the Primary Capacity Incident
records may get out of order.
Consider the following table.
Incident Occurs Record is Created Event Number Assigned

January 1, 2008
January 1, 2008 1
January 2, 2008
January 2, 2008 2
January 3, 2008
January 6, 2008 4
January 4, 2008
January 4, 2008 3
In this example, one incident occurred each day, beginning January 1 and ending January
4. On January 1 and January 2, a record was created immediately after the incident
occurred. On January 3, however, a record was not created immediately after the incident
occurred. Another incident occurred on January 4, and the data was immediately entered
into a record. It was not until January 6 that a record was created to record the incident
from January 3.
In other words, the order in which the records were created does not reflect the order in
which the events occurred. To avoid confusion when reviewing the records, you need a
way to populate the Event Number fields with values that represent the order in which the
incidents actually occurred.
The Meridium APM Framework provides a query that evaluates the event start date of all
Primary Capacity Incident records for a specific unit for a specific year. The query
updates the values in the Event Number fields so that they reflect the event order based
upon start date rather than creation date. The Record ID will also be updated in any
record where the Event Number field is updated.
Sorting Primary Capacity Incident

Records
To put Primary Capacity Incident record event numbers in the correct order:
1. On the Meridium APM Framework toolbar, click the Catalog button.
2. Navigate to the folder \\Public\Meridium\Modules\Generation
Management\Configuration, and double-click the query Resequence Incidents.
The Enter parameter values dialog box appears.
3. In the Unit ID list, select the value for the Generation Unit record whose Primary
Capacity Incident records you want to renumber.
4. In the Year list, select the year in which the Primary Capacity Incidents occurred.
5. Click OK.
A message appears, indicating that one record will be updated.

The Query Builder page appear, displaying a blank page.
The Primary Capacity Incident records for the selected unit and year are now numbered
according to date of occurrence instead of date of record creation.
About the Record ID in Incident

Records
The Record ID field in all Incident records is generated automatically, but the fields that
are used to generate the values are different for Primary Capacity Incident records and
Contributing Capacity Incident records.
The value in the Record ID field for each Primary Capacity Incident record is
unique to all Primary Capacity Incident records that are linked to a given
Generation Unit record. The Record ID in Primary Capacity Incident records is
generated automatically using the following format:
<Event ID> ~ <Cause Code> ~ <Capacity Event Type>

...where:
1.
o
<Event ID> is the value in the Event ID field.
<Cause Code> is the value in the Cause Code field.
<Capacity Event Type> is the value in the Capacity Event Type field.
The value in the Event ID field in Primary Capacity Incident records is generated using
the following format:
<Unit ID> ~ <Reporting Year> ~ <Event Number>
...where:
<Unit ID> is the value in the Unit ID field.
<Reporting Year> is the value in the Reporting Year field.
<Event Number> is the Value in the Event Number Field. If the

value in the Event Number field is fewer than four digits, zeros
will be added in front of the value so that the event number in the
Event ID field will be four digits.
The Value in the Record ID field in Contributing Capacity Incidents identifies the
Primary Capacity Incident record to which the Contributing Capacity Incident
record is linked. The values in the Record ID field in ALL Contributing Capacity
Incident records that are linked to a given Primary Capacity Incident record will
match one another. The Record ID in Contributing Capacity Incident records is
generated using the following format:
<Primary Incident ID> ~ <Capacity Event Type>

...where:
1.
o
<Primary Incident ID> is the value in the Primary Incident ID field.
<Capacity Event Type> is the value in the Capacity Event Type field.
The Primary Incident ID field is populated automatically with the value in the Event ID
field in the Primary Capacity Incident record for which the Contributing Capacity
Incident record exists. The value in the Primary Incident ID field for all Contributing
Capacity Incident records will match the value in the Event ID field in the Primary
Capacity Incident record to which they are linked.
For example, consider the following diagram.
The Record ID of the first Primary Capacity Incident record begins with Generation Unit
~ 2008 ~ 0001. You can identify the Contributing Capacity Incident record that is linked
to this Primary Capacity Incident record because its Record ID also begins with
Generation Unit ~ 2008 ~ 0001.
The Record ID of the second Primary Capacity Incident record begins with Generation
Unit ~ 2008 ~ 0002. This record is linked to TWO Contributing Capacity Incident
records, both of which begin with Generation Unit 1 ~ 2008 ~ 0002, which allows you to
determine that both Contributing Capacity Incident records are linked to the second
Primary Capacity Incident record.
About Capacity Event Types

Each Primary Capacity Incident or Contributing Capacity Incident record must be
classified using a value in the Capacity Event Type field. There are two types of capacity
events:
Outage Events: The unit could generate NO power during the event.
Derate Events: The unit could produce power during the event, but at a reduced
capacity.
Outage Events
If a Primary Capacity Incident or Contributing Capacity Incident record contains one of
the following values in the Capacity Event Type field, it is considered an outage event:
U1
U2
U3
MO
PO
ME
PE
SF
RS
MB
IR
RU
Derate Events
If a Primary Capacity Incident or Contributing Capacity Incident record contains one of

the following values in the Capacity Event Type field, it is considered a derate event:
D1
D2
D3
D4
DM
PD
DP
NC
About GADS Cause Codes

In Incident records, the cause code fields store values that are used to identify the cause
of the incident. The values in the cause code fields are populated using values in GADS
Cause Codes records. Each GADS Cause Codes record represents a GADS cause code
and can be used to populate the cause code fields in Incident records.
The baseline Meridium APM database contains GADS Cause Codes records that are
already populated with values that identify cause codes as they are defined by NERC. We
recommend that you:
NOT modify the baseline GADS Cause Codes records so that they match what is
defined by NERC.
NOT create your own GADS Cause Codes records.
Note: For GADS cause codes that can be used to identify the cause of an incident for
more than one GADS unit type, multiple GADS Cause Codes records exist in the
baseline Meridium APM database, one for each cause code and unit type combination.
The GADS cause codes themselves are defined by NERC in the GADS DRI. NERC
divides cause codes into systems and components to group the codes into categories. As a
result, the Meridium APM system uses three fields to define cause codes.
Cause Code System

Cause code Component
Cause Code
How GADS Cause Code Fields are

Populated
Cause code fields are populated using values in GADS Cause Codes records. In Incident
records, the Cause Code System field will contain a list of each unique value in the
System field in all GADS Cause Codes records with the value in the Unit Type field that
matches the value in the GADS Unit Type field in the Generation Unit record with which
the Incident record is associated.
For example, using the baseline GADS Cause Codes records, consider a Primary
Capacity Incident record that is linked to a Generation Unit record with the value
Miscellaneous (800) in the GADS Unit Type field. In this case, the Cause Code System
field will contain a list of each unique value in the System field in all GADS Cause
Codes records with the value Miscellaneous (800) in the Unit Type field.
In an Incident record, when the Cause Code System field is populated with a value, the
Cause Code Component field will contain only values in the Component field in GADS
Cause Codes records with a value in the System field that matches the value in the Cause
Code System field in the Incident record. Note that the Cause Code Component field will
NOT contain a list of values until the Cause Code System field contains a value. So in
this example, if you select External in the Cause Code System field, the Cause Code
Component field would contain a list of the following values:
Catastrophe
Economic
Fuel Quality
Miscellaneous (External)
If you populate the Cause Code Category field, the Cause Code field will contain only
values in the Cause Code and Cause Code Description fields in GADS Cause Codes
records with values in the System and Component fields that match the values in the
Cause Code System and Cause Code Component fields in the Incident record. The list in
the Cause Code field in Incident records is displayed using the format Cause Code
(Cause Code Description). Note that the Cause Code field will NOT contain a list of
values until the Cause Code Component field contains a value. So in this example, if you
select Miscellaneous (External) in the Cause Code Component field, the Cause Code
field would contain a list of the following values:
9300 (Transmission System Problems Other Than Catastrophe)

9305 (Ash Disposal Problem)
9310 (Operator Training)
9320 (Other Miscellaneous External Problems)
Incidents with Only One Cause

Some types of incidents have only one possible cause. In Incident records where the
value in Capacity Incident Type field identifies a single-cause incident, the Cause Code
System, Cause Code Component, and Cause Code fields will be disabled and populated
automatically with the appropriate cause code. The following table lists these Capacity
Incident Type values and their corresponding cause codes.
Capacity Incident
Type
Cause Code System
Cause Code
Component
Cause Code
RS
External
Economic
0000 (Reserve
Shutdown)
IR
Inactive State
Inactive State
0002 (Inactive
Reserve)
MB
Inactive State
Inactive State
9991 (Mothballed
Unit)
RU
Inactive State
Inactive State
9990 (Retired Unit)
About Calculating Incident Cost

The Meridium APM system can calculate the potential cost of an incident automatically.
You can specify whether or not the potential incident cost should be calculated and, if so,
the method that will be used for the calculation by selecting a value in the Generation
Cost Model field in the Generation Unit record to which a Primary Capacity Incident
record is linked. You have three options for calculating incident cost:
Do not calculate the cost of incidents. You should choose this option if you plan to
calculate the cost of incidents using a system other than GM.
Calculate cost using a reference value.
Calculate cost using Power Price Curve records.
Note: If the value in the Capacity Event Type field in a Primary Capacity Incident record
is RS or NC , the Capacity Incident Cost field will be disabled and populated
automatically with the value $0.00.
Using a Reference Value to Calculate

Incident Cost
If you want to determine the value in the Capacity Incident Cost field based upon a
reference value, in the Generation Unit record to which the Incident records will be
linked, you need to:
Set the value in the Generation Cost Model field to Reference Value.
Specify a value in the Generation Cost Reference Value field.
The value that you specify in the Generation Cost Reference Value field will be
considered the cost in dollars per hour for the entire duration of the incident. The
Meridium APM system will use this value to calculate the Capacity Incident Cost using
the following equation:
Capacity Incident Cost = Generation Cost Reference Value x (Event End Date - Event
Start Date) x (Net Dependable Capacity - Net Available Capacity)
For example, consider a Primary Capacity Incident record that contains the following
values:
Event Start Date: January 1, 2008 12:00 A.M.

Event End Date: January 1, 2008 4:00 A.M.
Net Dependable Capacity: 200
Net Available Capacity: 100
If the value in the Generation Cost Reference Value field in the Generation Unit record is
set to 1 (one), the Meridium APM system will assume a power cost of $1.00 per hour for
the entire event duration. Therefore, the cost of power for the event duration will be
calculated as follows:
Capacity Incident Cost = ($1.00 x 4 hours) x (100)
Capacity Incident Cost = $400.00
Using Power Price Curve Records to

Calculate Incident Cost
If you want to calculate incident cost using Power Price Curve records, you need to:
In the Generation Unit record for whose incidents you want to calculate cost using
Power Price Curve records, set the Generation Cost Model field to Price Curve.
In the same Generation Unit record, populate the Zone field with the value that
matches the value in the Zone field in the Power Price Curve records that you
want to use to calculate the incident cost.
Before you create a Primary Capacity Incident record for the Generation Unit
record, create Power Price Curve records for the duration of the incident.
-orIf you create power Price Curve records after you have created the Primary Capacity
Incident record, you should recalculate the capacity incident cost.
About Power Price Curve Records

When an incident occurs that causes a power company to generate less power than what
is required to fulfill the power needs of all its customers, that company must purchase
power from an outside source. The price of power at that time directly affects the cost of
the incident. To predict the potential cost of an incident accurately, you can record power
price data in Power Price Curve records. Each Power Price Curve record stores the price
of power ending at a specific time on a specific date in a specific zone. The information
in these records is used to determine the value in the Potential Capacity Incident Cost
field in a Primary Capacity Incident record based on the event duration.
For example, if an incident began on January 1, 2006, at 12:00 P.M. and ended on
January 1, 2006, at 4:00 P.M., the Potential Capacity Incident Cost would be calculated
based upon Power Price Curve records whose Power Price Date contains a date and time
between January 1, 2006, 12:00 P.M. and January 1, 2006, 4:00 P.M.
Note: For Power Price Curve records to be used to calculate the incident cost, the value
in the Zone field in the Power Price Curve record must match the value in the Zone field
in the Generation Unit record to which it is linked.
You can create Power Price Curve records whenever it makes sense within your business
processes. We recommend that you create these records before you create a Primary
Capacity Incident record IF you want that Primary Capacity Incident record to contain a
value for the Potential Capacity Incident Cost immediately after it is first saved. If,
however, you create Power Price Curve records for a specific time period after you create
a Primary Capacity Incident record for the same time period, you can recalculate the
capacity incident cost.
If you specify in a Generation Unit record that you want to use Power Price Curve
records to calculate cost, the Meridium APM system expects at least one Power Price
Curve record to exist for each reporting month. If one does not exist and you create a
Primary Capacity Incident record linked to that Generation Unit record for that reporting
month, the incident cost cannot be calculated.
Creating Power Price Curve Records

To create Power Price Curve records:

2. In the list, select Power Price Curve.
3. Click OK.
A new Power Price Curve record appears in the Record Manager.
This image displays the baseline Price Curve datasheet. These instructions provide details
on creating a new Power Price Curve record using this datasheet.
4. In the Zone list, select the zone for which you want to record power price data.
5. In the Power Price Date cell, select the date for which you are recording the price
of power. Note that if time is important to your pricing increments, be sure to
select the appropriate time. The default time is 12:00:00 AM. Note that the value
you select in this field determines the values that will appear in the Power Price
Month and Power Price Year cells.
6. In the Price text box, type the price value that represents the cost of power per
hour for the specified date and month. Note that if you do not type a decimal point
yourself, Meridium APM Framework will insert a decimal point after the last digit
you type. So, if you type 100, it will assume that you mean $100.00.
The Power Price Curve record is created and saved to the database.
Managing Power Price Curve Records
Regardless of when you create Power Price Curve records, you will want to make sure
that they represent consistent time intervals. The Power Price Date value determines these
intervals. For example, consider four Power Price Curve records with the following
values in the Power Price Date field:
1-1-2001 12:00 AM
1-1-2001 12:15 AM
1-1-2001 12:30 AM
1-1-2001 12:45 AM
These four records represent 15-minute intervals of time. If your database contained these
records, you would want to create all other Power Price Curve records representing 15minute intervals of time. If Power Price Curve records do NOT represent consistent time
intervals, the Meridium APM system may not be able to calculate the cost of incidents
that occurred during the time for which the Power Price Curve records represent.
Keep in mind that the price you type in a Power Price Curve record indicates the price
ending on the date and time that you select in that record. Meridium APM assumes that
this price is valid each minute before that date and time until the end of the interval that is
represented by the preceding Power Price Curve record.
If you create only one record to store pricing data for the month, the Meridium
APM system assumes an interval of one month, which means that the price is
assumed valid beginning on the date in the record until the end of the month.
If you create multiple Power Price Curve records for a given month, Meridium
APM:
1. Calculates the interval (e.g., 15 minutes) between the records.

2. Assumes that the price in each record is valid ending on the date and time
in the record.
3. Determines the start time of each record by subtracting the calculated
interval from the time in each record.
For example, if an event spans from 2:00 P.M. to 3:50 P.M. and you have three Power
Price Curve records (2:00 P.M., 3:00 P.M., and 4:00 P.M.), Meridium APM assumes an
interval of 60 minutes. This means that the cost in each record is valid ending on the time
in the record and starting 60 minutes before that time.
How is Cost Calculated Based on Power

Price Curve Records?
The value in the Potential Capacity Incident Cost field is calculated using:
The duration of the event: Determined from the Event Duration value.
The amount of power you lost: Determined by subtracting the value in the Net
Available Capacity field in the Primary Capacity Incident record from the value in
the Net Dependable Capacity field in the Generation Unit record.
The cost of power at that time: Determined based upon the number of Power Price
Curve records that exist for the time period in which the event took place and the
cost in those records.
One of two formulas is used to calculate the value in the Capacity Incident Cost field,
depending on whether you have one or multiple Power Price Curve records for the event
month.
If you have only ONE Power Price Curve record for the month in which the event
occurred, the formula is:
Capacity Incident Cost = Event Duration x Amount of Power Lost x Cost of Power
The cost of power is specified in the Power Price Curve record.
If you have multiple Power Price Curve records for the month in which the event
occurred, the formula is:
Capacity Incident Cost = Cost of Power for Event Duration x Amount of Power Lost
The cost of power for the event duration is calculated using the following formula:
Cost of Power for Duration = (Number of Minutes the Event Lasted in
Interval/Total Number of Minutes in Interval) x Cost during Interval
The Meridium APM system calculates the cost of power for each interval in the event
duration and adds the values together to arrive at the Cost of Power for Event Duration,
which is used in the Capacity Incident Cost calculation.
The Potential Capacity Incident Cost calculation for multiple Power Price Records is best
understood through an example.
Example of Cost Calculation: Multiple

Power Price Curve Records
Suppose an event begins at 4:09 A.M. and ends at 8:57 A.M. The Event Duration,
therefore, is 4.80 hours. The Net Dependable Capacity is 300, and the Net Available
Capacity is 200, so the amount of power lost is 100 (300-200). Based upon this
information, we know one part of the Potential Capacity Incident Cost formula:
Amount of Power Lost = 100
To calculate the value in the Capacity Incident Cost field, we also need to know the cost
of power for the event duration. Suppose your database contains the following Power
Price Curve data. Each row in the table represents an individual Power Price Curve
record.
Time
Cost of
Power/Hr
4:00
A.M.
$1.00/Hr
5:00
$2.00/Hr
Cost During Time Interval ((#

# Minutes Event
# Minutes in
minutes event lasted in interval/total
Lasted in This
This Interval
number of minutes in interval) x
Interval
cost during interval))
0 minutes
Note that this
record indicates
that the cost of
$1.00/Hr ends at
4:00 A.M. The
$0.00
event did not
occur until 4:09
60 minutes
A.M., so this cost ((60 minutes/60 minutes) x $0.00))
is not used in the
calculation. It is
used, however, to
determine the start
time for the cost
that ends at 5:00
A.M.
$1.70
60 minutes 51 minutes (i.e.,
the event starts at

((51 minutes/60 minutes) x $2.00))
4:09 A.M.)
$3.00
A.M.
6:00
A.M.
$3.00/Hr
60 minutes 60 minutes
7:00
A.M.
$4.00/Hr
8:00
A.M.
$5.00/Hr
$3.00/Hr
$2.85
57 minutes (i.e.,
60 minutes the event ended at
8:57 A.M.)
9:00
A.M.

$4.00
$5.00
To arrive at the total cost of power for the entire event duration, we must add the values
that represent the cost of power during each interval. In this example, we need to add
$1.70, $3.00, $4.00, $5.00, and $2.85. So, the total cost of power for the Event Duration
is $16.55.
All factors in the Potential Capacity Incident Cost formula are now available:
Cost of power for event duration = $16.55
Amount of Power Lost = 100 megawatts
Again, because there are multiple Power Price Curve records for the month in which the
event occurred, the formula is:
Potential Capacity Incident Cost = Cost of Power for Event Duration x Amount of Power
Lost
Using the values in the example, the equation is:
Potential Capacity Incident Cost = $16.55 x 100
Potential Capacity Incident Cost = $1,655.00.
Viewing a Graph of Power Prices

To view a graph of power prices:
Management\Graphs, and double-click the Power Price Curve query.
Note: You could also access the graph via the Pricing link on the Associated Pages menu
that appears when you are viewing a Capacity History record.
The Enter Query Parameters dialog box appears.
3. In the Enter the Price Zone list, select the zone for which you want to view
pricing data.
4. In the Select the Year list, select the year for which you want to view pricing data.
5. In the Select the Month list, select the month for which you want to view pricing
data.
6. Click OK.
The graph appears on the Graph Viewer page.
Note: If you are using a SQL Server database, an error message will be displayed when
you try to open this graph.
Recalculating Potential Capacity

Incident Cost
After you create a Primary Capacity Incident record, you might need to recalculate the
cost of the incident. For example, you would need to do so if:
The potential capacity incident cost is based on Power Price Curve records whose
values change because of changes in pricing information.
The potential capacity incident cost is based on Power Price Curve records, but
when the Primary Capacity Incident was created, a Power Price Curve record that
corresponds to the date and time of the event did not exist yet but has since been
created.
To recalculate the potential capacity incident cost:
1. Open in the Record Manager the Primary Capacity Incident record whose cost
you want to recalculate.
2. On the Event tab of the default Primary Capacity Incident datasheet, select the
Refresh Incident Cost check box.
The cost is recalculated and stored in the Capacity Incident Cost field, and the record is
saved using the new value, along with any other changes that you made to the Primary
What Are Sequential Incidents?

Sometimes, one capacity incident will directly follow another capacity incident, where
each incident is represented by a separate Primary Capacity Incident record. There is no
limit to the chain of subsequent incidents that may occur, each of which will be
represented by its own Primary Capacity Incident record. In this documentation, we refer
to two Primary Capacity Incident records that represent two sequential incidents as
sequential Primary Capacity Incident records. A chain of sequential incidents can be
represented by multiple sequential Primary Capacity Incident record pairs.
The Meridium APM system determines that two Primary Capacity Incident records
represent sequential incidents when the value in the Event Start Date field in a new
Primary Capacity Incident record matches the value in the Event End Date field of an
existing Primary Capacity Incident record that is linked to the same Generation Unit
record. In this case, the value in the Capacity Event Type field in the record representing
the subsequent incident can contain only certain values, depending upon the value in the
Capacity Event Type field in the record representing the preceding incident.
Note: Because certain Capacity Event Type values are allowed only for subsequent
Primary Capacity Incident records, if you select one of these values in a new Primary
Capacity Incident record and the record for the preceding incident does not already exist,
a warning message appears.
When creating a subsequent Primary Capacity Incident record, if you select a Capacity
Event Type value that is not listed as an allowable event type in the subsequent Incident
record AND you specify a value in the Cause Code field, a warning message appears,
explaining that you have selected an invalid scenario that follows an existing Primary
Note: In a chain of incidents, only the value in the Capacity Event Type field of the
record representing the immediately preceding incident determines the allowable
Capacity Event Type in the record representing the subsequent incident.
Allowable Event Types in Sequential

Incidents
Use the following table to determine which event types are allowed in subsequent
Primary Capacity Incident records in sequential Primary Capacity Incident record pairs.
Capacity Event Allowable Event

Notes
Type in
Types in Subsequent
Preceding
Incident Record
Incident
Record
U1
U1, SF, MO, PO, RS,

D1, D2, D3, D4, PD, None
NC
U2
U1, SF, MO, PO, RS,

NC
U3
U1, SF, MO, PO, RS,

NC
SF1
U1, SF, MO, PO, RS, This Capacity Event Type cannot be the first
D1, D2, D3, D4, PD, event in a sequence and must follow an
NC
existing Primary Capacity Incident record. If it
does not follow a Primary Capacity Incident
record with an appropriate Capacity Event

Type, a warning message appears when you
navigate out of the field.
None
MO
U1, SF, MO, PO, SE,

ME, RS, D1, D2, D3,
D4, PD, NC
PO
U1, SF, PO, SE, PE,

RS, D1, D2, D3, D4,
PD, NC
SE1
This Capacity Event Type cannot be the first

event in a sequence and must follow an
U1, SF, SE, RS, D1,
D2, D3, D4, PD, NC
RS
U1, SF, MO, PO, RS,

NC
DE
U1, U2, U3, MO, PO,

None
RS, DE, NC
D1
U1, U2, U3, MO, PO,

None
RS, D1, NC
D2
U1, U2, U3, MO, PO,

None
RS, D1, D2, NC
D3
U1, U2, U3, MO, PO,

None
RS, D1, D2, D3, NC
D4
DE, D4, U1, U2, U3,

MO, PO, RS, DM,
None
NC
PD1
None
DE, PD, U1, U2, U3, This Capacity Event Type cannot be the first
SF, MO, PO, RS, NC event in a sequence and must follow an

PE1

U1, SF, RS, D1, D2,
D3, D4, PD, PE, NC
ME1

U1, SF, RS, D1, D2,
D3, D4, PD, ME, NC
DP1

U1, U2, U3, SF, MO,
PO, RS, DP, NC
DM1

U1, U2, U3, SF, MO,
PO, RS, DM, NC
NC
U1, U2, U3, SF, MO,

ME, DM, PO, PE, SE,
RS, DE, D1, D2, D3, None
D4, PD, DP, NC, MB,
IR, RU
Creating Sequential Incident Records:

An Example
Consider an example of Generation Unit A, represented by the Generation Unit record
Generation Unit A. On January 3, 2009, Generation Unit A suffered an unplanned outage
due to an external influence and had to be repaired before it could be used again. Repairs
began at 9:00 A.M. on January 5 and continued until 5:00 P.M., when it was determined
that a new part had to be ordered to complete the repairs. The new part arrived on January
8, and the repairs were finished by 5:00 P.M. on January 8.
In this scenario, you would have needed to create three Primary Capacity Incident
records:
One to capture the initial outage

One to capture the maintenance
One to capture the extended maintenance due to other circumstances.
Consider the following table, where each column represents a record that you would have
created in this scenario.
Primary Capacity
Incident 1
Primary Capacity
Incident 2
Primary Capacity
Incident 3
Capacity Event
Type
U1 (Unplanned
(forced) Outage Immediate)
MO (Maintenance
Outage)
ME (Maintenance
Outage Extension)
Event Start Date
January 3, 2009, 9:00 January 5, 2009, 9:00 January 5, 2009, 5:00

A.M.
A.M.
P.M.
Event End Date
January 5, 2009, 9:00 January 5, 2009, 5:00 January 8, 2009, 5:00

A.M.
P.M.
P.M.
In this example, you would have created two sequential Primary Capacity Incident record
pairs:
Pair 1: Primary Capacity Incident 1 + Primary Capacity Incident 2
Pair 2: Primary Capacity Incident 2 + Primary Capacity Incident 3
None of these Primary Capacity Incident records can stand alone because none of them
tells the full story of what happened to Generation Unit A.
Primary Capacity Incident 1 indicates that the unit was out during the time
between when it stopped producing power and repairs began. By itself, it would
not indicate that any repairs were attempted on the unit.
Primary Capacity Incident 2 indicates that repairs on the unit began at 9:00 A.M.
on January 5, 2009 and ended at 5:00 P.M. the same day. By itself, it neither
indicates that the unit had stopped producing power before the repairs began nor
that maintenance was extended to account for the time it takes to order and
receive a new part. Notice that the Capacity Event Type value for Primary
Capacity Incident 2 is MO, which is a valid event type for subsequent incidents of
type U1, as defined in Primary Capacity Incident 1.
Primary Capacity Incident 3 indicates that maintenance was extended but does not
indicate when repairs began on the unit or that it had stopped producing power
before the repairs began. Notice that the Capacity Event Type value for Primary
Capacity Incident 3 is ME, which is a valid event type for subsequent incidents of
type MO, as defined in Primary Capacity Incident 2.
Note: The event type ME is NOT valid when the event type of the preceding incident is
U1. But because valid event type for subsequent incidents are determined only by the
immediately preceding incident, the event type of the first incident is NOT considered
when determining allowable event types for the third incident.
Event Contribution Code

The value in the Event Contribution Code field identifies the way in which an incident
contributed to a capacity event.
In Primary Capacity Incident records, the Event Contribution Code field is

disabled and populated automatically with the value Primary Cause of Event. This
value indicates that the Incident record represents the primary cause of the event.
When you create a Primary Capacity Incident record, the Event Contribution
Code field is disabled and populated automatically with this value.
In Contributing Capacity Incident records, the Event Contribution Code field is
enabled, must always contain a value, and contains a list of the following values:
1.
o
2-Contributed to Primary Cause: Indicates that the incident represents a

secondary cause that contributed to the primary cause of the event.
3-Work done during the event: Indicates that the incident represents work
that was done during the event.
5-After startup, delayed unit from reaching load point: Indicates that the
incident delayed the unit from reaching its dependable capacity after
startup and prevented the unit from filling its load requirement.
What Happens When an Event Spans

Multiple Years?
Sometimes an event will start in one year and end in the next year. A single Incident
record, however, cannot span multiple years because the year in the Event Start field
must match the year in the Event End field. This means that if a given event starts in one
year and ends in the next year, you must create two Incident records to represent that
event.
For example, if an event started December 15, 2007 and ended January 15, 2008, you
would create two Primary Capacity Incident records with the following event dates to
represent that event.
Primary Capacity Incident 1
Primary Capacity Incident 2
Event Start
December 15, 2007, 5:00 A.M.
January 1, 2008 12:00 A.M.
Event End
December 30, 2007 11:59 P.M.
January 15, 2008 1:00 P.M.
To identify these two records as representing the same event, you must also:
In Primary Capacity Incident 1, set the End Date Is Estimated? field to True.
In Primary Capacity Incident 2, set the Start Date is Estimated? field to True.
If either of these fields is NOT set to True, the Meridium APM system will assume that
the Primary Capacity Incident record represents an event that does NOT span both years
and that the Event Start and Event End dates and time are correct. In this example, if the
End Date Is Estimated? field in Primary Capacity Incident 1 were set to False, the
Meridium APM system would assume that Primary Capacity Incident 1 had a valid value
in the Event End field and would NOT associate it with Primary Capacity Incident 2.
Then, when you created Primary Capacity Incident 2, a warning message would display
indicating that there is no Primary Capacity Incident record in the database that would
represent the start of the event. You would not be able to set the value in the Incident
Reporting Status field in Primary Capacity Incident 2 to Unit Level Approval until the
End Date Is Estimated? field in Primary Capacity Incident 1 was set to True.
Fields that Can Be Populated from One

of Three Related Records
When you create a Primary Capacity Incident record, you will specify in the Unit ID field
the Unit ID of the Generation Unit record to which the Incident record will be linked.
When you save the Primary Capacity Incident record, the Meridium APM system will
attempt to populate various fields in the Incident record with values based upon the Unit
ID value. These values will NOT necessarily come directly from the Generation Unit
record itself.
1. First, the Meridium APM system will attempt to populate each field with the
corresponding value in the Capacity History record that is linked to the specified
Generation Unit record for the month in which the incident occurred.
2. If the associated Capacity History record does not exist or does not contain a
value in a given field, the Meridium APM system will attempt to populate the
field with the corresponding value in the Generation Forecast record that is
linked to the specified Generation Unit record for the month in which the incident
occurred.
3. If a Generation Forecast record does not exist or does not contain a value in a
given field, the Meridium APM system will attempt to populate the field with the
corresponding value in the Generation Unit record.
4. If the Generation Unit record does not contain a value in a given field, that field
will NOT be populated automatically.
Note that:
These fields are populated automatically only when a Primary Capacity Incident
record is first created. After the record exists, the Unit ID field is disabled. Since
this value cannot be modified, these fields will never be updated automatically.
Fields in new Contributing Capacity Incident records are populated using these
same rules. In other words, fields in Contributing Capacity Incident records will
NOT necessarily be populated with the same values that exist in the Primary
Capacity Incident record. Instead, they will be populated with the values that exist
in the Capacity History, Generation Forecast, and Generation Unit record at the
time the Contributing Capacity Incident record is created.
The following tables provides a list of fields in Incident records that are populated in this
way and specifies the corresponding fields in Capacity History, Generation Forecast, and
Generation Unit records that will be used to populate them.
Incident Record
Capacity History
Record
Generation Forecast Generation Unit

Record
Record
GADS Unit Code
GADS Unit Code
GADS Unit Code
GADS Unit Code
GADS Unit Type
Unit Type
GADS Unit Type
GADS Unit Type
GADS Utility Code
GADS Utility Code
GADS Utility Code
GADS Utility Code
Gross Dependable
Capacity
Gross Dependable
Capacity (G)
Forecast Depend
Capacity (G)
Gross Dependable
Capacity
Gross Maximum
Capacity
Gross Max Capacity Forecast Maximum

(G)
Capacity (G)
Gross Maximum
Capacity
Net Dependable
Capacity
Net Dependable
Capacity (N)
Forecast Depend
Capacity (N)
Net Dependable
Capacity
Net Maximum
Capacity
Net Maximum
Capacity (N)
Forecast Maximum
Capacity (N)
Net Maximum
Capacity
Unit Name
Unit Name
Unit Name
Unit Name
Starting a Root Cause Analysis for an

Incident
The Meridium APM Framework offers the Root Cause Analysis module, which allows
you to conduct a root cause analysis (RCA) to evaluate and determine the root cause of
equipment failures. By creating an RCA Analysis in Root Cause Analysis, you can
determine the root cause of an incident and implement actions to prevent future incidents
from occurring.
To start building a PROACT Analysis for an incident:
1. Search for and open in the Record Manager the Primary Capacity Incident record
that contains data about the incident for which you want to create an RCA
Analysis.
2. On the Associated Pages menu, click the RCA link, and then click RCA Analysis
Builder.
The New Analysis Builder appears.
You can use the New Analysis Builder to create a PROACT analysis based on your
incident data.
About Capacity History Records

Capacity History records store statistical data about capacity incidents and fuel
consumption for a particular unit within a given month of a specific year. Each Capacity
History record should be linked to the Generation Unit record that represents the unit for
which the Capacity History record stores data. For a given Generation Unit record, one
Capacity History record should exist for each month and year combination for which data
exists.
The values in Capacity History records are used for reporting incident data to NERC and
fuel consumption data to the EIA. All capacity incident and generation statistics are
calculated using the calculations defined by NERC in the GADS DRI. For fields that are
neither calculated nor populated automatically by Meridium APM but are required for
reporting, you will need to collect the data and enter values into the fields manually if
you want that information to be reported.
Capacity History records can be created in two ways. You can:
Allow the Meridium APM system to create Capacity History records

automatically.
Create Capacity History records manually.
After Capacity History records exist, they will need to be updated manually on a regular
basis to ensure that all values within the records are up-to-date before that information is
reported.
How Capacity History Records Are

Created Automatically
For a given Generation Unit record, if a Capacity History record does not already exist
for a given month and year combination, when you create a Primary Capacity Incident
record for that month and year and link it to that Generation Unit record, a Capacity
History record will be created automatically. The Primary Capacity Incident record will
be linked to the Capacity History record that stores statistics for the month and year in
which the incident occurred.
Note: The Meridium APM system checks for an existing Capacity History record using
the values in the Reporting Month and Reporting Year fields in Capacity History and
Primary Capacity Incident records.
This automatic creation occurs only when you create the first Primary Capacity Incident
record for a Generation Unit record for a given reporting month and year and a Capacity
History record does NOT already exist. If a Capacity History record already exists for a
given month and year, when you create a Primary Capacity Incident record for the same
Generation Unit record for that reporting month and year, another record will NOT be
created. Instead, the Meridium APM system will link the new Primary Capacity Incident
record to the existing Capacity History record. In this way, the Meridium APM system
will use the Capacity History record for that unit, month, and year combination to
calculate values based upon the ALL Primary Capacity Incident records that exist for the
same Generation Unit record for the same reporting month and year.
Note: Calculations in Capacity History records will NOT be updated automatically as
new Primary Capacity Incident records are created. Instead, at the end of the reporting
period, Capacity History records must be updated manually to account for all the
incidents that occurred during that period.
About Creating Capacity History

Records Manually
In addition to being created automatically, Capacity History records can be created
manually. You might create these records manually for a couple reasons, such as:
You allowed Capacity History records to be created automatically as Primary

Capacity Incident records were created. At the end of the reporting period,
however, before you can start reporting data, you may need to create Capacity
History records for months in which incidents did NOT occur.
At the beginning of a reporting period, you want to create ALL the Capacity
History records for each month in that reporting period. This way, at the end of
the reporting period, you will know that you have all the Capacity History records
that you need for reporting data. You simply need to update them before you
report the data.
While you are not required to have a Capacity History record for every month in a
reporting period before you can report data, data will be reported only for the months for
which Capacity History record exist. So if you need to report data for a given month, you
will need to make sure that the Capacity History record has been created and is up-todate.
Creating Capacity History Records that

Exclude OMC Events
Some incidents, such as a power outage that occurred as the result of a thunderstorm, are
not preventable. These types of incidents are considered to be outside management
control (i.e., OMC events). Other preventable incidents, such a loss in generation
capacity that resulted from an equipment failure or operator error are considered to be
within management control.
All incident data, regardless of its cause, must be reported to NERC. For internal tracking
purposes, however, you may not be concerned with statistics associated with incidents
that could not be avoided. Instead, you may want to review data associated with incidents
that could have been avoided since these are the incidents from which strategies could be
developed to prevent future, similar incidents. In other words, only the incidents that are
within management control represent potential cost savings.
The Meridium APM Framework provides you with the option of collecting a separate set
of statistics for the events that are within management. To do so, you must complete two
steps:
1. In Generation Unit records, set the Create Outside Management Control
Statistics? field to True.
2. In any Incident record that represents an incident outside management control, set
the OMC Event? field to True.
Whenever the Create Outside Management Control Statistics? field in a Generation Unit
record is set to True, two Capacity History records will exist for each reporting month and
year.
One record will include values from ALL Incident records, regardless of the value
in the OMC Event field in the Primary Capacity Incident record that is linked to
the Capacity History record. The Capacity History Statistics Type field in this
Capacity History record will contain the value All Incidents.
The other record will exclude values from Incident records in which the OMC
Event field is set to True. The Capacity History Statistics Type field in this
Capacity History record will contain the value Excludes OMC Incidents.
Note: If the Create Outside Management Control Statistics? field in a Generation Unit
record is set to False, only ONE Capacity History record will be created for each month
and will include calculations for ALL incidents, regardless of the value in the OMC Event
field.
Note that:
Capacity History records that exclude data for OMC events will be created when
Capacity History records are created automatically IF the Create Outside
Management Control Statistics? field in the Generation Unit record is set to True
at the time the Capacity History record is created. They will also be created
automatically with Capacity History records are updated, if the Create Outside
Management Control Statistics? field in the Generation Unit record is set to True
and the Capacity History records that exclude data for OMC events do not already
exist.
The Meridium APM system will always use the Capacity History record that
contains the value All Incidents in the Capacity History Statistics Type field for
reporting data to NERC.
Fuel Code Fields

The fuel code fields in Capacity History records correspond to the fuel code fields in
Generation Unit records and are populated automatically with the corresponding values
in the Generation Unit records to which they are linked.
In Capacity History records, fuel codes are stored within 16 distinct fields. While these
fields appear as 16 separate cells on the Capacity History datasheet, the names of the cells
do not correspond exactly to the names of the field captions. Throughout this
documentation, we use the field captions when referring to these fields. Therefore, the
following table maps the datasheet cell to the field caption.
Field Caption
Datasheet Tab
Datasheet Row
Primary Fuel
AER Fuel Type Code
Secondary Fuel
AER Fuel Type Code
Tertiary Fuel
AER Fuel Type Code
Quaternary Fuel
AER Fuel Type Code
Common Fuel Code 1
Primary Fuel
Common Fuel Code
Common Fuel Code 2
Secondary Fuel
Common Fuel Code
Common Fuel Code 3
Tertiary Fuel
Common Fuel Code
Common Fuel Code 4
Quaternary Fuel
Common Fuel Code
EIA Energy Source 1
Primary Fuel
EIA Energy Source Code
EIA Energy Source 2
Secondary Fuel
EIA Energy Source 3
Tertiary Fuel
EIA Energy Source 4
Quaternary Fuel
Primary Fuel Code
Primary Fuel
Primary Fuel Code
Quaternary Fuel
Secondary Fuel Code
Secondary Fuel
Secondary Fuel Code
Tertiary Fuel Code
Tertiary Fuel
Tertiary Fuel Code
Fuel Information Fields

In addition to the fuel code fields, which define the fuel itself, Capacity History records
use several fuel information fields to store information about how a fuel is used. Like fuel
code fields, there is a separate set of fuel information fields for each fuel level.
For example, the Primary Quantity Burned field is used to identify how much of the
primary fuel was used. Similarly:
The Secondary Quantity Burned field identifies how much of the secondary fuel
was used.
The Tertiary Quantity Burned field identifies how much of the tertiary fuel was
used.
The Quaternary Quantity Burned field identifies how much of the quaternary fuel
was used.
The following fields in Capacity History records have four versions, one for each fuel
level, where <Fuel Level> is Primary, Secondary, Tertiary, Quaternary, depending on the
fuel level for which the field exists:
<Fuel Level> Ash Softening Temp

<Fuel Level> Average Heat Content
<Fuel Level> Fuel BTUs - Contract
<Fuel Level> Fuel BTUs - Electrical Generation
<Fuel Level> Fuel BTUs - Plant Heat and Cooling
<Fuel Level> Fuel BTUs - Process Steam
<Fuel Level> Fuel BTUs Total
<Fuel Level> Grindability Index/Percent Vanadium
<Fuel Level> Percent Alkalines
<Fuel Level> Percent Ash
<Fuel Level> Percent Moisture
<Fuel Level> Percent Sulfur
<Fuel Level> Quantity Burned
<Fuel Level> Quantity Burned Unit of Measure
For example, consider the following image of the Primary Fuel tab of the baseline
Capacity History datasheet.
When you specify a value in the Primary Fuel Code cell, that value will be stored in the
Primary Fuel Code field. When this field is populated with a value, the fuel information
Primary Quantity Burned Unit of Measure will be populated automatically. The EIA
Energy Source Code, AER Fuel Type Code, and Common Fuel Code fields will store the
fuel code for the other fuel schemes for the primary fuel.
The corresponding fuel information fields are also displayed on this tab and contain
information about the primary fuel, which is defined by the value in the Primary Fuel
Code field. Note that these fields are not calculated automatically like most of the other
fields in Capacity History records. You will need to collect this information outside of
Meridium APM and enter the correct values into these fields manually.
Inactive Hours Field

The Meridium APM system calculates the time between the values in the Event Start
Date and the Event End Date fields in each Primary Capacity Incident record and stores it
in the Event Duration field of the Primary Capacity Incident record. The value in the
Event Duration field will be used to populate the Inactive Hours field in the Capacity
History record that is linked to the Primary Capacity Incident record IF the Capacity
Event Type field in the Primary Capacity Incident record contains one of the following
values:
IR Inactive Reserve
MB Mothball
RU Retired
If multiple Primary Capacity Incident records are linked to a Capacity History record,
then the sum of the values in the Event Duration field in ALL Primary Capacity Incident
records will be used as the total event duration. This calculated value is then used to
populate the Inactive Hours field.
Consider the following example.
Primary Capacity
Incident - Inactive
Reserve (IR)
Primary Capacity
Incident - Mothball
(MB)
Primary Capacity
Incident - Retired
(RU)
Event Start
01/01/2009 12:00
AM
01/02/2009 12:00
AM
01/03/2009 12:00
AM
Event End
01/02/2009 12:00
AM
01/03/2009 12:00
AM
01/04/2009 12:00
AM
In this example, the event duration for each Primary Capacity Incident record is 24 hours.
In the Capacity History record for January 2009 for the Generation Unit record to which
these three Primary Capacity Incident records are linked, the Inactive Hours field would
contain the sum of the duration of these three incidents, or 72 hours.
What Happens When an Outage Event

and a Derate Event Overlap?
In Capacity History records, the Total Eqv Derate Hrs (N) and Total Eqv Derate MWh
(N) fields store the sum of the values in the Total Equivalent Derate Hours w/out
Shadowing and Total Equivalent Derate MWh w/out Shadowing fields in all Primary
Capacity Incident records for a given reporting month and year. If an outage event
overlaps a derate event, the values in the Total Eqv Derate Hrs (N) and Total Eqv Derate
MWh (N) will NOT include derate data for the time during which the outage event was
also occurring.
Consider an example of two Primary Capacity Incident records, Primary Capacity
Incident - Outage and Primary Capacity Incident - Derate, whose fields are populated as
shown in the following table. Assume that both Primary Capacity Incidents records are
linked to the Generation Unit record Generation Unit 1, which has a Gross Dependable
Capacity of 600 MW and a Net Dependable Capacity of 500 MW.
Primary Capacity Incident - Primary Capacity Incident Outage

Derate
Capacity Event Type
U1
D1
Event Start
11/1/2008 12:00 PM
11/2/2008 12:00 PM
Event End
11/4/2008 12:00 AM
11/5/2008 12:00 PM
Gross Available Capacity
500
Net Available Capacity
400
Event Duration
60
72
Total Equivalent Derate

Hours w/out Shadowing
14.4
Total Equivalent Derate

MWh w/out Shadowing
7200
The date range established by the values in the Event Start Date and Event End Date
fields of the two Primary Capacity Incident records overlap between 11/02/2008 12:00
P.M. and 11/04/2008 12:00 A.M., or 36 hours. So although the derate event lasted 72
hours total, for 36 of those hours, an outage event was also occurring.
In this example, if the entire derate event were included in the Capacity History
calculations, in the Capacity History record for November 2008 that is linked to
Generation Unit 1, the following values would be calculated and stored in the Capacity
History record:
Total Eqv Derate Hrs (N): 14.4

Total Eqv Derate MWh (N): 7200
Because an outage event was occurring during 36 hours of the derate event, however,
half of the derate event is NOT counted, and the values in the Capacity History record
become:
Total Eqv Derate Hrs (N): 7.2

Total Eqv Derate MWh (N): 3600
How Capacity Event Types Affect

Capacity History Records
In Capacity History records, the following fields are populated using the sum of the
values in the Event Duration field in Primary Capacity Incident records that are linked to
the Capacity History record:
Planned and Ext Outage Hrs: Populated using the sum of the values in the Event
Duration field in Primary Capacity Incident records in which the value in the
Capacity Event Type field is either PE or PO.
Ext Sched Outages Hrs: Populated using the sum of the values in the Event
Duration field in Primary Capacity Incident records in which the value in the
Capacity Event Type field is any of the following Capacity Event Types: ME,
DM, PE, SE, DE, or DP.
Eqv Upl Frcd Derate Hrs RS (G) and Eqv Upl Frcd Derate Hrs RS (N): Populated
with calculated values when the Primary Capacity Incident records to which it is
linked have a Capacity Event Type of D1, D2, D3, D4, PD, or RS with values
entered for both the Gross Derate Amount and the Net Derate Amount in the
following cases:
If a Reserved Shutdown event occurred during a Derate event.
If a Derate event occurred during a Reserved Shutdown event.
A Derate event started and ended during a Reserved Shutdown event.
A Derate event started during a Reserved Shutdown event but ended after
the Event End date of the Reserved Shutdown.
A Derate event and a Reserved Shutdown event had the same Event Start
and Event End dates.
Note: If none of the following cases have occurred during the month for which the
Capacity History record stores generation data, the Eqv Upl Frcd Derate Hrs RS (G) and
Eqv Upl Frcd Derate Hrs RS (N) fields will be populated with the value 0 (zero).
Workflow for Reporting Data

One of the main purposes of the Generation Management module is to report the data
that you have collected about capacity incidents and fuel consumption to the necessary
organizations. Meridium APM provides options for letting you report data to the Energy
Information Administration (EIA) and to the North American Electric Reliability
Corporation (NERC). Your company policies and the requirements of each organization
will determine whether you need to report data to the EIA, to NERC, or to both. The
workflow described in this topic supports reporting to one or both of these organizations.
To report data to the EIA and/or NERC, we recommend that you complete the following
steps:
1. Approve Incident records.
2. Update Capacity History records.
3. Approve Capacity History records.
4. Report data to the desired organization:
The Energy Information Administration.
The North American Electric Reliability Corporation.
This workflow represents the steps that should be followed for a given reporting period,
which is the period of time for which you are reporting data to a given organization. The
reporting period will be determined by your company policies and the requirements of
the organization to which you are reporting. If you need to report data to both
organizations using different reporting periods, simply follow these steps at the end of the
reporting period defined for each organization.
About Approving Incident Data

In most cases, after incident data has been recorded in Incident records and incident
statistics have been gathered in Capacity History records, you will need to report that data
to NERC. Before you report the data, we recommend that you approve it. The approval
process allows you to review the information in these records before you report the data.
The baseline Meridium APM Framework provides two approval levels for Incident
records:
Unit Level Approval: Intended to be used at the unit level for approving all
incidents associated with that unit.
Corporate Approval: Intended to be used at the corporate level for approving all
incidents for ALL units.
The recommended workflow for approving Incident records assumes that you will use
both of these approval levels. It also assumes that because Contributing Capacity Incident
records are linked to Primary Capacity Incident records, you will approve a Primary
Capacity Incident record after you have approved all the Contributing Capacity Incident
records that are linked to it.
When approving Incident records, note that certain actions can only be completed by
members of certain Security Groups. Only members of the MI Generation Management
Administrator or MI Generation Management Analyst Security Group can set a record's
approval level to or lower it from Unit Level Approval, while only members of the MI
Generation Management Administrator Security Group can set a record's approval level
to or lower it from Corporate Approval.
Also consider the following notes for setting or modifying approval levels for Incident
records:
All required fields, as defined in the Configuration Manager, must contain a value
before you can change the approval level.
When an Incident record is set to Corporate Approval, all fields within that record
become disabled. If you decide that you need to modify any of the values in the
Incident record, you will have to change the approval to a lower level.
To approve an Incident record, one of the following conditions must be met:
The Gross Max Capacity (G) AND Gross Dependable Capacity (G) must
contain a value.
-or
The Net Maximum Capacity (N) AND Net Dependable Capacity (N) must
contain a value.
Note: You can also approve an Incident record if all four of these fields contain a value.
When you report incident data to NERC, the Meridium APM system actually gathers
information from Capacity History records to build the report results. So approving
Incident records is just the first step in the process. After you have approved all the
Incident records for a given reporting period, you will want to update all the Capacity
History records that are associated with them and approve those records as well.
Incident Record Approval Workflow

To approve Incident records, complete the following steps:
1. Identify all Primary Capacity Incident records for the reporting period.
2. Set all Contributing Capacity Incident records that are linked to those Primary
Capacity Incident records to Unit Level Approval.
3. Set the Primary Capacity Incident records that you identified in step 1 to Unit
Level Approval.
4. Set all Contributing Capacity Incident records that you identified in step 2 to
Corporate Approval.
5. Set all Primary Capacity Incident records that you identified in step 1 to
Corporate Approval.
Restrictions When Approving Incident

Records
Because of the Incident Record approval workflow, there are some general restrictions
that specify when Capacity History records may be approved and when they may be
modified. Note the following when approving:
In order to enter new values or modify existing ones in fields on an Incident

record, it may be necessary to revert the status from Corporate Approval to Unit
Approval. This will mean that you will be changing the approval level from a
higher level, Corporate Approval, to a lower level, Unit Approval.
Approving Contributing Capacity

Incident Records
To approve a Contributing Capacity Incident Record:
1. In the Record Manager, open the Contributing Capacity Incident record that you
want to approve.
2. In the Incident Reporting Status list, select either Unit Level Approval or
Corporate Approval, depending on your responsibility within the company.
The record is saved with the selected approval level, along with any other changes that
you made to the Contributing Capacity Incident record.
Approving Primary Capacity Incident

Records
To approve a Primary Capacity Incident Record:
1. In the Record Manager, open the Primary Capacity Incident record that you want
to approve.
2. In the Incident Reporting Status list, select either Unit Level Approval or
Corporate Approval, depending on your responsibility within the company. Note
that:
If the value in the Incident Validation Status field contains the value
INVALID, when you select Unit Level Approval in the Incident Reporting
Status list, an error message appears, indicating that you must resolve the
invalid information before you can approve the record.
When you select either Unit Level Approval or Corporate Approval, the
Cause Code field will become required. Note that the Cause Code list will
not contain any values until the values in the Cause Code System and
Cause Code Component fields have been specified.

The record is saved with the selected approval level, along with any other changes that
you made to the Primary Capacity Incident record.
Why Do I Need to Update Capacity

History Records?
When a Capacity History record is created automatically, it will be populated
automatically with various values. When you create a Capacity History record manually,
it will be populated with the values that you specified when you created it.
Regardless of how the record was first created, after it exists, it will NOT be updated
automatically by the Meridium APM system. Because values in Capacity History records
will be used in reports, before you begin reporting incident and fuel consumption data,
you will want to make sure that all the Capacity History records for that reporting period
are up-to-date.
There are two steps that you will need to perform to make sure that all Capacity History
records are fully up-to-date for a given reporting period:
1. Update calculated values.
2. Update non-calculated values.
Note: These steps assume that all the Capacity History records for a given reporting
period have already been created.
Updating Calculated Values in Capacity

History Records
When a Capacity History record is first created, the Meridium APM system populates it
using the most current data available. If additional Primary Capacity Incident records are
created for the same Generation Unit record for the same reporting month and year
combination, those Primary Capacity Incident records will be linked automatically to the
Capacity History record, but the Capacity History record will NOT be updated
automatically to reflect the data in the new Primary Capacity Incident records. To make
sure that Capacity History records contain the most current data, you must update them
manually.
Note: In some cases, two Capacity History records may exist for a given reporting month
and year. In this case, when either Capacity History record is updated, the other one will
also be updated.
You can update the calculated fields in Capacity History records by:
Clicking the Perform Incident Rollup link on the Associated Pages menu when
you are viewing a Primary Capacity Incident record in the Record Manager. In
this case, the Meridium APM system will update any Capacity History record that
exists for that reporting month and year.
Selecting the Refresh Incident Rollup check box on the Identification tab of a
Capacity History record.
Running the query History Rollup Query, which the Meridium APM system
supplies for this purpose.
The following instructions provide details on updating Capacity History records using the
query History Rollup Query.
To update a Capacity History record:
1. On the Meridium APM toolbar, click the Catalog button.
Management\Configuration, and double-click the query History Rollup Query.
The Enter parameter values dialog box appears.
3. In the Plant ID text box, type the Plant ID of the Generation Plant record whose
Capacity History records you want to update. The Generation Plant record must
be linked to a Generation Unit record, and that Generation Unit record must be
linked to Primary Capacity Incident records that are linked to the Capacity
History records that you are going to update.
4. In the Unit ID text box, type the Unit ID of the Generation Unit record whose
Capacity History records you want to update. The Generation Unit record must be
linked to Primary Capacity Incident records that are linked to the Capacity
History records that you are going to update.
5. In the Start Month text box, type the first month in the period of time associated
with the Capacity History records that you want to update. For example, if the
Capacity History records contain 08 in the Reporting Month field, type 08.
6. In the End Month text box, type the last month in the period of time associated
with the Capacity History records that you want to update.
7. In the Start Year text box, type the first year in the period of time associated with
the Capacity History records that you want to update. For example, if the
Capacity History records have 2006 in the Reporting Year field, type 2006.
8. In the End Year text box, type the last year in the period of time associated with
the Capacity History records that you want to update.
9. Click OK.
A message appears, indicating the number of Capacity History records that will be
updated.
Note: If you typed invalid data or left any prompt fields blank, the message will indicate
that 0 (zero) records will be updated.
All Capacity History records that are associated with the criteria that you entered in the
prompts are updated.
Updating Non-Calculated Values in

Capacity History Records
Certain fields in Capacity History records are not populated or calculated automatically.
For example, many of the fuel information fields that are used for reporting data to the
EIA are not populated by Meridium APM. And while some of the fields that are included
in NERC reports are calculated by the Meridium APM system, others are not.
When you generate EIA or NERC reports, if you want any non-calculated value to be
included, you will need to populate the Capacity History record with the correct value
manually.
You should verify the accuracy of the values in all fields in the Capacity History record
before you approve it.
About Approving Capacity History

Records
When you report data to NERC and to the EIA, the data included in the reports comes
directly or indirectly from Capacity History records. For this reason, we recommend that
you approve Capacity History records before you report the data to the NERC or to the
EIA. Approving Capacity History records allows you to review the information in those
records before you report the data for a given reporting period.
The baseline GM module provides two approval levels for Capacity History records:
Unit Level Approval: Intended to be used at the unit level for approving all data
associated with that unit.
Corporate Approval: Intended to be used at the corporate level for approving all
data for all units.
We recommend that you use both approval levels by first setting Capacity History records
to Unit Level Approval and then setting them to Corporate Approval. Additionally, we
recommend that you update Capacity History records before approving them. We also
recommend that you approve any Primary Capacity Incident records that are linked to a
Capacity History record before approving it.
When approving Capacity History records, note that certain actions can only be
completed by members of certain Security Groups. Only members of the MI Generation
Management Administrator or MI Generation Management Analyst Security Group can
set a record's approval level to or lower it from Unit Level Approval, while only members
of the MI Generation Management Administrator Security Group can set a record's
approval level to or lower it from Corporate Approval.
Also consider the following notes for setting or modifying approval levels for Capacity
History records:
All required fields, as defined in the Configuration Manager, must contain a value
before you can change the approval level.
When a Capacity History record is set to Corporate Approval, all fields within that
record become disabled. If you decide that you need to modify any of the values
in the Capacity History record, you will have to change the approval to a lower
level.
Before you can set a Capacity History record to Unit Level Approval or Corporate
Approval, the Gross Actual Generation (G) and Net Actual Generation (N) fields
must contain values.
To set or change the approval level when the value in the Actual Generation field
is greater than 0 (zero), the value in the Service Hours field must also be greater
than 0 (zero).
You cannot approve a Capacity History record that is linked to a Primary Capacity
Incident record with the value Invalid in the Incident Validation Status field.
To approve a Capacity History record, one of the following conditions must be

met:
The Gross Max Capacity (G) AND Gross Dependable Capacity (G) must
contain a value.
-or
The Net Maximum Capacity (N) AND Net Dependable Capacity (N) must
contain a value.
Note: You can also approve a Capacity History record if all four of these fields contain a
value.
Approving Capacity History Records

To approve a Capacity History record:
1. Open the desired Capacity History record in the Record Manager.
2. In the Reporting Status list, select the desired level of approval.
3. Supply values in the appropriate fields as needed.
The Capacity History record is saved with the selected approval level.
How to Report Data to the EIA

After you have collected fuel consumption data for the units in your company, you may
need to report that data to the EIA. The following workflow provides the steps that you
need to complete to report data after it has been collected and approved.
To report data to the EIA:
1. Create Generation Fuel Annual Report records or Generation Fuel Monthly
Report records for each plant in the company for which you want to report fuel
consumption data for that year or month.
2. Run the associated EIA report.
3. Send the report results to the EIA. The results of the EIA reports contain the
information required by the EIA in the format that they prefer. After you have run
the reports, you can print them out and mail them to the EIA, export the results
and send them electronically, or provide the information in another way, as
specified by the EIA.
IMPORTANT: Before you complete these steps, you should repeat all preliminary steps
outlined in the overall reporting workflow.
What Data Will Be Reported to the

EIA?
You can run EIA reports to generate reports about the fuel usage of units in a given plant.
EIA reports collect data from generation fuel report records. To make sure that your
records contain the data that you need to report to the EIA, you will need to make sure
that your generation fuel report records contain the correct information. The following
fields in generation fuel report records will be included in EIA reports:
Address 1
Address 2
City
Comments
Energy Source Code
Energy Source Consumption
Gross Generation of Electricity
Heat Content Per Unit of Fuel
Net Generation of Electricity
Prime Mover
Quantity on Hand
Report Status
Report Submitted Date
Reporting Month
Reporting Year
Respondent ID
Respondent Name
State
Survey Contact 1 Email
Survey Contact 1 Fax Number
Survey Contact 1 Name
Survey Contact 1 Phone
Survey Contact 1 Title
Survey Contact 2 Email
Survey Contact 2 Fax Number
Survey Contact 1 Name
Survey Contact 2 Phone
Survey Contact 2 Title
Type of Respondent
Zip Code
Note: Much of the data that is included in generation fuel report records comes from
Capacity History records. For this reason, before you create generation fuel report
records, we recommend that you update and approve all the Capacity History records for
a given reporting period. This will help ensure that the generation fuel report records
contain accurate information.
About Generation Fuel Report Records

Generation fuel report records can be used to run generation fuel reports to report fuel
consumption data to the EIA. Much of the data included in generation fuel report records
comes from Capacity History records. Therefore, after you have approved all the
Capacity History records for a given plant in a given reporting period, you can create:
Generation Fuel Monthly Report Records: For a given plant, these records store
information about the fuels used by units for a particular month. If you report data
to the EIA on a monthly basis, you will create one Generation Fuel Monthly
Report record per month for each fuel type used by the units in a plant.
Generation Fuel Annual Report Records: For a given plant, these records store
information about the fuels used by units for an entire year. If you report data to
the EIA on a yearly basis, you will create one Generation Fuel Annual Report
record per year for each fuel type used by the units in a plant.
Generation Fuel Monthly Report and Generation Fuel Annual Report records share many
of the same characteristics and are used for largely the same purpose. Therefore,
throughout this documentation, we refer to Generation Fuel Annual Report and
Generation Fuel Monthly Report records collectively as generation fuel report records.
Each generation fuel report record is linked to a Generation Plant record and collects the
fuel data for units represented by Generation Unit records that are linked to that
Generation Plant record and meet the following criteria:
Contain a value in one of the EIA Energy Source <1, 2, 3, 4> fields that matches
the value in the Energy Source Code field in the generation fuel report record.
-and
Contain a value in the EIA Prime Mover Type field that matches the value in the
Prime Mover field in the generation fuel report record.
-and
Contain the value True in the Report EIA906 Annually? field (for Generation Fuel
Annual Report records) or Report EIA906 Monthly? field (for Generation Fuel
Monthly Report records).
How Many Fuel Report Records Do I

Need for Reporting Data?
The number of records that you need to create for a given reporting period will depending
upon the how many types of fuel were used during that reporting period and the amount
of time in the reporting period itself. Because four EIA Energy Source fields exist in
Generation Unit records, up to four fuel types can be defined for a given unit. So, if a
plant has one unit that uses four types of fuel, you would need to create four Generation
Fuel Report Monthly records to report the monthly fuel usage for that plant. If a plant has
more than one unit, each of which uses more than one fuel type, you may need to create
many more records.
Consider the example of a Generation Plant record, Generation Plant 1, which represents
a plant that contains three units, represented by the Generation Unit records, Generation
Unit 1, Generation Unit 2, and Generation Unit 3. These Generation Unit records store
information about the fuel used by the units, as shown in the following table. Each
column in the table represents one of the Generation Unit records, and each row
represents a field in each record.
Generation Unit 1
Generation Unit 2
Generation Unit 3
GADS Unit Type
Fossil-Steam (100)
Fossil-Steam (100)
Fossil-Steam (100)
EIA Prime Mover
Steam Turbine (ST)
Steam Turbine (ST)
Combined cycle
Type
single shaft (CS)
EIA Energy Source 1
Bituminous Coal
(BIT)
Municipal Solid
Waste (MSW)
EIA Energy Source 2
Subbituminous Coal Bituminous Coal

(SUB)
(BIT)
Waste Heat (WH)
EIA Energy Source 3
Coal Based Synfuel

(SC)
Other BioMass Solids

(OBS)
EIA Energy Source 4
Other BioMass Solids Waste/Other Coal

(OBS)
(WC)
Petroleum Coke (PC)
Bituminous Coal
(BIT)
Municipal Solid
Waste (MSW)
Now, assume that each unit used each type of fuel during January 2009 and that you need
to report fuel consumption data for that month. In this case, you will need to create ONE
Generation Fuel Monthly Report record for each unique prime mover and fuel type
combination across all three Generation Unit records. In total, you would need to create
the following 11 Generation Fuel Monthly report records to store all of the fuel data for
these three units for January 2009:
Generation Plant 1 ~ 2009 ~ 01 ~ Steam Turbine (ST) ~ Bituminous Coal (BIT)

Generation Plant 1 ~ 2009 ~ 01 ~ Steam Turbine (ST) ~ Subbituminous Coal
(SUB)
Generation Plant 1 ~ 2009 ~ 01 ~ Steam Turbine (ST) ~ Coal Based Synfuel (SC)
Generation Plant 1 ~ 2009 ~ 01 ~ Steam Turbine (ST) ~ Other BioMass Solids

(OBS)
Generation Plant 1 ~ 2009 ~ 01 ~ Steam Turbine (ST) ~ Municipal Solid Waste

(MSW)
Generation Plant 1 ~ 2009 ~ 01 ~ Steam Turbine (ST) ~ Petroleum Coke (PC)
Generation Plant 1 ~ 2009 ~ 01 ~ Steam Turbine (ST) ~ Waste/Other Coal (WC)
Generation Plant 1 ~ 2009 ~ 01 ~ Combined cycle single shaft (CS) ~ Bituminous

Coal (BIT)
Generation Plant 1 ~ 2009 ~ 01 ~ Combined cycle single shaft (CS) ~ Waste Heat
(WH)
Generation Plant 1 ~ 2009 ~ 01 ~ Combined cycle single shaft (CS) ~ Other

BioMass Solids (OBS)
Generation Plant 1 ~ 2009 ~ 01 ~ Combined cycle single shaft (CS) ~ Municipal

Solid Waste (MSW)
Creating Generation Fuel Report

Records
To create a generation fuel report record:
2. In the list, select:
Generation Fuel Annual Report if you want to create a Generation Fuel Annual
Report record.
-OR
Generation Fuel Monthly Report if you want to create a Generation Fuel Monthly
Report record.
3. Click OK.
A new Generation Fuel Annual Report or Generation Fuel Monthly Report record
appears.
This image displays the baseline Fuel Monthly Report datasheet. The baseline Fuel
Annual Report datasheet is different from this datasheet, but the same required fields that
appear on the Monthly Values tab of the Fuel Monthly Report datasheet also appear on
the Annual Values tab of the Fuel Annual Report datasheet. These instructions provide
details on creating a new generation fuel report record using these baseline datasheets.
4. In the Plant ID list, select the ID of the Generation Plant record to which you want
to link the Generation Fuel Monthly Report record.
Note: When you select a value in the Plant ID list, many other fields will be populated
automatically with the appropriate values from the Generation Plant record that you
select.
5. In the Prime Mover list, select the prime mover of the units whose fuel data you
want to report that reside in the plant identified by the value in the Plant ID list.
6. In the Energy Source Code list, select the EIA energy source code of the fuel that
is used by the units whose data you want to report.
Note: After you select a value in the Energy Source Code list, the disabled fields AER
Fuel Type Code, Quantity Units of Measure, and Heat Content Unit of Measure are
populated automatically.
The generation fuel report record is created, linked to the Generation Plant record
identified by the value that you selected in the Plant ID list, and saved to the database.
Running EIA Reports

After you have a created a generation fuel report record for the report that you want to
send to the EIA, you must run a report to create a report that you can send to the EIA.
To run an EIA report:
Management\Reports.
3. Double-click the desired report.
The Enter Query Parameters dialog box appears.
4. In the Select the Company Name list, select, the name of the company for which
you want to report data to the EIA.
5. In the Select the Reporting Year list, select the year for which you want to report
data to the EIA.
6. Click OK.
The report appears on the Report Viewer page.
How to Report Data to NERC

For a given reporting period, after you have collected the data for the incidents that have
occurred at units, you may need to report that incident data to NERC. To do so, you can
run a NERC report to compile incident data and then send the output to NERC. In
Generation Management, a NERC report consists of two components:
A query that specifies which results should be returned.

A Generation NERC Report record that defines which query should be used for
returning results and allows the data to be formatted according to NERC's
specifications.
Note: A NERC report, as defined in the GM documentation, is NOT represented by a

report object in the Meridium APM Catalog. Rather, as explained above, it is the
combination of a query and a record that together create the report definition. To run the
report, you will execute the query through a link on the Associated Pages menu in the
Record Manager to see the formatted report results.
To report data to NERC, you must:
1. Locate the appropriate Generation NERC Report record and run the associated
report.
2. Send the report output to NERC.
IMPORTANT: Before you complete these steps, you should repeat all preliminary steps
outlined in the overall reporting workflow.
Types of NERC Reports

Meridium APM provides two types of NERC reports, each of which reports a different
set of data:
NERC Event Reports: Return data about capacity incidents. Meridium APM
provides the following baseline Generation NERC Report records that can be
used to generate NERC event reports:
NERC GADS Event Report 07: Returns event data in the 07 format
required by NERC.
NERC GADS Event Report 97: Returns event data in the 97 format
required by NERC.
NERC Performance Reports: Return data about unit performance. Meridium APM
provides the following baseline Generation NERC Report records that can be
used to generate NERC performance reports:
NERC GADS Performance Report 05: Returns performance data in the 05

format required by NERC.
NERC GADS Performance Report 95: Returns performance data in the 95
format required by NERC.
Each of the records in the preceding list uses a query of the same name stored in the
Catalog folder \\Public\Meridium\Modules\Generation Management\Queries\NERC
Queries.
What Data Is Included in Event

Reports?
Values from the following fields in capacity Incident records are included in NERC event
reports:
Amplification Code
Capacity Event Type
Cause Code
Dominant Derate
Event Contribution Code
Event End Date
Event Start Date
GADS Unit Code
GADS Utility Code
Verbal Description
Work Ended
Work Started
Note: In NERC event reports, the following values are gathered only from Primary
Capacity Incident records: Event End Date, Event Start Date, Work Ended, and Work
Started. Even if these values also exist in Contributing Capacity Incident records, those
values are not used.
What Data Is Included in Performance

Reports?
Values from the following fields in Capacity History records are included in NERC
performance reports:
Actual Unit Starts

Attempted Unit Starts
Available Hrs
<Fuel Level> Average Heat Content
Forced Outage Hrs
<Fuel Level> Fuel Code
GADS Unit Code
GADS Utility Code
<Fuel Level> Grindability Index
Gross Actual Generation (G)
Gross Dependable Capacity (G)
Gross Max Capacity (G)
Inactive Hours
Net Actual Generation (N)
Net Dependable Capacity (N)
Net Maximum Capacity (N)
Period Hours
<Fuel Level> Percent Alkalines
<Fuel Level> Percent Ash
<Fuel Level> Percent Moisture
<Fuel Level> Percent Sulfur
<Fuel Level> Quantity Burned
Reporting Month
Reporting Year
Reserve Shutdown Hrs
Revision
Service Hrs
Synchronous Condensing Hrs
Typical Unit Loading
Unavailable Hrs
Verbal Description
Options for Running NERC Reports

To run a NERC report, you open a Generation NERC Report record and run the
associated query. These records reference queries with the same names that are stored in
the Catalog folder \\Public\Meridium\Modules\Generation Management\Queries\NERC
Queries. Meridium APM gives you the option of:
Viewing the results on the Query Builder page.

Formatting the results as a text file in the format accepted by NERC. After you
run the report, you can send the results to NERC.
Viewing Report Results in the Query

Tool
To run the query used by a Generation NERC Report record:
2. In the Search In list, select Generation NERC Report, and then click Find Now.
3. From the search results, click the Record ID hyperlink of the desired record
whose query you want to run. This may be a baseline Generation NERC Report
record or a custom Generation NERC Report record.
The Generation NERC Report record appears in the Record Manager.
4. On the Associated Pages menu, click the Run link, and then click Query.
The results are displayed on the Query Builder page.
Formatting Report Results as a Text File

To run a Generation NERC Report and format the results into a text file:
2. In the Search In list, select Generation NERC Report, and then click Find Now.
3. From the search results, click the Record ID hyperlink of the record for which you
want to run a NERC report. This may be a baseline Generation NERC Report
record or a custom Generation NERC Report record.
4. On the Associated Pages menu, click the Run link, and then click Report.
The report query is run the results are sent to a text file. The Save Report As dialog box
appears.
Note: If a value exists in the Report File field of the Generation NERC Report record, the
Save Report As dialog box will NOT appear, and the text file will be saved automatically
to that location.
5. Specify a name for the text file, and save the file to the desired location.
6. Click the Save button.
The NERC Report is saved as a text file, which can be sent directly to NERC.
Why Do I Need to Customize NERC

Reports?
By default, the queries used to generate NERC event reports return results for ALL
Primary Capacity Incident and Contributing Capacity Incident records in the database.
Similarly, the queries used to generate NERC performance reports return results for ALL
Capacity History records in the database. If you want your report results to include a
subset of the data that is stored in the database, you will need to develop custom reports.
For example, you might want to add a filter that:
Limits report results to a particular month or unit.
Takes into account the value in the Report Capacity Data field in Generation Unit
records.
In Generation Management, each NERC report consists of two components:
A query that specifies which results should be returned.
A Generation NERC Report record that identifies the query and allows you to run
the report and format the results according to NERC's specifications.
Therefore, to create custom NERC reports, you must:

1. Create a custom query. As a starting point, you can use the baseline queries in the
Catalog folder \\Public\Meridium\Modules\Generation
Management\Queries\NERC Queries. Simply create a copy of the desired query,
make the necessary changes, and save the query with a new name.
2. Create a Generation NERC Report record that defines the custom query that you
created in step 1.
After you have developed custom reports, you can run them in the same way you run the
baseline reports.
Customizing the Baseline NERC

Queries
To develop a custom NERC report, you will need to create a custom query and then
define that query in a Generation NERC Report record. How you customize the query is
up to you and will depend upon the results that you want to include in the report output.
The following instructions provide an example of how you can customize the report
NERC GADS Event Report 97 by filtering the results on the Report Capacity Data field.
To customize a baseline NERC report query:
Management\Queries\NERC Queries.
3. Open the query NERC GADS Event Report 97.
If any existing Primary Capacity Incident records meet the query criteria, the query
results will appear.
4. On the Query Tasks menu, click the Design View link.
The query design appears, displaying the fields that are included by default in the query.
5. On the Query Tasks menu, click the Add Source link.
The Add Query Source dialog box appears.
6. Select the Generation Unit family from the list, and click the Add button.
7. Click the Links tab.
8. Select the Has Incident relationship family, and click the Add button.
9. Click the Close button.
The design canvas displays your selections.
10. In the list of fields that appear in the Generation Unit source, double-click Report
Capacity Data.
The Report Capacity Data field appears in the design grid.
11. In the Report Capacity Data column, in the Criteria cell, type ONE of the
following values:
'NERC'
'Internal'
'NERC and Internal'
'Do Not Report'
Hint: You will need to create a custom query for each distinct results set that you want to
generate. These instructions provide details on creating ONE query. You can repeat these
instructions to create additional queries.
12. On the Query Tasks menu, click the Run Query link.
The results are displayed.
13. On the Common Tasks menu, click the Save As link.
The Save Query As dialog box appears.
14. Type a name for the query. We recommend that you use a descriptive name that
indicates the type of filter you applied. For example, you could type NERC
GADS Event Report 97 NERC ONLY or NERC GADS Event Report 97 NOT
REPORTING, depending on the criteria that you used.
IMPORTANT: You must save the query to the Catalog folder
\\Public\Meridium\Modules\Generation Management\Queries\NERC Queries.

The query is saved with the new Report Capacity Data filter. When you create a new
Generation NERC Report record, this query will now appear in the list of values in the
Report Query cell.
Creating Generation NERC Report

Records
To create a Generation NERC Report record:
2. In the list, select Generation NERC Report.
3. Click OK.
A new Generation NERC Report record appears in the Record Manager.
4. In the Report Name cell, type a name for the report. The Report Name field is
required.
5. In the Report Type list, select Event or Performance. The value you choose in this
field will determine the values that are available in the Report Format cell. This
field is required.
6. In the Report Format list, select the desired format.
If the Report Type list is set to Event, the values available in the Report
Format list will be 97 and 07.
If the Report Type list is set to Performance, the values available in the
Report Format list will be 95 and 05.

7. In the Report Query list, select the query that corresponds to the value you
selected in the Report Format list. This field displays a list of queries that exist in
the Catalog folder \\Public\Meridium\Modules\Generation
Management\Queries\NERC Queries.
8. In the Report File cell, type the desired path for where you want the report to be
saved. This field is optional. If you do NOT specify a desired path, when you run
a report, the Save Report As dialog box will appear, where you can navigate to the
desired location of where you want to save.
Note: If the path specified is invalid, when you run the report, an error message appears.
The Generation NERC Report record is created and saved to the database. Afterwards,
the Run link is enabled on the Associated Pages menu.
Capacity History Associated Pages

The following Associated Page is configured by default for the Capacity History family:
Power Price by Zone: Displays the baseline Power Price Curve by Zone graph
where the zone is set to North. This Associated Page appears on the Pricing
submenu.
application.
Contributing Capacity Incident

Associated Pages
The following Associated Page is configured by default for the Contributing Capacity
Incident family:
Revision History: Displays the Revision History query in the Query Builder.
application.
Generation Nameplate Associated Pages

The following Associated Page is configured by default for all Generation Nameplate
subfamilies (it is NOT configured for the parent Generation Nameplate family):
application.
Generation NERC Report Associated

Pages
The following Associated Pages are configured by default for the Generation NERC
Report family.
Note: To see the underlying URL for each Associated Page, you can use the URL
Manager application.
Caption Description
Report
Displays the Save Report As dialog box, where you can export the report as a
text file. This Associated Page appears on the Run submenu.
Query
Displays the NERC GADS Performance Report 95 query in the Query Builder.
This Associated Page appears on the Run submenu.
Generation Unit Associated Pages

The following Associated Pages are configured by default for the Generation Unit family.
Caption
Description
Generation Pools
for this Unit
Displays the Show Generation Pools for this Unit query in the
Query Builder. This associated page appears on the Unit
Information submenu.
Revision History
Displays the Revision History query in the Query Builder.
Generation Unit Loading Profile

Associated Pages
The following Associated Page is configured by default for the Generation Unit Loading
Profile family:
application.
Generation Unit Starting Profile

Associated Pages
The following Associated Page is configured by default for the Generation Unit Starting
Profile family:
application.
Primary Capacity Incident Associated

Pages
The following Associated Pages are configured by default for the Primary Capacity
Incident family.
Caption
Create
Contributing
Incident
RCA Analysis
Builder
Description
Displays a new Contributing Capacity Incident record, which is linked
to the current Primary Capacity Incident record. The Unit ID field in
the Contributing Capacity Incident record is populated based on the
value in the Unit ID field in the Primary Capacity Incident record.
This Associated Page appears on the Create submenu.
Displays the New Analysis Builder, which you can use to build a new
RCA Analysis based on your incident data.
This Associated Page appears on the RCA submenu.
Updates calculated fields in all Capacity History that exist for the
Perform
reporting month and year that are associated with the current Primary
Incident Rollup
GM Catalog Folder Structure

The following table provides a list of the subfolders and items that exist in the Catalog
folder \\Public\Meridium\Modules\Generation Management.
Note: All the items in the Public folder are also available in the corresponding Baseline
folder.
Folder
Associated Page
Item Names
Revision History query
Behavior and Usage
You can run any of these

Show Generation Pools for this Unit queries to view the results
query
on the Query Builder page.
Create Company query
Create Plant query
Create Pool by Criteria query
Create Unit query
Configuration
History Rollup Query

List Units by Generation Pool query
The queries in this folder

can be used for creating
various GM records and
help facilitate various GM
workflows.
Resequence Incidents query

Unit List query
GadsCauseCodes query
Configuration\PlugIn
GMUNITS query
If desired, you can use

these queries with
Meridium APM Plug-In
for DataStage jobs.
Meridium APM does not,
however, supply the jobs
in the baseline product.
Explorers
Generation Nameplate Explorer

configured explorer
You can use this

configured explorer to
open Generation Unit
records.
Graphs
Power Price Curve graph
This graph displays a

graph of power prices for a
selected zone.
Availability Factor by Date and Plant

- All Incidents Metric View
Costs by Plant and Cause Metric
View
Metrics
Queries
EFOR (G) by Date and Plant - All

Incidents Metric View
You can open any of these

Metric Views to view the
results in the Results
Viewer.
EFOR (N) by Date and Plant - All

Incidents Metric View
Capacity History Records Changed in
the Last 30 days query
queries to view the results
Capacity History Revision query
Capacity Loss Summary by Plant
query
Capacity Summary by Unit query
Capacity Summary by Unit and Event
Type query
Capacity Summary listing by Unit
and Event Types query
Create Monthly Fuel Report Records
query
Field Value Changes for Capacity
History in Last 30 days query
Field Values Changes for Primary
Capacity Incident in Last 30 days

query
Forced Outage Incident Cost Pareto
query
Heating Range Values query
Incident Cost Pareto query
NERC GADS Report List query
Primary Capacity Cost by Unit and
Year query
Primary Capacity Incident Records
Changed in Last 30 days query
Query Units by Region query
Unit Nameplate Data query
Unit Startup Data query
Queries\Graph
Queries
Power Price Curve by Zone query
The Meridium APM

system runs this query
automatically when you
access the Power Price
Curve graph.
NERC GADS Event Report 07 query

NERC GADS Event Report 97 query
Queries\NERC
Queries
Queries\Report
Queries
These queries return data

using the corresponding
NERC GADS Performance Report 05
format for all Capacity
query
History or Capacity
Incident records.
NERC GADS Performance Report 95
query
Cause Code Impact Report query
Deratings Event Types by Cause
queries to view the results
Code query
EIA 906 Fuel Report Annual query
EIA 906 Fuel Report Monthly query

Monthly Capacity History and
Incident Query
Monthly Fuel Report - Quantity on
Hand query
MWh by Cause Code Report query
Reports

reports to view the results
on the Report Viewer page.
EIA 906 Fuel Report Monthly report The reports in this folder
are SQL Server Reporting
Services reports.
Searches
This folder is empty.
EIA 906 Fuel Report Annual report
N/A
The reports in the Reports

and SSRS folders contain
the same content. The
EIA 906 Fuel Report Monthly report Meridium APM system
does not use the SSRS
folder or its contents.
EIA 906 Fuel Report Annual report
SSRS
About the GM Field Reference

The Meridium APM Generation Management module consists almost entirely of
managing different types of records. By creating and updating records in GM, you will
collect the information that you need to report generation capacity and fuel consumption
data to NERC and the EIA. Therefore, it is important to understand the details of the
records that are used in GM.
This section of the documentation provides reference information about the fields in
various GM record families and provides descriptions of their behavior in the baseline
Generation Management module. You can use this information to help you further
understand and use Meridium APM Generation Management.
Note: The information in this section of the documentation is not comprehensive. It does
not include all GM families and may not describe every baseline field in detail.
APM Event
APM Event records can be used to track the total cost of an event represented by a
Primary Capacity Incident record. If your system has been configured to use work order
history data, the cost of work history events can be included in the Sum of Work History
Costs and Total Costs fields.
When you create a Primary Capacity Incident record that meets the conditions specified
by the value in the APM Event Creation field in the Generation Unit record to which the
new Primary Capacity Incident record is linked, an APM Event record will be created
automatically and linked to that Primary Capacity Incident record.
APM Event records contain various fields that store information about the events
represented by Primary Capacity Incident records. Each APM Event record is linked to a
single Primary Capacity Incident record and stores information about that incident. Most
of the values in an APM Event record are populated automatically using the values in the
Primary Capacity Incident record that is linked to the APM Event record and records
associated with that Primary Capacity Incident record.
The following table provides a list and description of the fields that are defined for the
APM Event family in the baseline Meridium APM database. The descriptions in the
following table reflect baseline behavior. Fields are listed in alphabetical order in the
following table; they may not appear or may appear in a different order on each
datasheet.
Note: The following list is not comprehensive and does not include all the fields that
exist in the APM Event family in the baseline Meridium APM database.
Field
APM Event Date
Description
A value that indicates when the event began. This field is populated
automatically using the value in the Event Start Date field in the
Primary Capacity Incident record that is linked to the APM Event
record.
APM Description A value that describes the APM event. You can type a description
APM ID
into this field.

A value that identifies the APM event. This field is populated
automatically using the following template:
APM~<Unit Name>~<Event Start Date>
...where:
<Unit Name> is the value in the Unit ID field in the

Generation Unit record that is linked to the Primary Capacity
Incident record for which the APM Event record exists.
<Event Start Date> is the value in the Event Start Date field
in the Primary Capacity Incident record that is linked to the
APM Event record.
Critical Event Flag A value that indicates if the event was a critical event. If the value in
this field is True, the event was a critical event. If the value in this
field is False, the event was NOT a critical event.
Plant ID
A value that indicates the plant in which the event occurred. This
field is populated automatically with the value in the Plant ID field
in the Generation Plant record that is linked to the Generation Unit
record that is linked to the Primary Capacity Incident record for
which the APM Event record exists.
Plant Name
A value that indicates the plant in which the event occurred. This
field is populated automatically with the value in the Plant name
field in the Generation Plant record that is linked to the Generation
Unit record that is linked to the Primary Capacity Incident record for
which the APM Event record exists.
Primary Capacity A value that indicates the capacity event type for the event. This
Event Description field is populated automatically with the value in the Capacity Event
Type Descr field in the Primary Capacity Incident record that is
linked to the APM Event record.
Primary Capacity A value that indicates the NERC event code for the capacity event
Event Type
type for the event. This field is populated automatically with the
value in the Capacity Event Type field in the Primary Capacity
Incident record that is linked to the APM Event record.
Primary Cause
A value that indicates the cause code for the event. This field is
populated automatically with the value in the Cause Code field in
the Primary Capacity Incident record that is linked to the APM

Event record.
Primary Cause
Description
A value that indicates the cause code description for the event. This
field is populated automatically with the value in the Cause Code
Description field in the Primary Capacity Incident record that is
linked to the APM Event record.
Primary Contact
A value that indicates the person responsible for information about

the APM event. You can type an alphanumeric value into this field.
Sum of Capacity
Loss Costs
A value that represents the cost of the event from lost generation
capacity. This field is populated automatically with the value in the
Capacity Incident Cost field in the Primary Capacity Incident record
that is linked to the APM Event record.
Sum of Work
History Costs
A value that represents the maintenance related cost of the event. If

your system has been configured to do so, this field can be
automatically populated using a work order history system.
A value that represents the total cost of the event. This field is
populated automatically using the following formula:
Total Costs
Sum of Capacity Loss Costs + Sum of Work History Costs

Unit ID
A value that indicates the unit to which the event occurred. This
field is populated automatically with the value in the Unit ID field in
the Generation Unit record that is linked to the Primary Capacity
Incident record for which the APM Event record exists.
Unit Name
A value that indicates the unit to which the event occurred. This
field is populated automatically with the value in the Unit Name
field in the Generation Unit record that is linked to the Primary
Capacity Incident record for which the APM Event record exists.
Capacity History
Capacity History family in the baseline Meridium APM database. In the following table,
note that:
The descriptions reflect baseline behavior.

Wherever we refer to the unit, we mean the unit represented by the Generation
Unit record to which the Capacity History record is linked.
Most fields are listed in alphabetical order by field caption. They may not appear
or may appear in a different order on each datasheet. Fuel information fields have
been sorted by ignoring the first word in the field caption (i.e., Primary,
Secondary, Tertiary, or Quaternary). For example, the fields <Fuel Level> Ash
Softening Temp are sorted alphabetically using only Ash Softening Temp.
The list of fields is not comprehensive and does not include all the fields that exist
in the Capacity History family in the baseline Meridium APM database.
Field
Description
Actual Unit Starts
Specifies the number of actual times the unit started within a given
month and year. When the value in the Reporting Status field is set
to Unit Level Approval, validation is performed on this field to
ensure that the value is equal to the number of Attempted Unit
Starts minus the number of Startup Failures.
AER Fuel Type

Code <1, 2, 3, 4>
Identifies the AER fuel type code for the primary, secondary,
tertiary, or quaternary fuel used by the unit. This field is populated
automatically with the value in the AER Fuel Type Code <1, 2, 3,
4> field in the Generation Unit record to which the Capacity
History record is linked.
<Fuel Level> Ash

Softening Temp
Identifies the ash softening temperature for a given fuel type. This
is an optional numeric field. This value is defined by NERC in the
GADS DRI.
Attempted Unit
Starts
Availability Factor
Specifies the number of attempted starts for the unit within a given
month and year. When the value in the Reporting Status field is set
to Unit Level Approval, validation is performed on this field to
ensure that the value is equal to the number of outage events that
occurred within the month that the Capacity History record
represents.
Indicates the percentage of total time in the unit was available.
This field is disabled and populated automatically using the
following formula:
(Available Hours / Period Hours) x 100
This value is defined by NERC in the GADS DRI.
Indicates the total number of hours in which the unit was available.
This field is disabled and populated automatically as the sum of the
values in the following fields:
Available Hours
Pumping Hrs
Reserve Shutdown Hrs
Service Hrs
Synchronous Condensing Hrs
This value is defined by NERC in the GADS DRI and included in

NERC performance reports.
<Fuel Level>
Average Heat
Content
For a given fuel type, indicates the heat content in BTUs per unit
of measure stored in the corresponding <Fuel Level> Quantity
Burned Unit of Measure field. This value is defined by NERC in
the GADS DRI.
Identifies the percentage of the total potential gross capacity that
was generated by the unit. This field is disabled and calculated
automatically using the following formula:
Capacity Factor (G) (Gross Actual Generation / (Period Hours x Gross Maximum
Capacity)) x 100
Identifies the percentage of the total potential net capacity that was
generated by the unit. This field is disabled and calculated
Capacity Factor (N) (Net Actual Generation / (Period Hours x New Maximum
Capacity)) x 100
Contains a value that indicates what type of data is stored in the
Capacity History record. This field can contain the following
values:
All Incidents: The Capacity History record contains data

calculated using data from all Primary Capacity Incident
records for a given unit for a given month and year
combination.
Excludes OMC Incidents: The Capacity History record

contains data using only Primary Capacity Incident records in
which the value in the OMC Event field is False.
Capacity History
Statistics Type
Identifies the common fuel code for the primary, secondary,

Common Fuel Code
automatically with the value in the Common Fuel Code <1, 2, 3,
<1, 2, 3, 4>
4> field in the Generation Unit record to which the Capacity
History record is linked.
Identifies the demonstrated gross maximum capacity of the unit.
This field is populated automatically with the value in the
Demonstrated Max
Demonstrated Gross Maximum Capacity field in the Generation
Capacity (G)
Unit record to which the Capacity History record is linked. This
value is defined by NERC in the GADS DRI.
Identifies the demonstrated net maximum capacity of the unit. This
field is populated automatically with the value in the Demonstrated
Demonstrated Max
Net Maximum Capacity field in the Generation Unit record to
Capacity (N)
which the Capacity History record is linked. This value is defined
by NERC in the GADS DRI.
Identifies the EIA energy source code for the primary, secondary,
EIA Energy Source
automatically with the value in the EIA Energy Source <1, 2, 3, 4>
<1, 2, 3, 4>
field in the Generation Unit record to which the Capacity History
record is linked.
<Fuel Level> Fuel
BTUs - Contract
Identifies the BTUs generated as a result of burning fuel of a given

type as part of a contract to external parties. This is an optional
numeric field. This value is defined by NERC in the GADS DRI.
<Fuel Level> Fuel

BTUs - Plant Heat
and Cooling
Identifies the BTUs generated for plant heating and cooling for a
given fuel type. This is an optional numeric field. This value is
defined by NERC in the GADS DRI.
<Fuel Level> Fuel

BTUs - Process
Steam
Identifies the BTUs generated to create process steam for a given

fuel type. This is an optional numeric field. This value is defined
For a given fuel type, identifies the total BTUs generated by the
unit during the month for which the Capacity History record stores
generation data. This field is disabled and populated automatically
as the sum of the values in the following fields for the
corresponding fuel level:
<Fuel Level> Fuel

BTUs Total
<Fuel Level> Fuel BTUs - Electrical Generation

<Fuel Level> Fuel BTUs - Plant Heat and Cooling
GADS Unit Code
<Fuel Level> Fuel BTUs - Process Steam
<Fuel Level> Fuel BTUs - Contract
Identifies the unit represented by the Generation Unit record to

which the Capacity History record is linked. This field is disabled
and populated automatically with the value in the GADS Unit
Code field in the Generation Unit record to which the Capacity
History record is linked. This value is defined by NERC in the
GADS DRI and included in NERC performance reports.
Identifies the utility under which the unit represented by the

Generation Unit record to which the Capacity History record is
linked operates. This field is disabled and populated automatically
GADS Utility Code
with the value in the GADS Utility Code field in the Generation
Unit record. This value is defined by NERC in the GADS DRI and
included in NERC performance reports.
<Fuel Level>
Grindability
Index/Percent
Vanadium
Identifies the grindability index of a given fuel type. This is an

optional numeric field. This value is defined by NERC in the
GADS DRI.
Identifies the actual gross generation of the unit during the month
for which the Capacity History record stores generation data. This
field is used to calculate the value in the Gross Generation of
Electricity field in Generation Fuel Report records that are linked
to the Capacity History record.
Gross Actual
Generation (G)
This field accepts both positive and negative numbers. In some

cases, if a unit does not produce power during the month, the
equipment in the plant still consumes power, causing a negative
Gross Actual Generation value.
This field becomes required when the value in the Reporting Status
field is set to Unit Level Approval.
Gross Dependable
Capacity (G)
Identifies the gross dependable capacity of the unit. This field is

populated automatically with the value in the Gross Dependable
Capacity field in the Generation Unit record to which the Capacity

Gross Max
Capacity (G)
Inactive Hours
Net Actual
Generation (N)
Identifies the gross maximum capacity of the unit during the month
field is populated automatically with the value in the Gross
Maximum Capacity field in the Generation Unit record that is
linked to the Capacity History record. This value is defined by
NERC in the GADS DRI and included in NERC performance
reports.
Identifies the number of hours the unit was inactive during the
month for which the Capacity History record stores generation
data. This field that is populated automatically with the value from
the Event Duration field in the Primary Capacity Incident record
that is linked to the Capacity History record. This value is defined
Identifies the actual net generation of the unit during the month for
which the Capacity History record stores generation data. This
field is used to calculate the value in the Net Generation of
Electricity field in Generation Fuel Report records that are linked
to the Capacity History record.
This field accepts both positive and negative numbers. In some
cases, if a unit does not produce power during the month, the
equipment in the plant still consumes power, causing a negative
Net Actual Generation value.
This field becomes required when the value in the Reporting Status
field is set to Unit Level Approval.
Net Dependable
Capacity (N)
Net Maximum
Capacity (N)
Identifies the net dependable capacity of the unit. This field is

populated automatically with the value in the Net Dependable
Capacity field in the Generation Unit record to which the Capacity
Identifies the net maximum capacity of the unit during the month
field is populated automatically with the value in the Net
Maximum Capacity field in the Generation Unit record to which
the Capacity History record is linked. This value is defined by

NERC in the GADS DRI and included in NERC performance
reports.
<Fuel Level>
Percent Alkalines
Identifies the average sodium and potassium content for a given

fuel type. This is an optional numeric field. This value is defined
<Fuel Level>
Percent Ash
Identifies the average ash content for a given fuel type. This is an
GADS DRI.
<Fuel Level>
Percent Moisture
Identifies the average moisture content for a given fuel type. This
is an optional numeric field. This value is defined by NERC in the
GADS DRI.
<Fuel Level>
Percent Sulfur
Identifies the average sulfur content for a given fuel type. This is
an optional numeric field. This value is defined by NERC in the
GADS DRI.
Plant ID
Identifies the plant in which the unit resides. This field is disabled
and populated automatically with the value in the Plant ID field in
the Generation Plant record that is linked to the Generation Unit
record for which the Capacity History record exists.
Plant Name
Identifies the full name of the plant in which the unit resides. This
field is disabled and populated automatically with the value in the
Plant Name field in the Generation Plant record that is linked to the
Generation Unit record for which the Capacity History record
exists.
Identifies the NERC fuel code for the primary fuel used by the
unit. This field is populated automatically with the value in the
Primary Fuel Code Primary Fuel Code field in the Generation Unit record to which the
Capacity History record is linked. This value is defined by NERC
in the GADS DRI.
Pumping Hrs
Indicates the number of hours the unit operated as a pump. This

field is enabled in Capacity History records that contain the value
Pumped Storage/Hydro in the Unit Type field. This field is an
GADS DRI.
<Fuel Level>
Quantity Burned
For a given fuel type, identifies the amount of fuel that was
consumed by the unit during the month for which the Capacity
History record stores generation data. The value in this field is
used to calculate the value in the Energy Source Consumption field
in Generation Fuel Report records that are linked to the Capacity
History record. This is an optional numeric field. This value is
<Fuel Level>
Quantity Burned
Unit of Measure
Stores the unit of measure associated with a given fuel type. This
field is disabled and populated automatically with the value in the
Fuel Unit of Measure field in the Heating Value Ranges record
with values in the NERC Fuel Description and NERC Fuel Code
fields that match the values in the Primary Fuel Code field. This
Quaternary Fuel
Code
Identifies the NERC fuel code for the quaternary fuel used by the
Quaternary Fuel Code field in the Generation Unit record to which
NERC in the GADS DRI.
Determines what happens when the Capacity History record is
saved.
If the value in this field is True when the Capacity History

record is saved, the Meridium APM system will recalculate
any values based on values in associated records and set the
value in this field to False before saving the Capacity History
record.
If the value in this field is False when the Capacity History

record is saved, the Meridium APM system will save any
changes you have made to the Capacity History record but will
NOT recalculate any values based on values in associated
records.
Refresh Incident
Rollup
Reporting Date
Indicates the date on which the Capacity History record was

approved and reported. When the value in the Reporting Status
field is set to Corporate Approval, this field is populated
automatically with the current date.
Reporting Month
Indicates the month that the Capacity History record represents.

The combination of the value in this field and the Reporting Year
field represent a unique year and month combination. This value is
Reporting Status
Indicates the level of approval of the Capacity History record:

Created, Unit Level Approval, or Corporate Approval. In new
Capacity History records, this field is set to Created by default.
Reporting Year
Indicates the year that the Capacity History record represents. The
combination of the value in this field and the Reporting Month
field represent a unique year and month combination. This value is
Revision
Identifies the revision number of the Capacity History record and

should be incremented each time you resubmit a report which
includes information in the Capacity History record to NERC. This
Secondary Fuel
Code
Identifies the NERC fuel code for the secondary fuel used by the
Secondary Fuel Code field in the Generation Unit record to which
Identifies the number of hours that the unit was in service. This
field is disabled and populated automatically using the following
formula:
Available Hours - Synchronous Condensing Hours
Service Hrs
Sched Outage Hrs
When the value in the Reporting Status field is set to Unit Level
Approval and the value in the Gross Actual Generation or Net
Actual Generation field is greater than 0 (zero), the Service HRs
field cannot be empty or contain the value 0 (zero). If it does, an
error message will be displayed when you attempt to save the
record. This error condition indicates that the Gross Actual
Generation, Net Actual Generation, Available Hours, or
Synchronous Condensing Hours fields contain invalid data.
Identifies the number of hours that the unit was scheduled to be
inactive. This field is populated automatically as the sum of the
Planned and Ext Outage Hrs

Maint and Ext Outage Hrs
Forced Outage Hrs
Total Eqv Derate Hrs (N)
NonCurtailing Event Hrs

Identifies the starting reliability of the unit. This field is disabled
and populated automatically using the following formula:
Start Reliability
Attempted Unit Starts / Actual Unit Starts
Sum of Fuel BTUs
Identifies the sum of all BTUs generated by all fuels consumed by

the unit during the month for which the Capacity History record
stored generation data. This field is disabled and populated
automatically as the sum of the values in the ALL <Fuel Level>
Fuel BTUs Total fields. This value is defined by NERC in the
GADS DRI.
Synchronous
Condensing Hrs
Indicates the number of hours the unit operated in synchronous

condensing mode. This field is enabled in Capacity History records
that contain the value Pumped Storage/Hydro in the Unit Type
field. This is an optional numeric field. This value is defined by
Identifies the NERC fuel code for the tertiary fuel used by the unit.
This field is populated automatically with the value in the Tertiary
Tertiary Fuel Code Fuel Code field in the Generation Unit record to which the
Capacity History record is linked. This value is defined by NERC
in the GADS DRI.
Typical Unit
Loading
Indicates the time during which the unit was responsible for
generating power. This field is populated automatically with the
value in the Default Unit Loading field in the Generation Unit
record to which the Capacity History record is linked. This value is
Unit ID
Identifies the unit. This field is populated automatically with the

value in the Unit ID field in the Generation Unit record to which
the Capacity History record is linked.
Unit Name
Identifies the full name of the unit. This field is disabled and
populated automatically with the value in the Unit Name field in
the Generation Unit record to which the Capacity History record is
linked.
Unit Type
Unavailable Hrs
Identifies the type of unit. This field is disabled and populated

automatically with the value in the GADS Unit Type field in the
Generation Unit record to which the Capacity History record is
linked.
Identifies the number of hours that the unit was unavailable. This
field is disabled and populated automatically as the sum of the
Forced Outage Hrs

Maint Outage Basic Hrs
Maint Outage Sched Ext Hrs
Planned Outage Basic Hrs
Pln Outage Sched Ext Hrs
This value is included in NERC performance reports.

Indicates additional information about the Generation Unit record
Verbal Description that is linked to the Capacity History record. This is an optional
character field.
YTD Actual Unit

Starts
Identifies the number of times the unit has been started during the
year up to the end of the month for which the Capacity History
record stores generation data. This field is disabled and populated
automatically as the sum of values in the Actual Unit Starts field in
ALL the Capacity History records that represent months in the
same year before the month that the current Capacity History
record represents AND the value in the Actual Unit Starts field in
the Capacity History record. This value is defined by NERC in the
GADS DRI.
YTD Attempted
Unit Starts
Identifies the number of times that starting the unit has been
attempted during the year up to the end of the month for which the
Capacity History record stores generation data. This field is
disabled and populated automatically as the sum of values in the
Attempted Unit Starts field in ALL the Capacity History records
that represent months in the same year before the month that the
current Capacity History record represents AND the value in the
Attempted Unit Starts field in the Capacity History record. This
YTD Start
Reliability
Identifies the starting reliability of the unit during the year up to

the end of the month for which the Capacity history record stores
generation data. This field is disabled and populated automatically
using the following formula:
(YTD Attempted Unit Starts / YTD Actual Unit Starts) x 100
Zone
Identifies the zone for which you want to record power price data.
Daylight Saving Time Reference

Daylight Saving Time Reference family in the baseline Meridium APM database. The
descriptions in the following table reflect baseline behavior and assume that you have
created Daylight Saving Time Reference records using the recommended workflow.
Fields are listed in alphabetical order in the following table; they may not appear or may
appear in a different order on each datasheet.
Field
Description
DST Adjustment
Indicates the duration of the time shift during Daylight Saving

Time. This is a numeric field that is disabled and populated
automatically with the value 1 (one), which indicates that the clock
moves forward by one hour when Daylight Saving Time begins and
moves backward one hour when Daylight Saving Time ends.
DST End
Indicates when Daylight Saving Time ends in a given year. This is a

required date field. Note that the value in the DST End field must
represent a date in the same year as the value in the DST Start field.
DST Region Code
Identifies the region that observes Daylight Saving Time as

identified by the Daylight Saving Time Reference record. This is a
required character field.
DST Start
Indicates when Daylight Saving Time begins in a given year. This

is a required date field. Note that the value in the DST Start field
must represent a date in the same year as the value in the DST End
field.
Enterprise Support An optional character field that is not used by Generation
<1-8> Code
Management.
Enterprise Support An optional character field that is not used by Generation
<1-8> Description Management.
EIA Federal Region

The following table provides a list of the fields that are defined for the baseline EIA
Federal Region family and describes how they are used to populate values in Generation
Plant records. Fields are listed in alphabetical order in the following table; they may not
appear or may appear in a different order on each datasheet.
Field
Census Division
Description
Used to populate the EIA Census Division field. This value is
defined by the Energy Information Administration (EIA).
Enterprise Support
Not used.
<1-8> Code
Enterprise Support
Not used.
<1-8> Description
Federal Region
Used to populate the EIA Federal Region field. This value is

State
Used to locate the EIA Federal Region record whose fields will be
used to populate the EIA Census Division and EIA Federal Region
fields in a Generation Plant record.
GADS Cause Codes

The following table provides a list and description of the fields in the GADS Cause
Codes family that are used to populate the cause code fields in Primary Capacity Incident
records. The descriptions in the following table reflect how the fields will be used to
populate the cause code fields in Incident record.
Note: Any field that is NOT listed in the following table is NOT used in the baseline GM
product.
Field
Description
Cause Code
Description
Used to populate the Cause Code and Cause Code Description fields. This
Cause Code
Used to populate the Cause Code field. This value is defined by NERC in
the GADS DRI.
Component
Used to populate the Cause Code Component field and to restrict the list
in the Cause Code field to values in GADS Cause Codes records that
contain a value in this field that matches the value in the Cause Code
Component field in the incident record. This value is defined by NERC in
the GADS DRI.
Used to set the value in the OMC Event field automatically. In Incident
record, when you set the value in the Cause Code field, if the value in this
field is:
OMC Code
True, the Meridium APM system will automatically set the value
in the OMC Event field to True.
False, the Meridium APM system will automatically set the value
in the OMC Event field to False.
System
Used to populate the Cause Code System field and to restrict the list in the
Cause Code Component and Cause Code fields to values in GADS Cause
Codes records that contain a value in this field that matches the value in
the Cause Code System field in the incident record. This value is defined
Unit Type
Used to restrict the list in the Cause Code System, Cause Code
Component, and Cause Code fields to values in GADS Cause Codes
records that contain a value in this field that matches the value in the
GADS Unit Type field in Generation Unit record with which the incident
record is associated. This value is defined by NERC in the GADS DRI.
Generation Company
Generation Company family in the baseline Meridium APM database. The descriptions in
the following table reflect baseline behavior and assume that you have created Generation
Company records using the recommended workflow. Fields are listed in alphabetical
order in the following table; they may not appear or may appear in a different order on
each datasheet. Any field NOT designated as required in the following table is optional.
Note: The following list is not comprehensive and does not include all the fields that
exist in the Generation Company family in the baseline Meridium APM database.
Field
Description
Address 1
Identifies the first line of the address of the company.
Address 2
Indicates the second line of the address of the company.
City
Indicates the city in which the company is based.
Company Financial
Web Address
Identifies the URL of the company's financial website.
Company ID
Identifies the company and is used to populate the Record ID.

This is a character field that is required for all Generation
Company records.
Company Name
Indicates the full name of the company and is used to populate

the Record ID. This is a character field that is required for all
Generation Company records.
Company Web Site

Address
Contact
Identifies the URL of the company's corporate website.

Identifies the name of a person within the company to contact in
regards to NERC reporting.
Council
Indicates NERC council to which the company belongs and is

used to populate the Record ID. A baseline rule exists to
populate the Council field with a list of System Codes in the
MI_GM_POWER_REGION System Code Table.
Email Address
Identifies the email address of the person identified by the value

in the Contact field.
Enterprise <1-8> Code Optional character fields that are not used by Generation
Management.
Enterprise <1-8>
Description
Optional character fields that are not used by Generation

Management.
GADS Utility Code
Indicates the three-digit code that is assigned to the company by

NERC.
Keyword
Indicates the NERC keyword for the company.
Phone Fax
Indicates the fax number for the person identified by the value
in the Contact field.
Phone Voice
Indicates the phone number for the person identified by the

value in the Contact field.
State
Indicates the state in which the company is based. This is a

required field, and a baseline rule exists to populate the State
field with a list of System Codes in the MI_GM_STATE System
Code Table.
Stock Symbol
Identifies the symbol that represents the company in stock

trading.
Zip Code
Indicates the zip code of the location where the company is

based.
Generation Fuel Report
Generation Fuel Annual Report and Generation Fuel Monthly Report families in the
baseline Meridium APM database. In the following table, note that:
The descriptions reflect baseline behavior.

Whenever we refer to:
The plant, we mean the plant represented by the Generation Plant record
to which the generation fuel report record is linked.
The units, we mean the units for which the generation fuel report record
stores data. These units are represented by Generation Unit records that
are linked to the Generation Plant record to which the generation fuel
report record is linked.
The fuel, we mean the fuel that is used by the units for which the
generation fuel report record stores data. The fuel for which data is stored
is determined by the values in the Energy Source Code and Prime Mover
fields in the generation fuel report record.
Fields are listed in alphabetical order by field caption; they may not appear or
may appear in a different order on each datasheet.
Any field that is defined for these families but NOT listed in the following table is
NOT used in the baseline GM product.
Field
Address 1
Address 2
Description
Identifies the first line of the address of the plant. This is an optional
character field that is populated automatically with the value in the
Address 1 field in the Generation Plant record to which the generation
fuel report record is linked.
After the fuel report record has been created, this value can be modified
and is not required to match the value in the field from which it was
populated. We recommend, however, that you do not modify the value
so that the values will match. This value is included in EIA reports.
Identifies the second line of the address of the plant. This is an optional
Address 2 field in the Generation Plant record to which the generation
Identifies the AER fuel type code for the fuel. This field is disabled and
populated automatically with the value in the AER Fuel Description
AER Fuel Type and AER Fuel Code fields in the Heating Value Ranges record in which
Code
the value in the Fuel Type field matches the value in the Energy Source
Code field in the generation fuel report record. This value is defined by
the Energy Information Administration (EIA).
Identifies the city in which the plant resides. This is an optional
character field that is populated automatically with the value in the City
field in the Generation Plant record to which the generation fuel report
record is linked.
City
Indicates whether the plant is a cogeneration plant. If the value in this
field is:
Combined Heat
and Power
Plant
True, the plant IS a cogeneration plant.

False, the plant is NOT a cogeneration plant.
This value is defined by the Energy Information Administration (EIA).

Comments
Company ID
Company Name
Indicates additional information about the generation fuel report record.

This is an optional text field.
Identifies the company that owns the plant. This is an optional
Company ID field in the Generation Plant record to which the
generation fuel report record is linked.
so that the values will match.
Identifies the full name of the company that owns the plant. This is an
optional character field that is populated automatically with the value in
the Company Name field in the Generation Plant record to which the
Identifies the county in which the plant resides. This is an optional

County field in the Generation Plant record to which the generation
County
EIA Plant ID
EIA Plant
Name
EIA Utility
Code
Identifies the plant ID to be used on EIA forms. This is an optional
numeric field that is populated automatically with the value in the EIA
Plant ID field in the Generation Plant record to which the generation
fuel report record is linked. This value is defined by the Energy
Information Administration (EIA).
Identifies the name of the plant as it is reported to the EIA. This is an
optional character field that is populated automatically with the value in
the EIA Plant Name field in the Generation Plant record to which the
Identifies the company under which the plant operates. This is an
optional numeric field that is populated automatically with the value in
the EIA Utility Code field in the Generation Plant record to which the
Identifies the EIA energy source code for the fuel. This is a required
field, and a baseline rule exists to populate this field with values in the
Fuel Type and Fuel Type Description fields in Heating Value Ranges
records using the format Fuel Type Description (Fuel Type).
Energy Source
Code
Energy Source Identifies the total amount of consumption of the fuel by the units. This
Consumption is an optional numeric field that is calculated as the sum of ALL the
values in the <Fuel Level> Quantity Burned fields in ALL the Capacity
History records that are linked to a Generation Unit record for which
the generation fuel report record collects data. This value is defined by
Indicates whether or not the following fields in the generation fuel
report record will be calculated using values in the associated
Generation Unit and Capacity History records:
Energy Source Consumption

Generation Nameplate Capacity
Gross Generation of Electricity
Net Generation of Electricity
Energy Source
Consumption When you save a generation fuel report record, if the value in this field
Rollup
is:
True, the values in the preceding fields will be calculated based

upon information in the associated Generation Unit and Capacity
History records. If the values in these records have changed since
the generation fuel report record was last saved, these fields will be
updated.
False, the fields in the preceding list will be populated with the
value 0 (zero).
Generator
Nameplate
Capacity
Identifies the total generator nameplate capacity of all the units. This is
an optional numeric field that is calculated as the sum of ALL the
values in the EIA Generator Nameplate Capacity field in ALL the
Generation Unit records for which the generation fuel report record
collects data. This value is defined by the Energy Information
Administration (EIA) and is included in EIA reports.
Gross
Generation of
Electricity
Identifies the total gross generation of all the units. This is an optional
numeric field that is calculated as the sum of ALL the values in the
Gross Actual Generation field in ALL the Capacity History records that
are linked to a Generation Unit record for which the generation fuel
report record collects data. This value is defined by the Energy
Identifies the average heat content of the fuel consumed by all units.
This field is populated automatically with a value that is calculated
using the following formula:
Average Heat Content /
Quantity Burned
...where:
Heat Content
Per Unit of Fuel
Average Heat Content is the sum of the values in the <Fuel

Level> Average Heat Content fields in ALL associated Capacity
History records in which a value in the corresponding EIA
Energy Source <1, 2, 3, 4> field matches the value in the
Energy Source Code field in the generation fuel report record.
Quantity Burned is the sum of the values in the <Fuel Level>
Quantity Burned fields in ALL associated Capacity History
records in which a value in the corresponding EIA Energy
Source <1, 2, 3, 4> field matches the value in the Energy
Source Code field in the generation fuel report record.
This value is included in EIA reports.

Identifies the unit of measure associated with the value stored in the
Heat Content Per Unit of Fuel field. This field is disabled and
Heat Content populated automatically with the value in the Heat Content Unit of
Unit of Measure Measure field in the Heating Value Ranges record with a value in the
Fuel Type field that matches the value in the Energy Source Code field
in the generation fuel report record.
Identifies the total net generation of all the units. This is an optional
numeric field that is calculated as the sum of ALL the values in the Net
Net Generation
Actual Generation field in ALL the Capacity History records that are
of Electricity
linked to a Generation Unit record for which the generation fuel report
record collects data. This value is included in EIA reports.
Identifies the plant ID. This is a required field, and a baseline rule
exists to populate this field with a list of values in the Plant ID field in
all Generation Plant records that you have permission to modify.
Plant ID
Plant Name
Identifies the name of the plant. This is an optional character field that
is populated automatically with the value in the Plant Name field in the
Generation Plant record to which the generation fuel report record is
linked.
Prime Mover
Identifies the prime mover of the units. This is a required field, and a
baseline rule exists to populate this field with a list of System Codes
from the MI_GM_PRIME_MOVER_CODE System Code Table. This
value is defined by the Energy Information Administration (EIA) and is
included in EIA reports.
Quantity on
Hand
Identifies the amount of the fuel that is on hand at the time the
generation fuel report record is approved. This is a numeric field that
becomes required when the value in the Report Status field is changed
to Approved. The unit of measure for this value can be specified in the
Quantity Units of Measure field. This value is included in EIA reports.
Identifies the unit of measure associated with the value in the Quantity
on Hand field. This field is disabled and populated automatically with
Quantity Units
the value in the Fuel Unit of Measure field in the Heating Value Ranges
of Measure
record with a value in the Fuel Type field that matches the value in the
Energy Source Code field.
Identifies the level of approval of the generation fuel report record. If
desired, you can use this field to manage a custom approval process for
generation fuel report records. This field must contain a value, and a
baseline rule exists to populate this field with a list of the following
values:
Report Status
Created: Assigned to generation fuel report records when they

are first created.
Submitted: Indicates that the information in the record has been
submitted to the EIA. When this field is set to Submitted, the
Report Submitted Date field is populated automatically with the
current date and time.
Approved: Indicates that the EIA has accepted and approved the
information. When this field is set to Approved, the Energy Source
Consumption and Quantity on Hand fields become required.
This value is included in EIA reports.

Report
Identifies the date on which the value in the Report Status field was
Submitted Date changed to Submitted. This field is disabled and populated
automatically with the date and time that the value in the Report Status
field is changed to Submitted. This value is included in EIA reports.

Identifies the month for which the generation fuel report record exists.
This field is disabled, and:
In Generation Fuel Annual Report records, this field is an

optional character field that is not used.
In Generation Monthly Report records, this field must contain a

value, is populated automatically with a list of values that represent
each month, and is populated automatically with the current month.
Reporting
Month
Identifies the year for which the generation fuel report record exists.
This field must contain a value and is populated with a list of values
Reporting Year
that represent each year from 1960 to 2019. This field is populated
automatically with the current year.
Identifies the ID assigned to the plant by the EIA. This is an optional
numeric field that is populated automatically with the value in the EIA
Respondent ID field in the Generation Plant record to which the
Respondent ID
generation fuel report record is linked. This value is defined by the
Energy Information Administration (EIA) and is included in EIA
reports.
Identifies the name of the respondent identified by the value in the EIA
Respondent ID field. This is an optional character field that is
populated automatically with the value in the EIA Respondent Name
record is linked.
Respondent
Name
Identifies the state in which the plant resides. This is an optional
State field in the Generation Plant record to which the generation fuel
report record is linked.
State
Survey Contact
1 Email
Survey Contact
1 Fax Number
Survey Contact
1 Name
Survey Contact
1 Phone
Identifies the email address of the person identified by the value in the
Survey Contact 1 Name field. This is an optional character field that is
populated automatically with the value in the EIA Contact 1 Email field
in the Generation Plant record to which the generation fuel report
record is linked.
Identifies the fax number of the person identified by the value in the
populated automatically with the value in the EIA Contact 1 Fax
Number field in the Generation Plant record to which the generation
Identifies the primary person within the company for the EIA to contact
with questions about the information in the report. This is an optional
character field that is populated automatically with the value in the EIA
Contact 1 Name field in the Generation Plant record to which the
Identifies the phone number of the person identified by the value in the
populated automatically with the value in the EIA Contact 1 Phone
record is linked.
Identifies the title of the person identified by the value in the Survey
Survey Contact Contact 1 Name field. This is an optional character field that is
populated automatically with the value in the EIA Contact 1 Title field
1 Title
record is linked.
Survey Contact
2 Email
Survey Contact
2 Fax Number
Survey Contact
2 Name
Survey Contact
2 Phone
Identifies the email address of the person identified by the value in the
populated automatically with the value in the EIA Contact 2 Email field
record is linked.
Identifies the fax number of the person identified by the value in the
populated automatically with the value in the EIA Contact 2 Fax
Number field in the Generation Plant record to which the generation
Identifies an alternate person within the company for the EIA to contact
with questions about the information in the report. This is an optional
character field that is populated automatically with the value in the EIA
Contact 2 Name field in the Generation Plant record to which the
Identifies the phone number of the person identified by the value in the
populated automatically with the value in the EIA Contact 2 Phone
record is linked.
Survey Contact
2 Title
Thermal
Output for
Processes
Type of
Respondent
Identifies the title of the person identified by the value in the Survey
Contact 2 Name field. This is an optional character field that is
populated automatically with the value in the EIA Contact 2 Title field
record is linked.
Identifies the thermal output of cogeneration plants for processes other
than power generation. This is an optional numeric field.
Indicates whether the plant is a utility or an independent power
producer. This field is populated automatically with the value in the
EIA Respondent Type field in the Generation Plant record to which the
fuel report record is linked. This field must contain a value, and a
baseline rule exists to populate this field with a list of the following
values:
Regulated Generator
Unregulated Generator
so that the values will match. This value is defined by the Energy
Information Administration (EIA) and is included in EIA reports.
Zip Code
Identifies the zip code of the location of the plant. This is an optional
character field that is populated automatically with the value in the Zip
Code field in the Generation Plant record to which the generation fuel
report record is linked. This value is defined by the Energy Information
Administration (EIA) and is included in EIA reports.
Generation Plant
Generation Plant family in the baseline Meridium APM database. The descriptions in the
following table reflect baseline behavior and assume that you have created Generation
Plant records using the recommended workflow. Fields are listed in alphabetical order in
the following table; they may not appear or may appear in a different order on each
datasheet. Any field not designated as required in the following table is optional.
Field
Description
Identifies the first line of the address of the plant. We recommend that
you use
Address 1
the address that is on file with the EIA.
Address 2
Identifies the second line of the address of the plant. We recommend that
you use the address that is on file with the EIA.
Area
Used to group Generation Plant records into an area. A baseline rule

exists to populate this field with a list of each unique value that exists in
the Area field in all other Generation Plant records.
City
Identifies the city in which the plant resides. We recommend that you
use the city associated with the address that is on file with the EIA.
Company ID
Identifies the company that owns the plant. When a Generation Plant
record is created, this field is populated automatically with the value in
the Company ID field in the Generation Company record to which the
Generation Plant record is linked. After the Generation Plant record
exists, the value in this field can be modified and is not required to
match the value in the Generation Company record.
Company
Name
Identifies the full name of the company that owns the plant. When a
Generation Plant record is created, this field is populated automatically
with the value in the Company Name field in the Generation Company
record to which the Generation Plant record is linked. After the
Generation Plant record exists, the value in this field can be modified
and is not required to match the value in the Generation Company
record.
County
Indicates the county in which the plant resides. We recommend that you
use the county associated with the address that is on file with the EIA.
Date/Time
Alternate
Format
Indicates the date and time format that will be used in records that are
associated with the Generation Plant record.
DST Region
Indicates the DST region to be used when using Daylight Saving Time
in Incident records. A baseline rule exists to populate this field with a list
of each unique value that exists in the DST Region Code field in all
Daylight Saving Time Reference records.
EIA Census
Division
Identifies the name of the EIA census division of the plant. This field is
disabled and populated automatically using the EIA Federal Region
reference table. This value is defined by the Energy Information
Administration (EIA).
EIA Contact 1 Identifies the email address of the person identified by the value in the
Email
EIA Contact 1 Name field.
EIA Contact 1 Identifies the fax number of the person identified by the value in the EIA
Fax Number Contact 1 Name field.
EIA Contact 1 Identifies the primary person within the company for the EIA to contact
Name
with questions.
EIA Contact 1 Identifies the telephone number of the person identified by the value in
Phone
the EIA Contact 1 Name field.
EIA Contact 1 A value that identifies the title of the person identified by the value in
Title
EIA Contact 2 Identifies the email address of the person identified by the value in the
Email
EIA Contact 2 Name field.
EIA Contact 2 Identifies the fax number of the person identified by the value in the EIA
Fax Number Contact2 Name field.
EIA Contact 2 Identifies an alternate person within the company for the EIA to contact
Name
with questions.
EIA Contact 2 Identifies the telephone number of the person identified by the value in
Phone
EIA Contact 2 Identifies the title of the person identified by the value in the EIA
Title
Contact 2 Name field.
EIA Federal
Region
Identifies the EIA federal census division code of the plant. This field is
disabled and populated automatically using values in EIA Federal
Region records. This value is defined by the Energy Information
EIA Operator Indicates the name of the person that operates the plant. This value is
ID
EIA Plant
Code
Identifies the plant code to be used on EIA forms. This value is defined
by the Energy Information Administration (EIA).
EIA Plant ID
Identifies the plant ID to be used on EIA forms. This value is defined by

EIA Plant
Name
Identifies the name of the plant as it is reported to the EIA. This value is
EIA
Identifies the ID assigned to the plant by the EIA. This value is defined
Respondent ID by the Energy Information Administration (EIA).
EIA
Respondent
Name
EIA
Respondent
Type
Identifies the name of the respondent identified by the value in the EIA
Respondent ID field. This value is defined by the Energy Information
Indicates whether the plant is a utility or an independent power
producer. This field must contain a value, and a baseline rule exists to
populate this field with a list of the following options:
Regulated Generator
Unregulated Generator
This value is defined by the Energy Information Administration (EIA).

EIA Sector
Name
Identifies the name of the EIA sector of the plant. This value is defined
EIA Sector
Number
Identifies the number of the EIA sector of the plant. This value is
EIA Utility
Code
Identifies the company under which the plant operates. This value is
Enterprise <1Optional character fields that are not used by Generation Management.
8> Code
Enterprise <1Optional character fields that are not used by Generation Management.
8> Description
GADS Region Indicates the GADS region code of the plant. A baseline rule exists to
populate this field with a list of System Codes in the
MI_GM_POWER_REGION System Code Table. This value is defined

GADS
Subregion
Indicates the GADS subregion of the plant. A baseline rule exists to

populate this field with a list of the System Codes in the
MI_GM_POWER_SUBREGION System Code Table that contain a
System Code Reference to the System Code identified by the value in
the GADS Region field. This value is defined by NERC in the GADS
DRI.
NAICS Code
Identifies the plant's NAICS code. This value is defined by the Energy
Organization
Identifies the organization to which the plant belongs.
Plant ID
Identifies the plant and is used to populate the Record ID. This is a
character field that is required for all Generation Plant records. This
value is defined by the Energy Information Administration (EIA).
Plant Name
Identifies the full name of the plant and is used to populate the Record
ID. This is a character field that is required for all Generation Plant
records. This value is defined by the Energy Information Administration
(EIA).
State
Use Daylight
Saving Time
Zip Code
Indicates the state in which the plant resides. We recommend that you
use the state associated with the address that is on file with the EIA. A
baseline rule exists to populate this field with a list of System Codes in
the MI_GM_STATE System Code Table.
Indicates whether Daylight Saving Time should be used in records that
are associated with the Generation Plant record. If the value in this field
is:
True, Daylight Saving Time will be used.
False, Daylight Saving Time will not be used.
Identifies the zip code of the location of the plant. We recommend that
you use the zip code associated with the address that is on file with the
EIA.
Generation Pool
Generation Pool family in the baseline Meridium APM database. The descriptions in the
following table reflect baseline behavior. Fields are listed in alphabetical order in the
following table; they may not appear or may appear in a different order on each
datasheet.
Field
Description
Business Category
A value that represents the category to which the Generation

Unit record that is associated with the Generation Pool record
belongs. This field contains a list of values in the Business
Category field in all existing Generation Pool records and is a
character field.
Enterprise Support
<1-8> Code
A field that is not used by Generation Management and contains

no value in the baseline Meridium APM database.
Enterprise Support
<1-8> Description
A field that is not used by Generation Management and contains

no value in the baseline Meridium APM database.
GADS Unit Type
A value that indicates the GADS unit type of the Generation

Unit with which the Generation Pool record is associated. This
field is disabled and populated automatically with the value in
the GADS Unit Type field in the Generation Unit record
identified in the Unit ID field.
Generation Pool
Description
A value that describes the generation pool.
Generation Pool Name A value that identifies the generation pool. This field contains a
list of values in the Generation Pool Name field in all existing
Generation Pool records and is a character field.
Gross Maximum
Capacity
A value that indicates the gross maximum capacity of the

Generation Unit record that is associated with the Generation
Pool record. This field is disabled and populated automatically
with the value in the Gross Maximum Capacity field in the
Generation Unit record identified in the Unit ID field.
Net Maximum
Capacity
A value that indicates the net maximum capacity of the

Generation Unit record that is associated with the Generation
Pool record. This field is disabled and populated automatically

with the value in the Net Maximum Capacity field in the
Unit ID
A value that indicates the Generation Unit that is associated with

the Generation Pool record. This field is required.
Unit Name
A value that indicates the Generation Unit that is associated with

the Generation Pool record. This field is disabled and populated
automatically with the value in the Unit Name field in the
Weighting Factor
A value that indicates the weighting factor for the Generation

Unit record that is associated with the Generation Pool record.
This field is required and is populated automatically with the
value in the Net Maximum Capacity field in the Generation Unit
record identified in the Unit ID field.
Generation Unit
Generation Unit family in the baseline Meridium APM database. The descriptions in the
following table reflect baseline behavior and assume that you have created Generation
Unit records using the recommended workflow. Fields are listed in alphabetical order in
the following table; they may not appear or may appear in a different order on each
datasheet.
Note: The following list is not comprehensive and does not include all the fields that exist
in the Generation Unit family in the baseline Meridium APM database.
Field
Description
Identifies the AER fuel type code for the primary, secondary,
AER Fuel Type Code tertiary, or quaternary fuel used by the unit. These are optional
<1, 2, 3, 4>
character fields, and baseline rules exists to populate these fields
with values in Heating Value Ranges records.
APM Event Creation

Reference Value
Used to determine when an APM Event record will be created.

This is a numeric field that becomes enabled and required if the
value in the APM Event Creation is MWH Loss Exceeds
Reference or Production Loss Exceeds Reference.
Determines under what conditions APM Event records will be
created. This is a required field, and a baseline rule exists to
populate this field with a list of the following values:
APM Event Creation
All Primary Capacity Incidents

MWH Loss Exceeds Reference
Production Loss Exceeds Reference

Identifies the generation block for the unit. This is an optional
character field and contains a list of all values in the Block
Number field in all other Generation Unit records.
Block Number
In Primary Capacity Incident records and Contributing Capacity

Incident records that are linked to a Generation Unit record that
has a value in the Block Number field, the following fields will
contain the cause code values that are associated with the value
in the GADS Unit Type field of ALL Generation Unit records
which contain the same value in the Block Number field.
Cause Code System

Cause Code Component
Cause Code fields
Common Fuel Code

<1, 2, 3, 4>
Identifies the common fuel code for the primary, secondary,

tertiary, or quaternary fuel used by the unit. These are optional
character fields, and baseline rules exist to populate these fields
with values in Heating Value Ranges records.
Company ID
Identifies the company that owns the unit. When a Generation

Unit record is first created, this field is populated automatically
with the value in the Company ID field in the Generation Plant
record to which the Generation Unit record is linked. After the
Generation Unit record exists, the value in this field can be
modified and is not required to match the value in the Generation
Plant record. This is an optional character field.
Company Name
Identifies the full name of the company that owns the unit. When
a Generation Unit record is first created, this field is populated
automatically with the value in the Company Name field in the
Generation Plant record to which the Generation Unit record is
linked. After the Generation Unit record exists, the value in this
field can be modified and is not required to match the value in
the Generation Plant record. This is an optional character field.
Indicates whether a Capacity History record will be created to
exclude Primary Capacity Incident records and Contributing
Capacity Incident records in which the value in the OMC Event
field is True. If the value in this field is:
Create Outside
Management Control
Statistics?
True, a Capacity History record will be created to exclude

data for OMC events.
False, a Capacity History record will NOT be created to
exclude data for OMC events.
Indicates the time during which the unit is responsible for

generating power. This is a required field, and a baseline rule
Default Unit Loading
exists to populate this field with a list of System Codes in the
MI_GM_UNIT_LOADING System Code Table.
Indicates the gross maximum capacity that the unit has
Demonstrated Gross
demonstrated on a continuous basis. This is an optional numeric
Maximum Capacity
field.
Demonstrated Net
Maximum Capacity
Indicates the net maximum capacity that the unit has

demonstrated on a continuous basis. This is an optional numeric
field.
Used by the History Rollup Query when it rolls up incident data

in the order that the incidents occurred based on their start date.
Derating Calculation
This field must contain a value. You should accept the default
Method
value, Event Order Number. You should NOT select Ranked
Masking and All Additives.
Indicates whether the unit generates both heat and electricity. If
the value in this field is:
True, it indicates that the unit IS a combined heat and

power unit.
False, it indicates that the unit is NOT a combined heat

and power unit and generates either heat OR power, but not
both.
EIA Combined Heat

and Power Unit
EIA Energy Source

<1, 2, 3, 4>
Identifies the EIA energy source code for the primary, secondary,
tertiary, or quaternary fuel used by the unit. These fields are
optional but are required for each fuel for which a NERC fuel
code is defined in order to generate useful EIA fuel reports.
Baseline rules exist to populate these fields with values from
Heating Value Ranges records.
EIA Generator ID
Identifies the generator. This is an optional character field. This

value is defined by the Energy Information Administration
(EIA).
EIA Generator
Nameplate Capacity
Identifies the generator nameplate capacity of the unit. This is an

optional numeric field. This value is defined by the Energy
EIA Plant Code
Identifies the plant in which the unit resides. This is an optional

numeric field. We recommend that you populate this field with
the value in the EIA Plant Code field in the Generation Plant
record to which the Generation Unit record is linked. This value
is defined by the Energy Information Administration (EIA).
EIA Prime Mover

Type
Identifies the prime mover of the of the unit. A baseline rule

MI_GM_PRIME_MOVER_CODE System Code Table. This is
an optional field but is required to generate useful EIA fuel
reports.
EIA Utility Code
Identifies the EIA Utility Code of the plant in which the unit
resides. This is an optional numeric field. We recommend that
you populate this field with the value in the EIA Utility Code
field in the Generation Plant record to which the Generation Unit
record is linked. This value is defined by the Energy Information
Enterprise Support
<1-8> Code

Management.
Enterprise Support
<1-8> Description

Management.
Determines whether Primary Capacity Incident or Capacity
History records that are linked to the Generation Unit record can
be modified. If the value in this field is:
GADS Data Locked
True, only a member of the MI Generation Management

Administrator Security Group will be allowed to create
Primary Capacity Incident or Capacity History records to
link to the Generation Unit record or modify Primary

Capacity Incident records or Capacity History records that
are already linked to the Generation Unit record.
False, the ability to create and modify Primary Capacity

Incident records and Capacity History records will be
controlled by GM Role-Based Security.
GADS Net Rating
Identifies the manufacturer's official net rating for the unit. This
is an optional numeric field. This value is defined by NERC in
the GADS DRI.
GADS Region
Indicates the GADS region code of the plant in which the unit
resides. This is a required field, and a baseline rule exists to
populate this field with a list of System Codes in the
MI_GM_POWER_REGION System Code Table. This value is
GADS Subregion
Indicates the GADS subregion of the plant in which the unit

resides. This is an optional field, and a baseline rule exists to
populate this field with a list of the System Codes in the
MI_GM_POWER_SUBREGION System Code Table that
contain a System Code Reference to the System Code identified
by the value in the GADS Region field. This value is defined by
GADS Unit Code
Identifies the unit in NERC reports. This is an optional numeric

field. This value is defined by NERC in the GADS DRI.
GADS Unit Type
Identifies the type of unit. This is a required field, and a baseline

rule exists to populate this field with a list of System Codes in
the MI_GM_UNIT_TYPE System Code Table. Note that the
value in this field will be used in conjunction with the Gross
Maximum Capacity or Net Maximum Capacity to calculate
missing capacity values. This value is defined by NERC in the
GADS DRI.
GADS Utility Code

Generation Cost
Model
Identifies the utility under which the unit operates. This is an

GADS DRI.
Determines how the Potential Capacity Incident Cost will be
calculated in Primary Capacity Incident records that are linked to
the Generation Unit record. This is a required field, and a
baseline rule exists to populate this field with a list of the
following values:
Price Curve
Reference Value
No Cost Calculation
Generation Cost
Reference Value
Determines the cost of power lost by reduced capacity of the

unit. This is a numeric field that becomes enabled and required
when the value in the Generation Cost Model field is set to
Reference Value.
Gross Dependable
Capacity
Identifies the gross dependable electrical generation capacity of

the unit. This is a numeric field that must contain a value.
Gross Maximum
Capacity
Identifies the gross maximum electrical generation capacity of

the unit. Either this field or the Net Maximum Capacity field
must be populated in order to save a Generation Unit record.
Net Dependable
Capacity
Identifies the net dependable electrical generation capacity of the

unit. This is a numeric field that must contain a value.
Net Maximum
Capacity
Identifies the net maximum electrical generation capacity of the

unit. Either this field or the Gross Maximum Capacity field must
be populated in order to save a Generation Unit record.
Percent Generation
Represents the percentage of the unit's generation from the unit

that belongs to the company represented by the Generation
Company record that is associated with the Generation Unit
record. This is an optional numeric field.
Percent Operated
Represents the percentage of the unit's operation that belongs to

the company represented by the Generation Company record that
is associated with the Generation Unit record. This is an optional
numeric field.
Percent Owned
Represents the percentage of the unit owned by the company

represented by the Generation Company record that is associated
with the Generation Unit record. This is an optional numeric
field.
Plant ID
Identifies the plant in which the unit resides. When a Generation

Unit record is created, this field is populated automatically with
the value in the Plant ID field in the Generation Plant record to
which the Generation Unit record is linked. After the Generation
Unit record exists, the value in this field can be modified and is
not required to match the value in the Generation Plant record.
This is an optional character field.
Plant Name
Identifies the full name of the plant in which the unit resides.
When a Generation Unit record is created, this field is populated
automatically with the value in the Plant Name field in the
Generation Plant record to which the Generation Unit record is
linked. After the Generation Unit record exists, the value in this
field can be modified and is not required to match the value in
the Generation Plant record. This is an optional character field.
Primary Fuel Code
Identifies the NERC fuel code for the primary fuel used by the
unit. This is a required field, and a baseline rule exists to
populate this field with values in Heating Value Ranges records.
Identifies the NERC fuel code for the quaternary fuel used by the
Quaternary Fuel Code unit. This is an optional field, and a baseline rule exists to
populate this field with values in Heating Value Ranges records.
Specifies how incident data should be reported for Primary
Capacity Incident records that are linked to the Generation Unit
record. This is a required field, and a baseline rule exists to
Report Capacity Data
populate this field with a list of the following values: NERC,
Internal, NERC and Internal, and Do Not Report. This field is set
to NERC by default.
Report EIA906
Annually?
Indicates whether you will use the information in the Incident

records that are linked to the Generation Unit record to create
Generation Fuel Annual Report records with the same Prime
Mover and Energy Source Code values as the current Generation
Unit record. This field is optional but is required to generate
useful EIA annual reports.
Report EIA906
Monthly?
Indicates whether you will use the information in the Incident

records that are linked to the Generation Unit record to create
Generation Fuel Monthly Report records with the same Prime
Mover and Energy Source Code values as the current Generation
Unit record. This field is optional but is required to generate
useful EIA monthly reports.
Secondary Fuel Code Identifies the NERC fuel code for the secondary fuel used by the
unit. This is an optional character field, and a baseline rule exists
to populate this field with values in Heating Value Ranges
records.
Identifies the demonstrated net capacity under summer
Summer Net Capacity conditions. This is an optional numeric field. This value is
Tertiary Fuel Code
Identifies the NERC fuel code for the tertiary fuel used by the
unit. This is an optional character field, and a baseline rule exists
to populate this field with values in Heating Value Ranges
records.
Unit Hyperlink
Address
Determines the URL of the hyperlink contained in the Unit Web

Site Link field. This is an optional character field. Note that for
the link in the Unit Web Site Link field to function properly, you
must include the scheme (e.g., http://) in the value in this field.
Unit ID
Identifies the unit and is used to populate the Record ID. This is
a required character field. The value in this field should not
exceed 50 characters in length. While you can save a Generation
Unit record that contains more than 50 characters in this field,
when you attempt to create a Primary Capacity Incident record
for that unit, an error message will be displayed.
Unit Name
Identifies the full name of the unit and is used to populate the
Record ID. This is a required character field.
Unit Operating
Characteristics
Unit State
Stores any information about the unit that is not captured in other
fields. This is an optional character field.
Indicates whether the unit represented by the Generation Unit
record is active. This is a required field, and a baseline rule exists
to populate this field with a list of the following values:
Active
Inactive
Note that in new Generation Unit records, the value in this field
is Active by default.
Can be used to link to a website for the unit.
Unit Web Site Link
If the Unit Hyperlink Address field contains any value,

this field will display a hyperlink with the text Unit Web Site
Link. If the value in the Unit Hyperlink Address field is a
value URL, clicking the link will open the associated
website in Internet Explorer.
Verbal Description
If the Unit Hyperlink Address field contains NO value,

this field will display a hyperlink with the text Website not
found that will open the Meridium, Inc. website (i.e.,
www.meridium.com).
Stores a description of the unit. This is an optional character

field.
Identifies the demonstrated net capacity under winter conditions.

Winter Net Capacity This is an optional numeric field. This value is defined by the
Energy Information Administration (EIA).
Zone
Identifies the zone in which the unit resides for the purpose of
associating Power Price Curve records with the Generation Unit
record. If the value in the Generation Cost Model field is Price
Curve, this field becomes required and the value will be used to
associate Power Price Curve records with the same Zone with
incidents linked to the Generation Unit record. A baseline rule
MI_GM_POWER_PRICE_ZONE System Code Table.
Heating Value Ranges

The following table provides a list and description of the fields in the Heating Value
Ranges family that are used to populate fuel code fields in Generation Unit, Capacity
History, and fuel report records. Any field that is NOT listed in this table is NOT used in
the baseline GM product.
Field
Description
AER Fuel Code
Identifies the fuel using the EIA AER fuel code for the fuel. This
value is defined by the Energy Information Administration (EIA).
AER Fuel
Description
Describes the fuel as defined in the EIA AER. This value is defined
Common Fuel
Code
Identifies a common code for the fuel as defined by Meridium APM.
Common Fuel
Description
Describes the fuel as define by Meridium APM.
Fuel Type
Description
Describes the fuel as defined by the EIA.
Fuel Type
Identifies the EIA energy source code for the fuel.
Fuel Unit of
Measure
Identifies the unit of measure associated with the fuel.
Heat Content
High
Identifies the highest potential heat content of the fuel. This value is
Heat Content Low Identifies the lowest potential heat content of the fuel. This value is
Heat Content Unit Identifies the unit of measure used in measuring heat content
of Measure
associated with the fuel. This value is defined by the Energy
NERC Fuel Code Identifies the NERC fuel code for the fuel. This value is defined by
NERC Fuel
Description
Describes the fuel as defined by NERC. This value is defined by

Incident
Primary Capacity Incident and Contributing Capacity Incident families in the baseline
Meridium APM database. The descriptions in the following table reflect baseline
behavior and assume that you have created Primary Capacity Incident and Contributing
Capacity Incident records using the recommended workflow. Fields are listed in
alphabetical order in the following table; they may not appear or may appear in a
different order on each datasheet.
Note: Any field that is defined for these families but not listed in the following table is
not used in the baseline GM product.
Field
Amplification
Code
Description
Identifies the failure mode of the event. This field becomes enabled
when the Cause Code field is populated with a value. A baseline rule
MI_GM_AMPLIFICATION_CODE System Code Table. This value is
defined by NERC in the GADS DRI and included in NERC event
reports.
Identifies the block number in which the event occurred. This field is
disabled and is populated automatically with the value in the Block
Block Number
Number field in the Generation Unit record to which the Primary
Capacity Incident record is linked.
Identifies the type of event.
Capacity Event
Type
In Primary Capacity Incident records, this field contains a list of

System Codes defined in the MI_GM_EVENT_TYPE_CODE
System Code Table.
In Contributing Capacity Incident records, this field is disabled
and populated automatically with the value in the Capacity Event
Type field in the Primary Capacity Incident record to which it is
linked.

NERC event reports.
Describes the event. This field is disabled and populated automatically
Capacity Event with the value in the Capacity Event Type field. The field caption for
Type Descr
this field in Contributing Capacity Incident records is Capacity Event
Type Desc.
Capacity
Incident Cost
Identifies the potential cost of the event. This is an optional field that is
disabled and populated automatically with the calculated incident cost, if
a cost has been calculated. This field exists in the Primary Capacity
Incident family but not the Contributing Capacity Incident family.
Cause Code
Identifies the cause code of the cause for the incident. This is an optional
field, and a baseline rule exists to populate this field with a list of values
in fields in GADS Cause Codes records using the format Cause Code
(Cause Code Description). This value is defined by NERC in the GADS
DRI.
Cause Code
Component
Identifies the cause code component for the cause of the incident. This is
an optional field, and a baseline rule exists to populate this field with a
list of values in the Component field in GADS Cause Codes records.
Cause Code
Description
Describes the cause code associated with the incident. This field is
disabled and populated automatically with the value in the Cause Code
Description field in the GADS Cause Code record with a value in the
Cause Code field that matches the value in the Cause Code field in the
Incident record. This value is defined by NERC in the GADS DRI.
Cause Code
System
Identifies the system for the cause code associated with the incident.
This is an optional field, and a baseline rule exists to populate this field
with a list of values in the System field in GADS Cause Code records.
Indicates the number of Contributing Capacity Incident records that

exist for the Primary Capacity Incident record. This field is disabled and
populated automatically with a value that indicates the number of
Contributing Capacity Incident records that are linked to the Primary
Contributing
Capacity Incident record. The value in this field is updated each time
Incidents Count you link a new Contributing Capacity Incident record to the Primary
Capacity Incident record and each time you unlink a Contributing
Capacity Incident record from the Primary Capacity Incident record.
This field exists in the Primary Capacity Incident family but not the
Contributing Capacity Incident family.
Cost
Calculation
Status
Dominant
Derate
Indicates the status of the cost calculation. This field is populated

automatically with information regarding the status of the calculation
performed in the Capacity Incident Cost field. This field exists in the
Primary Capacity Incident family but not the Contributing Capacity
Incident family.
Indicates whether the Incident record represents the dominant derate
event. This field is optional and becomes enabled when the Capacity
Event Type field contains a value that identifies the event as a derate
event. If the value in this field is:
True, the Incident record represents the dominant derate event.

False, the Incident record does not represent the dominant derate
event.
This value is defined by NERC in the GADS DRI. This field exists in
the Primary Capacity Incident family but not the Contributing Capacity
Incident family.
Indicates whether the value in the Event End Date field is an estimate. If
the value in this field is:
End Date is
Estimated?
Event
Contribution
Code
True, the value in the Event End Date field represents an

estimate of when the event ended.
False, the value in the Event End Date field represents the actual
time that the event ended.
Indicates how the incident contributed to the event. This field will
always contain a value. This value is defined by NERC in the GADS
DRI and included in NERC event reports.
Indicates how long the event lasted. This field is disabled and calculated
Event Start Date + Event End Date
Event Duration
Note that the Event Duration takes into account any existing Daylight
Saving Time Reference records for the time period between the Event
Start Date and Event End Date. This value is defined by NERC in the
GADS DRI.
Indicates the date and time that the incident ended.
Event End Date
In Primary Capacity Incident records, this field will always

contain a value by may or may not appear on the datasheet.
When you save the Primary Capacity Incident record:
If this field contains a value and the Event End Date

(Alternate Format) field does not, the Event End Date
(Alternate Format) field will be populated automatically
with the value in this field.
If neither the Event End Date field NOR the Event End
Date (Alternate Format) field contains a value, they will
both be populated automatically with a value that
indicates that the incident ended on the last day of the
month specified in the value in the Event Start Date field
at 11:59 P.M. and the End Date is Estimated? field will be
set to True.

and is populated automatically with the value in the Event End
Date field from the Primary Capacity Incident record to which it
is linked.
Note that you cannot specify a value in the Event End Date field with a
year that is different from the year in the value in the Event Start field.
NERC event reports.
Indicates the date and time that the incident ended. This is an optional
field that will always contain a value that uses the date and time format
specified for the Generation Plant record that is associated with the
Event End Date
(Alternate
Format)
When you populate this field with a value, the Event End Date
field will be populated automatically with that value.
If this field does not contain a value, it will be populated with the
value in the Event End Date field when the Incident record is
saved.
In Primary Capacity Incident records, this value identifies the
incident with a value that is unique to all Primary Capacity
Incident records that are linked to a given Generation Unit
record. This field is disabled and populated automatically.
Event ID
In Contributing Capacity Incident records, this value identifies

the Primary Capacity Incident record for which the Contributing
Capacity Incident record exists. This field is disabled and
populated automatically.
Indicates the order in which the incident occurred with respect to other
incidents that exist for the same unit.
Event Number
In Primary Capacity Incident records, a value that indicates the

chronological order in which the event took place. When you
create a Primary Capacity Incident record, this field is populated
automatically. For example, when you create the third Primary
Capacity Incident record for a given Generation Unit record for a
given reporting month and year, this field will be populated
automatically with the value 3 (three).
In Contributing Capacity Incident records, this field is populated
automatically with the value in the Event Number field in the
Primary Capacity Incident record to which it is linked.

Indicates the date and time that the incident began.
Event Start
Date
In Primary Capacity Incident records, if neither this field nor the

Event Start Date (Alternate Format) fields contain a value, this is
a required date field. When you save the Primary Capacity
Incident record, if this field contains a value and the Event Start
Date (Alternate Format) field does not, the Event Start Date
(Alternate Format) field will be populated automatically with the
value in this field. Note that you cannot specify a value in the
Event Start Date field with a year that is different from the year
in the value in the Event End field.
and is populated automatically with the Event Start Date value in
the Primary Capacity Incident record to which it is linked.

NERC event reports.
Indicates the date and time that the incident started. This is an optional
field that will contain a value that uses the date and time format
specified for the Generation Plant record that is associated with the
Event Start
Date (Alternate
Format)
When you populate this field with a value, the Event Start Date
field will be populated automatically with that value.
If this field does not contain a value, it will be populated with the
value in the Event Start Date field when the Incident record is
saved.
Event Type
Failure
Mechanism
Indicates the type of event represented by the Incident record. This is an

optional character field.
Indicates the manner in which the component failed. This is an optional
field, and a baseline rule exists to populate this field with a list of
System Codes in the MI_GM_FAILURE_MECHANISM System Code
Table.
Incident family.
GADS Unit
Code
Identifies the GADS Unit Code of the unit at which the incident
occurred. This field is populated automatically using values from
Capacity History, Generation Forecast, or Generation Unit records. This
value is defined by NERC in the GADS DRI and included in NERC
event reports.
GADS Unit
Type
Identifies the GADS Unit Type of the unit at which the incident
occurred. This field is populated automatically using values from
Capacity History, Generation Forecast, or Generation Unit records. This
GADS Utility
Code
Identifies the GADS Utility Code of the utility under which the unit at
which the incident occurred operates. This field is populated
automatically using values from Capacity History, Generation Forecast,
or Generation Unit records. This value is defined by NERC in the
GADS DRI and included in NERC event reports.
Identifies the method that will be used to calculate the cost of the
incident. This is an optional character field that is populated
automatically with the value in the Generation Cost Model field in the
Generation Unit record that contains a value in the Unit ID field that
Generation Cost matches the value in the Unit ID field in the Incident record. After the
Model
Incident record has been created, this field can be modified, and the
value is not required to match the value in the Generation Cost Model
field in the Generation Unit record. We recommend that you do not
modify the value in this field. If you do so, the incident cost will not be
calculated.
Identifies the reference value that will be used to calculate the cost of
the incident if the value in the Generation Cost Model field is Reference
Value. This field is populated automatically with the value in the
Generation Cost Reference Value field in the Generation Unit record
Generation Cost that contains a value in the Unit ID field that matches the value in the
Ref Value
Unit ID field in the Incident record. After the Incident record has been
created, this field can be modified, and the value is not required to
match the value in the Generation Cost Model field in the Generation
Unit record. If you change the value in this field, the incident cost will
be calculated using the new value.
Identifies the gross available generation capacity of the unit during the
event.
In Primary Capacity Incident records, this field contains a value

that is calculated depending on the value in the Capacity Event
Type field. If the value in the Capacity Event Type field contains
a value that identifies the event as:
Gross Available
Capacity
A derate event, this field will become required, and the

value must be less than the value in the Gross
Dependable Capacity field. This field is cleared and
becomes required when the Gross Derate Amount field
contains no value or the value 0 (zero). If the Gross
Derate Amount field contains a value other than 0 (zero),
this field will be populated automatically using the
following formula:
Gross Dependable Capacity - Gross Derate Amount
Gross
Dependable
Capacity
An outage event, this field will become disabled and

populated with the value 0 (zero).

and populated automatically with the value in the Gross
Available Capacity field in the Primary Capacity Incident record
to which it is linked.

Identifies the gross dependable generation capacity of the unit at which
the incident occurred. This field is populated automatically using values
from Capacity History, Generation Forecast, or Generation Unit records.
Incident family.
Indicates the gross amount of generation capacity that was lost during
the event.
In Primary Capacity Incident records, this value is used to

calculate the value in the Gross Available Capacity field. The
default value is 0 (zero). If the value in the Capacity Event Type
field contains a value that identifies the event as:
A derate event, this field will be optional. If this field

contains a value other than 0 (zero), the value in the
Gross Available Capacity field will be disabled and
populated automatically using the following formula:
Gross Dependable Capacity - Gross Derate Amount
Gross Derate
Amount
If this field contains NO value or the value 0 (zero), the

Gross Available Capacity field becomes required.


and populated automatically with the value in the Gross Derate
Amount field in the Generation Unit record for which the
Contributing Capacity Incident record exists.

Gross
Maximum
Capacity
Identifies the gross maximum generation capacity of the unit. This field
is populated automatically using values from Capacity History,
Generation Forecast, or Generation Unit records. This value is defined
The date and time that the incident was reported. When the Incident
Reporting Status field is set to Corporate Approval, this field becomes
Incident
disabled and populated automatically with the current date and time
Reported Date when the Incident Reporting Status field is set to the value Corporate
Approval. This field exists in the Primary Capacity Incident family but
not the Contributing Capacity Incident family.
A value that represents the level of approval for the Incident record. This
field is set to the value Created by default, and a baseline rule exists to
populate this field with a list of the following values:
Incident
Reporting
Status
Created: The Incident record has not begun the approval process.
Unit Level Approval: The incident has unit-level approval.
Corporate Approval: The unit has corporate-level approval.

When this field is set to the value Corporate Approval, all other
fields in the Incident record become disabled.
A value that indicates the validity of the record. If this field contains the
value:
Incident
Validation
Status
INVALID, one or more values in the Incident record are invalid,

and you will be unable to set the value in the Incident Reporting
Status field to Unit Level Approval. If the value in this field
contains INVALID, this field will contain additional information
regarding what value is invalid and why.
Valid, all calculations and values in the Incident record are valid.
Man-hours
Worked
Identifies the number of man hours that were worked correcting the
cause of the event or repairing the unit. This is an optional numeric
field. This value is defined by NERC in the GADS DRI.
Identifies the family to which the Incident record belongs.
In Primary Capacity Incident records, this field is disabled and

populated automatically with the value Primary Capacity
Incident.

and populated automatically with the value Contributing
Capacity Incident.
Meridium Event
Family
Identifies the net available capacity of the unit during the event.
In Primary Capacity Incident records, this field contains a value

that is calculated depending on the value contained in the
Capacity Event Type field. If the value in the Capacity Event
Type field contains a value that identifies the event as:
Net Available
Capacity
A derate event, this field will become required, and the

value must be less than the value in the Net Dependable
Capacity field. This field is cleared and becomes required
when the Net Derate Amount field contains no value or
the value 0 (zero). If the Net Derate Amount field
contains a value, this field will be populated
Net Dependable Capacity - Net Derate Amount


and populated automatically with the value in the Net Available
Capacity field in the Generation Unit record that contains a value
in the Unit ID field that matches the value in the Unit ID field in
the Incident record.

Identifies the net dependable generation capacity of the unit at which the
incident occurred. This field is populated automatically using values
Net Dependable
Capacity
Incident family.
Indicates the net amount of generation capacity that was lost during the
event.
In Primary Capacity Incident records, this value is used to

calculate the value in the Net Available Capacity field. The
default value is 0 (zero). If the value in the Capacity Event Type
field contains a value that identifies the event as:
Net Derate
Amount
A derate event, this field is an optional field. If this field

contains a value other than 0 (zero), the value in the Net
Available Capacity field will be disabled and populated
Net Dependable Capacity - Net Derate Amount
If this field contains no value or the value 0 (zero), the Net
Available Capacity field is cleared and becomes required.

and populated automatically with the value in the Net Derate
Amount field in the Generation Unit record that contains a value
in the Unit ID field that matches the value in the Unit ID field in
the Incident record.

Identifies the net maximum generation capacity of the unit at which the
Net Maximum incident occurred. This field is populated automatically using values
Capacity
Indicates whether the incident occurred for reasons that are outside of
management control, such as a flood or lightning. If the value in this
field is:
OMC Event
True, the event is considered outside of management control.

False, the event is considered to be within management control.
Plant ID
Identifies the plant in which the unit at which the incident occurred
resides. This field is populated automatically with the value in the Plant
ID field in the Generation Plant record to which the Generation Unit
record for which the Incident record exists is linked.
Plant Name
Primary
Incident ID
Problem Alert
Identifies the plant in which the unit at which the incident occurred
resides. This field is populated automatically with the value in the Plant
Name field in the Generation Plant record to which the Generation Unit
record for which the Incident record exists is linked.
Identifies the Primary Capacity Incident for which the Contributing
Capacity Incident record exists. This field is disabled and populated
automatically with the value in the Event ID field in the Primary
Capacity Incident record to which the Contributing Capacity Incident
record is linked. This field exists in the Contributing Capacity Incident
family but not the Primary Capacity Incident family.
Indicates whether the problem that caused the event is the result of a
design flaw or standard operating practices. If the value in this field is:
True, the problem was the result of a design flaw or standard

operating practices.
False, the problem was the result of another cause.

Indicates whether the Meridium APM system should refresh the cost
calculation for the Primary Capacity Incident record. When you save the
Primary Capacity Incident record, if the value in this field is:
True, the Meridium APM system will update the value in the
Capacity Incident Cost field and then save the new value, along
with any other changes that you made the Primary Capacity
Incident record.
False, the Meridium APM system will save any changes that you
made to the Primary Capacity Incident record but will NOT
update the value in the Capacity Incident Cost field.
Refresh
Incident Cost
Reporting
Month
Identifies the month for which the data in the Primary Capacity Incident
record should be reported. This field is populated automatically with the
month indicated by the value in the Event Start Date field. This field
exists in the Primary Capacity Incident family but not the Contributing
Capacity Incident family.
Identifies the year for which the data in the Primary Capacity Incident
record should be reported. This field is populated automatically with the
year indicated by the value in the Event Start Date field. This value is
Reporting Year
defined by NERC in the GADS DRI. This field exists in the Primary
Capacity Incident family but not the Contributing Capacity Incident
family.
Revision
Identifies the revision number of the Incident record and should be

incremented each time you re-submit a report which includes
information in the Incident record to NERC. This value is defined by
Indicates whether the value in the Event Start Date field is an estimate.
If the value in this field is:
Start Date is
Estimated?
True, the value in the Event Start Date field represents an

estimate of when the event began.
False, the value in the Event Start Date field represents the actual
time that the event began.
Identifies the total number of engine starts the unit had experienced as of
Total Eng Starts the time the event occurred. This value is defined by NERC in the
at Evnt Time
GADS DRI. This field exists in the Primary Capacity Incident family
but not the Contributing Capacity Incident family.
Identifies the total loss of capacity in terms of the number of hours that
were lost if the unit operated at the net dependable capacity as a result of
the event. This field is disabled and populated automatically using the
following formula:
Total Eqv
Derate Hrs wo
((Net Dependable Capacity - Net Available Capacity) / Net
Shadow
Maximum Capacity) x Event Duration
Identifies the total MWH lost as a result of the event. This field is
disabled and populated automatically using the following formula:
Total Eqv
Derate MWh
wo Shadow
(((Net Dependable Capacity - Net Available Capacity) / Net

Maximum Capacity) x Event Duration) x Net Maximum Capacity
This value is defined by NERC in the GADS DRI and.
Identifies the total cumulative number of hours the unit spent generating
Total Fired Hrs
power as of the time the event occurred. This value is defined by NERC
at Evnt Time
in the GADS DRI.
Indicates how the unit was shut down during the event. This is an
optional field that contains no value by default, and a baseline rule exists
to populate this field with a list of the following values:
Trip
Mechanism
A - Automatic: The unit shut down automatically.

M - Manual: The unit was shut down manual by an operator.
Note that after you select a value in this field and save the Incident
record, you will not be able to clear the field.
Incident family.
Identifies the Unit ID of the Generation Unit record with which the
Incident record is associated.
In Primary Capacity Incident records, this field is required, and a

baseline rule exists to populate this field with a list of values
from the Unit ID and Unit Name fields in all Generation Unit
records that you have permission to modify using the formula
Unit ID (Unit Name). Note that after the Primary Capacity
Incident record has been created, this field will become disabled.

and populated automatically with the value in the Unit ID field
in the Primary Capacity Incident record for which the
Contributing Capacity Incident record exists.
Unit ID
Unit Name
Validate
Incident
Identifies the name of the unit to which the incident occurred. This field
is populated automatically using values from Capacity History,
Generation Forecast, or Generation Unit records.
Indicates whether the Meridium APM system will validate the record
against all other existing Primary Capacity Incident records. When you
save the Primary Capacity Incident record, if the value in this field is:
True, the Meridium APM system will check all other Primary
Capacity Incident records to validate any sequential incident
pairs of which the Primary Capacity Incident record is a part,
update the value in the Incident Validation Status field if
necessary, and then save the Primary Capacity Incident record to
the database.
False, the Meridium APM system will save any changes that you
made to the record, but will not validate the Primary Capacity
Incident record against any other Primary Capacity Incident
records.
Verbal
Description
Work Duration
Describes the incident. This is an optional character field that can be

used to store any information about the incident that is not captured in
the other fields in the Incident record. If the Cause Code field is
populated with any value, the Verbal Description field is required. The
value in this field cannot match the value in the Cause Code Description
field, except when the Cause Code Description field contains the value
Reserve Shutdown.
Indicates the duration of the work that was completed as a result of the
event. This field is disabled and populated automatically using the
following formula:
Work Started + Work Ended
Work Ended
Indicates the date and time when work on the unit ended as a result of
the incident. This is an optional date field. You can populate either this
field or the Work Ended (Alternate Format) field, and the empty field
will be populated automatically with the same value. This value is
reports.
Work Ended
(Alternate
Format)
Indicates the date and time when work on the unit ended as a result of
the incident. This is an optional field that must contain a value that uses
the date and time format specified for the Generation Plant record that is
associated with the Incident record. You can populate either this field or
the Work Ended field, and the empty field will be populated
automatically with the same value.
Work Started
Indicates the date and time when work on the unit started as a result of
the incident. This is an optional date field. You can populate either this
field or the Work Started (Alternate Format) field, and the empty field
will be populated automatically with the same value. This value is
reports.
Work Started
(Alternate
Format)
Indicates the date and time when work on the unit started as a result of
the incident. This is an optional field. When it contains a value, the
value must use the date and time format specified for the Generation
Plant record that is associated with the Incident record. You can populate
either this field or the Work Started field, and the empty field will be
populated automatically with the same value.
Plant Reference
Plant Reference family in the baseline Meridium APM database. The descriptions in the
following table reflect how the fields will be used when Plant Reference records are used
to create Generation Plant records using the Create Plant query. Fields are listed in
different order on each datasheet. Any field that is NOT listed in this table is NOT used in
Field
Description
Address 1
Used to populate the Address 1 field.
Address 2
Area
Used to populate the Area field.
City
Used to populate the City field.
County
Used to populate the County field.
EIA Plant Code Used to populate the EIA Plant Code and EIA Plant ID fields.
EIA Utility Code Used to populate the EIA Utility Code field.
Plant ID
Used to populate the Plant ID.
Plant Name
Used to populate the Plant Name field.
State
Used to populate the State field.
Utility ID
Used to populate the Company ID field.
Utility Name
Used to populate the Company Name field.
Zip Code
Used to populate the Zip Code field.
Power Price Curve

Power Price Curve family in the baseline Meridium APM database. The descriptions in
the following table reflect baseline behavior and assume that you have created Power
Price Curve records using the recommended workflow. Fields are listed in alphabetical
order in the following table; they may not appear or may appear in a different order on
each datasheet.
Field
Description
Enterprise
Support <1-8>
Code
Not used.
Enterprise
Support <1-8>
Description
Not used.
Power Price Date Indicates the time, day, month, and year for which the Power Price
Curve record represents the price. This is a required date field.
Power Price
Month
Indicates the month for which the Power Price Curve record
represents the price. This field is disabled and populated
automatically with the month in the Power Price Date field.
Power Price Year Indicates the year for which the Power Price Curve record represents
the price. This field is disabled and populated automatically with the
year in the Power Price Date field.
Price
Identifies the price of power ending at the time indicated in the

Power Price Date field. This is a required numeric field.
Zone
Identifies the zone for which the Power Price Curve Record
represents the price of power. When the price of power is calculated
for a Primary Capacity Incident record, the Meridium APM system
uses Power Price Curve records with a value in the Zone field that
matches the value in the Zone field in the Generation Unit record to
which the Primary Capacity Incident record is linked. This is a
required field, and a baseline rule exists to populate this field with a
list of System Codes in the MI_GM_POWER_PRICE_ZONE
System Code Table.
Unit Reference
Unit Reference family in the baseline Meridium APM database. The descriptions in the
following table reflect how the fields will be used when Unit Reference records are used
to create Generation Unit records via the Create Unit query. Fields are listed in
Field
GADS Region
Code
Description
Used to populate the GADS Region field. The Create Unit query
contains a prompt on this field so that when you run the query, you can
select a region and limit the results based upon that selection.
GADS Unit
Code
Used to populate the GADS Unit Code field.
GADS Unit
Name
Used to populate the Unit Name field.
GADS Utility
Code
Used to populate the GADS Utility Code field.
MW Rating
Used to populate the GADS Net Rating field.
State
Used as a prompt in the Create Unit query. When you run the query,
you can select a state and limit the results based upon that selection.
Unit Type
Used to populate the GADS Unit Type field.
Utilities Reference
Utilities Reference family in the baseline Meridium APM database. The descriptions in
the following table reflect how the fields will be used when Utilities Reference records
are used to create Generation Company records via the Create Company query. Fields are
listed in alphabetical order in the following table; they may not appear or may appear in a
Field
Description
Address 1
Address 2
City
Used to populate the City field.
Council
Used to populate the Council field.
GADS Utility Code
Used to populate the GADS Utility Code field.
GADS Utility Name
Used to populate the Company Name field.
GADS Utility Record

Number
Not used to populate any fields but is a required numeric

field.
Keyword
Used to populate the Keyword field.
Phone Fax
Used to populate the Phone Fax field.
Phone Voice
Used to populate the Phone Voice field.
State
Used to populate the State field.
Zip Code
Used to populate the Zip Code field.
System Code Tables Used by GM

The following table provides a list of the System Code Tables that are used by GM.
Table ID
MI_GM_AER_FUEL_CODE
Table Description Function

Generation
Management, AER
Fuel Types and
Description
Generation
Management,
MI_GM_AMPLIFICATION_CODE
Amplification
Code
Populates the list of values in

the Primary Fuel Code field
on the Defaults tab of
the Amplification Code field
in Primary Capacity Incident
records.
MI_GM_ENERGY_SOURCE

Generation
the Energy Source Code field
Management, EIA in Generation Fuel Annual
Energy Source
Report and Generation Fuel
Monthly Report records.
MI_GM_EVENT_TYPE_CODE

Generation
the Capacity Event Type field
Management, GM
in Primary Capacity Incident
Event Type Code
records.
MI_GM_EVENT_TYPE_DESC
Generation
Management, GM
Event Type
Description
MI_GM_FAILURE_MECHANISM

Generation
the Failure Mechanism Code
Management,
field in Primary Capacity
Failure Mechanism
Incident records.
Not currently used.

the following fields in
Generation Unit records:
MI_GM_FUEL_CODE
Generation
Management, GM
Fuel Code
Primary Fuel Code

Secondary Fuel Code
Tertiary Fuel Code
Quaternary Fuel
Code
Also populates the list of

values in the Fuel Code field
in Generation Forecast
records.
MI_GM_POWER_PRICE_ZONE

Generation
the Zone field in Power Price
Management,
Curve and Generation Unit
Power Price Zone
records.
MI_GM_MFG
Generation
Management,
Manufacturers
Contains all System Codes

that are used as references in
the
MI_GM_MFG_REFERENCE
System Code Table.
Generation
Management,
Manufacturer
Reference

various Manufacturer fields in
Generation Nameplate
records. System codes in this
System Code table contain
references from the
MI_GM_MFG System Code
Table.
MI_GM_MFG_REFERENCE
Generation
Management,
MI_GM_NERC_REPORT_FORMAT
NERC Report
Formats

the Report Format field in
Generation NERC Report
records.
Generation
Management,
NERC Report
Types

the Report Type field in
Generation NERC Report
records.
MI_GM_NERC_REPORT_TYPE
MI_GM_POWER_REGION
Generation
Management, GM
the GADS Region field in
Power Region or
Generation Plant records.
Council
MI_GM_POWER_SUBREGION
Generation
Management, GM the GADS Subregion field in
Power Subregion Generation Plant records.
MI_GM_PRIME_MOVER_CODE
Generation
Management,
Prime Mover
Codes
MI_GM_STATE
Generation
Management,
American and
Canadian States
MI_GM_UNIT_STATE
MI_GM_UNIT_LOADING
MI_GM_UNIT_TYPE

the Prime Mover field in
Generation Fuel Annual
Report and Generation Fuel
Monthly Report records.
the State field in the following
records:
Generation Company
Generation Plant
Utilities Reference
Plant Reference
Unit Reference
Generation State

the Unit State field in
Generation
Management,
Typical Unit
Loading

the Default Unit Loading field
in Generation Unit records,
the Unit Loading Profile
Expected field in Generation
Forecast records, and the Unit
Loading Characteristics field
in all Generation Nameplate
records.
Generation
Management, GM the GADS Unit Type field in
Unit Type
Generation Unit and GADS
Description
Cause Codes records.
URL Paths for Generation Management

Features
The following table lists and describes the URL paths for accessing Generation
Management features in Meridium APM. 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 following the path.
Feature
URL Path
Description
NERC
Reports
GM/NERC Runs the report for the specified entity.
Record
Linking
GM/Utilities
Lets you link two existing records together using a specified

relationship.
Parameters for the NERC Report URL

The URL for running a Generation NERC Report, meridium://GM/NERC, accepts the
parameters described in the following table. Click here for examples of using these
parameters.
Parameter
Name
Description
Accepted Value(s)
Notes
Key
Specifies which
A numeric Entity Key of the This parameter
Generation NERC Report desired Generation NERC

you want to run.
Report record.
is required.
Examples of the NERC Report URL
meridium://GM/NERC?Key=64251696617
Prompts you to save the results of the report to the desired location and then runs the
NERC report for the Generation NERC Report record with the Entity Key 64251696617.
Parameters for the GM Record Linking

URL
The URL for invoking the GM record linking functionality, meridium://GM/Utilities,
accepts the parameters described in the following table. For examples of using these
parameters, click here.
Parameter
Name
PredKey
Prompt
Description
Accepted Value(s) Notes
The Entity Key of

Specifies the
the record that will
predecessor record in
serve as the
This parameter is required.
the link that you
predecessor in the
want to create.
link.
Specifies whether a True
dialog box will
appear confirming False
the link.
A value of True will display a

message if the records are
successfully linked together. A
value of False will cause
Meridium APM NOT to display
this message.
RelKey
Routine
SucKey
The Entity Key of

Specifies the
relationship that you
serve as the
want to use to link
relationship in the
the records together.
link.
Invokes the record
linking functionality.
link
Specifies the
successor record in
the link that you
want to create.
The Entity Key of

serve as the
successor in the
link.
Examples of the GM Record Linking

URL
meridium://GM/Utilities?
Routine=link&PredKey=2004649&SuccKey=2003222&RelKey=1001&Prom
pt=True
Links the record with the Entity Key 2004649 to the record with the Entity Key 2003222
using the relationship with the relationship Family Key 1001 and afterwards displays a
confirmation message indicating that the records have been linked.
Generation Availability Database

System (GADS)
A series of databases that is used to collect and record data that is reported to the North
American Electric Reliability Corporation (NERC) and the Energy Information
Administration (EIA). Generation Management uses GADS data-reporting requirements.
Overview of Metrics and Scorecards

Meridium APM Metrics and Scorecards functionality empowers an organization to
clarify its vision and strategy for equipment performance and translate them into
objectives. Metrics and Scorecards integrates performance management theory with
sophisticated data analysis tools to prompt and facilitate actions that will improve
organizational performance.
Meridium APM Metrics and Scorecards, which uses Microsoft SQL Server Analysis
Services, enables the selection of dimensions and measures for easy access to data, multidimensional views, drill-down analysis, Scorecards, and Key Performance Indicators
(KPIs). Using Meridium APM Metrics and Scorecards functionality, you can measure
and examine your company's work requests, locations, equipment, work orders, and task
information. Through data analysis, you can regulate your maintenance and reliability
measurements. In addition, you can track progress by focusing on specific areas within
the organization using KPIs. These KPIs allow you to monitor the most important
variables that reflect mission success and company performance.
Note: For Meridium APM Metrics and Scorecards functionality to work properly,
Meridium APM must be able to connect to the SQL Server Analysis Server. If the
connection is lost or broken for any reason (e.g., the Analysis Server machine is offline
for maintenance), certain aspects of Meridium APM Metrics and Scorecards functionality
will not work until the connection is restored.
The primary tools that you will use within Meridium APM Metrics and Scorecards
include:
Metric Views: A visual representation of a multidimensional cube that has been

defined in SQL Server Analysis Services. When you create a Metric View, you
can choose the dimensions within the cube that contains the data you wish to use.
After the Metric View has been created, it can be presented in graphical and
tabular format.
Key Performance Indicator (KPI): A list of metrics that have been identified as
the most important variables reflecting mission success or organizational
performance. A KPI is a measure that is monitored over time, based on a
predetermined frequency. Users can create KPIs, schedule updates, create data
sources for KPIs, and define alerts for KPIs. A KPI can also be displayed on a
Home Page using a dial or a trend chart representation. By monitoring a list of
KPIs, your organization can spot performance problems and set steps for
improvement.
Scorecards: Reports that reflect the status of the KPIs. Via the Scorecards, users
can organize the KPIs that help the organization achieve various objectives. The
tabular view summarizes the status of multiple KPIs, helping you see the overall
trends in succinct format. Users can also drill down into a single KPI to view
more details. D
Metrics and Scorecards System

Requirements
The Metrics and Scorecards license is required to take advantage of Metrics and
Scorecards functionality. In addition, your system must contain the basic Meridium APM
system architecture and a SQL Server Analysis Services Server machine that will host the
Microsoft SQL Server Analysis Services software. The following versions of SQL Server
Analysis Services are supported in this version of Meridium APM:
Microsoft SQL Server Analysis Services 2008 R2

Microsoft SQL Server Analysis Services 2012
Note: The Meridium APM testing environment uses SQL Server Analysis Services 2008
R2 SP2 and SQL Server Analysis Services 2012.
Microsoft SQL Server Analysis Services provides the ability to analyze large amounts of
data quickly and easily. Analysis Services provides a means for accessing warehouses of
data by letting you create dimensional cubes from information in the database and
dimension tables. Numeric measures can be summed into pre-aggregated values while
cubes are being created. Cubes can contain data that is summarized, copied, or read
directly from the data warehouse. Cubes, dimensions, and partitions can be processed
(i.e., updated) to incorporate new or changed data from the data warehouse. Time,
location, equipment type, or sizes are common dimensions against which measures are
calculated and displayed in Meridium APM. Note that the data warehouse can be created
as a separate database, combining information from Meridium APM and other data
sources. On the other hand, dimensional cubes can be created by accessing the Meridium
APM database directly.
Together, Microsoft SQL Server Analysis Services and the Meridium APM Metrics and
Scorecards module functionality provide Meridium APM users with the ability to analyze
data in the Meridium APM database using the features of Analysis Services through the
Meridium APM Framework interface. To use the Meridium APM Metrics and Scorecards
functionality, you must incorporate SQL Server Analysis Services into your Meridium
APM system.
perform some configuration tasks specifically for the Metrics and Scorecard module. If
you choose to implement the Metrics and Scorecards module within your system, we
recommend using a configuration in which the Analysis Server exists on a machine that is
separate from the Meridium APM Application Server. This deployment scenario most
accurately reflects the Meridium APM testing environment. The following illustration
shows how the SQL Server Analysis Services Server connects to the basic Meridium
APM System architecture.
Note: While this image depicts only a single, dedicated Meridium APM Application
Server, keep in mind that your implementation may contain one or more of these
machines. The purpose of this image is to depict the interaction of the SQL Server
Analysis Server with the basic Meridium APM components not to provide details on the
basic components themselves. Note that while your Meridium APM system may contain
multiple dedicated Application Servers, it will contain only a single SQL Server Analysis
Server that ALL of those Application Servers will access.
What Are Cubes?

A cube is an Analysis Services object that provides a multi-dimensional representation of
data. When you build a cube in Analysis Services, you define measures and dimensions.
Measures are the quantitative values in the database that you want to analyze (e.g., Mean
Time Between Failures and Total Costs). Dimensions define exactly what you want to
measure (e.g., Location or Equipment Type). Hierarchies define how the dimensions are
aggregated.
Dimensions, hierarchies, and measures define a cube. For each intersection of a
dimension and measure, a value is calculated. For example, the Mean Time Between
Failures for Centrifugal Pumps in FCC Unit during 1999 could equal 152 Days.
Defining Measures for the Cube

Measures are the quantitative values in the database that you want to analyze. Typical
measures are sales, cost, and budget data. Measures are analyzed against the different
dimension categories of a cube. For example, you may want to analyze sales and budget
data (your measures) for a particular product (a dimension) across various countries
(specific levels of a geography dimension) during two particular years (levels of a time
dimension).
Defining Dimensions for the Cube
The dimensions of a cube represent distinct categories for analyzing business data.
Categories such as time, geography, or product line breakdowns are typical cube
dimensions.
Dimensions are usually organized into hierarchies of information that map to columns in
a relational database. Dimension hierarchies are grouped into levels consisting of
dimension members. Each level in a dimension can be rolled together to form the values
for the next highest level. For example, in a time dimension, days roll into months, and
months roll into quarters. The following hierarchy provides an example how different
levels might be arranged within a dimension:
Refinery
Unit
Function Location
Equipment
Rotating
Pump
Year
Month
Day
For more information on the time levels that are supported for use with Meridium APM
KPIs, see the topic Defining Time Levels for KPIs.
Overview of the Metrics and Scorecards

Data Model
The Metrics and Scorecards module allows you to work with three distinct items:
Scorecards
Key Performance Indicators (KPIs)
Metric Views
Meridium APM leverages its fundamental entity and relationship family infrastructure to
store data related to Scorecards, KPIs, and Metric Views. When attempting to understand
and make sense of the Meridium APM Metrics and Scorecards functionality, it is helpful
to visualize the data model. It may also be useful to remember that Scorecards, KPIs, and
Metric Views are simply customized views of individual records and Catalog items that
work together to make up the Scorecard, KPI, and Metric View.
A Scorecard is represented by a Scorecard record and all the records to which it is linked.
Each Scorecard record can be linked to the following records:
One or more KPI records.

One or more Reference Document records.
One or more KPI Objective records.
One or more KPI Perspective records.
A KPI is represented by a KPI record and all the records to which it is linked. Each KPI
record can be linked to the following records:
One or more KPI records.

One or more Reference Document records.
One or more KPI Measurement records.
One or more Scorecard records.
A Metric View is a Catalog item that displays data from an Analysis Services Cube,
which is represented by an Analysis Services Cube record. In order to build a Metric
View, the following items must be configured:
A SQL Server connection, which is defined in an SSAS Servers record.

An Analysis Services Cube, whose connection information is stored in the
Analysis Services Cube record.
Metrics and Scorecards Data Model

The following diagram illustrates how the entity and relationship families that are used in
Metrics and Scorecards are related to one another. The shaded boxes represent entity
families, and the arrows represent relationship families. You can determine the
predecessor and successor in each relationship definition from the direction of the arrow
head:
The box from which the arrow originates is the predecessor in that relationship
definition.
The box to which the arrow head points in the successor in that relationship
definition.
In this image, you can see that:
KPI records can be related to other KPI records through the Has Sub-Indicators
relationship.
The SSAS Servers family is not related to any other families. SSAS Servers
records support Metric Views.
The Analysis Services Cube family is not linked to any other KPI families.
Analysis Services Cube records support Metric Views.
About Security in Metrics and

Scorecards
Family-level permissions configured in the Configuration Manager serve as the
foundation for determining which records in Metrics and Scorecards users can and cannot
access in the Meridium APM Framework application. In addition to family-level
permissions, entity-level privileges can be defined to control access to specific Metrics
records.
For example, consider a user who has been granted View permissions on the Pump
family. That user will be able to view any Pump record in the Meridium APM Framework
application via the Record Manager. Similarly, any user who has been granted View
permissions to the KPI family will be able to open KPI records via the Record Manager.
To open records in Metrics and Scorecards, however, the user must be granted View
privileges on that specific KPI.
Via the Meridium APM Framework application, you can manage privileges for specific:
KPIs.
Scorecards.
Analysis Services Cube records.
Note that:
Only Super Users and members of the MI Metrics Administrator Security Group
can manage privileges for the Analysis Services Cube records.
Members of the MI Metrics Administrator Security Group can manage the entitylevel privileges for all KPIs and Scorecards. Other users can manage privileges
only for the KPIs and Scorecards that they created and for which they have been
granted entity-level update privileges.
Accessing the Metrics and Scorecards

Start Page
To access the Metrics and Scorecards Start Page:
Elimination, and then click Metrics and Scorecards.
The Metrics and Scorecards Start Page appears.
Aspects of the Metrics and Scorecards

Start Page
The Metrics and Scorecards Start Page contains the following links, which give you
quick access to various functions:
Create Metric View: Displays the Metric View Builder, which takes you step-bystep through the process of creating a Metric View.
Open Metric View: Displays the Open Metric View dialog box, from which you
can open a Metric View that currently exists in the Meridium APM Catalog.
Manage Key Performance Indicators: Displays the Key Performance Indicators

page, which displays a list of existing KPIs. From the Key Performance Indicators
page, you can access an existing KPI or create a new KPI.
Manage Scorecards: Displays the Scorecards page, where you can manage
existing Scorecards and create new Scorecards.
Administer Cube Privileges: Displays the Metrics Manager Administration page,

where you can manage Analysis Services Cube records and their privileges.
Note: This link appears only if you are a Super User or a member of the MI Metrics
Administrator Security Group.

Deploying and configuring the Metrics and Scorecards module 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 will need to deploy and
configure the Metrics and Scorecards module on top of the basic Meridium APM system
architecture.
are marked as Required if you must perform that step to take advantage of the Metrics
and Scorecards functionality.
Step Task
Deploy SQL Server Analysis Services on the SQL Server
Analysis Server machine.
1
These instructions assume that you have read the Metrics and
Scorecards hardware and software requirements and that you
have obtained the SQL Server Analysis Services software
installer.
Deploying SQL Server Analysis Services on the SQL Server
Analysis Server machine includes the following steps:
Install SQL Server Analysis Services.

Create the Analysis Services databases, data sources,
and cubes that you want to use with Meridium APM.
Grant permissions to the cubes that exist on the

Analysis Server.
Required/Optional
Required
Configure permissions necessary for updating KPIs.
Define time levels for KPIs.
Configure a cube for usage metrics tracking on the SQL

Server Analysis Server. This step will need to be completed
Optional
only if you will use Metrics and Scorecards to view the usage
metrics in a cube.
Schedule cubes for processing on the SQL Server Analysis

Server.
If needed, migrate SQL Server cubes from one version of SQL

Required
Server Analysis Services to another.
Assign Security Users to the Metrics and Scorecards Security

Required
Groups via the Configuration Manager application.
Create Analysis Services Cube records for each cube that has
been defined in SQL Server Analysis Services, via the
Required
Meridium APM Framework application.
Grant Security Users and Groups access rights to Analysis

Services Cube records via the Meridium APM Framework
application.
Required
Create a master KPI schedule item in Schedule Manager in

order for KPI measures to be updated on a recurring basis.
Required
Configure privileges for KPI via the Meridium APM

Framework application.
Required
10
Configure privileges for Scorecards via the Meridium APM

Framework application.
Required
Optional
Upgrade Workflow
are upgrading:
V3.5.1
V3.5.0 SP1 LP
V3.5.0
V3.4.5
Upgrading Metrics and Scorecards from

V3.5.1 to V3.6.0.0.0
The Metrics and Scorecards module 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.

V3.5.0 SP1 to V3.6.0.0.0
The following table lists the steps that are required to upgrade and configure Metrics and
Scorecards from V3.5.0 SP1 to V3.6.0.0.0. These steps assume that you have completed
the steps for upgrading the basic Meridium APM system architecture.
Step Task
1
Optional
Migrate your SQL Server
Analysis Services
were previously using SQL Server
database and cubes to
Analysis Services 2008 R2 and want
SQL Server Analysis
to use SQL Server Analysis Services
Services 2012.
2012 instead.

V3.5.0 to V3.6.0.0.0
Scorecards from V3.5.0 to V3.6.0.0.0. These steps assume that you have completed the
steps for upgrading the basic Meridium APM system architecture.
Step Task
1
Optional
Analysis Services
were previously using SQL Server
database and cubes to
Analysis Services 2008 R2 and want
SQL Server Analysis
to use SQL Server Analysis Services
Services 2012.
2012 instead.

V3.4.5 to V3.6.0.0.0
Scorecards from V3.4.5 to V3.6.0.0.0. These steps assume that you have completed the
steps for upgrading the basic Meridium APM system architecture.
Step Task
Optional
This step is required if you were
Analysis Services database and
previously using SQL Server
1
cubes to either of the following
Analysis Services 2005.
supported SQL Server Analysis
Services versions:
2008 R2
2012
This step is optional if you were

previously using SQL Server
Analysis Services 2008 R2 and
want to use SQL Server
Analysis Services 2012 instead.
Create a master scheduled item Required

for managing automatic KPI
updates, via the Schedule
This step is necessary for

supporting automatic KPI
updates.
Installing SQL Server Analysis Services

on the Sever
Why Does This Software Need to Be Installed?
SQL Server Analysis Services is the foundation for the Meridium APM Metrics and
Scorecards module because it serves as a storage and management mechanism for cubes,
which can then be accessed and viewed via the Meridium APM Framework application.
To support Metrics and Scorecards features, SQL Server Analysis Services must be
installed on the machine that will serve as the Analysis Server. The Analysis Server must
be set up as a machine that is separate from the Meridium APM Application Server.
Where Does This Software Need to Be Installed?

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

SQL Server Analysis Services can be installed using the SQL Server Standard Edition
installation package, which you may have received from Meridium, Inc. or from a thirdparty vendor, depending upon the licensing options you selected when you purchased the
Meridium APM product. Instructions for performing the installation can be found in the
documentation included in the SQL Server Standard Edition installation package.
Migrating SQL Server Cubes
If you are upgrading from a previous version of Meridium APM and you have existing
Metrics and Scorecards objects (e.g., Metric Views and KPIs) that are based upon SQL
Server 2005 or SQL Server 2008 R2 Analysis Services cubes, you may be able to migrate
your cubes while maintaining the proper functioning of your existing Meridium APM
objects.
If you have SQL Server Server 2005 cubes, you can migrate them to SQL Server
2008 R2 or SQL Server 2012.
If you have SQL Server 2008 R2 cubes, you can migrate them to SQL Server
2012.
The following workflow provides a general overview of the process for migrating cubes
from an older version of SQL Server Analysis Services to a newer version of SQL Server
Analysis Services. For more details, you should consult your SQL Server documentation.
IMPORTANT: Depending upon the complexity of your cubes, you may or may not be
able to migrate them successfully. We recommend that you attempt to migrate them using
the following procedure. If you review the cubes after the migration and determine that
the migration was not successful, the cubes will need to be rebuilt. In that case, any
Meridium APM KPIs and Metric Views that were based upon those cubes must also be
rebuilt.
To migrate cubes from an older version of SQL Server Analysis Services to a new version
of SQL Server Analysis Services:
1. On the SQL Server Analysis Services Server where the older version of SQL
Server Analysis Services is installed, open the SQL Server Management Studio
window.
2. Connect to the SQL Sever Analysis Services database that you want to upgrade.
3. In the Object Explorer pane, right-click Databases, and click Backup.
The Backup Database - <Database Name> window appears, where <Database Name> is
the name of the database that you want to upgrade.
4. To the right of the Backup file text box, click the Browse button, and specify the
location where the database will be backed up.
5. Specify any additional settings, and then click OK.
The selected database is saved to an ABF file in the specified location.
6. Open the SQL Server Management Studio window for the new version of SQL
Server Analysis Services.
7. In the Object Explorer pane, right-click Databases, and click New Database.
The New Database window appears.

8. In the Database name cell, enter a name for the database that you are migrating to
the new version of SQL Server Analysis Services.
9. Specify any additional settings, and then click OK.
The specified database is created, and a corresponding node appears in the Object
Explorer pane.
10. Right-click the node representing the new database, and click Restore.
The Restore Database window appears.
11. In the Backup file cell, enter the file path or click the Browse button and navigate
to the database file that you backed up in step 5.
12. Specify an additional settings, and then click OK.
Your SQL Server Analysis Services database is migrated to the new SQL Server Analysis
Services version.
13. In the Meridium APM Framework application, in the Analysis Services Cube
records that are associated with the cubes that you migrated, change the value in
the Analysis Services Type field so that it represents the newer version of SQL
Server Analysis Services. For example, if the current value is SSAS2005, you will
want to change it to SSAS2008 R2.
You can make this change manually via the Record Manager or by using an Update
Query. The following code represents a sample Update Query that you can use for
changing the Analysis Server Type from SSAS2005 to SSAS2008 R2. When you run the
query, you will be prompted to select from a list of Analysis Services Cube records that
contain SSAS2005 in the Analysis Server Type field. All records that you select from the
list will be updated with the value SSAS2008 R2.
UPDATE [MI Analysis Services Cube]
SET [MI Analysis Services Cube].[MI_AS_CUBE_ANALY_SERV_TYPE_C] =
'SSAS2008 R2'
WHERE [MI Analysis Services Cube].[MI_AS_CUBE_CUBE_NAME_CHR] IN (?
:s :mv :caption='Cube ID' :id=CUBEID :query='SELECT DISTINCT
[MI_AS_CUBE_CUBE_NAME_CHR] FROM [MI Analysis Services Cube] WHERE
[MI_AS_CUBE_ANALY_SERV_TYPE_C]=''SSAS2005'' ORDER BY
[MI_AS_CUBE_CUBE_NAME_CHR] ' :excl)
14. In the Meridium APM Framework application, in the Metrics and Scorecards
module, modify the remaining properties of each Analysis Services Cube record,
including selecting the appropriate new SQL Server Analysis Server. You can do
using the Change Cube builder, which is accessible via the Change Existing link
on the Cube Tasks menu.
15. View existing objects (e.g., Metric Views and KPIs) that are based upon the
migrated cubes to ensure that the correct data is being displayed. If the correct
data is not displayed, rebuild the cubes and the objects that are based upon them.
For details on rebuilding cubes, consult your SQL Server documentation.
Creating the Analysis Services Database,

Data Source, and Cubes
In addition to creating the Analysis Services database, data source, and cubes, the cubes
must be processed before they will be available for use in the Meridium APM system. For
details on completing these tasks, consult your SQL Server documentation.
Granting Permissions to Cubes in

Analysis Services
Permission to access and manage objects on the Analysis Server, including databases and
cubes, can be granted in various ways through SQL Server Analysis Services. Any
Meridium APM user who will need to access and manage Analysis Services objects,
either directly on the Analysis Server or indirectly through Meridium APM, will need to
have the proper permissions in order to access those objects. To ensure the proper
functioning of the Metrics and Scorecards module, we recommend that you grant
privileges to Analysis Services objects by assigning users the Analysis Services server
role on the Analysis Server. This level of permissions represents environment used by
Meridium, Inc. for testing the Metrics and Scorecards module.
Membership to the Analysis Services server role can be granted at the Windows user or
group level. You can assign this role to the individual Windows user accounts that will be
used to access cubes on the Analysis Server through Meridium APM, or you can assign
this role to Windows groups. For example, you might create a Meridium APM Metrics
Windows group, assign to that group all the Windows users who will need to access and
manage objects on the Analysis Server through Meridium APM, and then assign the
appropriate Windows users to that group.
For details on assigning users and groups to the Analysis Services server role, see your
SQL Server documentation.
Configuring Permissions Necessary for

KPI Updates
KPIs are built upon SQL Server Analysis Services Cubes and can be updated periodically
to reflect the most current data in those cubes. When a user attempts to update KPIs from
Meridium APM , a request is sent from Meridium APM to the Analysis Server. This
request is sent under the Anonymous user account. Therefore, for KPIs to be updated
successfully:
The Analysis Server must be configured to allow anonymous access.
-and
The Anonymous user account must have permission to access the database in
which the cube is stored.
If these steps have not been completed, an error message will be displayed when users
attempt to update KPIs in the Meridium APM system.
Enabling Anonymous Access

Anonymous access is not enabled by default on a new installation of SQL Server
Analysis Services but can be enabled via the SQL Server Surface Area Configuration
tool, which can be installed with SQL Server. For details on enabling anonymous access
to the Analysis Server, launch the SQL Server Surface Area Configuration tool, open the
Help, and search for the topic on allowing anonymous connections in SQL Server
Analysis Services.
Granting Permissions to the Anonymous User Account
After anonymous access has been enabled on the Analysis Server, you must configure
permissions that will give the ANONYMOUS LOGON account access to the cubes on
that server. The ANONYMOUS LOGON account must be granted at least Read
permissions to all cubes on the Analysis Server on which KPIs have been built. Read
permissions can be granted by creating a Role for the database which the cubes are
stored, granting members of that Role Read permissions to the desired cubes within that
database, and then assigning the ANONYMOUS LOGON account to that Role. For more
information on configuring permissions for Analysis Services, see your SQL Server
documentation.
Defining Time Levels for KPIs

When you build a KPI in the Metrics and Scorecards module, you will be prompted to
select a Time Dimension and Time Level from the source cube that will be used for
generating measurements over the specified period of time. The Metrics and Scorecards
module supports the use of Time Levels that are based upon standard calendar only. You
will not be able to select Time Levels that are based upon fiscal calendar.
The following table provides a list of the hierarchy levels that are supported by the
Meridium APM system. When you create a KPI, any hierarchy level that is not supported
by Meridium APM will not be available for selection in the KPI Builder. The Meridium
APM system uses the Key Columns and the Type defined in Analysis Services for each
level to validate the level and gather the information needed to build the KPI. For each
level listed in the following table, the Key Columns and Type must be defined as
specified.
Level
Key Columns set to:
Type
Year
Calendar year
Years
Semester
Calendar year semester
HalfYear
Quarter
Calendar year quarter
Quarters
Month
Calendar year month
Months
Week
Calendar year week
Weeks
Day
Calendar month day
Days
The Meridium APM system supports hierarchies that use any number and combination of
the levels listed in this table, with the following restrictions:
Year must be at the root level in all hierarchies.

Only Month can be used as the direct parent of the Day level (e.g., Year, Month,
Day is supported: Year, Week, Day is not supported).
Only Year can be the direct parent of the Week level (e.g., Year, Week is
supported: Year, Quarter, Week is not supported).
Providing Access from the Drill

Through Feature to the Record
Manager
3.
If desired, you can configure Analysis Services cubes so that when a user accesses the
Drill Through page, a link will be available to provide access to the associated record in
the Record Manager.
Note that the first column in the drill-through results grid contains the hyperlinked
Record ID of the associated record. If the Entity ID field is null, the hyperlink displays
the text Empty. Users can click any link to open the associated record in the Record
Manager.
Access to the Record Manager will be available in a Metric View only if the associated
cube has been properly configured in Analysis Services to include a link. The Drill
Through feature will provide access to the Record Manager if ENTY_KEY is returned as
one of the drill-through columns in the cube.
Note: In addition to having the proper cube privileges, users must have at least View
privileges at the family level to access a record in that family in the Record Manager.
Configuring a Cube for Usage Metrics

Tracking
You can track the usage of users in your system. Usage metrics are stored in the
MI_USAGE_METRICS system table. When a user logs in to Meridium APM, actions for
which usage metrics tracking has been enabled will be stored for that session and saved
in batch to the MI_USAGE_METRICS table when the user logs out of Meridium APM.
The following actions can be recorded in the MI_USAGE_METRICS table:
Login.
Logout.
Session time.
URL visit.
The following columns of data are stored in the MI_USAGE_METRICS table:
USME_KEY: The key value assigned to the action to identify it in the usage
metrics table.
USME_EVENT_TYPE_DVD: The type of event (login, logout, session time, or
URL visit).
SEUS_KEY: The key value associated with the Security User who performed the
action.
USME_EVENT_DT: The date and time the action was performed.
USME_EVENT_DESC_TX: A description of the action. For URL visits, this

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

the session time.
Note: Usage metrics are recorded only for activities performed via the Meridium APM
Framework application. Usage metrics are not recorded for activities performed in the
Meridium APM Administrative Applications.
To view the usage metrics that have been tracked for your system, you must create a cube
based upon the MI_USAGE_METRICS table. After you create the cube, you must create
a join between the MI_USAGE_METRICS table and the MIV_MI_IS_A_USER table.

You must also join the MIV_MI_IS_A_USER table to the
MIV_MI_HUMAN_RESOURCE table.
Note: Before you can use the cube in the Metrics and Scorecards module, you must
enable usage metrics tracking via the Configuration Manager application. For more
information, see the Configuration Manager Help.
How Are Cubes Used by Metrics and

Scorecards?
The Metrics and Scorecards module provide access through the Meridium APM
Framework application to the cubes that exist in SQL Server Analysis Services and
allows you to develop Metric Views and KPIs using the data that is stored in those cubes.
Before you can access Analysis Services cubes through Meridium, you will need to
complete various configuration tasks. Configuring cubes for use with Meridium APM
Metrics and Scorecards functionality consists of the following tasks:
Creating cubes in Analysis Services. Cubes are Analysis Services objects that can
be created, modified, and managed using tools that can be installed with SQL
Server Analysis Services. The first step in enabling Meridium APM Metrics and
Scorecards functionality is to create the desired cubes in Analysis Services.
For details on creating and managing cubes in Analysis Services, consult

the documentation that was included with your SQL Server Analysis
Services installation.
For information that is specific to Meridium APM, see the following

topics in this Help system:
Granting Permissions to Cubes in Analysis Services
Guidelines for Building Cubes for KPIs
Configuring a Cube for Usage Metrics Tracking
Providing Access from the Drill Through Feature to the Record

Manager
Creating Analysis Services Cube records in Meridium APM. After you have
created the desired Analysis Services cubes, you can create Meridium APM
objects (i.e., Metric Views and KPIs) that are based upon those cubes. Before you
can do so, you must first establish a link between the cubes and Meridium APM.
To establish this link, you will create an Analysis Services Cube record in
Meridium APM to contain all the identifying information for the cube and allow
Meridium APM to connect to the appropriate Analysis Server to access the
information associated with that cube.
Configure privileges for Analysis Services Cube records. After you have created
the necessary Analysis Services Cube records to make the desired cubes available
in Meridium APM, you will need to configure privileges for those Analysis
Services Cube records. In addition to Meridium APM standard family-level
security, Metrics uses entity-level security to control access to individual records.
Users must be able to access Analysis Services Cube records in order to access
and manage the Meridium APM objects (i.e., Metric Views and KPIs) that are
based upon the associated cubes.
All Meridium APM-specific tasks described above can be performed via the Metrics
Manager Administration page.
Accessing the Metrics Manager

Administration Page
From the Metrics Manager Administration page, you can manage Analysis Services Cube
records and their privileges.
To access the Metrics Manager Administration page:
In the Meridium APM Framework application, on the Metrics and Scorecards

Start Page, click the Administrative Cube Privileges link.
Note: The Administer Cube Privileges link appears only to Super Users and members of
the MI Metrics Administrator Security Group.
The Metrics Manager Administration page appears.
From the Metrics Manager Administration page, you can perform any of the following
tasks:
Create Analysis Services Cube records.

Modify Analysis Services Cube records.
Define which Security Users and Security Groups have permission to access
Delete Analysis Services Cube records.
Overview of the Metrics Manager

Administration Page
The Metrics Manager Administration page contains the following items:
Metrics Manager Cubes workspace: Contains a grid that displays a list of existing
Cube Tasks menu: Contains options that allow you to perform administrative
tasks for Analysis Services Cube records.
Metrics Manager Cube Workspace

The Metrics Manager Cubes workspace contains a grid that displays a list of existing
Each row in the grid contains a separate Analysis Services Cube record. By default, for
each row in the grid, the following columns are displayed:
Cube ID: Displays the value that exists in the Cube ID field of the Analysis
Services Cube record.
Short Description: Displays the value that exists in the Short Description field of
the Analysis Services Cube record.
Analysis Services Server: Displays the value that exists in the Analysis Services
Server field of the Analysis Services Cube record.
Database Name: Displays the value that exists in the Database Name field of the
Cube Name: Displays the value that exists in the Cube Name field of the Analysis
Last Processed Date: Displays the date on which the cube was last processed.
This value is not stored in the Analysis Services Cube record and is instead
retrieved from the associated cube in SQL Server Analysis Services when you
access the Metrics Manager Administration page.
Note: If a connection cannot be made to SQL Server Analysis Services, either because the
server is unavailable or because no value exists in the Analysis Services Server field of
the Analysis Services Cube record, then no date will be displayed in the Last Processed
Date column for that record.
Cube Tasks Menu
The Cube Tasks menu contains the following links:
Add Cube: Displays the Add Cube builder, which takes you step-by-step through
the process of creating a new Analysis Services Cube record.
Remove Cube: After displaying a confirmation message, deletes the selected
Change Existing: Displays the Change Cube builder, which takes you step-bystep through the process of modifying an Analysis Services Cube record.
Manage Privileges: Displays the Manage Cube Privileges window, where you
can define the Security Users and Security Groups that have privileges to the
selected Analysis Services Cube records.
Creating an Analysis Services Cube

Record
These instructions provide details on accessing and using the Add Cube builder to create
a new Analysis Services Cube record, which will store the information of a cube that has
been defined in SQL Server Analysis Services. After you create an Analysis Services
Cube record, you can create Metric Views based upon that cube.
To create a new Analysis Services Cube record:
1. In the Meridium APM Framework application, on the Metrics Manager

Administration page, on the Cube Tasks menu, click the Add Cube link.
The Add Cube builder appears, displaying the Select Analysis Server screen. The Select
Analysis Server screen displays a list of Analysis Servers that are configured for the
selected version. You can add new servers by clicking the Add Server button or delete
existing servers by clicking the Delete Server button.
2. In the list of available servers, select the server that contains the cube for which
you want to create an Analysis Services Cube record.
The Select Database screen appears.
4. In the Databases on [Server] list, select the database in which the cube resides,
and click the Next button.
The Select Cube screen appears, displaying a list of cubes that exist for the selected
database.
5. Select the desired cube, and click the Next button.

The Provide a name for the Cube screen appears.
6. In the Name text box, type the name of the Analysis Services Cube record. The
name should be unique and can contain no more than 50 characters.
7. In the Description text box, type a brief description of the cube. This field can
contain no more than 255 characters.
The Analysis Services Cube record is added to the database. The cube can now be used to
create Metric Views.
Modifying the Properties of an Analysis

Services Cube Record
To modify the properties of an Analysis Services Cube record:

Administration page, in the list of Analysis Services Cube records, select the
record that you want to modify.
2. On the Cube Tasks menu, click the Change Existing link.
The Change Cube builder appears, displaying the Select Analysis Server screen.
The list contains the Analysis Servers that are configured on the current Application
Server.
3. In the list of available servers, select the desired Analysis Server, and click the
Next button.
The Select Database screen appears.
4. Select the database in which the cube resides, and click the Next button.
The Select Cube screen appears.
5. Select the desired cube, and click the Next button.

The Provide a name for the cube screen appears.
6. In the Name text box, type the name for the Analysis Service Cube record.
7. In the Description text box, type a description for the cube.
Your changes are saved.
Deleting an Analysis Services Cube

Record
From the Metrics Manager Administration page, you can delete any Analysis Services
Cube record. Because an Analysis Services Cube record cannot be deleted if it is being
used by a Metric View, if you want to delete an Analysis Services Cube record, you must
first delete all of the associated Metric Views. Note that deleting an Analysis Services
Cube record from Meridium APM does not delete the associated cube from Analysis
Services.
To delete an Analysis Services Cube record:

1. In the Meridium APM Framework application, o the Metrics Manager
Administration page, in the list of existing Analysis Services Cube records, select
the row containing the record that you want to delete.
2. On the Cube Tasks menu, click the Remove Cube link.
A confirmation message appears.
The Analysis Services Cube record is deleted.
About Managing Cube Privileges

Cube privileges determine which Analysis Services Cube records are available for
selection for use within Metric Views. You can see the list of the users and groups that
have access to any Analysis Services Cube record by viewing its privileges. From the
Manage Cube Privileges window, you can:
Grant users and groups access rights to an Analysis Services Cube record.
Remove existing privileges for a user or group.
Note: Permission to access existing Metric Views is controlled by the privileges assigned
to the Analysis Services Cube records upon which Metric Views are based.
Accessing the Manage Cube Privileges

Window
To access the Manage Cube Privileges window:

Administration page, in the list of Analysis Services Cube records, select the
record whose privileges you want to manage.
2. On the Cube Tasks menu, click the Manage Privileges link.
The Manage Cube Privileges window appears, displaying a list of users and groups that
have been granted privileges to the cube associated with the selected Analysis Services
Cube record.
Granting Access to Analysis Services

Cube Records
When users have been granted access to Analysis Services Cube records, they will be
able to view the Metric Views, Scorecards, and reports that are based on the associated
Analysis Services cubes. Administrative users can give entire Security Groups or
individual Security Users permission to access particular Analysis Services Cube records
and can also delete these privileges.
Note: Privileges that are assigned in the Meridium APM Framework application work in
conjunction with family-level permissions defined via the Configuration Manager. To
access a given cube, not only must a user be granted access to the appropriate Analysis
Services Cube record using the following instructions, the user must also be granted the
necessary family-level permissions.
To grant a user or group access to an Analysis Services Cube record:
1. On the Manage Cube Privileges window, click the Add button.
The Add New Privilege dialog box appears.
2.
Click the option that corresponds to the type of privileges that you want to
assign: User or Group.
3. Select the desired user or group from the list.
Note: Inactive Security Groups may appear in the list.
4. Click OK.
The Add New Privileges dialog box closes, and the new user or group appears in the list
on the Manage Cube Privileges window. You can repeat these steps for each user or
group to whom you want to grant privileges to the cube associated with the Analysis
5. When you are finished setting up privileges, on the Manage Cube Privileges
window, click OK.
Your changes are saved to the database.
Deleting Cube Privileges

To delete privileges that are assigned to Security Users or Security Groups:
1. On the Manage Cube Privileges window, select the Security User or Security
Group whose privileges you want to delete.
2. Click the Remove button.
The Security User or Security Group is deleted from the list.
3. Continue deleting users and groups in this way until you have deleted all the
necessary privileges.
4. Click OK.
About Updating KPIs Automatically

KPIs can be scheduled to be updated automatically on a one-time or recurring basis.
Enabling this feature is a two-part process:
An administrative user must create a master scheduled item in the Meridium APM
Schedule Manager.
Individual KPIs must be scheduled for updates according to the desired frequency
via the Key Performance Indicators page.
The master scheduled item defines the maximum frequency with which individual KPIs
can be updated. For example, if you schedule the master scheduled item to run weekly,
individual KPIs cannot be scheduled to be updated more than once per week. Be sure to
create the master scheduled item to accommodate the most frequent schedule desired for
your KPIs.
Scheduling information for each KPI is stored in the KPI record along with a next
execution date. When the master schedule item is executed, all KPIs with a next
execution date that is on or before the current date will be updated, and their next
execution date will be incremented. Therefore, while the schedule information is stored at
the KPI level, the master scheduled item must be running for that schedule information to
be used. In other words, all KPIs that are scheduled as recurring items rely on the
execution of the master scheduled item.
Creating the Master Scheduled Item
To create a master KPI schedule item in the Schedule Manager:

1. Launch the Meridium APM Schedule Manager and log in.
2. On the Scheduled Items window, click the Add New... link.
The Choose a Meridium Assembly window appears.
3. Select the file Meridium.Metrics.dll, and click the Open button.

The KPI Update Schedule dialog box appears, displaying the Task tab.
4. Select the Recurring item check box, and then select the frequency for the
execution.
5. Click the User tab.
6. In the User ID text box, type the user ID of the Security User whose account you
want to use for executing this scheduled item. This user must a member of the MI
Metrics Administrator Security Group.
Note: If you specify the User ID of a Security User who is not a member of the MI
Metrics Administrator Security Group, when you click OK, a message will appear stating
that you have insufficient privileges to create a master KPI schedule item.
7. In the Password text box, type the password associated with the user ID that you
specified in the previous step.
8. Click OK.
The scheduled item is saved and appears in the Scheduled Items window.
Note: Only one master KPI schedule item can be saved in Schedule Manager at a time. If
you try to add an additional KPI schedule item in Schedule Manager, an error message
will appear and you will not be able to save the second schedule item.
About Scheduling Cubes for Processing

An Analysis Services cube is a combination of measures and dimensions that together
determine how a set of data can be viewed and analyzed. A cube is a static object and
initially represents the data that existed in Analysis Services for the selected measures
and dimensions when the cube was created. To keep a cube current, it must be processed
regularly, whereby the cube is updated with the most current data in Analysis Services.
To make sure that a cube always provides users with the most current data, you should
schedule it for processing regularly, usually on a daily basis. One way to process cubes
and shared dimensions successfully is to do so manually on the Analysis Server. Using
this method, you can process shared dimensions first and then process the related cubes.
Processing cubes manually, however, is not a viable option if you have many cubes that
you want to process on a daily basis.
Instead, a preferable option would be to schedule cubes for processing using Data
Transformation Services (DTS). This functionality is available in the SQL Server
Business Intelligence Development Studio, which is included in SQL Server Standard
Edition. For details on creating a DTS package that can be used to process objects
according to a custom schedule, see your SQL Server documentation.
About Full Processing and Incremental

Processing
When you process a cube on the Analysis Server, either manually or using a schedule,
you have the option of choosing full processing or incremental processing.
You should use full processing whenever structural changes have been made to
the cube. Structural changes include:
Deleting Meridium APM records that will delete Members from a

Dimension.
Updating Meridium APM records that will result in changing Member

names.
Rearranging levels or adding and deleting dimensions.
You can use incremental processing whenever you want to update the cube based
on the most recent data, as long as changes to the data do not have any affect on
the structure of the cube.
Note that full processing is performed, Metric Views will become inaccessible to users
who are currently logged in to the Meridium APM Framework and have already accessed
the Views. Users will need to restart the Meridium APM Framework application to access
Views after a cube has been processed using full processing, if they are logged in at the
time the processing occurred. Meridium APM does not need to be restarted when
incremental processing is used.
Therefore, if you are scheduling cubes for processing and need to use the full processing
option, you should schedule the processing so that it occurs at a time when users are not
using the Meridium APM system. If you are scheduling cubes that are unlikely to change,
you can use incremental processing and schedule the processing to occur at any time.
About KPI Privileges

The KPI privileges that you set up in the Meridium APM Framework application are
applied in addition to family-level permissions defined for the KPI families. To view a
KPI, a user must first have at least View permissions on the KPI families. In addition, a
user must be granted privileges to specific KPIs via the Meridium APM Framework
application. By managing privileges, you select the users and groups that should have
access rights to a given KPI. Additionally, via the Manage Privileges feature, you can
revoke privileges for users and groups that no longer need to access the KPI.
Note that Super Users and members of the MI Metrics Administrator Security Group can
manage privileges for ALL KPIs. Other users can manage the privileges for any KPI that
they create by default, unless those privileges are revoked by an administrative user. Nonadministrative users can also manage privileges for KPIs to which they have been granted
Update privileges.
Granting Access Rights to a KPI

To grant a user or group access rights to a KPI:
1. In the Meridium APM Framework application, on the Key Performance Indicators
page, in the list of KPIs, select the KPIs whose privileges you want to modify.
Note: If you select multiple KPIs, the Manage Privileges window will display only user
and group privileges that are assigned to all selected KPIs. Any user or group privilege
that does not apply to all selected KPIs will be hidden.
2. On the Selected KPI menu, click the Manage Privileges link.
The Manage Privileges window appears.
3. Click the Add button.
4. Select the option that corresponds to the type of privilege that you want to add:
User or Group.
5. In the list box, which appears below the option buttons, click the
select the user or group to which you want to grant access rights.
button, and

6. Click OK.
The user or group is added to the list on the Manage Privileges window.
7. In the new row, select the check box which corresponds to the type of privileges
that you want to assign to the user or group:
View: Allows the user or group to view the KPI.
Update: Allows the user or group to edit the KPI.
Delete: Allows the user or group to delete the KPI.
8. Click the Add button again to assign additional privileges.

-orClick OK to save your changes and close the Manage Privileges window.
Revoking Access Rights to a KPI
To revoke access rights to a KPI from a user or group:

1. In the Meridium APM Framework application, on the Key Performance Indicators
page, in the list of KPIs, select the KPIs whose privileges you want to modify.
Note: If you select multiple KPIs, the Manage Privileges window will display only user
and group privileges that are assigned to all selected KPIs. Any user or group privilege
that does not apply to all selected KPIs will be hidden.
2. On the Selected KPI menu, click the Manage Privileges link.
3. In the list, select the user or group whose privileges you want to revoke.
5. Click OK.
About Scorecard Privileges

The Scorecard privileges that you set up in the Meridium APM Framework application
are applied in addition to family-level permissions defined for the Scorecard family and
its related families. To view a Scorecard, a user must first have at least View permissions
on these families. In addition, a user must be granted privileges to specific Scorecards via
the Meridium APM Framework application. By managing privileges, you select the users
and groups that should have access rights to a given Scorecard. Additionally, you can
revoke privileges for users and groups that no longer need to access the Scorecard.
Note that Super Users and members of the MI Metrics Administrator Security Group can
manage privileges for ALL Scorecards. Other users can manage the privileges for any
Scorecard that they create by default, unless those privileges are revoked by an
administrative user. Non-administrative users can also manage privileges for Scorecards
to which they have been granted Update privileges.
Granting Access to a Scorecard

To grant a user or group access to a Scorecard:
1. In the Meridium APM Framework application, on the Scorecards page, in the list
of Scorecards, select the Scorecards whose privileges you want to modify.
Note: If you select multiple Scorecards, the Manage Privileges window will display only
the user and group privileges that are assigned to ALL the selected Scorecards. Any user
or group privilege that does not apply to all selected Scorecards will be hidden.
2. On the Scorecard menu, click the Manage Privileges link.

4. Select the Assign Privilege To option that corresponds to the type of privilege that
you want to add: User or Group.
5. In the list that appears below the option buttons, click the
the user or group to which you want to grant access rights.
button, and select

6. Click OK.
The user or group is added to the list on the Manage Privileges window.
7. In the new row, select the check box that corresponds to the type of privileges that
you want to assign to the user or group:
View: Allows the user or group to view the Scorecard.
Update: Allows the user or group to modify the Scorecard.
Delete: Allows the user or group to delete the Scorecard.
8. Click the Add button again to assign additional privileges.

Note: On the Manage Privileges window, you can also click the Remove button to revoke
privileges from a user or group.
-orClick OK to save your changes and close the Manage Privileges window.
Revoking Access Rights to a Scorecard

To revoke access rights to a Scorecard from a user or group:
1. In the Meridium APM Framework application, on the Scorecards page, in the list
of Scorecards, select the Scorecard whose privileges you want to modify. To
select multiple Scorecards, press the Shift key or the Ctrl key.
Note: If you select multiple Scorecards, the Manage Privileges window will display only
the user and group privileges that are assigned to ALL the selected Scorecards. Any user
or group privilege that does not apply to all selected Scorecards will be hidden.
2. On the Scorecard menu, click the Manage Privileges link.
3. In the list, select the user or group whose privileges you want to revoke.
5. Click OK to save your changes.
Metrics and Scorecards Security Groups

The following baseline Security Groups are provided for the Metrics and Scorecards
module:
MI Metrics Administrator: Provides users with full access to all Metrics and
Scorecards features and functions.
MI Metrics User: Provides users with view-only access to Metrics and Scorecards
functionality, provided that they have been granted the necessary entity-level
permissions.
The baseline privileges for these Security Groups are summarized in the following table.
Family
MI Metrics Administrator
MI Metrics User
Analysis Services Cube
View, Update, Insert, Delete View
Human Resource
View
KPI
KPI Measurement
KPI Objective
KPI Perspective
Reference Document
Scorecard
Security Group
View
View
Security User
View
View
SSAS Servers
Group Assignment
View
View
View
Has Privileges
Has Reference Documents
Has Sub Indicators
Is a User
View
Has KPI Measurement
Is Used By Scorecard
User Assignment
View
View
None
In addition to performing functions associated with the family-level privileges described

in this table, members of the MI Metrics Administrator Security Group:
Can see the Administer Cube Privileges link on the Metrics Manager Start Page in
the Meridium APM Framework application.
Can manage privileges for all KPIs in the Meridium APM Framework application.
Can manage privileges for all Scorecards in the Meridium APM Framework
application.
Have full access to all KPIs, Scorecards, and Cubes without needing to be granted
additional privileges via the Meridium APM Framework application.
About Navigating the Metrics and

Scorecards Module
Within the Meridium APM Framework application, the Metrics and Scorecards module
provides the following navigational tools:
A start page with links that provide access to various functions regarding Cube
Privileges, Metric Views, Key Performance Indicators, and Scorecards.
A Site Map that you can use to navigate within the Metrics and Scorecards
module. The Site Map indicates your current location and shows the typical path
for arriving there. To access a previous page, you can click its hyperlinked name
in the Site Map.
Note: If the Site Map includes the Results for <Metric View> page, the <Metric View> in
the Site Map hyperlink will be the Catalog caption of the Metric View.
Using the Metrics and Scorecards Site

Map
The Site Map in Metrics and Scorecards allows you to navigate from the current page to
other pages in Metrics and Scorecards. The Metrics link, which provides access to the
Metrics and Scorecards Start Page, will always be available. Links to other pages may
also be available depending upon your location in the application. You can click any link
that is available to access the corresponding page.
The following image shows an example of what the Site Map looks like on the View KPI
page. A red outline has been added to the image to highlight the Site Map.
Overview of Metric Views

Metric Views allow you to preserve portions of multi-dimensional cubes that have been
defined in SQL Server Analysis Services so they can be accessed for future analyses. A
Metric View saves a cube's parameter selections (e.g., dimensions and levels) so that you
can load these parameters automatically each time you want to view the information.
You can filter the data that is displayed in the Metric View by adding slices. Slices allow
you to specify a subset of data that you want to analyze. For example, you might have a
Metric View that contains failure and inventory data on all of the bearing types that exist
in a particular facility. Using this Metric View, you can see:
All the bearing types that exist in the facility.
How many of each bearing type exists in the facility.
How many bearing failures occurred last year in the facility.
Adding slices to this Metric View could allow you to view a more specific subset of data
to determine:
Which type of bearing fails most often?

How much did it cost last year to fix the bearings that failed most often?
A Metric View is displayed in both graph and table formats on the Results for <Metric
View> page, where <Metric View> is the Catalog caption of the saved Metric View. After
you create a Metric View you can:
Add a filter to the Metric View.

Drill-down in the Metric View.
Link a different Metric View to the current Metric View.
Export a Metric View.
Customize the appearance of the Metric View graph, using the standard graph
features.
Note: You will be able to view and manage only the Metric Views that are based upon
cubes associated with Analysis Services Cube records to which you have been granted
permission to access by an administrative user.
Creating a New Metric View

The Metric View Builder takes you step-by-step through the process of creating a Metric
View. When you create a Metric View, you select dimensions associated with a cube to
display and compare specific data.
To create a Metric View:
1. On the Metrics and Scorecards Start Page, click the Create Metric View link.
The Metric View Builder appears, displaying the Welcome screen.

The Select Metrics Cube screen appears.
3. In the Metric Cube list, select the cube for which you want to create the Metric
View. The list contains all Analysis Services Cube records that represent cubes
that have been defined in Analysis Services. This list is limited to the Analysis
Services Cube records that you have permission to access. As you select a cube,
its description appears in the Description display box.
The Select Measure(s) screen appears.
Note: If the SSAS server is not available or the Analysis Services Cube you select is not
available under the SSAS server, an error message will appear and you will not be able to
access the Select Measure(s) screen.
5. From the list of available measurements, select the desired measures.
The Select A Category screen appears.
7. Select a category, and click the Next button.

The Select Another Category screen appears.
8. If you want to define another category, select the Define a second category check
box, click the Next button, select a second category, and then click the Next
button.
Note: You cannot select the same value twice. If you select a value on the Select a
Category screen, that value will not appear on the Select Another Category screen. If you
select a value that has subcategories, the value will appear on the Select Another
Category screen so you can select one of the subcategories, but if you try to select that
value twice, when you click the Next button, an error message will appear.
-orIf you do not want to define another category, leave the check box cleared, and click the
Next button.
The Select Filters screen appears.
9. Select filters for the results. You can choose:

Show the top __ highest values or Show the bottom __ lowest values to
return the results which meet the criteria. The default number is 20. You
can change the number by typing another number in the field or clicking
the up or down button.
Don't use a filter if you do not want the results to be filtered.
Exclude Empty Values if you do not want empty values to be returned.

The View is created and displayed on the Results for <Metric View> page.
Opening an Existing Metric View

You can open any Metric View from the Metrics and Scorecards Start Page or directly
from the Meridium APM Catalog. In either case, to open a Metric View, you must first be
granted permission to access the cube upon which the Metric View is based.
To open an existing Metric View:
1. On the Metrics and Scorecards Start Page, click the Open Metric View link.
The Open Metric View dialog box appears.
2. Navigate to the Metric View that you want to open, select it, and click the Open
button.
The view appears on the Results for <Metric View> page, where <Metric View> is the
Catalog caption of the Metric View.
Hint: You can view the Metric View on the Design page by clicking the View in Designer
link on the Viewer Tasks menu.
Aspects of the Results for <Metric

View> Page
When you create a new Metric View or open an existing Metric View, the Results for
<Metric View> page will appear. The Results for <Metric View> page offers two views
of the Metric View, presented on two different tabs: Graph and Table.
Graph Tab
Table Tab
Viewer Tasks Menu

The Viewer Tasks menu offers various options depending on whether the Graph tab or the
Table tab is selected. The following image shows the options that are displayed when you
are viewing the Graph tab.
The Viewer Tasks menu on the Results for <Metric View> page contains the following
links:
View in Designer: Displays the Metric View on the Design page, where you can
see the columns, rows, slices, and measures included in the cube.
Linked Views: Displays the Linked Views page, where you can manage the
linked views for the current Metric View and perform tasks, such as
displaying a list of Views, adding a View, or deleting a View.
Reload Metric View: Refreshes the cube view with its saved values.
Note: After you click the Reload Metric View link, you must click the View in Designer
link and then navigate back to the Results for <Metric View> page to see the refreshed
values.
Drill Up: Drills up to the last dimension. This link appears only when you are
viewing the Graph tab after you have drilled down into the graph.
Toggle Slices: Displays or hides the slices at the bottom of the page. If the slices
are currently displayed, clicking this link will hide them. If the slices are currently
not displayed, clicking this link will display them.
Modify Title: Displays the Modify Title dialog box, where you can modify the title
of the graph. This link appears only when you are viewing the Graph tab.
Auto Scale Graph: Resets the Minimum, Maximum, and Step values of the y-axis
scale(s) to Auto, which creates a scale that is appropriate for the datapoints that
are plotted. You can click this link to revert the graph to the automatic scale after
setting a manual scale. This option will reset the right scale, the left scale, or both,
depending on which exists.
Transpose: Replaces the column members with the row members.
Export To: Displays a submenu that lets you export the View to Bitmap, HTML,
or XML.
Float Graph/Table: Opens the graph or table in its own window. You can un-float
the graph or table by closing the window that appears.
Common Tasks Menu

The Common Tasks menu on the Results for <Metric View> page contains the following
links:
New Metric View: Displays the Metric View Builder, which you can use to create
a new Metric View.
Open Metric View: Displays the Open Metric View dialog box, where you can
open an existing Metric View.
Save Metric View: Lets you save the Metric View to the Catalog.
Save Metric View As: Displays the Save As dialog box, where you can save the
Metric View to a new Catalog location in the Catalog or with a different name.
Delete Metric View: After asking for confirmation, deletes the current Metric
View.
Print Metric View: Displays the Print Dialog box, where you can specify how you
want to print the Metric View.
Page.
Help: Displays the context-sensitive Help topic for the Results for <Metric View>
page.
Overview of the Table Tab

The Table tab displays the same information in a grid format that is displayed on the
Graph tab in a graphical format. The table title displays the Catalog caption of the Metric
View.
Each row in the table corresponds to a value that appears along the x-axis of the graph. If
the rows of data correspond to actual Meridium APM records, the first column will be
hyperlinked so that you can open that record in the Record Manager. The columns in the
table represent the values that are plotted on the y-axis of the graph. Using the table tab,
you can see at a glance the actual values that have been plotted on the graph. For
example, the preceding table shows the number of customers for various cities. These
same values are represented graphically in the following image.
The values displayed on the Table tab are dynamic and always correspond to the current
graphical view. For example, if you drill up to see all customers for all cities, the
following information might be displayed.
In this case, the Table tab would be updated as shown in the following image.
If desired, you can filter or sort the values in the table.
About the Filter Options

If desired, you can add a filter to the table on the Table tab on the Results for <Metric
View> page to view a subset of the information that is currently displayed. A table that
has a filter applied shows the columns or rows that meet the criteria you specify for a
given column or row and temporarily hides the columns or rows that you do not want
displayed. You can modify the filter, remove the filter, or add multiple filters, if desired.
The filter options that you select on the Filter Dialog box function as a formulaic
expression, meaning that all the selections that you make work together to create a logical
statement, which tells the Meridium APM system which columns or rows to exclude from
the table.
The following filter options are available on the Filter Dialog box:
Limit Type: A list that contains options that you can select to display a specific
subset of the data that is currently displayed. After you select an option in the
Limit Type list, the Measure and Operator options are enabled.
The Limit Type list contains the following options.

1.
None: Displays the table as it appears when you first access it. If a filter
was applied to the table in the Metric View Builder, that filter is still
applied. When this option is selected, all options except the Non empty?
check box are disabled.
Top Count: Displays the top X number of values that appear in the column
that you specify in the Measure list, where X is the number that you
specify in the Value text box.
After you select this option in the Limit Type list, the Measure list and the Value text box
are enabled, and the default value in the Value text box is 0. You can modify this value, if
desired.
1.
Top Percent: Displays the top X percent of values that appear in the
column that you specify in the Measure list, where X is the number (i.e.,
percentage) that you specify in the Value text box.
After you select this option in the Limit Type list, the Measure list and Value text box are
enabled, and the default value in the Value text box is 100. You can modify this value, if
desired.
1.
Bottom Count: Displays the lower X number of values that appear in the
column that you specify in the Measure list, where X is the number that
you specify in the Value text box.
After you select this option in the Limit Type list, the Measure list and the Value text box
are enabled, and the default value in the Value text box is 0. You can modify this value, if
desired.
1.
Bottom Percent: Displays the lower X percent of values that appear in the
column that you specify in the Measure list, where X is the number (i.e.,
percentage) that you specify in the Value text box.
After you select this option in the Limit Type list, the Measure list and Value text box are
enabled, and the default value in the Value text box is 100. You can modify this value, if
desired.
1.
Measure Filter: Displays the values in the table that meet the requirements
that you select in the remaining options.
After you select the Measure Filter option in the Limit Type list, all the remaining options
are enabled. Note that only this option enables the Operator option.
Measure: A list that contains the column names that appear on the Select
Measure(s) screen in the Metric View Builder. You can use this option to select a
column that appears in the table and to which you want to apply the filter.
Operator: A list that contains operators, which function as the rule in the formula
expression. Operators let you compare the values in the rows in the table with the
value that appears in the Value text box to exclude only the rows that meet the
criteria specified in the formula expression.
The Operator list contains the following options:

1.
Greater Than: Displays the values in the X column that are greater than the
Y value.
Less Than: Displays the values in the X column that are less than the Y
value.
Equal To Or Greater Than: Displays the values in the X column that are
equal to or greater than the Y value.
Equal To Or Less Than: Displays the values in the X column that are equal
to or less than the Y value.
Value: A text box where you can specify a numeric value to which the values in
the column that you selected in the Measure list will be compared. The value in
this text box completes the formulaic expression.
Non empty: A check box that lets you specify whether or not you want to display
only those rows that contain values. You can select this check box to display only
rows that contain a value (i.e., not empty), or clear this check box if you want to
display rows that contain no value. Note that this check box is always enabled.
Note: If you select the Bottom Count option and the Non empty? option, fields that
contain a value of 0 will be included in the bottom count value that you specified and
then filtered from the table as empty values. For example, if the results contain 10 fields
whose value is 0 and you want to see in the results the bottom 20 values, if you select the
Non empty check box, the results will contain only 10 fields.
Adding a Filter to the Table

To filter the table on the Results for <Metric View> page:
1. Right-click any column or row header, and click Add Filter.
The Filter Dialog box appears.
2. Select the desired filter options.

3. Click OK.
The filter is applied, and the table is refreshed to show only the data that satisfies your
filter options.
Note: You can add additional filters by repeating these steps.
Modifying a Filter
To modify a filter that has already been applied:
1. Right-click any column or row header, and point to Edit Filter.
A submenu appears displaying a list of filters that have already been applied to the table.
2. Click the filter that you want to modify.

The Filter Dialog box appears, displaying the current filter selections.
3. Modify the filter selections as desired.

4. Click OK.
Your changes are saved, and the table is refreshed to reflect the changes.
Removing a Filter
To remove a filter that has been applied to the table:
1. Right-click any column or row header, and point to Remove Filter.
A submenu appears displaying the current filter selections.
2. Click the filter that you want to remove.

The filter is removed from the table, and the table is refreshed to reflect the changes.
Sorting the Table

When you sort a column, the rows in the table are arranged according to the contents of
the column you choose to sort. You can sort any column either in ascending or
descending order. When you use the Ascending option, the data in the column will be
sorted in ascending alphanumeric order: 0-9 then A to Z. When you use the Descending
option the data in the column will be sorted in descending alphanumeric order: 9 to 0 then
Z to A. For example, to sort a list of repair costs in order from the highest cost to the
lowest cost, sort the Repair Cost column using the Descending option.
Note: If there are multiple columns in the table, the rows will be sorted by the total
amount of data in those columns. For example, if Row A has values of 2,000 in the
Repair Cost column and 2,000 in the Maintenance Cost column, Row A will be sorted
according to a total of 4,000.
To sort a column in the table on the Results for <Metric View> page:
1. Right-click the column header of the column that you want to sort, and click Add
Sort.
The Sort Dialog box appears.
2. Select the desired options. You can select from the following options:
Measure: Select the measurement for the sorting.
Sort order: Select Ascending or Descending.
3. Click OK.
Your sort selections are applied to the table.
Note: You can add another level of sorting by repeating these steps.
Overview of the Graph Tab

The Graph tab on the Results for <Metric View> page provides a visual representation of
the Metric View. The graph title displays the Catalog caption of the Metric View.
Various options are available on the Graph tab. Most of the available options, particularly
those that let you modify the appearance of the graph, are similar to the options that are
available in standard graphs. This documentation assumes that you are familiar with the
standard functionality of the Graph Tool, and as such, limits discussion of the Graph tab
to features that are specific to Metric Views.
About the Graph Toolbar
The graph toolbar appears at the top of the graph on the Graph tab on the Results for
<Metric View> page. This toolbar is the same as the standard toolbar that appears on the
Graph page. It offers options that let you change the appearance of the graph.
About the Drill Down and Drill Up

Features
By drilling down into a graph, you can view the details of each item represented in the
graph. The items contain different levels, each with a greater amount of detail about a
given category. For example, consider the following graph.
This graph shows the number of customers for various cities. You can see that across all
cities, there are 18,000 customers. When you drill down into the All Customers bar, you
can see which specific cities have the highest and lowest number of customers, as the
following image shows.
You can continue to drill down into each bar to view additional details about each
category. After you drill down to the desired level of detail, you can drill up to return to
the previous level.
Drilling Down Into a Metric View

To drill down into a Metric View:
1. Position your pointer over the area of the graph where you want to view details.
Your pointer appears as a hand icon

selected component.
, indicating that you can drill down into the
2. Right-click the area, point to Drill Down, and then choose from a submenu of
available levels.
The details of the selected component are revealed.
Drilling Up in a Metric View

After you have drilled down into a Metric View, you can drill up to return to the previous
level.
To drill up in a Metric View:
1. On the Common Tasks menu, click the Drill Up link.
The system drills up one level.
2. Continue clicking the Drill Up link until you reach the desired level of detail.
Modifying the Title of the Graph

The following instructions provide details on modifying the title of a graph.
To change the title of a graph:
1. On the Results for <Metric View> page, on the Graph tab, on the Viewer Tasks
menu, click the Modify Title link.
The Modify Title dialog box appears, displaying the current title of the graph in the Title
text box.
2. In the Title text box, type the new title.

3. Click OK.
The graph title is updated with the new title. Note that you will need to save the Metric
View in order to save the updated title permanently.
About Right and Left Y-Axis Scales

When you create a new Metric View, the y-axis label and scale appear by default on the
left side of the graph. If the graph contains multiple measures for each x-axis category, all
the measures initially use the same scale, which is determined automatically using the
plotted minimum and maximum values. The default scale is not necessarily appropriate
for all the plotted values.
For example, consider the following graph, which shows the Average Sales Amount,
Average Unit Price, and Customer Count for a group of customers. In this example, note
that the upper limit of the y-axis scale has been determined automatically using the
largest plotted value: $3,491 as the average sales amount for all products.
In this figure, the Customer Count values are so small in comparison to the other plotted
values that they do not appear on the graph.
When a single scale is not appropriate for plotting all the values on the y-axis, you can
use two scales, one on the right and one on the left and choose which values should use
each scale. For example, look what happens to the graph shown above when we plot the
Customer Count against its own scale on the right:
Plotted against a much smaller scale, the red bars now appear on the graph. This has no
effect on the Average Sales Amount values, which are still plotted against the left y-axis
scale.
Choosing the Right or Left Y-Axis Scale

for a Measure
In a Metric View graph, you can choose whether each measure is plotted against the left
y-axis scale or the right y-axis scale. By default, all measures will be plotted against the
left y-axis scale in a new Metric View graph. You can move any or all measures to the
right y-axis scale, as desired. After you move a measure to the right y-axis scale, you can
move it back to the left y-axis scale, if desired.
When you move a measure from one scale to the other, the Meridium APM system will
reset the minimum and maximum values of both scales automatically as appropriate for
all measures plotted against each scale, even if either scale had previously been set to use
a manual range via the Properties dialog box. Therefore, we recommend that you first
choose which scale to plot each measure against and then adjust the scale manually if
needed.
To move a measure to the scale opposite from where it is currently plotted:
1. On the graph, right-click an item representing the measure that you want to move.
The item that you click will depend upon which gallery is being used. For example, in a
bar graph, you would point to any bar associated with any value for the measure that you
want to move. In the following graph, you would point to a green bar to move the
Average Unit Price.
Hint: Alternatively, you can point to the item on the legend representing the measure that
you want to move. This is especially useful in cases where the values are so small with
respect to the current scale that they do not appear on the graph (e.g., Customer Count on
the preceding graph).
2. Point to Y-Axis, and then click:
Right: To move the measure to the right scale.
Left: To move the measure to the left scale.
The measure is moved to the side that you selected. Note that the y-axis scales are reset
automatically based on values that are plotted against them. You can modify the ranges
manually, if desired. When you save the Metric View, your y-axis scale selections will be
saved along with it.
About the Drill Through Feature

In a Metric View, you can drill through certain values in a table or a graph to view the
underlying intersection data or source data. The intersection data displayed on the Drill
Through page is made up of data that is associated with the end value.
For example, suppose you have a Metric View that measures the total number of work
orders over time. In this case, you could drill through the total number of work orders
value for 2005 and view the underlying data that is associated with the work order, such
as the equipment to which the work order was assigned, the department in which the
equipment was located, and the manufacturer of the equipment to which the work order
was assigned. Drill through data provides you with a more complete understanding of the
Metric View.
The availability of the Drill Through feature and the data that is displayed in the Drill
Through window is determined by how the associated cube has been configured in
Analysis Services.
Accessing the Drill Through Page

To drill through a Metric View on the Results for <Metric View> page:
On the Graph tab, right-click the graph anywhere that the pointer appears as a
hand, and click Drill Through.
-orOn the Table tab, click a value in the table.

The Drill Through page appears, displaying the intersection data for the selected value.
Note: If you have performed a calculation on the Metric View, the Drill Through option is
disabled. The Drill Through operation cannot be performed on a calculated measure.
From the Drill Through window you can:
Access the record associated with any row if the cube has been configured
properly.
Export the results as a Microsoft Excel file, a text file, or an XML file.
Print the results.
Aspects of the Drill Through Page

The main display area of the Drill Through page contains a grid that displays the drillthrough results. By default, 1000 records are displayed per page. You can filter each
column by right-clicking the column header and selecting the desired filter from the list.
You can sort each column by clicking the column header, and you can adjust the column
width by clicking the column divider and sliding it to the right or left.
Below the grid, the following information and options are available:
Page X of X: Displays the current page number in the results and the total number
of pages in the Drill Through results.
X records found: Displays the total number of records in the Drill Through
results.
First link: Displays the first page in the Drill Through results. This link is enabled
when you are viewing any page other than the first page.
Previous link: Displays the previous page in the Drill Through results. This link is
enabled when you are viewing any page other than the first page.
Next link: Displays the next page in the Drill Through results. This link is
disabled only when you are viewing the last page in the Drill Through results.
Last link: Displays the last page in the Drill Through results. This link is enabled
when you are viewing any page other than the last page.
Page Size test box: Displays the number of rows of Drill Through data that is
currently displayed per page. You can change the page size by deleting the current
value in the Page Size text box, typing the desired value, and then pressing the
Enter key.
The Drill Through page contains two task menus, which you can use to perform tasks
related to the drill-through results: Drill Through Tasks and Common Tasks.
Drill Through Tasks Menu

The Drill Through Tasks menu on the Drill Through page contains the following link:
Export To: Displays the Export Drill Through Results dialog box, which lets you
export the drill-through results to a Microsoft Excel, Text, or XML file.
Apply Number Format: Displays the Drill Through Result Number Format dialog
box, which you can use to define the format for numeric values on the Drill
Through page.
Common Tasks Menu

The Common Tasks menu on the Drill Through page contains the following links:
a new Metric View.
Save Metric View: Saves any changes that you have made to the Metric View for
which you are viewing drill-through results.
Save Metric View As: Displays the Save As dialog box, where you can save the
Metric View to a new Catalog location in the Catalog or with a different name.
Delete Metric View: After asking for confirmation, deletes the Metric View for
which you are viewing drill-through results.
Print: Displays the Preview window, where you can print the Metric View.
Page.
Help: Displays the context-sensitive Help topic for the Drill Through page.
About Modifying the Format for

Numeric Values on the Drill Through
Page
On the Drill Through page, numeric values will be displayed using decimal notation (e.g.,
.18) by default. You can change the format of these values to be displayed using scientific
notation (e.g., 1.8e-001) using the Drill Through Result Number Format dialog box.
You can apply a format for:
All numeric values that are displayed on the Drill Through page.
Numeric values that are displayed in a single column on the Drill Through page.
When you use the Drill Through Result Number Format dialog box to specify a format
for numeric values displayed on the Drill Through page, your selections on the dialog
box are saved as a user preference.
Aspects of the Drill Through Results

Number Format Dialog Box
You can use the Drill Through Result Number Format dialog box to specify the format
for:
All numeric values that are displayed on the Drill Through page.
Numeric values that are displayed in a single column on the Drill Through page.
-or-
The Drill Through Result Number Format dialog box contains the following items:
Select Number Format list: Contains the following values:

o None: This value is selected by default the first time you access the Drill
Through Result Number Format dialog box.
o
Scientific: Specifies that numeric values will be displayed using scientific

notation (e.g., 1.8e-001).
Numeric: Specifies that numeric values will be displayed using decimal

notation (e.g., .18).
When a value is selected in this list, a box appears to the right of the list that you can use
to set the number of decimal points that are displayed. The value 0 (zero) is specified in
this box by default. Below the box, an example value appears that corresponds with the
value specified in the box.
OK button: Closes the Drill Through Result Number Format dialog box and
updates the format of the numeric values that are displayed on the Drill Through
page according to your changes.
Cancel button: Closes the Drill Through Result Number Format dialog box
without making any changes to the format of the numeric values displayed on the
Drill Through page.
Help button: Displays the context-sensitive Help topic for the Set Y-Axis Max
Value dialog box.
Modifying the Format For All Numeric

Values Displayed on the Drill Through
Page
On the Drill Through page, numeric values are displayed using standard decimal notation
by default. You can modify the number of decimal places that are displayed for this
notation or specify that all numeric values on the page be displayed using scientific
notation via the Drill Through Result Number Format dialog box. You can also modify
the format for numeric values that are displayed in a single column on the Drill Through
page.
To modify the number format for all numeric values displayed on the Drill Through page:
1. On the Drill Through Tasks menu, click the Apply Number Format link.
The Drill Through Result Number Format dialog box appears.
2. In the Select Number Format list, select the format that you want to apply to all
numeric values on the page.
A box that contains the value 0 (zero) appears to the right of the Select Number Format
list. For example, the following image shows an example of the Drill Through Result
Number Format dialog box when Numeric is selected in the Select Number Format list.
3. In the box, use the

buttons to specify the number of decimals places that will
be displayed for all numeric values on the page.
The value below the box is updated automatically to reflect the number of decimal places
you selected. Continuing with the example, the following image shows what this value
looks like when you have specified the value 2 in the box.
4. Click OK.
The Drill Through Result Number Format dialog box closes, the number format is
applied, and the Drill Through page returns to focus. Continuing with the example, the
following image shows what the Drill Through page looks like when you have specified
a Numeric format (i.e., decimal notation) with 2 decimal places.
Modifying the Format For Numeric

Values Displayed in a Single Column on
the Drill Through Page
On the Drill Through page, numeric values are displayed using standard decimal notation
by default. You can modify the number of decimal places that are displayed for this
notation or specify that numeric values be displayed using scientific notation via the Drill
Through Result Number Format dialog box. If the numeric values in one column should
be displayed in a different format than the rest of the numeric values on the page, you can
modify the format for the numeric values that are displayed in that column only. You can
also modify the format for all the numeric values that are on the Drill Through page.
To modify the number format for numeric values that are displayed in a single column on
the Drill Through page:
1. Right-click the name of the column that contains the numeric values for which
you want to modify the format.
A submenu appears.
2. Click the Apply Number Format link.

The Drill Through Result Number Format dialog box appears.
3. In the Select Number Format list, select the format that you want to apply to the
numeric values in the column.
A box that contains the value 0 (zero) appears to the right of the Select Number Format
list. For example, the following image shows an example of the Drill Through Result
Number Format dialog box when Numeric is selected in the Select Number Format list.
4. In the box, use the

buttons to specify the number of decimals places that will
be displayed for the numeric values in the column.
The value below the box is updated automatically to reflect the number of decimal places
you selected. Continuing with the example, the following image shows what this value
looks like when you have specified the value 2 in the box.
5. Click OK.
The Drill Through Result Number Format dialog box closes, the number format is
applied, and the Drill Through page returns to focus. Continuing with the example, the
following image shows what the Drill Through page looks like when you have specified
a Numeric format (i.e., decimal notation) with 2 decimal places. Note that the format was
applied to a single column only.
Exporting the Drill Through Results

From the Drill Through page, you can export the results that are displayed in the grid to a
Microsoft Excel file, a text file, or an XML file. The following instructions provide
details on performing the export operation.
To export the result displayed on the Drill Through page to a file:
1. On the Drill Through page, on the Drill Through Tasks menu, click the Export
link.
The Export Drill Through Results dialog box appears.
2. In the File Type list, choose the type of file that you want to create. You can select
MS Excel, Text, or XML.
3. Click the OK button.
The Export to File dialog box appears.
4. Navigate to where you want to save the file.

5. In the File name text box, type a name for the file that will be created.
Note: The selection in the Save as type list corresponds to the file type that you selected
on the Export Drill Through Results dialog box. You cannot change this selection. If you
want to create a different type of file, click Cancel, and start over.
The file is created in the location that you specified.
Printing the Drill Through Data

From the Drill Through page, you can print the results that are displayed in the grid. The
following instructions provide details on performing this procedure.
To print the results that are displayed on the Drill Through page:
1. On the Drill Through page, on the Common Tasks menu, click the Print link.
The Preview window appears.
2. Using the toolbar on the Preview window, customize the print options as desired.
3. Click the Print button.
The Print dialog box appears.
4. Choose the desired options, and click OK.
The Drill Through results print to the selected printer.
Hiding and Displaying Slices

If desired, you can hide or display the descriptions of the slices that are applied to a
Metric View.
The following instructions provide details on hiding or displaying slices via the Results
for <Metric View> page. These instructions assume that you are viewing a Metric View
that includes slices.
To hide or display the slices:
On the Viewer Tasks menu, click the Toggle Slices link.
The slices are displayed or hidden below the Metric View as appropriate.
If the slices are currently displayed, clicking this link will hide them.
If the slices are currently not displayed, clicking this link will display them.
The following image shows the Graph tab for a Metric View, where the slices are
displayed at the bottom of the page. A red outline has been added to the image to
highlight the slices.
Exporting a Metric View

On the Results for <Metric View> page, you can export a Metric View to a location
outside the Meridium APM Framework application. You can export a Metric View in the
following formats: bitmap, XML, HTML, and Microsoft Excel file.
Note: You can export a Metric View to a Microsoft Excel file only when you are viewing
a table. You can export a file to a bitmap only when you are viewing a graph.
To export a Metric View:

1. On the Viewer Tasks menu, click the Export To link, and select the desired format:
Bitmap, HTML, XML, or Excel.
Note: If you choose to export a table to an Excel file and you do not have Microsoft
Excel installed on your computer, you will receive an error message. This is not a fatal
error.
The Save As dialog box appears. Note that the type of file that you selected appears in the
Save As Type text box.
3. In the Save As dialog box, specify the name and location of the exported file.
The Metric View is exported to the specified location.
Floating the Metric View

If desired, you can open a Metric View in its own window by "floating" it. This option is
available for both the Graph tab and the Table tab.
To float a graph or table:
On the Viewer Tasks menu, click the Float Table or Float Graph as appropriate.
The View is opened in a separate window.
To close the separate window and return to the Results for <Metric View> page, click the
X in the upper, right corner of the window.
About Linked Metric Views

You can associate one Metric View with another Metric View via the Linked Views page.
The purpose of linking two items is to create a connection or a relationship between
them. Note that because Metric Views are Catalog items and not records, a link between
two Metric Views is not the same as a link between two records.
Accessing the Linked Views Page

To access the Linked Views page:
On the Results for <Metric View> page, on the Viewer Tasks menu, click the
Linked Views link.
The Linked Views page appears.
Aspects of the Linked Views Page

The Linked Views page displays a list of Metric Views that are associated with the current
Metric View.
For each associated Metric View, the list displays the following information:
ID: The name of the Metric View as defined when the Metric View was last
saved.
Description: A description of the Metric View as defined when the Metric View
was last saved.
Slices: All slices that have been added to the Metric View.
From the Linked Views page, you can perform the following tasks:
Add a Metric View to the list.

Open a Metric View from the list.
Remove a Metric View from the list.
Add a slice to a Metric View in the list.
Remove a slice from a Metric View in the list.
Note that any changes that you make to linked views via the Linked Views page will be
saved automatically when you navigate away from that page.
Linking a New Metric View to the

Current Metric View
To add a Metric View to the list:
1. On the Linked View Tasks menu, click the New Linked View menu.
The Link Cube View dialog box appears.
2. Navigate to the folder containing the Metric View you want to add to the list,
select the Metric View, and click the Open button.
The Metric View you selected appears in the list on the Linked Views page. Your changes
will be saved automatically when you navigate away from the Linked Views page.
Opening a Metric View From the List of

Linked Views
To open a Metric View from the list:
1. On the Linked Views page, in the list of Metric Views, select the row containing
the Metric View you want to open.
2. In the Linked View Tasks menu, click the Open Linked View link.
The linked Metric View appears on the Results for <Metric View> page.
Adding Slices to a Linked Metric View

To add a slice to a linked Metric View:
the Metric View to which you want to add a slice.
2. In the Slices Tasks menu, click the Add Slice link.
The Add Slice Dialog box appears.
3. Expand the tree, and select the desired slices to add the Metric View.
The selected slices appears in the Linked Views list in the Slices column for the row
containing the selected Metric View.
Your changes will be saved automatically when you navigate away from the Linked
Views page.
Removing a Slice from a Linked Metric

View
To remove a slice from a linked Metric View:
the Metric View from which you want to remove a slice.
2. In the Slices Tasks menu, click the Remove Slice link.
The Remove Slice Dialog box appears.
3. Select the row containing the slice you want to remove from the Metric View, and
click the Remove button.
A confirmation message appears, asking if you are sure you want to remove the selected
slice form the Metric View.
4. Click OK.
5. Click the Close button on the Remove Slice Dialog box.
On the Linked Views page, in the slices column, note that the slice you removed no
longer appears.
Your changes will be saved automatically when you navigate away from the Linked
Views page.
Removing a Linked Metric View

To remove a linked Metric View:
1. On the Linked Views page, in the list of Metric Views, select the row that contains
the linked Metric View that you want to remove.
2. On the Linked View Tasks menu, click the Remove Linked View link.
A confirmation message appears, asking if you are sure you want to remove the Metric
View from the list.
3. Click OK.
The selected Metric View is removed from the list. Your changes will be saved
automatically when you navigate away from the Linked Views page.
About Including Actions in Metric

Views
If desired, you can configure SQL Server Analysis Services cubes to contain Actions,
which can provide users with access to extended data and information. When a user rightclicks the Target in the Metric View that has been built upon a cube that contains Actions,
those Actions will appear on the shortcut menu. When a user clicks an Action, the Action
will be invoked, and the target data will appear. If desired, you can configure multiple
Actions for a cube.
The available Actions and the information that is displayed is determined by how the
associated cube has been configured in Analysis Services.
Actions are attached to Targets, which correspond to member levels in a Metric

View.
Note: Actions can be attached to a Target at ALL member levels, including the cube
level. Additionally, if an Action has been configured on a member level, you will be able
to see the Action only after you have drilled down to the associated level. For example, if
an Action has been configured at the Customer A level and you right-click the graph on
the All Customers level, the Action will not appear on the shortcut menu. You will be able
to see the Action on the shortcut menu after you drill down to the Customer level and
right-click the Customer A member.
Meridium APM supports the use of any Action for which a URL has been defined.
The URL that is defined for the Action will determine the result of the Action.
The Meridium APM documentation does not include details on configuring Actions.
Rather, we limit our discussion of Actions to how they can be invoked after they have
been properly configured. For more information on defining Actions within Analysis
Services cubes, refer to the SQL Server documentation.
Invoking Actions
Actions that have been defined in Analysis Services cubes will be available in Meridium
APM Metrics and Scorecards within the Metric Views that have been built upon those
cubes. When you click the Action, the Meridium APM system will launch the URL
behind that Action.
If the URL is a Meridium APM URL, the target will open within the Meridium
APM Framework Application. For example, an Action can be configured to open
a record in the Record manager. When you click the Action, the Record Manager
page will appear, displaying the record specified in the URL.
If the URL specifies a target that is external to Meridium APM, the appropriate
application will be opened.
For example, Actions could be configured to display your customers' website on each
customer level member.
To invoke an Action that has been defined within an Analysis Services cube:
1. Open the Metric View that is built up on the cube for which the Action has been
defined.
The Metric View appears on the Results for <Metric View> page.
2. On the Results for <Metric View> page, on the Graph tab, right-click the Target
in the graph.
The submenu appears, displaying the standard graph tools and all the Actions that have
been defined for that cube.
3. Click the Action that you want to open.

The URL is invoked, and the results appear as specified in the URL.
Accessing the Design Page

To access the Design page:
On the Results for <Metric View> page, on the Viewer Tasks menu, click the View
in Designer link.
The Design page appears.
Aspects of the Design Page

The Design page allows you to modify a Metric View by adding or removing slices and
changing the x-axis, column, and measure values. The following image shows the Design
page. Labels have been added to the image to call out the sections on this page.
The Design page consists of the following sections, which are labeled according to the
call outs shown in the preceding image:
A: The designer tree, which contains the list of dimensions that are available for
the cube from which the Metric View was created. The name of the cube is
displayed in the label above the tree. You can use this tree to add elements to the
Metric View.
B: The designer workspace, which displays the elements that are currently
selected for the columns, rows, measures, and slices in the Metric View. The
designer workspace contains the following areas, which display the elements that
are currently selected from the designer tree:
Legend/Columns: Displays the element that is currently selected for the

legend values in the graph and the column values in the table.
X-Axis/Rows: Displays the element that is currently selected for the x-axis
vales in the graph and the row values in the table.
Select Measure: Displays the element that is currently selected for the
measure values in the graph and the table.
Select Slices: Displays the element that is currently selected for the slice
values in the graph and the table.
When you add an element to the designer workspace, the MDX query syntax that defines
that element is displayed below the area label. In these expressions, the first level of the
dimension appears first, followed by the drill-down path or hierarchy in that dimension.
C: The MDX Query pane, which contains the MDX Query syntax that defines the
Metric View. This section is displayed by default. You can, however, hide this
section by clicking the
in the top right corner of the pane.
Adding Slices to a Metric View

On the Design page, you can add slices to a Metric View. A slice restricts the data that is
shown in a Metric View. After you add a slice to a Metric View:
The data shown in the Metric View will change to reflect the selected slice(s).
A description of the slice(s) will appear below the title of the graph.
The following image shows an example of the Graph tab in a Metric View to which
multiple slices have been added. A red outline has been added to the image to highlight
the slices.
To add a slice to a Metric View:

1. On the Design Page, in the designer tree, select the slice element that you want to
add to the Metric View.
2. Drag the element from the designer tree and drop it in the Select Slices section in
the designer workspace.
The slices element is added to the Metric View and appears in the Select Slices section of
the designer workspace.
Additionally, if you view the Metric View graph, you can see that the data displayed in
the graph has changed to reflect the slices that you selected.
Viewer Tasks Menu

The Viewer Tasks menu on the Design page contains the following links:
View Results: Displays the Metric View on the Results for <Metric View> page.
Toggle MDX: Displays the MDX query at the bottom of the page.
Toggle Graph: Displays the graph preview in a floating window.
Note: Changes you make to the graph in the floating window will not be reflected in the
graph when you access it on the Results for <Metric View> page.
Toggle Table: Displays the table preview in a floating window.

Calculation: Displays a submenu with three options: Contribution, Custom, and
Difference. Each option displays the Calculated Member Wizard, which lets you
design the appropriate calculation option.
Transpose: Switches the column members with the row members.
Common Tasks Menu

The Common Tasks menu on the Design page contains the following links:
a new Metric View.
Save Metric View: Lets you save the Metric View to the Catalog.
Save Metric View As: Displays the Save As dialog box, where you can save an
existing Metric View to a new Catalog location or with a different name.
Delete Metric View: After displaying a confirmation message, deletes the current
Metric View.
Results for <Metric View> page on your desktop (create shortcut), in an email
message, or on a Home Page. This link appears if the Metric View has been
saved.
Note: The Send To option on the Design page does not create a link to the Design page. It
creates a link to the Results for <Metric View> page.
Help: Displays the context-sensitive Help topic for the Design page.
Changing the Current Selections

You can change the current selections on the Design page by using these options:
To add an element to the Metric View, select the element from the left side and
drag it into the area under the appropriate heading. Note that you can select any
element in the designer tree and not necessarily the lowest level member in the
hierarchy. You can choose a high-level member, such as "Store" or lower level
such as "Store Country" or "Store State," or even the particular store number.
To remove an element from the Metric View, right-click the selected element and
choose Remove.
To obtain a cross-join of multiple dimensions in rows or columns, select the

element from the list on the right and drop it in a different area of the field.
Rules for Working on the Design Page

When working on the Design page, it is helpful to keep in mind the following rules:
An element cannot be used twice in the designer workspace. For example, you
cannot add the same element to the Legend/Column area that already appears in
the Select Measure area.
You can add only one member of each dimension as a slice. You cannot add a
slice to the Legend/Column, X-Axis/Rows, or Select Measures areas.
You can use the drag-and-drop method to move elements from the designer tree to
the designer workspace. If you select a dimension element, all members of that
dimension will be included in the area to which it is added.
You can replace an element in the Legend/Column and X-Axis/Rows areas by

dragging the element that you and dropping it on the element that you want to
replace
You can cross-join two dimensions or add an additional element by dragging the
element that you want and dropping it into the blank space in the Legend/Column
or X-Axis/Rows areas.
If you will not be selecting Measures on rows or columns, the default measure
will automatically populate. You can drag a different measure here to use one
other than the default. If you are selecting Measures on rows or columns, this
section will be blank.
Overview of MDX Queries

Multidimensional Expressions (MDX) is the language that Microsoft included with
OLAP Services to allow access to OLAP data from client applications. MDX is used to
describe multidimensional queries.
In Metrics and Scorecards, you can examine the corresponding MDX query, which can
handle numerous measures and dimensions. The MDX Query window allows you to
manipulate the code on which the data is generated. It is strongly suggested that you do
not use the MDX Query window without prior knowledge of how to manipulate MDX
Query code. Note that if you open the MDX Query window while the Design page is
open, the MDX Query window will reflect the dimensions and levels currently selected.
By default, the MDX Query window is hidden on the Design page until you select to view
it. When writing an MDX statement, the View in Designer link is disabled.
To specify a dataset, an MDX query must contain the following information:
The number of axes.

The members from each dimension to include on each axis of the MDX query.
The name of the Cube that sets the context of the MDX query.
The members from a slicer dimension on which data is sliced for members from
axis dimensions.
The general syntax of an MDX statement is:

SELECT [<axis_specification>
[, <axis_specification>]]
FROM [<Cube_specification>]
WHERE [<slicer_specification>]]
In MDX, the SELECT statement is used to specify a dataset containing a subset of
multidimensional data. The SELECT clause determines the axis dimensions of an MDX
SELECT statement. The FROM clause determines which Cube is to be used when
extracting data to populate the result set of the MDX SELECT statement. The optional
WHERE clause determines which dimension or member to use as a slicer dimension; this
restricts the results to a specific dimension or member.
Accessing the MDX Query Window

To access the MDX Query Page:
1. On the Design page, click the Toggle MDX link on the Viewer Tasks menu.
The MDX Query display area appears at the bottom of the screen.
Hint: You can drag and dock the MDX query window to any other location on the screen.
2. If desired, make changes to the query, if desired, and test your changes by
clicking the Test button or reset your changes by clicking the Reset button.
3. Any changes that you make will be saved when you save the Metric View.
Types of Calculations
On the Design page, you can make three types of calculations on existing Metric Views.
Based on your selections, the expression will then become an additional column or row in
the Metric View. After adding the expression to the Metric View Builder, it will be listed
as a column, row, measure, or slice, based on your preferences.
The following calculation types are available on the Design page.
Contribution: A calculation that determines the contribution per portion for

different factors. For example, you can calculate the percentages from different
categories from total cost, such as maintenance, repair, and lost opportunity.
When using a contribution calculation, you can choose to evaluate the improvement
opportunity for a particular family in comparison to all other families. An "improvement
opportunity cost" means the potential for saving money if a particular factor is properly
evaluated to prevent failures and downtime.
Custom: A calculation that lets you specify a query based on a more sophisticated
calculation than the difference or contribution. As a result, customized
calculations are generally the most difficult ones to create.
Difference: A calculation that involves he subtraction of one member from

another to compute a value. A value expression can be used to evaluate overall
repair cost and the costs within a site.
The difference in a repair cost can be compared between all repairs for a site and then all
repairs for a particular piece of equipment. For this type of calculation, you would type in
the [Measures] dimension and then the measure Cube, [Site Repair]. Note that when
calculating the difference in a repair cost column, drilling down the hierarchy will
automatically calculate the difference.
Select the calculation that best suits your needs. Note that the contribution and difference
calculations involve a user interface, while the custom calculation requires you to write
an MDX query without assistance.
Making Contribution Calculations

To make a contribution calculation:
1. On the Viewer Tasks menu, click the Calculation link, and then click
Contribution.
The Metrics - Calculated Member Wizard appears, displaying the Select Axis screen.
2. Select the option that corresponds to your creation preference:

Select the first option to create a calculation on columns
Select the second option to create a calculation on rows.

The Select Contributing Member screen appears.
4. In the list of members in the Metric View, select the first member for the
calculation. Note that you cannot create a contribution if a cross-join exists on the
opposite axis of the column or row.
The Specify Name screen appears.
6. Type a name in the Calculated Member Name field. There is no character limit to
the name.
7. Click the Finish button to complete the builder.
The new calculated member is added to the Metric View.
Calculating Difference
To calculate difference:
1. On the Viewer Tasks menu, click the Calculation link, and select Difference from
the menu.

Select the first option to create a difference calculation on columns
Select the second option to create a difference calculation on rows.

The Select First Difference Member screen appears.
4. From the list of members in the Metric View, choose the first member for the
calculation.
The Select Second Difference Member screen appears.
6. From the list of members in the Metric View, select the second member for the
calculation. Note that you cannot create a difference if a cross-join exists on the
same axis as the chosen row or column.
8. In the Name text box, type a name for the calculation.

The new calculated member is added to the Metric View.
Performing a Customized Calculation

To perform a customized calculation:
1. On the Viewer Tasks menu, click the Calculation link, and then click Custom.

Select the first option to create a calculation on columns
Select the second option to create a calculation on rows.

The Specify Expression screen appears.
4. Select a dimension for the expression. Also, provide the expression for the
customized calculation.
6. In the Name field, type the name of the calculated member. There is no limit to
the number of characters.
The calculation is added to the Metric View.
Editing a Calculation
To edit an existing calculation:
1.
On the Design page, right-click the calculation that you want to edit, and then
click Edit.
The Calculated Member Wizard appears.
2. Modify the calculation as desired.
3. Click the Finish button

Examples of Calculations
Example 1:
In the following example, a particular piece of equipment, in addition to its family and
subfamilies, is being evaluated on its financial opportunity in comparison to all pieces of
equipment. The user has chosen to work with the dimension Measures, and the Financial
Opportunity within the dimension. This number has been divided by a sum based on the
current member's ancestor and children, and its Financial Opportunity.
[Measures].[Opportunity_$$]/Sum({Ancestor([Equipment].CurrentMember,
1).Children}, [Measures].[Opportunity_$$]))
Example 2:
You may choose to elaborate on a basic query to specify the results for null
measurements. The following example builds on the previous example. This instance
illustrates the opportunity cost divided by low-level children of a high-level parent. In the
first line, the MDX query specifies that if the current member (the piece of equipment)
does not have a parent family, the result for the calculation result will be 1. The blue
section of the following code states that if the measure Opportunity Cost equals 0, then
the results should return the calculation 0.
IIF(Ancestor([Equipment].CurrentMember, 1) IS NULL, 1, IIf([Measures].
[Opportunity_$$]=0 ,0,[Measures].[Opportunity_$
$]/Sum({Ancestor([Equipment].CurrentMember, 1).Children}, [Measures].
[Opportunity_$$])))
Note that the color red denotes a function in the query.
Example 3:
A value expression can be used to evaluate overall repair cost, and the costs within a site.
The difference in a repair cost can be compared between all repairs for a site, and then all
repairs for a particular piece of equipment. For this type of calculation, you would type in
the [Measures] dimension, and then the measure Cube, [Site Repair] (see example). Note
that when calculating the difference in a repair cost column, drilling down the hierarchy
will automatically calculate the difference.
Difference in repair cost
[Measures].[Site_Repair_Cost] - [Measures].[Company_Wide_Repair_Cost]
Example 4:
An MTBF calculation can be created with a fixed analysis period. For example, the
percentage of repairs within a given time period can be calculated. In this case, we will
limit the length of the fixed analysis period to 1748 days. As stated in the highlighted
area, if the number of repairs equals 0, then the result for the calculation will be 0.
IIf([Measures].[N of Repair]= 0, 0, 1748 x [Measures].[N of Equipment]/[Measures].[N
of Repair])
Example 5:
The next example shows an MTBF calculation with 12-month Moving analysis period
(length 12 month). The calculation results will change depending on the current member
(the current month). Figures are calculated dynamically. If there's no monthly data, a 0
will be calculated.
12 x ([Measures].[Number of Equipment], [Failure Date].[All Failure Dates])/
IIf(isempty([Failure Date].currentmember.lag(11)), 0, Sum({[Failure
Date].currentmember.lag(11): [Failure Date].currentmember},[Measures].[Total Number
of Failures]))
Sum({set: date from last 11 month to current month}, measure)
To specify that the system should check to see if there are a total of 12 months (11 back
from the current month), type in the following code. If 12 months do not exist, the value
is calculated as 0. Otherwise, the MTBF is calculated in the Month unit.
IIf(isempty([Failure Date].currentmember.lag(11)), 0, otherwise)
Saving a Metric View

After you create or modify a Metric View, you can save your changes from either the
Results for <Metric View> page or the Design page.
To save a Metric View:
1. On the Results for <Metric View> page or the Design page, on the Common Tasks
menu, click the Save Metric View link.
If the Metric View already exists in the Catalog, your changes are saved to
the existing View in its current location.
If the View has not yet been saved, the Save As dialog box appears. The
rest of these instructions assume that you are saving a Metric View that
has not yet been saved.
Note: If you want to save an existing Metric View with a new name or in a different
location, you can click the Save Metric View As link on the Common Tasks menu.
2. In the Catalog, navigate to the folder in which you want to save the Metric View.
The Caption text box is populated automatically with the value that you typed in the
Name text box.
3. If desired, click the
button to view and modify the translations for the
specified caption.
4. If desired, type a description of the Metric View in the Description text box. This
is not required to save the Metric View.
5. If desired, select the Add to Home Page check box if you want to add a link to the
Metric View to a Home Page. This is not required to save the Metric View.
If you:
4.
o
Selected the Add to Home Page check box, the search is saved to the
Catalog, and the Send to Home Page - Select Home Page dialog box is
displayed.
Did not select the Add to Home Page check box, or you have completed
the process of adding the search to a Home Page, the Save Graph dialog
box closes, and the search is saved to the Catalog.
Deleting a Metric View

You can delete a Metric View from either the Results for <Metric View> page or the
Design page.
To delete a Metric View:
1. Open the Metric View either on the Results for <Metric View> page or the
Design page.
2. On the Common Tasks menu, click the Delete Metric View link.
A confirmation message appears, asking if you really want to delete the Metric View.
The Metric View is deleted from the database.
Printing a Metric View

Printing a Metric View is similar to printing other screens in the Meridium APM
Framework application. There is, however, an additional level of options that you must
set before you can print the Metric View. Note also that you can print the Metric View
only from the Results for <Metric View> page.
To print a Metric View:

1. Open the Metric View on the Results for <Metric View> page.
2. On the Common Tasks menu, click the Print Metric View link.
The Print Dialog box appears.
3. Set the What to Print options:
To print a copy of the graph, select the Print the Metric View data in a
graphical format check box.
To print a copy of the table, select the Print the Metric View data in a
tabular format check box.
To print both the graph and the table, select both check boxes.
Set the Graph Options (enabled only if you selected the Print the Metric View
data in a graphical format check box):
If you want the graph to fit on a single page, select the Compress the
graph so that it fits on one page check box. This option works well with
graphs that have a small to moderate amount of information. If a graph

contains a lot of data, it will be difficult to view on one page.
If you want the graph to be printed in color, select the Force the graph to
print in colors even on a black and white printer check box. On a black
and white printer, this will print in gray scale. Note that by default, a
Metric View is printed in black and white.
Set the Table Options (enabled only if you selected the Print the Metric View data
in a tabular format check box):
If you want to print the table at 100% its actual size, select the Print the
table in its actual size; columns and rows may span multiple pages check
box.
If you want the width of the table to be confined to one page, but not
necessarily the length, select the Fit the width of the table to a page; rows
may span multiple pages check box.
If you want the table to be confined to one page, select the Fit entire table
to a page; neither columns nor rows will span multiple pages check box.
Print the Metric View:

1.
If you want to print the Metric View with the current options, click the
Print button.
If you want to set additional options on the Preview window, click the
Preview button.
Overview of Key Performance

Indicators
Key Performance Indicators (KPIs) are metrics that quantify the objectives of an
organization for the purpose of allowing that organization to monitor their performances.
Every KPI should be linked directly to a business goal. If the variables within a metric
are performing successfully, a business goal can be attained for a company. Likewise, if
certain variables within the metric are not up to par, a company may fall short of its
business goal. By closely tracking the variables within a KPI, problem areas can be
assessed and targeted, while efficient areas can still be improved.
The first step to establishing an efficient KPI monitoring process is developing the KPIs.
After KPIs have been developed, they can be tracked and monitored on a continual basis.
When developing KPIs, you should focus on:
Developing a set of metrics that reflect the objectives of the company in

delivering outputs. These metrics will be aligned with business unit objectives and
KPIs within each relevant perspective.
Developing indicators of processes and activities that measure drivers and

enablers of performance and point to action.
The Metrics and Scorecards module provides two tools for managing KPIs:
The KPI Viewer, where you can view and manage existing KPIs.
The KPI Designer, where you can design new KPIs and modify the design of
existing KPIs.
Accessing the List of KPIs

To access the list of KPIs:
On the Metrics and Scorecards Start Page, click the Manage Key Performance
Indicators link.
The Key Performance Indicators page appears.
Aspects of the Key Performance

Indicators Page
The Key Performance Indicators page includes a list of KPI records that exist in the
database. Each KPI record is represented by a hyperlink, and the total number of KPI
records appears at the bottom of the page.
The following KPI record fields are displayed as columns in the grid by default:
Entity ID
Last Update Date
Last Updated By
Last Measure Update
Scheduler Update Frequency
Schedule Next Run Date
Schedule Last Run date
The Key Performance Indicators page contains two task menus: Selected KPI and
Common Tasks.
Selected KPI Menu
The Selected KPI menu on the Key Performance Indicators page contains the following
links:
Designer: Displays the selected KPI on the KPI Editor page. This link appears
only when you select a row containing a KPI record.
Schedule Update: Displays the KPI Update Schedule dialog box, where you can
schedule a KPI to be updated at a certain interval. This link is enabled only when
you select a row containing a KPI record.
Update Now: Updates the selected KPI record. This link is enabled only when
you select a row containing a KPI record.
Note: If you update a parent KPI, all other KPIs in that hierarchy will also be updated.
Manage Privileges: Displays the Manage Privileges window, where you can
assign or revoke access rights to the KPI for users or groups. This link is enabled
only when you select a row containing a KPI record.
Common Tasks Menu
The Common Tasks menu on the Key Performance Indicators page contains the
following links:
New KPI: Opens the KPI Builder, where you can create a KPI record.
Open KPI: Opens the selected KPI on the View KPI page. This link is disabled
until you select a row containing a KPI record.
Save KPI: This link is disabled on the Key Performance Indicators page.
Save As: This link is disabled on the Key Performance Indicators page.
Delete KPI: After displaying confirmation message, deletes the selected KPI.
Print KPI: This link is disabled on the Key Performance Indicators page.
Documents: This link is disabled on the Key Performance Indicators page.
Page. If you are creating a new KPI record, this link is disabled until you save the
KPI record.
Help: Displays the context-sensitive Help topic for the Key Performance
Indicators page.
Options for Creating a KPI

You can create a KPI in several ways:
Manually Entered Data Input: By manually defining the input for the KPI, you
are choosing to use the specific values that you provide in lieu of a data source.
Aggregation from Sub-indicators: By using an aggregation, you specify that the
sub-indicators, or the lower level variables of the KPI, should be calculated
together for the data source. An aggregation is a table or structure containing precalculated data for a Cube.
Analysis Services Query: By using an Analysis Services query, you are extracting
data directly from a cube that has been configured in SQL Server Analysis
Services.
Meridium APM Query: By using a Meridium APM query, you are extracting
data directly from the Meridium APM database.
About Specifying Limits for a KPI

When you create a KPI for equipment via the KPI Builder, on the Specify Limits screen,
you will be prompted to specify Limit values for the KPI. The limits that you specify are
values that will define a performance range for the KPI based on your expectations for
the equipment. The actual performance of the equipment will be evaluated based on this
range. For example, your monthly water bill could be a Key Performance Indicator of the
plumbing system in your home. This means that, based on your expectations, a high
water bill (i.e., the Actual value) could indicate leaks in your system, and a low water bill
should indicate a leak-free plumbing system.
The KPI range is essentially a scale from Worst to Best, and the Limit values are
essentially thresholds for these ranges that are based upon your expectations for the
equipment. The following image shows the KPI ranges and where the Limit values that
define these ranges appear. When measurements are taken, the Actual value may fall
between or equal the Limit values, which will indicate where the equipment is in terms of
performance (e.g., If the Actual value falls between the Target and Stretch Limit values,
the KPI is in the Target-Stretch range).
The Limit values will vary depending on what you want to measure. For example, if you
create a KPI based on your monthly water bill, the range values will be measured in
dollar amount, and your Best value would be a low number (e.g., $30.00), while your
Worst value would be a high number (e.g., $300.00). In another case, the KPI may be
based on a water heater, which would require that Best value to be a high number and the
range to be measured in degrees Fahrenheit.
To continue with the water bill example, the monthly cost for water usage in your home
would be the key indicator of the overall performance of the equipment involved in the
plumbing system. A high water bill might indicate that a person in your home is using an
excessive amount of water, that there is a leak in a pipe, or that a piece of equipment is
malfunctioning, or all of the above. The KPI should serve as the first step in tracking the
performance of the system.
Continuing with the water bill example, the following table shows:
The KPI ranges.

The Limit values that define the ranges.
Where the Actual Value would fall on the range. The Actual Value corresponds to
the amount due on a monthly water bill.
What these values could indicate about the water system in your home.
The following image shows the KPI Ranges key and the Dial as it would appear on the
View KPI page after you create a KPI based on the water bill example. The Dial is a
formatted view of the KPI Range that you define when you specify the Limit values.
Manually Entering Data for a KPI
When you manually define input for a KPI, you are choosing to use specific values that
you provide instead of an external data source.
To create a new KPI from manually entered data:
1. On the Key Performance Indicators page, on the Common Tasks menu, click the
New KPI link.
The KPI Builder appears, displaying the Welcome screen.

The Hierarchy screen appears.
3. If the KPI should function as a sub-indicator for another KPI, in the Parent KPI
list, select the parent KPI for which this KPI will be a sub-indicator.
4. If this KPI will serve as a parent KPI with sub-indicators, click the Change button,
and then select the desired sub-indicators.
The Data Source screen appears.
6. Select the Manually Entered option, and then click the Next button.
The Range screen appears.
7. Choose the collection time for the measurement. This represents the time period
in which the measurement takes place. The Start Date and End Date should be
selected from the drop-down boxes. Note that an End Date is optional, as you can
continuously track the KPI measures collection. You can select the Unlimited
check box if you do not want to specify a final date.
The Specify Limits screen appears.
9. Specify limiting values for the KPI measurement. Supply values for each of the
fields:
Worst Value: The value that should be strictly avoided.
Critical Value: The value that will Indicate that the KPI is not reaching its
potential target. If an aggregation function was selected for that field, enter
a value of zero.
Target Value: A quantitative measurement of a performance metric that is

to be achieved by a given time. If an aggregation function was selected for
that field, enter a value of zero.
Stretch Target: A much higher quantitative measurement than a Target

Value, demanding breakthrough performance for achievement. If an
aggregation function was selected for that field, you may enter a value of
zero.
Best Value: The optimal output level.

The KPI Number Format screen appears.
11. Select the desired format for numeric values in the KPI.
The New Wizard Page appears.
Note: If you chose to make the End Date unlimited, the End Date appears as 1/1/0001 in
the summary.
13. Click the Finish button to finalize the creation of the KPI.
The KPI Editor page appears.
Defining an Aggregation from Subindicators for a KPI

An aggregation is a table or structure containing pre-calculated data for a cube. By using
an aggregation, you are specifying that the sub-indicators, or the lower-level variables of
the KPI, should be calculated together for the data source. Within Metrics and
Scorecards, you can aggregate sub-indicators by using a sum, an average, a weighted
average, a minimum, or a maximum function. The values that can be aggregated are the
actual value, the target value, the stretch value and the critical value.
In many situations, KPIs need to be reported in a hierarchical manner. For instance, the
availability measures for each individual process unit may be aggregated by using
capacity rates as a weight factor to evaluate the overall availability performance of a
plant. Sometimes KPIs are reported in hierarchies just for the purpose of facilitating
performance analysis. As another example, normalized scores of mean time between
failure (MTBF) from pumps, compressors, fans, and gas turbines in a plant might
aggregated to indicate the overall MTBF performance of the rotating equipment. Other
examples include sub-indicators of a KPI in different locations.
To define an aggregation from sub-indicators:
1. On the Key Performance Indicators page, on the Common Tasks menu, click
the New KPI link.

Note: A sub-indicator is a KPI that provides additional details about the current KPI or is
the KPI from which you will pull values using an aggregation function.
6. Select the Aggregated from sub-indicators option, and click the Next button.
The KPI Data Source Selection builder appears, displaying the Aggregation Type screen.
7. If you want only a normalized score to be calculated from sub-indicators, select

the Aggregate Score Only check box. The actual value will not be populated.
Since a normalized score must be a value between 0.0 and 1.0, certain aggregation
functions, such as the sum, cannot be used to aggregate scores, and limiting values cannot
be aggregated at all. Therefore, if you select the Aggregate Score Only check box, the
Sum option in the Function used to calculate the Actual/Score Value section is disabled.
Also, the Target Value, Critical Value, and Stretch Value options are disabled in the Use
the same function for section.
8. Set the Function used to calculate the Actual/Score Value option. If you selected
the Aggregate Score Only check box, then you are determining the function used
to calculate the score value. If you did not check the Aggregate Score Only check
box, then you are determining the function used to calculate the actual value.
Select any of the following functions:
1.
Sum: The addition of all sub-indicator measurements.
Average: The calculated average of the sub-indicators.
Weighted Average: The value of the KPI is calculated from the value of its
sub-indictors (e.g., V1, V2, V3, and V4) and the value of pre-determined
weight factor associated with each sub-indicator (e.g., K1, K2, K3, and
K4). The weighted average is usually calculated as (K1 x V1 + K2 x V2 +
K3 x V3 + K4 x V4)/(K1 + K2 + K3 + K4).
1.
o
Minimum: The smallest sub-indicator measurement possible.
Maximum: The largest sub-indicator measurement possible.
9. Set the Use the same function for options. The function you selected to calculate
the Actual/Score value will also be used to calculate the values you select in this
section.
If you select the Target Value, Critical Value, and Stretch Value check boxes, each of
these values will be calculated by the same function. In this case, you can skip to step 14.
-orIf you leave one or more of the Target Value, Critical Value, or Stretch Value check boxes
empty, when you click the Next button, the Range Aggregation screen will appear, where
you will be able to select a different aggregation function for the remaining attributes or
select not to use an aggregation function at all. In this case, you can continue with step
10.
The Range Aggregation screen appears.
11. In the Attribute list, select the attribute type for which the value will be calculated
from sub-indicators. The attributes are the same options that appeared in the Use
the same function for section on the Aggregation Type screen in step 9.
12. In the Aggregation function area, select the aggregation function for the attribute
that is currently selected in the Attribute list. The aggregation functions are the
same options that appeared on the Aggregation Type screen in step 8.
13. Repeat steps 11 and 12 for until you have selected or reviewed the aggregation
function for each attribute (i.e., Target, Critical, and Stretch).
If you selected the Weighted Average option on the Select the Aggregation Type screen,
the Average Weights screen appears, displaying the sub-indicators you selected for the
KPI. If you did not select the Weighted Average option, you can skip to step 16.
15. If desired, you can manually change the weight of each sub-indicator in the
Weight column. The greater the value, the more weight that is given to the
associated sub-indicator when the weighted average is calculated.
Note: The sum of the weight factors must be greater than zero, or an error message will
be displayed when you click the Next button.
Click the Next button.
16. The KPI Data Source Selection builder appears, displaying a summary of the data
source settings.

The KPI Builder displays the Range screen.
15. Choose the collection time for the measurement. This represents the time period
in which the measurement takes place. The Start Date and End Date should be
selected from the drop-down boxes. Note that an End Date is optional, as you can
continuously track the KPI measures collection. You can select the Unlimited
check box if you do not want to specify a final date.
fields:
1.
o
Critical Value: The value that will Indicate that the KPI is not reaching its
potential target. If an aggregation function was selected for that field, enter
a value of zero.
Target Value: A quantitative measurement of a performance metric that is

to be achieved by a given time. If an aggregation function was selected for
that field, enter a value of zero.
Stretch Target: A much higher quantitative value than a target value,

demanding breakthrough performance for achievement. If an aggregation
function was selected for that field, enter a value of zero.

Creating a KPI Based on An Analysis

Services Query
To create a new KPI from an Analysis Services query:
New KPI link.

6. Select the Queried from Analysis Services option, and then click the Next button.
The KPI Data Source Selection builder appears, displaying the Cube Selection screen.
7. In the Data Source Cube list, select a cube that contains the data that will be used
to update the KPI measurements.
8. If you want to link Metric Views to the KPI, click the Add button, navigate
through the Catalog, select the desired Metric View, and then click the Open
button.
Note: If you want to remove a Metric View from the list, select the View in the Linked
Cube Views list, and click the Remove button.
The Measure screen appears.
10. Select the measure used to calculate the actual value for the KPI. The actual value
is the current value.
The Time Dimension screen appears.
12. In the Time Dimension list, select the desired dimension.

13. In the Time Level list, select the desired hierarchy level.
Hint: When you highlight a hierarchy level, a tooltip will appear, displaying the unique
member name of the time level to distinguish it from other hierarchy levels in the list.
The Slice Members screen appears.
15. If you want to add slice members to reduce the scope of the measure, follow steps
16-17. If you do not want to add slice members, proceed to step 18.
16. On the Slice Members screen, click the Add button.
The Select a Slice Member dialog box appears.
17. Expand the tree, select the desired slice members, and then click OK.
Note: Only elements with the
icon to the left of the label can be selected.
The selected slice members appear on the Slice Members screen.
Note: To remove a slice, select the slice in the Slice Members list and click the Remove
button.
The Finishing screen appears, displaying a summary of the data source settings.

The KPI Builder appears, displaying the Hierarchy screen.
23. Select the Cube member for which the KPI will be created.
The Range screen appears.
25. Select the collection time for the measurement. This represents the time period in
which the measurement takes place. The start date and end date should be selected
from the Start Date and End Date drop-down boxes, respectively.
Note: An End Date is optional, as you can continuously track the KPI measures
collection. You can select the Unlimited check box if you do not want to specify a final
date.
fields:
Critical Value: A value that indicates that KPI is not reaching its potential
target. If an aggregation function was selected for that field, enter a value
of zero.
Target Value: The value that will be your aim for the KPI measurement. A
target is a quantitative measurement of a performance metric that is to be
achieved by a given time. If an aggregation function was selected for that
field, enter a value of zero.
Stretch Target: A much higher quantitative value than a target value,

demanding breakthrough performance for achievement. If an aggregation
function was selected for that field, enter a value of zero.

Note: If the FormatString value for the cube in Analysis Services is Currency, Percent, or
a custom format, that number format will appear in the Select KPI Number Format list by
default. Otherwise, the number format will be set by default to None. You can accept the
default value or modify it if desired.
30. If you do not want the selected number format to be applied to sub-indicators,
clear the Apply format to all sub-indicators check box.
Note: This check box is enabled and selected by default if sub-indicators will be created
for the KPI, based upon the selections that you made on the Hierarchy screen. If subindicators will not be created for the KPI, this check box is disabled.
the summary.
Opening an Existing KPI

You can open an existing KPI from the Key Performance Indicators page. KPIs can be
opened in the Viewer and Designer. Each page offers different options, depending on the
task that you want to perform.
To open an existing KPI:
1. On the Metrics and Scorecards Start Page, click the Manage Key Performance
Indicators link.
The Key Performance Indicators page appears.
2. To view the KPI on the View KPI page, in the Entity ID column, click the link
associated with the KPI you want to view.
-orTo view the KPI on the KPI Editor page, select the desired row, and then click the
Designer link on the Selected KPI tasks menu.
The KPI opens on the View KPI page or KPI Editor page as appropriate. Note that after
you open the KPI on either the View KPI page or KPI Editor page, you can toggle back
and forth between the two Views as needed.
Creating a KPI Using a Meridium APM

Query
You can create a query that returns any data that you want to view as a KPI. You can then
use the KPI to send alerts when values in the query meet certain conditions. For example,
you could create a query that returns all measurement values associated with a Thickness
Measurement Location for a Piping Circuit. Your KPI could then track the measurement
values as they are entered into the Meridium APM database. You could set up an alert
such that if a measurement value were to get below the critical value, an email message
would be sent to the appropriate management personnel.
To use a query as the source of a KPI, any field alias that includes spaces must be
surrounded with single quotation marks. For example, if the query includes the field
Measurement Taken Date, the alias for that field should be exactly 'Measurement Taken
Date'.
Note that the following instructions assume that the query has been created and saved in a
Catalog folder to which you have at least View permissions. They also assume that you
have at least View permissions to any family included in the query.
To create a new KPI using a Meridium APM query:
New KPI link.

4. If this KPI will serve as a parent KPI with sub-indicators, click the Change
button, and then select the desired sub-indicators.
Note: A sub-indicator is a KPI that provides additional details about the current KPI or is
the KPI from which you will pull values using an aggregation function.
6. Select the Queried from Meridium option, and click the Next button.
The KPI Data Source Selection Builder appears, displaying the Query screen.
7. In the hierarchy on the left, which mimics the Meridium APM Catalog structure,
select the folder containing the query you want to use to build the KPI.
8. In the area on the right, select the query.
The KPI Data Source Selection builder displays the Mapping screen.
10. In each list, select an appropriate field from the query. For example, in the
Measurement Date list, you would select a field from the query that represents the
measurement date. Note that the Measurement Date list contains a list of only
Date fields in the query.
The remaining lists contain only Numeric fields from the query. Note that after you select
a Numeric field in one of the lists, that field will not be available for selection in the
remaining lists.
The KPI Datasource Selection builder displays the Finishing screen.
12. Review the summary displayed on the Finishing screen. If desired, you can click
the View Results link to view the values in the fields you selected on the previous
screen.
The KPI Builder displays the Range screen.
14. Choose the collection time for the measurement. In the Start Date field, select the
date on which you want to start recording measures. The value is set
automatically to the first date returned by the query in the field you selected in the
Measurement Date list on the Mapping screen of the KPI Datasource Selection
builder.
15. If you want to select a date on which to stop recording measurements, clear the
Unlimited check box, and select a date in the End Date text box. Otherwise, if you
do not want to specify a final measurement date, select the Unlimited check box.
16. In the Frequency list, select the frequency by which you want to take
measurements. You can click the Advanced button to specify a frequency other
than the default value.
18. Supply values for each of the following fields:
Critical Value: Indicates that the KPI is not reaching its potential target.
Target Value: The value that will be your aim for the KPI measurement. A
target is a quantitative measurement of a performance metric that is to be
achieved by a given time.
Stretch Target: Has a much higher quantitative value than a target value,
demanding breakthrough performance for achievement.

the summary.
22. Review the summary information. If you are satisfied with the selections you
have made, click the Finish button. If desired, you can modify the information by
using the Back button to navigate to the screen on which you want to modify a
value.
The KPI Editor page appears, displaying the new KPI.
Overview of the View KPI Page

The View KPI page displays the values that have been recorded for the KPI, indicates
where the values fall within the defined limits, and shows how the values have changed
over time.
The View KPI page is divided into four areas: KPI Details, Dial, Trend Chart, and Trend
Data. The page also contains the following task menus, which you can use to perform
various tasks related to the KPI: Selected KPI Menu, Common Tasks Menu, KPI Pages
Menu, KPI Measurement Pages Menu.
KPI Details
The KPI Details section appears on the upper left portion of the View KPI page.
The KPI Details section displays the following information:
Owner(s): The person(s) who hold update privileges for the KPI.
Frequency: The frequency by which the KPI is measured. This can be daily,
weekly, monthly, or yearly.
Current Measure: The date of the currently displayed measurement.
Actual: The value of the current measurement.
Target: The value that will be your aim for the KPI measurement. A target is a
quantitative measurement of a performance metric that is to be achieved by a
given time.
Critical: The value that indicates that the KPI has reached a very low performance
level.
Stretch: The value that is achieved by breakthrough performance.
Score: A normalized value between 0.0 and 1.0 representing the relative strength
of the Actual Value.
Dial
The dial indicates the level of success for the organizational performance.
The colors on the dial indicate the following values, which are represented in the KPI
Ranges box:
Red: Below critical.

Yellow: Between target and critical.
Light Green: Between target and stretch.
Dark Green: Above stretch.
As you click the bars on the trend chart, the dial will change to provide a visual indication
of where each value falls within the determined ranges.
If any value on the dial is at least 10,000, all values on the dial will be scaled, and the dial
will be labeled with the measured unit (e.g., thousands).
Trend Chart
The trend chart displays the KPI results in a graphical format for a set period of time,
such as month to month.
Note: If the time frame for the KPI measurements exceeds the amount of data that can be
displayed in the graph window, use the scroll bar at the bottom of the graph to view the
values outside of the window view.
As you click the bars on the trend chart, the dial on the dashboard will change to provide
a visual indication of where each value falls within the determined ranges.
Trend Data
On the View KPI page, trend data is displayed in textual format below the trend chart.
You can use this data to interpret the trend chart. You cannot modify this data via the
View KPI page.
Selected KPI Menu

The Selected KPI menu on the View KPI page contains the following link:
Designer: Displays the KPI on the KPI Editor page, where you can manually add
data or modify the existing data. This link is disabled if you do not have Update
privileges to the KPI family.
Common Tasks Menu
The Common Tasks menu on the View KPI page contains the following links:
New KPI: Opens the KPI Builder, where you can create a KPI record.
Open KPI: Displays the Key Performance Indicators page, from which you can
open an existing KPI record.
Save KPI: This link is disabled on the View KPI page.
Save As: Displays the Save As dialog box, where you can save the current KPI
record with a different name or in a new location.
Delete KPI: Displays a confirmation message and then, deletes the current KPI. If
you are creating a new KPI record, this link is disabled until you save the KPI
record. This link is also disabled if you do not have Delete privileges to the KPI
family.
Print KPI: Displays the Print dialog box, where you can print the KPI.
Documents: Displays the reference documents associated with the KPI record. If
you are creating a new KPI record, this link is disabled until you save the KPI
record.
Page. If you are creating a new KPI record, this link is disabled until you save the
KPI record.
Help: Displays the context-sensitive Help topic for the View KPI page.
KPI Pages Menu

The KPI Pages menu on the View KPI page contains the Associated Pages that have been
configured for the KPI family.
KPI Measurement Pages Menu

The KPI Measurement Pages menu on the View KPI page displays the Associated Pages
that have been configured for the KPI Measurement family.
Sending KPI Images to a Home Page

The standard Send To feature lets you send a link to a page in the Meridium APM
Framework to personal or group Home Pages. The View KPI page provides the standard
Send To options via the Send To link on the Common Tasks menu. In addition to the
standard options, from the View KPI page, you can send an actual image from the KPI to
a Home Page. For example, the following image shows a KPI dial that has been sent to a
Home Page.
From the View KPI page, you can send an image of the Dial, Trend Chart, or Trend Data
to a Home Page.
To send a KPI image to a Home Page:

1. Right-click the image that you want to send.
2. On the shortcut menu that appears, point to Send To, and then click Home Page.
Note: The shortcut menu also gives you the option of sending a link to your desktop or to
another user via an email message. Creating a link in this way is the same as using the
Send To link on the Common Tasks menu.
The Send To Home Page - Select Home Page dialog box appears.
3. Select the Home Page where you want to send the image, and click OK.
The Send To Home Page - Select Section dialog box appears.
4. Select the desired section, and click OK.

The image is sent to the selected Home Page and placed in the designated section.
About Modifying the Maximum Y-Axis

Scale Value
By default, the minimum value plotted on the y-axis scale on the trend chart is 0 (zero)
and the maximum value is based upon the highest KPI value. In some cases, one or more
KPI values in the trend chart may be significantly higher or lower than other KPI values,
making it difficult to view trends in the majority of the data. You can modify the y-axis
scale range on the trend chart to view trends in KPI values more easily.
For example, suppose that a KPI is measuring failure costs for a facility. The KPI
measurements usually range from $10,000 to $50,000. After a fire, the KPI measurement
for one month increased to $300,000. The following image displays the trend chart for
this scenario. By default, the underlying data dictates that the maximum value on the yaxis scale should be $300,000, making it difficult to see trends in the data from the
months in which the fire did not occur.
You can adjust the y-axis scale range using the Y-Axis Range dialog box in order to see
data trends in the other KPI measurements more clearly. The following image shows an
example of the same trend chart shown in the preceding image when the maximum value
of $60,000 has been specified on the y-axis scale.
By adjusting the maximum value on the y-axis scale, you can see that the KPI
measurements for the months that did not include the cost of the fire are steadily
increasing. This may lead you to conclude that there are other issues in the facility that
are causing an increase in failure costs.
Aspects of the Y-Axis Range Dialog Box

You can use the Y-Axis Range dialog box to modify the minimum or maximum value
plotted on the y-axis scale on the trend chart.
The Y-Axis Range dialog box contains the following options:
Automatic: Specifies that the:

o Minimum value plotted on the y-axis scale will be 0.00 (zero)
Maximum value plotted on the y-axis scale will be based upon the highest
KPI value.
This option is selected by default.
Fixed: Specifies that the y-axis scale range will be user-defined. When you select
this option, the following text boxes below the Fixed option become enabled:
o Minimum: You should type the minimum value that you want plotted on
the y-axis scale in this text box. By default, this text box contains the value
0.00.
o
Maximum: You should type the maximum value that you want plotted on
the y-axis scale in this text box. By default, this text box contains the
maximum value currently plotted on the y-axis. In the image in this topic,
this text box contains the value 14,000.00.
These text boxes are enabled only when the Fixed option is selected.
Below these options, the following buttons appear:
OK: Closes the Y-Axis Range dialog box and updates the y-axis scale on the trend
chart according to your changes.
Cancel: Closes the Y-Axis Range dialog box without making any changes to the yaxis scale on the trend chart.
Help: Displays the context-sensitive Help topic for the Y-Axis Range dialog box.
Modifying the Y-Axis Scale Range

In cases where one or more KPI values is significantly lower or higher than other KPI
values plotted on the trend chart, you may want to modify the scale range of the y-axis to
make it easier to see trends in your data.
To modify the y-axis scale range on the trend chart:
1. On the View KPI page, right-click the trend chart.
A shortcut menu appears.
2. Click the Set Y-Axis Max value link.

The Y-Axis Range dialog box appears.
3. Select the Fixed option.

The Minimum and Maximum text boxes become enabled.
4. In the Minimum and Maximum text boxes, type the minimum and maximum
values that you want plotted on the y-axis, respectively.
5. Click OK.
The Y-Axis Range dialog box closes, the View KPI page returns to focus, and the trend
chart is redrawn according to your specifications.
Accessing the KPI Editor Page

To access the KPI Editor page:
1. On the Key Performance Indicators page, in the list of KPIs, select the row
containing the KPI that you want to open on the KPI Editor page.
2. On the Selected KPI menu, click the Designer link.
The KPI appears on the KPI Editor page.
Aspects of the KPI Editor Page

The KPI Editor page allows you to change the properties of the KPI. The KPI Editor
page is divided into the following sections:
KPI Datasheet: Displays properties of the KPI, such as Name, Description, Start
Date, and End Date.
Note: If selected, the Show Score Only check box allows you to view only the score in the
Trend chart and Trend Data sections of the View KPI page.
KPI Hierarchy: Displays the parent and children of the KPI.

Update Schedule: Displays the frequency with which the KPI is updated, the last
update date, the next update date, and recursive status of the KPI.
Alerts: Displays the Alert status of the KPI and any recipients of the Alert.
Data Source: Displays the selected data source that populates the KPI
measurements.
The KPI Editor page also contains the following task menus that let you perform tasks
associated with the current KPI:
Selected KPI
Common Tasks
KPI Pages
Selected KPI Menu

The Selected KPI menu on the KPI Editor page contains the following links:
Viewer: Displays the selected KPI on the View KPI page.

Select Data Source: Displays the KPI Data Source Selection builder, where you
can set up the data source for the KPI.
Edit Number Format: Displays the KPI Number Format dialog box, where you
can define the format for numeric values in the current KPI and (optionally) it
sub-indicators.
Change Frequency: Displays the KPI Frequency dialog box, where you can
indicate the frequency with which KPI measurements are conducted.
Configure Alerts: Displays the Alert Configuration dialog box, where you can set
up alerts.
Add Parent KPI: Displays the Add Parent KPI dialog box, where you can select
an upper-level KPI to add as the parent KPI. If a parent KPI is already defined for
the selected KPI, this link is labeled Remove Parent. When you click the Remove
Parent link, a confirmation message. After you confirm the action, the parent KPI
is removed from the selected KPI.
Sub-Indicators: Displays the Sub-indicators dialog box, where you can select subindicators for the KPI.
Edit Measures: Displays the KPI Measures window, where you can edit the
current values for the KPI.
Schedule Update: Displays the KPI Update Schedule dialog box, where you can
schedule an item to be updated at a certain interval. This link is disabled until you
save the KPI record.
assign or revoke access rights to the KPI for users or groups.
Common Tasks Menu

The Common Tasks menu on the KPI Editor page contains the following links:
New KPI: Displays the KPI Builder, where you can create a KPI record.
Open KPI: Displays the Key Performance Indicators page, where you can open
an existing KPI record.
Save KPI: Saves the KPI record. If you are viewing an existing KPI record, this
link is disabled until you make a change to the KPI record.
Save As: Displays the Save As dialog box, where you can save the current KPI
record with a different name or to a different location. If you are viewing an
existing KPI record, this link is disabled until you make a change to the KPI.
Delete KPI: Displays a confirmation message and then deletes the current KPI.
This link is disabled until you save the KPI record.
Print KPI: Displays the Print dialog box, where you can print the KPI.
Documents: Displays the reference documents associated with the KPI record.
This link is disabled until you save the KPI record.
Page. This link is disabled until you save the KPI record.
Help: Displays the context-sensitive Help topic for the KPI Editor page.
About KPI Data Sources

The values for a KPI measurement are pulled from a specified data source. Measures can
be created without a data source, using aggregations from sub-indicators or by generating
a data source from an Analysis Services Cube.
You can create a datasource by using:
An Analysis Services Cube: By using an Analysis Services Cube, you are

extracting data directly from a Cube that has been configured in the Analysis
Services application.
An Aggregation from Sub-Indicators: By using an aggregation, you are specifying
that the sub-indicators, or the lower level variables of the KPI, should be
calculated together for the data source.
Manual Input: By defining manual input for the KPI, you are choosing to use the
specific values that you provide in lieu of a data source.
A Meridium APM query: By using a query, you are specifying a saved query
whose data you want to use as the source of the KPI.
Using an Analysis Services Cube as a

KPI Data Source
When you use an Analysis Services Cube as a KPI data source, you are extracting data
directly from a cube that has been configured in the Analysis Services application and
using it to define a KPI.
The following instructions provide details on creating a KPI using an Analysis Services
Cube as the data source.
To create a KPI using an Analysis Services Cube as the data source:
1. On the KPI Editor page, on the Selected KPI menu, click the Select Data Source
link.
The KPI Datasource Selection builder appears, displaying the Welcome screen.

The Datasource Type screen appears.
3. Select the Analysis Services Cube option, and then click the Next button.
The Cube Selection screen appears.
4. In the Datasource Cube list, select a cube that contains the data that will be used
to update the KPI measurements.
5. If you want to link Metric Views to the KPI, click the Add button, navigate
through the Catalog, select the desired Metric View, and then click the Open
button.
Note: If you want to remove a Metric View from the list, select the Metric View in the
Linked Cube Views list, and click the Remove button.
The Measure screen appears.
7. Select the measure you want to use to calculate the actual value for the KPI. The
actual value is the current value.
The Time Dimension screen appears.
9. Choose a time dimension and level. The time dimension includes all time
measurements from the Analysis Services Cube. The time level includes the
frequency of the measurements. Use the Time Level drop down list to select a
hierarchy level, such as month, week or year.
Hint: When you highlight a hierarchy level, a tooltip will appear, displaying the unique
member name of the time level to distinguish it from other hierarchy levels in the list.
The Slice Members screen appears.
11. If you want to add slice members to reduce the scope of the measure, follow steps
12 and 13. If you do not want to add slice members, proceed to step 14.
12. On the Slice Members screen, click the Add button.
The Select a Slice Member dialog box appears.
13. Expand the tree, select the desired slice members, and click OK.
Note: Only elements with the
icon to the left of the label can be selected.
The selected slice members are displayed on the Slice Members screen.
Note: To remove a slice, select desired slice in the list and click the Remove button.
The Finishing screen appears, displaying a summary of the datasource settings.
15. Review the settings for the KPI datasource. The current entries are listed and can
be changed by using the Back button to navigate to the step that you want to
change. To close the Builder, click the Finish button.
The datasource is saved to the KPI.
Using an Aggregation of Sub-Indicators

An aggregation is a table or structure containing pre-calculated data for a Cube. By using
an aggregation, you are specifying that the sub-indicators, or the lower level variables of
the KPI, should be calculated together for the data source. Within Metrics and
Scorecards, you can aggregate sub-indicators by using their sum, average, weighted
average, minimum, maximum, actual value, stretch value or critical value.
To create a data source from an analysis services Cube:
link.
The KPI Data Source Selection builder appears, displaying the Welcome screen.

The Data Source Type screen appears.
3. Select the Aggregation from sub-indicators option, and click the Next button.
The Aggregation Type screen appears.
4. If you want only a normalized score to be calculated from sub-indicators, select

the Aggregate Score Only check box. The actual value will not be populated.
5. Set the Function used to calculate the Actual/Score Value option. If you selected
the Aggregate Score Only check box, then you are determining the function used
to calculate the score value. If you did not check the Aggregate Score Only check
box, then you are determining the function used to calculate the actual value.
Select any of the following functions:
sub-indictors (e.g., V1, V2, V3, and V4) and the value of pre-determined
K4). The weighted average is usually calculated as (K1 x V1 + K2 x V2 +
K3 x V3 + K4 x V4)/(K1 + K2 + K3 + K4).
1.
o
Minimum: The smallest sub-indicator measurement possible.
Maximum: The largest sub-indicator measurement possible.
6. Set the Use the same function for options. The function you selected to calculate
the Actual/Score value will also be used to calculate the values you select in this
section.
If you select the Target Value, Critical Value, and Stretch Value check boxes, each
of these values will be calculated by the same function. In this case, you can skip
to step 11.
-orIf you leave one or more of the Target Value, Critical Value, or Stretch Value
check boxes empty, when you click the Next button, the Range Aggregation
screen will appear, where you will be able to select a different aggregation
function for the remaining attributes or select not to use an aggregation function at
all. Continue with step 7.
from sub-indicators. The attributes are the same options that appeared in the Use
the same function for section on the Aggregation Type screen in step 6.
9. In the Aggregation function area, select the aggregation function for the attribute
that is currently selected in the Attribute list. The aggregation functions are the
same options that appeared on the Aggregation Type screen in step 5.
10. Repeat steps 8 and 9 for until you have selected or reviewed the aggregation
function for each attribute (i.e., Target, Critical, and Stretch).
If you selected the Weighted Average option on the Select the Aggregation Type screen,
the Average Weights screen appears, displaying the sub-indicators you selected for the
KPI. If you did not select the Weighted Average option, you can skip to step 13.
12. If desired, you can manually change the weight of each sub-indicator in the
Weight column. The greater the value, the more weight that is given to the
associated sub-indicator when the weighted average is calculated.
Note: The sum of the weight factors must be greater than zero, or an error message will
be displayed when you click the Next button.
13. Review the settings for the KPI data source. The current entries are listed and can
change. To close the KPI Data Source Selection builder, click the Finish button.
The data source is saved to the KPI.
Using Manual Input

To create a data source using manual input:
link.

3. Select the No Data Source option, and click the Next button.
from sub-indicators:
11.
o
Target: The value that will be your aim for the KPI measurement. A target
is a quantitative measurement of a performance metric that is to be
achieved by a given time.
Critical: This value indicates that the KPI has reached a very low
performance level.
Stretch: The target value that is achieved by breakthrough performance.
5. In the Aggregation function area, select the aggregation function:
sub-indictors (e.g., V1, V2, V3, and V4), and the value of pre-determined
K4). The weighted average is usually calculated as (K1 x v1 + k2 x V2 +
K3 x V3 + K4 x V4)/(K1 + K2 + K3 + K4).
Note: The sum of the weight factors must be greater than zero, or an error
message will be displayed when you click the Next button.
Minimum: The minimum measurement.

Maximum: The maximum measurement.
None: No measurement for the attribute.

The KPI Data Source Selection builder displays a summary of the data source settings.
change. To close the Builder, click the Finish button.
Using a Meridium APM Query for a

Data Source
link.

3. Select the Queried from Meridium APM option, and click the Next button.
The Query screen appears.
4. In the hierarchy on the left, which mimics the Meridium APM Catalog structure,
select the folder containing the query you want to use to build the KPI.
5. In the list on the right, select the query that you want to use.
The Mapping screen appears.
7. In each list, select an appropriate field from the query. For example, in the
Measurement Date list, you would select a field from the query that represents the
measurement date. Note that the Measurement Date list contains a list of only date
fields in the query.
The remaining lists contain only numeric fields from the query. Note also that after you
select a numeric field in one of the lists, that field will not be available for selection in the
remaining lists.
change. To close the builder, click the Finish button.
About KPI Scores

When a KPI is created, it is automatically assigned a score. A score is a normalized value
between 0.0 and 1.0 representing the relative strength of the Actual Value. The formula is
either:
(Actual Value Worst Value)/(Best Value Worst Value)
If the Best Value > Worst Value

-or
(Actual Value Best Value)/(Worst Value Best Value)
If the Best Value < Worst Value

The closer the score is to 1.0, the higher the strength of the Actual Value.
Scores are useful when comparing measures whose values cover a wide range. It
becomes difficult to work with such vastly different numbers, but working with scores
allows you to compare relatively close numbers. For example, when comparing ten
Actual Values that range from 20 to 500, the gap is almost too large to manage. When
you compare the scores of the measures, however, you only have to examine numbers
between 0.0 and 1.0, thus making it easier to make comparisons and conclusions.
Normally, the score is calculated using the Actual Value, Best Value, and Worst Value of
the current KPI, as indicated in the specified equations. If the Aggregate Score Only
option is selected in the KPI Builder, or the Has Score check box is selected in the KPI
Designer, however, the Actual Value will not be populated, and the Actual, Target,
Critical, and Stretch Values will not be displayed on the Trend Chart or Trend Data.
Instead, only the Score will be displayed for that KPI by aggregating scores of its subindicators using the selected aggregation function (i.e., Sum, Average, Weighted Average,
Minimum, or Maximum). Therefore, you should select only the Aggregate Score Only
option or the Show Score Only check box for a KPI that has one or more KPIs.
Viewing a KPI Score

Via the Show Score Only check box on the KPI Editor page, you can choose to view a
KPI score instead of Actual, Target, Critical, and Stretch Values in the trend chart and
trend data sections of the View KPI page.
To view a KPI Score:
1. On the KPI Editor page, select the Show Score Only check box.
2. On the Selected KPI menu, click the Viewer link.
The KPI is displayed on the View KPI page and only the score is displayed on the trend
chart, trend data, and dial. Note that if the Show Score Only check box is not selected, the
trend chart, trend data, and dial also display the actual values for the given time period.
Note: If you want to display the associated data in the dial, click a score bar in the chart.
Modifying the Collection Frequency

The frequency determines how often measurements are collected for a given KPI. The
collection frequency is set when the KPI is created, but you can modify it if desired. For
example, if you were measuring profit, you may want to collect profit figures and set the
collection frequency as monthly when you create the KPI. If you determine after several
collections that your profit is steadily decreasing, you may want to measure it more
frequently (e.g., biweekly or weekly).
To change the collection frequency:
1. On the KPI Editor page, on the Selected KPI menu, click the Change Frequency
link.
The KPI Frequency dialog box appears.
2. Select the frequency for collections of KPI measurements. Measurements can be

conducted daily, weekly, monthly, or yearly. The default frequency for a new KPI
is every month on the first day of the month. Select the check box next to the
desired option.
1.
Daily: Measurements will be taken X number of days apart, as indicated

by the value you select in the Every __ day(s) list. For example, selecting
5 specifies that measurements will be taken every 5 days. If you choose to
take measurements daily, the default frequency is every day.
Weekly: Measurements will be collected every X weeks, as indicated by

the value that you select in the every ___ week(s) list. For example,
selecting 13 specifies that measurements will be taken every 13 weeks.
Measurements will be taken on the day of the week selected in the Each
list. If you choose to take measurements weekly, the default frequency is
each Sunday of every week.
Monthly: Measurements will be taken every X months, as indicated by the

value that you select in the Every___ month(s) list. For example, selecting
3 specifies that measurements will be taken every three months. The value
in the on day ___ of the month list specifies the day of the month on which
the measurements should be taken. If you choose to take measurements
monthly, the default frequency is every month on the first day of the
month.
Yearly: Measurements will be taken every X year, as indicated by the

value that you select in the Every ___ year(s) list. For example, selecting 2
specifies that measurements will be taken every two years. The value in
the on list specifies the month of the year and the day of the month on
which the measurements should be taken. If you choose to take
measurements yearly, the default frequency is every year on the first day
of the first month.
Note: The time interval should match the frequency by which measures will be updated if
you want an email message to be sent the day that measures are updated and actual values
are not populated according to the date defined in the collection frequency.
3. Click OK.
About the KPI Number Format

The Metrics and Scorecards module offers an option that allows you to manually specify
the format of numeric values in KPIs. For each KPI, you can define a number format that
is appropriate for the type of data in that KPI. The format that you define will be applied
anywhere numeric values are displayed in the KPI. The same number format will also be
used for displaying numeric values in any Scorecards that include that KPI.
For example, if you specify that numeric values in a KPI should be displayed as currency,
when you view the KPI on the View KPI page, the numbers might be formatted as shown
in the following image.
This is just one example. The KPI number format feature gives you flexibility in
controlling how numbers will be displayed by providing various pre-defined options and
a custom format option that lets you define any numeric format supported by the .NET
Framework.
For new KPIs, you can configure the number format via the KPI Builder. For existing
KPIs, you can configure the number format for the KPI Number Format dialog box,
which is accessible from the KPI Editor page.
When you modify the number format for an existing KPI, you can choose whether to
apply that format to the sub-indicators that exist for that KPI. If you choose not to apply
the number format to sub-indicators, that format will be applied only to the parent KPI. If
you do choose to apply the number format to sub-indicators, any child KPIs will be
updated to use the same number format as the parent.
Available Number Formats

When you create a new KPI, you can define the format for numeric values via the KPI
Builder. Similarly, you can modify the number format for existing KPIs via the KPI
Number Format dialog box. The same options are available in either case and can be
selected from the Select KPI Number Format list.
You can choose from the following number formats:
None: Applies no format rules to numeric values.

Currency: Specifies that numeric values will be formatted as currency, according
to the Windows Regional Options of the computer on which the Meridium APM
Framework application is running and the number of digits past the decimal that
you specify. When you select this option, the example that appears on the KPI
Number Format dialog box uses the currency symbol associated with the
Windows Regional Options of the computer from which the Meridium APM
Framework application is being run.
Fixed Digits After Decimal Point: Specifies that numeric values will always be
displayed using a fixed number of digits to the right of the decimal point, as
defined by the number selected in the list to the right of the Select KPI Number
Format list. The thousands separator will not be displayed when this format is
selected.
Scientific: Specifies that numeric values will be formatted using scientific

notation, where the number selected in the list to the right of the Select KPI
Number Format list indicates the number of decimal places that will be displayed
to the right of the decimal in the significand.
General: Specifies that numeric values will be displayed in fixed or scientific

notation, whichever is shorter.
Numeric: Specifies that the thousands separator will be displayed. Additionally,

the number selected in the list to the right of the Select KPI Number Format list
defines the number of digits that will appear to the right of the decimal.
Percent: Specifies that the field will be formatted as a percentage, including

multiplying the base value by 100 and including a percent sign (%). Additionally,
number selected in the list to the right of the Select KPI Number Format list will
the number of digits that will appear to the right of the decimal.
Custom Format: Allows you to specify a custom number format. When you
select this option, a text box will appear to the right of the Select KPI Number
Format list, where you can type the desired format. You can specify any format
supported by the .NET Framework, using the appropriate syntax. Details on the
syntax for custom formats are not provided in this documentation but can be
obtained from Microsoft. The Meridium APM system does not validate custom
formats to determine whether or not they can be interpreted by the system or will
have the desired effect.
When you specify a number format, either by selecting one of the pre-defined formats or
defining a custom format, an example will be provided to indicate the effect that the
format will have on numeric values. You can use the example as a guide to determine
whether you have chosen the appropriate format. The example, however, is just a guide.
After you modify the number format, you will likely want to save your changes and then
view the numeric fields in the KPI to determine whether your changes had the desired
effect.
Modifying the Number Format for a

KPI
To modify the number format of a KPI:
1. On the KPI Editor page, on the Selected KPI menu, click the Edit Number Format
link.
The KPI Number Format dialog box appears.
2. In the Select KPI Number Format list, select the desired number format.
3. If you want to apply the selected number format to sub-indicators of this KPI,
select the Apply format to all sub-indicators check box.
Note: This option is enabled only if the current KPI is linked to one or more subindicators.
4. Click OK.
The KPI Number Format dialog box closes.
5. On the Common Tasks menu, click the Save KPI link.
Your changes are saved, and the number formatting is applied. You can validate the
number formatting by reviewing the numeric values in the Target, Critical, Stretch, Best
Value, and Worst Value fields on the KPI Datasheet section of the KPI Editor page. The
number format will be applied to all numeric fields wherever numbers are displayed for
the KPI.
How Number Formats Are Applied to

KPIs
When you define a number format for a KPI, information about that format is stored in
the Datasources (MI_KPI_DATAS_TX) field of the KPI record. Within the KPI family,
baseline rules exist on the following fields to format values in those fields according to
the rules that exist in the Datasources (MI_KPI_DATAS_TX) field:
Alert Value
Best Value
Critical
Stretch
Target
Worst Value
In other words, number format rule themselves do not exist within these fields
themselves. But these fields contain rules that will apply any number formatting that has
been defined. Because this feature is implemented via baseline rules, the number format
will not be applied if you have defined custom rules for any of these fields.
Defining Alerts for KPIs

You can set up email alerts to inform specific users when a KPI's Actual value falls
within a certain range or is not populated according to the collection frequency schedule.
If you update a KPI and its measurements meet the criteria specified, an Alert record is
created, and an email message will be sent. The benefit of configuring email alerts is that
users will be notified of the situation as soon as possible so that appropriate actions can
be taken.
To set up email alerts for a KPI:
1. On the KPI Editor page, on the Selected KPI menu, click the Configure Alerts
link.
The Alert Configuration dialog box appears.
2. Select the desired alert options for the KPI. Note that alerts are not triggered
unless measurements are updated. You can choose to send an alert when:
o The Actual value is worse than the Critical value.
o
The Actual value is better than the Stretch value.
The Actual value becomes worse than a specified value. Depending on the
direction of the scale, the Actual value must be either higher or lower than
the specified value to trigger an alert. For example:
o
On a scale where the Stretch value is 25 and the Critical value is

100, higher values are worse than lower values. In this case, an
alert will be generated when the Actual value is greater than the
specified alert value. For example, if you set the alert value to 75,
an alert will be triggered whenever the Actual value is greater than
75.
On a scale where the Stretch value is 100 and the Critical value is
25, lower values are worse than higher values. In this case, an alert
will be generated when the Actual value is less than the specified
alert value. For example, if you set the alert value to 75, an alert
will be triggered whenever the Actual value is less than 75.
The Actual value is not populated as scheduled. For example, if an Actual

value is scheduled to be entered manually or populated automatically
based on an Analysis Services query on January 25, 2006 at 1:00 p.m., and
the KPI measures are updated after 1:00 p.m. on January 25, 2006, but the
Actual value is not populated, an email message will be sent to the
specified recipient(s).
To make sure an email message is sent the same day an update is performed and an
Actual value meets the specified alert condition, you should define an update schedule
that matches the collection frequency. This ensures that the Meridium APM system will
know immediately when an Actual value meets an alert condition. If, on the other hand,
you schedule Actual values to be populated on one schedule, such as weekly, but you
update the measurements on a different schedule, such as monthly, and the Actual value
meets the alert condition the first week of the month, the Meridium APM system will not
know that the alert condition has been met until you run the update at the end of the
month. In this case the email message would not be sent in time to alert the recipient of
the problem.
3. In the section An alert will include the following information, type the message
that the recipient(s) will receive about the measurement. To create a message with
specific details, use the following syntax in the message:
o {KPI_NAME}: Indicates the name of the KPI.
o
{MEASURE_DATE}: Indicates the measurement date on which the

condition occurred.
{ACTUAL_VALUE}: Indicates the actual value of the KPI on the

specified measurement date.
{TRIGGERED_CONDITIONS}: Indicates the alert condition that was

met on the specified measurement date.
For example, a message could be formatted as follows:

An alert has been triggered while updating KPI {KPI_NAME} for the period ending on
{MEASURE_DATE}. The value of {ACTUAL_VALUE} meets the following criteria:
{TRIGGERED_CONDITIONS}
When this message is received in an email message, it would read as follows:
An alert has been triggered while updating Financial KPI for the period ending on
2/1/2005. The value of 0 meets the following criteria: The value was not automatically
updated as scheduled.
Where Financial KPI is the name of the KPI, 2/1/2005 is the measurement date on which
the Actual value was not populated, 0 is the Actual value that appeared on the specified
measurement date, and The value was not automatically updated as scheduled is the alert
condition that was met.
4. Click the Add button to insert a list of email recipients.
The Select User dialog box appears.
5. Select the desired Security User, and click OK.

Note: The Select User dialog box contains a list of Security Users who have an email
address defined. Security Users that do not have an email address will not appear in the
list. If you want to send an alert to a Security User that does not appear in the list, you
must first define a valid email address for that user.
The selected users are added to the list in the Alert Configuration dialog box.
6. If desired, click the Remove button to remove any email recipients.

7. Click OK.
The values you defined in the Alert Configuration dialog box are saved to fields in the
KPI record. If you update the KPI and its measurements meet the alert conditions you
defined, an Alert record will be created, and an email message will be sent to the
specified recipient(s).
Selecting Sub-Indicators for a KPI

To select sub-indicators for a KPI:
1. On the KPI Editor page, on the Selected KPI menu, click the Sub-Indicators link.
The Sub-Indicators dialog box appears, displaying a list of KPIs that are not currently
associated with a parent.
2. On the Sub-Indicators dialog box, select the check box next to each sub-indicator
that you want to include in the KPI.
3. Click OK.
Your selections are saved, and the dialog box closes.
Adding Reference Documents to a KPI

Reference Documents are a standard feature available throughout the Meridium APM
Framework and provide you with the option of associating files or websites with other
records in the Meridium APM database. Via the KPI Editor page, you can optionally add
a Reference Document to a KPI, which creates a link between the Reference Document
record and the KPI record and makes the associated file available when you are working
with that KPI.
Note: If you add a Reference Document to a parent KPI, it will be linked automatically to
the sub-indicators of the parent KPI. Note that if you add a Reference Document to only a
sub-indicator, the Reference Document record will be linked only to that sub-indicator
and not to the parent KPI or other sub-indicators.
To link a Reference Document record to a parent KPI:
1. On the KPI Editor page, select the parent KPI.
2. On the Common Tasks menu, click the Documents link.
The Reference Documents window appears, where you can manage Reference
Documents for the KPI as you would for any other record.
About Updating Measurements

Measurements can be scheduled using the following methods:
Manually.
Automatically through scheduled execution.
When measurements are updated via either of these methods, the Meridium APM system
will:
Create KPI Measurement records and link them to the current KPI record.
Use the values in following KPI fields to populate the KPI Measurement record:
KPI collection frequency
Start Date
End Date
Last Modified Date
Check the previous KPI Measurement record values, such as the Target value, to
determine if they have been modified since the last update. If any of the values for
a KPI Measurement record have changed since you last updated the
measurements, the Meridium APM system will automatically adjust the values in
the KPI Measurement records to contain the most current values.
Manually Updating Measurements

To update the measures associated with a KPI:
1. On the KPI Editor page, on the Selected KPI menu, click the Edit Measures link.
The KPI Measures window appears.
2. Click the Update button to display the all of the KPI Measurement records that are
linked to the current KPI record.
3. Modify the measures as desired. If a value is calculated based on an aggregation
function, the value is disabled and cannot be modified. For instance, if the Actual
value is calculated based on a Sum aggregation function, the Actual cell is
disabled.
Hint: You can copy a value by right-clicking the cell and selecting Copy from the shortcut
menu. Then, right-click another cell in the grid and click Paste to paste the value. You can
also use the Delete option on the shortcut menu to delete a KPI Measurement record. The
Delete option is not available, however, when focus is on a particular cell.
4. Click OK.
Your changes are saved, and the KPI Measures window closes. The updated values will
now appear on the View KPI page.
Note: If you delete a measure for a sub-indicator KPI, the parent KPI measure will be
updated automatically.
Automatically Updating Measurements

About Automatic Updates
KPI measurements can be updated automatically according to a schedule and frequency
defined within the KPIs themselves. You can define the desired schedule for each KPI via
the KPI Update Schedule dialog box, which you can access from the Key Performance
Indicators page and the KPI Editor page.
Automatic updates are typically performed on KPIs built from Analysis Services or
aggregated from sub-indicators. To avoid confusion and eliminate the possibility of
reviewing and analyzing out-of-date information, you should schedule an update of KPI
measurements at the same time that measurements are scheduled to be taken. For
example, if you are going to collect measurements every first day of each month, you
should also schedule the updates to run every first day of each month.
Note: The execution of automatic updates is dependent on a master scheduled item that
must be created via the Meridium APM Schedule Manager. This scheduled item defines
the minimum frequency at which individual KPIs can be updated. You will not be
allowed to schedule individual KPIs to be updated more often than the master scheduled
item allows.
KPIs can be scheduled for automatic updates one time or on a recurring basis. The
following table describes the schedules by which you can configure the KPI
measurements to be updated.
Frequency
Example
Default
Every x number of minutes.
Every thirty
minutes.
Every x number of days.
Every two days. Every day.
Every minute.
Every x day of every x

Every Sunday of
number of weeks, where you
Every Sunday of every week.
every two weeks.
define the day of the week.
Every x month on day x of
that month.
Every three
months on day
Every month on day 1 of the month.
10 of the month.
Every year on the current day of that
Every two years
Every x year on x date, where
year. For example, if the current date is
on March 15 of
you define the date.
January 9, the default value will be
that year.
every year on January 9.
Defining the Schedule for Updates

To schedule the automatic update of KPI measurements:
1. On the Key Performance Indicators page, select the KPI(s) that you want to
update.
2. On the Selected KPI menu, click the Schedule Update link.
The KPI Update Schedule dialog box appears. If you select multiple KPIs, or a KPI that
is part of a hierarchy, the dialog box will contain a list of the selected KPIs.
3. If the data will not be available for a given period of time, you can delay the
update by selecting the delay period in the Data Availability Delay field.
4. If desired, change the date of the next execution. You can view the next scheduled
execution by looking at the Next Execution field. To change this date, click the
button and select a date.
Hint: Setting the date here and not selecting the Recurring Item check box is how you
schedule a one-time update. Additionally, you can set the next execution date here and
select the Recurring Item check box if you want the recurring schedule to begin on a date
other than the one that is currently displayed.
5. If the item should be updated on a regular basis, click the Recurring Item check
box, and then select the frequency of the update.
Note: If you schedule a KPI to execute more frequently than the master KPI schedule
item, when you click the Save button, a message will appear stating that the selected
frequency conflicts with the master KPI, and an administrator must change the frequency
of master KPI scheduled item in Schedule Manager in order for the KPI to be scheduled
at the selected frequency.
7. Click OK.
The schedule is saved. The updated values will now appear on the View KPI page and the
Key Performance Indicators page.
Scheduling an Automatic Update for

Multiple KPIs
To schedule the automatic update of multiple KPIs:
1. On the Key Performance Indicators page, select the KPIs that you want to update.
The KPI Update Schedule dialog box appears.
Note: If one of the KPIs you selected is part of a hierarchy, a message will appear at the
top of the dialog box, stating that any changes you make to that KPI will be saved to all
other KPIs in that hierarchy. The Selected KPIs section displays both the KPIs you
selected and all other KPIs that will be updated as a result of the schedule change.
3. Define the desired schedule, just as you would for a single KPI.
4. Click OK.
The schedule is saved. The updated values will now appear on the View KPI page.
Disabling Automatic Updates
The following instructions provide details on removing the schedule information from a
KPI. Removing the schedule from a KPI will stop that KPI from being updated
automatically according to the schedule that was previously defined.
To remove a schedule from a KPI:
1. On the Key Performance Indicators page, select the KPIs for which you want to
remove a schedule.
The KPI Update Schedule dialog box appears, displaying the current update schedule for
that KPI.
3. Click the Delete button.

Note: This button only deletes the schedule information from the KPI. It does not delete
the KPI itself.
A confirmation message appears, asking if you really want to unschedule the KPI.
The schedule information is removed.
Deleting a KPI
The following instructions provide details on deleting a KPI from the Key Performance
Indicators screen. Note that you can also delete a KPI on the View KPI page and the KPI
Editor page.
To delete a KPI:
1. In the list on the Key Performance Indicators screen, select the row of the KPI
that you want to delete.
2. In the Common Tasks menu, click the Delete link.
A confirmation message appears, asking if you really want to delete the KPI.

The KPI record is deleted from the database.
Note: If you delete a sub-indicator KPI, the measures for the parent KPI will be updated
automatically.
Overview of Scorecards
A Scorecard is a tool designed to monitor various aspects of your organizations
performance. Scorecards allow you to monitor performance from a number of different
perspectives, based on specific objectives and KPIs your organization has identified. A
complete Scorecard will contain multiple instances of the following items:
Perspectives: Areas around which you want your company to focus. An example
of a perspective might be Cost Optimization.
Objectives: Specific goals towards which you want the company and its
employees to strive. Each objective is categorized under a specific perspective.
An example of an objective under the Cost Optimization perspective might be to
optimize day-to-day tasks.
KPIs: Indicators that measure the company's ability to meet its objectives. Each
KPI is categorized under a specific objective. An example of a KPI that measures
the company's ability to optimize day-to-day tasks is one that measures the
percent of equipment that has a new or reviewed Asset Strategy.
You can design a Scorecard using the Design Scorecard page. After a Scorecard has been
designed, as data is collected and tracked using the KPIs, you can view a summary of the
data on the View Scorecard page.
Accessing a List of Scorecards

To access a list of Scorecards:
On the Metrics and Scorecards Start Page, click the Manage Scorecards link.
The Scorecards page appears.
Aspects of the Scorecards Page

The Scorecards page includes a list of Scorecard records that exist in the database. Each
Scorecard record is represented by a hyperlink, and the total number of Scorecard records
appears at the bottom of the page.
The Entity ID is displayed for each Scorecard record that appears in the grid.
The Scorecards page contains two task menus: Scorecard and Common Tasks.
Scorecard Menu
The Scorecard menu on the Scorecards page contains the following link:
select the users and groups who will have access to the selected Scorecard.
Common Tasks Menu
The Common Tasks menu on the Scorecards page contains the following links:
New Scorecard: Displays the Design Scorecard page, where you can create a new
Scorecard Record.
Open Scorecard: Displays the View Scorecard page, where you can view the
selected Scorecard. This link is disabled until you select a row containing a
Scorecard record.
Save Scorecard: This link is disabled on the Scorecards page.
Save As: This link is disabled on the Scorecards page.
Delete Scorecard: Deletes the selected Scorecard record. This link is disabled
until you select a row containing a Scorecard record.
Print: This link is disabled on the Scorecards page.
Page.
Help: Displays the context-sensitive Help topic for the Scorecards page.
Creating a New Scorecard
To create a new Scorecard record, you can click the New Scorecard link on the Common
Tasks menu on the Scorecards, Design Scorecard, and View Scorecard pages. A blank
Scorecard will appear on the Design Scorecard page. To save the new Scorecard record to
the database, you must at least type a name in the Name text box, but you can further
design the Scorecard as desired before saving it to the Meridium APM database.
Opening an Existing Scorecard

To open an existing Scorecard:
On the Scorecards page, in the list of Scorecard records, click the link associated
with the Scorecard that you want to view.
The Scorecard appears on the View Scorecard page.
From the View Scorecard page, you can view the information in more detail. After you
open the Scorecard, you can access the Design Scorecard page to modify the content of
the Scorecard.
About the View Scorecard Page

The View Scorecard page displays a hierarchical view of a Scorecard's perspectives,
objectives, and KPIs. On the View Scorecard page, you can also see the following values
that are stored in the individual KPI records:
Actual
Previous
Target
Trend
Frequency
Measurement Date
On the View Scorecard page, you can perform any of the following tasks:
Click a perspective to view the record in the Record Manager.

Click an objective to view the record in the Record Manager.
Click a KPI to view its details on the View KPI page.
On the View Scorecard page, actual KPI values are highlighted according to where the
value falls within the values assigned to the worst value, critical value, target value,
stretch value, and best value. For example, if an actual value is 10.00, and the target value
is 5.00 and stretch value is 15.00, the value 10.00 would be highlighted in light green,
which indicates on the KPI dial that a value falls between the stretch value and the best
value.
The Previous column indicates the KPI value at its last measurement date, and the Target
column indicates the Target value that was assigned when the KPI was created. The
Frequency column indicates how often measurements are taken, and the Measurement
Date column displays the date of the most current measurement, which is associated with
the actual value displayed in the Actual column.
In the Trend column, an arrow appears that either points up, down, or sideways. An arrow
points up if the actual value is higher than the previous value, it points down if the actual
value is less than the previous value, and it points sideways if the actual value is the same
as the previous value.
Scorecard Menu
The Scorecard menu on the View Scorecard page contains the following links:
Designer: Displays the Scorecard on the Design Scorecard page. This link is
disabled if you do not have Update privileges to the Scorecard family.
select the users and groups who will have access to the selected Scorecard. This
link is enabled only if you have Update permissions on the Scorecard family.
Change Period: Displays the Scorecard Period dialog box, where you can change
the range of dates for the KPI measures.
Select Columns: Displays the Select Visible Columns dialog box, where you can
select columns to appear in the Scorecard on the View Scorecard page.
Common Tasks Menu

The Common Tasks menu on the View Scorecard page contains the following links:
New Scorecard: Displays a blank Design Scorecard page, where you can create a
new Scorecard record.
Open Scorecard: Displays the Scorecards page, from which you can select a
Scorecard record to open.
Save Scorecard: Saves a Scorecard record. This link is disabled until you make a
change to the Scorecard. This link is always disabled if you do not have Update
privileges to the Scorecard family.
Save As: Displays the Save As dialog box, where you can save the current
Scorecard with a different name or in a different location.
Delete Scorecard: Displays a confirmation, and then deletes the Scorecard record.
This link is disabled until you save the Scorecard record. This link is always
disabled if you do not have Delete privileges to the Scorecard family.
Print Scorecard: Displays the Print dialog box, from which you can print a
Scorecard.
Documents: Displays the reference documents associated with the Scorecard

record. This link is disabled until you save the Scorecard record.
Page. If you are creating a new Scorecard record, this link is disabled until you
save the Scorecard record.
Help: Displays the context-sensitive Help topic for the View Scorecard page.
Scorecard Pages Menu

The Scorecard Pages menu on the View Scorecard page displays the Associated Pages
that have been configured for the Scorecard family.
KPI Pages Menu

The KPI Pages menu on the View Scorecard page contains the Associated Pages that are
configured for the KPI family that is associated with the row that is currently selected in
the grid. The menu is dynamic, so the menu label and its links change as you select
different rows in the Scorecard grid:
When you select a KPI Perspective row, the menu is labeled KPI Perspective
Pages and displays the Associated Pages that are defined for the KPI Perspective
family.
When you select a KPI Objective row, the menu is labeled KPI Objective Pages
and displays the Associated Pages that are defined for the KPI Objective family.
When you select a KPI row, the menu is labeled KPI Pages and displays the
Associated Pages that are defined for the KPI family.
Changing the Scorecard Period

The Scorecard period is the time frame for which you want to view KPI measurements.
By default, there is no time frame specified for a new Scorecard. You can, however,
specify a start date and end date by which to view measurements. For example, if KPI
measurements span from January 1997 to December 1997, and you specify the Scorecard
period as January 1998-December 1998, you will not see any measurements on the View
Scorecard page.
The following instructions assume that the Scorecard is currently displayed on the View
Scorecard page.
To change the period of a Scorecard:
1. On the View Scorecard page, on the Scorecard menu, click the Change Period
link.
The Scorecard Period dialog box appears.
2. If you do not want to specify the date(s) by which to filter the measurements,
select the Don't use a filter check box for the Start Date and End Date. Both check
boxes are selected by default when you create a new Scorecard. You can use a
filter for one date and not the other, if desired, by clearing the check box.
-orIf you want to specify the Start Date or End Date, clear the Don't use a filter check box,
and then type or select the desired date.
3. Click OK.
The specified dates are applied, and you see only measurements that fall within the
specified time frame.
Example of a Completed Scorecard on

the View Scorecard Page
The following image shows an example of a completed Scorecard on the View Scorecard
page.
To view this Scorecard as it would appear on the Design Scorecard page, click here.
In this example, the Scorecard uses a Process perspective and a Financial perspective.
The objective for the Process perspective is to improve reliability, and the objective for
the Financial perspective is to optimize operating expense. Mechanical availability and
the total number of failures are used to measure whether the company is improving
reliability, and turnaround maintenance cost, routine maintenance cost, and total failure
cost are used to measure whether the company is optimizing its operating expense.
Note that the mechanical availability value has increased from the previous year, from
92.00 to 94.60. Therefore the Trend arrow is pointing up to indicate the increase. The
actual value is highlighted in light green, which indicates that the value falls within the
range of the Target value and the Stretch value. If you were to click the Mechanical
Availability link, the View KPI page for the Mechanical Availability KPI would appear,
showing the details of the KPI.
From the View KPI page, you could see the actual value of 94.60 reflected in the trend
data and the dial. Notice that the actual value on the trend dial falls within the values
shaded light green, which is the color used to highlight the actual value on the View
Scorecard page.
Below the trend data, you can also see the previous value of 92.00 and the current value
of 94.60.
Accessing the Design Scorecard Page

From the Design Scorecard page, you can design a new Scorecard or modify the content
of an existing Scorecard. The Design Scorecard page appears automatically when you
create a new Scorecard. The following instructions provide details on accessing the
Design Scorecard page for an existing Scorecard.
To open an existing Scorecard on the Design Scorecard page:
1. On the Scorecards page, in the list of Scorecard records, click the link associated
with the Scorecard that you want to view.
The selected Scorecard appears on the View Scorecard page.
2. On the Scorecard menu, click the Designer link.

The Design Scorecard page appears, displaying the content of the selected Scorecard.
Aspects of the Design Scorecard Page

On the Design Scorecard page, you can design a new Scorecard or modify the design of
an existing Scorecard.
Using the Design Scorecard page, you can select the KPI Perspective records, KPI
Objective records, and KPI records that you want to view in the Scorecard and attach
reference documents to the Scorecard. The Design Scorecard page contains the following
sections:
Name: Contains the name of the Scorecard.

Description: Contains a description of the Scorecard.
Contents: Contains the perspectives, objectives, and KPIs that you define for the
Scorecard. In the Contents section, you can add KPI Perspective records, KPI
Objective records, and KPI records; remove contents from the Scorecard; delete
contents from the database; and view the record for each perspective, objective, or
KPI.
Related Documents: Contains a list of reference documents associated with the

Scorecard. To add documents to the list or view the documents already attached to
the Scorecard, click the Reference Documents link on the Common Tasks menu.
Visible Columns: Contains a list of the columns that will appear on the View
Scorecard page.
You can sort the tree in the Contents section alphabetically by right-clicking anywhere in
the tree and then clicking Sort on the shortcut menu. The sort command will sort ALL
perspectives, objectives, and KPIs displayed in the pane (i.e., the sort operation is not
limited to the branch that is currently selected).Note that the sort operation cannot be
undone.
Scorecard Menu
The Scorecard menu on the Design Scorecard page contains the following links:
Viewer: Displays the View Scorecard page.

select the users and groups who will have access to the selected Scorecard.
Change Period: This link is disabled on the Design Scorecard page.
Select Columns: Displays the Select Visible Columns dialog box, where you can
select columns to appear in the Scorecard on the View Scorecard page.
Move Item Up: Moves the selected perspective, objective, or KPI up in the
Contents list. This link is disabled when an item is at the top of the hierarchy in
respect to similar items and cannot be moved up anymore.
Move Item Down: Moves the selected perspective, objective, or KPI down in the
Contents list. This link is disabled when an item is at the bottom of the hierarchy
in respect to similar items and cannot be moved down anymore.
Common Tasks Menu

The Common Tasks menu on the Design Scorecard page contains the following links:
New Scorecard: Displays a blank Design Scorecard page, where you can create a
new Scorecard record.
Open Scorecard: Displays the Scorecards page, from which you can select a
Scorecard record to open.
Save Scorecard: Saves the Scorecard record. If you are viewing an existing
Scorecard, this link is disabled until you make a change to the Scorecard.
Save As: Displays the Save As dialog box, where you can save the current
Scorecard with a different name or in a different location.
Delete Scorecard: Displays a confirmation message, and then deletes the

Scorecard record. This link is disabled until you save the Scorecard.
Print Scorecard: Displays the Print dialog box, where you can print the
Scorecard.
Documents: Displays the reference documents associated with the Scorecard

record. This link is disabled until you save the Scorecard.
Page. If you are creating a new Scorecard record, this link is disabled until you
save the Scorecard record.
Help: Displays the context-sensitive Help topic for the Design Scorecard page.
Scorecard Pages Menu

The Scorecard Pages menu on the Design Scorecard page contains the Associated Pages
that have been configured for the Scorecard family.
KPI Pages Menu

The KPI Pages menu on the Design Scorecard page contains the Associated Pages that
are configured for the KPI family that is associated with the node selected in the
Contents field. The menu is dynamic, so its label and links change as you select different
nodes in the Contents field.
When you select a KPI Perspective node, the menu is labeled KPI Perspective
Pages and displays the Associated Pages that are defined for the KPI Perspective
family.
When you select a KPI Objective node, the menu is labeled KPI Objective Pages
and displays the Associated Pages that are defined for the KPI Objective family.
When you select an KPI node, the menu is labeled KPI Pages and displays the
Associated Pages that are defined for the KPI family.
Note that the KPI Pages menu does not appear when no node or the Scorecard node is
selected in the Contents tree.
About Designing a Scorecard

On the Design Scorecard page, you can design a new Scorecard or modify the design of
an existing Scorecard by:
Adding the following contents to a Scorecard:
Perspectives
Objectives
KPIs
Removing contents from a Scorecard while keeping the records in the database
for use with other Scorecards.
Deleting contents from a Scorecard and removing the records from the database.
Modifying the data associated with contents of a Scorecard.
Selecting columns to include in a Scorecard.
Renaming a Scorecard.
Renaming a Scorecard
To rename a Scorecard:
1. On the Design Scorecard page, type a new name in the Name field.
2. On the Common Tasks menu, click the Save link to save the Scorecard record
with the new name.
Adding an Existing Perspective

To add an existing perspective to a Scorecard:
1. On the Design Scorecard page, in the Contents section, right-click the Scorecard
icon , and then click Add Perspective.
The Select a Perspective window appears, displaying a list of existing KPI Perspective
records.
2. Select a KPI Perspective record from the list, and click OK.
The perspective is added to the Contents list.
Creating a New Perspective

To create a new perspective and add it to a Scorecard:
1. On the Design Scorecard page, in the Contents section, right-click the Scorecard
icon , and then click Add Perspective.
The Select a Perspective window appears, displaying a list of existing KPI Perspective
records.
2. Click the Create button.

The Create New Perspective window appears, displaying a datasheet where you can type
a name and description for the perspective.
3. In the Perspective Name text box, type a name for the new perspective.
4. In the Perspective Description text box, type a description for the new
perspective, if desired.
The new KPI Perspective record is added to the list on the Select a Perspective window.
6. Select the new KPI Perspective record, and click OK.
The perspective is added to the Contents list.
Adding an Existing Objective

To add an existing objective to a Scorecard:
1. On the Design Scorecard page, in the Contents section, right-click a perspective,
and then click Add Objective.
The Select an Objective window appears, displaying a list of existing KPI Objective
records.
2. Select a KPI Objective record from the list, and click OK.
The objective is added to the Contents list.
Creating a New Objective

To create a new objective and add it to a Scorecard:
1. On the Design Scorecard page, in the Contents section, right-click a perspective,

and then click Add Objective.
The Select an Objective window appears, displaying a list of existing KPI Objective
records.
2. Click the Create button.

The Create New Objective window appears, displaying a datasheet where you can type a
name and description for the objective.
3. In the Objective Name text box, type a name for the new objective.
4. In the Objective Description text box, type a description for the new objective, if
desired.
The new KPI Objective record is added to the list on the Select a Perspective window.
6. Select the KPI Objective record, and click OK.
The objective is added to the Contents list.
Adding a KPI
To add a KPI to a Scorecard:
1. On the Design Scorecard page, in the Contents section, right-click an objective,
and then click Add KPI.
The Select a KPI window appears, displaying a list of existing KPI records.
2. Select any of the KPI records from the list, and click OK.
The KPI is added to the Contents list.
Removing Contents from a Scorecard

When you remove contents from a Scorecard, the record remains in the database for use
with other Scorecards.
To remove contents from a Scorecard:
On the Design Scorecard page, in the Contents section, right-click the

perspective, objective, or KPI that you want to remove, and click Remove.
The selection is removed from the Scorecard, but the record remains in the database and
is available for use with other Scorecards.
Deleting Content from a Scorecard

When you delete content from a Scorecard, you delete the record from the database. You
cannot delete a record that is being used by another Scorecard.
To delete content from a Scorecard:
1. On the Design Scorecard page, in the Contents section, right-click the perspective,
objective, or KPI to be deleted, and click Delete.
A confirmation message appears, asking if you are sure you want to permanently delete
the selection.
2. Confirm the deletion by clicking the Yes button.
The selected record is deleted from the database.
Modifying the Record Associated with

Scorecard Contents
You can access the record associated with Scorecard contents from the Design Scorecard
page and the View Scorecard page. These instructions assume that you are viewing the
Scorecard on the Design Scorecard page. Note that if you use the right-click and Rename
option, which is available on the shortcut menu in the Contents section, the name of the
item will be changed in the tree view only. The name stored with the item can be changed
only by performing the steps in the following instructions.
Note: You can also modify Scorecard contents via the Record Manager.
To modify the data associated with Scorecard contents:
1. On the Design Scorecard page, in the Contents section, right-click the desired
perspective, objective, or KPI, and click View.
If you selected a perspective or an objective, the associated datasheet appears in a
separate window. Note that the icons associated with the datasheet, such as the delete
icon
, are disabled. If you selected a KPI, the KPI Editor page appears, displaying
the selected KPI.
2. Modify the information as desired, and click the Save link on the Common Tasks
menu.
The selected record is modified and saved to the database.
Selecting Columns to Include in a

Scorecard
From the View Scorecard or Design Scorecard page, you can select the columns that you
want to see on the Scorecard.
To select columns to include in a Scorecard:
1. On the Design Scorecard page or the View Scorecard page, on the Scorecard
menu, click the Select Columns link.
The Select Visible Columns dialog box appears.
2. Select the check boxes next to the options in the list that you want to include as
columns. The values for the columns will be calculated in the Scorecard.
3. Click OK.
Example of a Completed Scorecard on

the Design Scorecard Page
The following image shows an example of a completed Scorecard on the Design
Scorecard page, including labels to indicate the perspectives, objectives, and KPIs.
To see this Scorecard as it would appear on the View Scorecard page, click here.
In this example, the Reliability and Maintenance Scorecard is using a Process perspective
to reach the objectives, or goal, of improving reliability, and a financial perspective to
reach another objective of optimizing operating expense. The company is using
mechanical availability and the total number of failures to measure whether it is meeting
its objective of improving reliability. The company is also measuring its ability to meet
the goal of optimizing operating expenses using turnaround maintenance cost, routine
maintenance cost, and total failure cost.
Deleting a Scorecard
To delete a Scorecard:
On the Scorecards page, select the row containing the Scorecard record you want
to delete, and click the Delete link on the Common Tasks menu.
-orOn the Design Scorecard page or the View Scorecard page, click the Delete link on the
Common Tasks menu. Note that you must save the Scorecard record before the Delete
link will be enabled.
The Scorecard record is deleted from the database.
KPI
KPI records store basic information about Key Performance Indicators. The following
table provides an alphabetical list and description of the fields that exist for the KPI
family. The information in the table reflects the baseline state and behavior of these
fields. This list is not comprehensive.
Field
Data
Type
Description
Behavior and Usage
Datasheet
Alert
Distribution Text
List
Alert
Message
The Security Users

who have been
designated to
receive alerts from
this KPI.
This field is populated

automatically with the names
of the recipients you defined
in the Alert Configuration
dialog box when you created
an alert.

The text of the
automatically with the text
email message sent
Character
you defined in the Alert
to a user when an
Configuration dialog box
alert is triggered.
when you created an alert.
This field is
not on a
datasheet by
default.
Default: Alerts
Tab
This field is automatically

populated with the number
you defined in the Alert
The value that a
Configuration dialog box
KPI must meet in when creating an alert. When Default: Alerts
Alert Value Number
order to trigger an the KPI reaches this value, the Tab
alert message.
text in the Alert Message field
is sent in an email message to
the users identified in the
Alert Distribution List field.
populated with the value you
entered on the Specify Limits
The optimal output screen of the KPI Builder.
Best Value Number
KPI Editor
level.
This value is used to calculate
the normalized score that is
assigned to the KPI when it is
created.
Critical
The output value

that indicates that
the KPI has
Number reached a low
performance level
and is not reaching
its potential target.

automatically with the value
you entered on the Specify
Limits screen of the KPI
Builder.
Default:
Defaults Tab,
KPI Editor
Default:
You can type a description of
A brief description
Identification
the KPI into this field
of the KPI.
Tab, KPI
manually.
Editor
End Date
Has Score
Only
KPI
Schedule
Last
Measure
Update
Date
The date the KPI

stopped being
measured.
Indicates whether
the Score is the
Logical only value
displayed on the
Trend Chart.

automatically with the end
date you chose on the KPI
Time Span screen in the KPI
Builder.
Default:
Identification
Tab, KPI
Editor
If this field is set to True, the

KPI's Actual, Target, Critical
and Stretch values are not
displayed on the Trend Chart
or Trend Data. Instead, only KPI Editor
the Score will be displayed for
that KPI by aggregating scores
of its sub-indicators using the
selected aggregation function.
Text
This field stores the schedule

information that you define
via the KPI Update Schedule
dialog box. This field
Information about
indicates to the master
the KPI schedule
scheduled item in Schedule
and how frequently
Manager whether or not the
to update
KPI should be updated. If the
measurements over
KPI is not scheduled as a
a period of time.
recurring item, after
successful completion, this
value in this field will be
deleted.
This field is
not on a
datasheet by
default.
Date
If the KPI is successfully

The date the KPI
executed, this value is
measurements were
populated automatically with
last updated.
the current date.
This field is
not on a
datasheet by
default.
The name of the

KPI.
Default:
Identification
Tab, KPI
Editor
You can type a name for the

KPI into this field manually.
Name
Character
Published
Indicates whether
Logical the KPI has been
published.
Default:
If the KPI has been published,
Identification
this value is set to True.
Tab
Recursive
Logical Indicates whether
If the KPI is scheduled to
This field is
Update
recursively, this value is set to

the KPI has been True. The master KPI
not on a
scheduled to update scheduled item will continue datasheet by
once or recursively. to update this KPI at the
default.
specified frequency.
Schedule
Last Run
Date
Date
If the KPI is scheduled as a

The most recent
date that a KPI was successful execution, this
updated by a
value is populated
scheduled update. automatically with the current
date.
This field is
not on a
datasheet by
default.
Date
If the KPI is scheduled as a

successful execution, this
value is populated
The next date that a
automatically with the next
KPI is scheduled to
scheduled run date based on
take place.
the KPI's schedule frequency.
If the KPI is not scheduled as
a recurring item, this field is
not populated with a value.
This field is
not on a
datasheet by
default.
Schedule
Next Run
Date
The date the KPI

began being
measured.
This value is populated

automatically with the start
date you chose on the KPI
Time Span screen in the KPI
Builder.
Default:
Identification
Tab, KPI
Editor
Start Date
Date
Stretch
The output value

that is much higher
than a target value,
Number
demanding a
breakthrough
performance.

Default:
Defaults Tab,
KPI Editor
screen of the KPI Builder.
Target
The output value

that is your aim for
Number the KPI
measurement at a
given time.

Default:
Defaults Tab,
KPI Editor
Worst Value Number The output value

that should be

KPI Editor
strictly avoided.

This value is used to calculate
the normalized score that is
assigned to the KPI when it is
created.
URL Paths for Metrics and Scorecards

The following table lists and describes the paths for accessing features in the Metrics and
Scorecards module. 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
Path
Description
Metrics Start
Page
Metrics
Displays the Metrics Manager Start Page. This

URL does not accept any parameters.
Metrics
Administration
Metrics/Admin
Displays the Metrics Manager Administration

page, where you can manage cubes.
Design page
Metrics/Designer
Opens the specified cube on the Design page.

This URL accepts a parameter that lets you
specify which Metric View to open.
Linked Views
Opens the Linked Views for the specified

Metric View. This path accepts one parameter
Metrics/LinkedViews
that lets you specify the Metric View for which
to display linked Views.
Opens the specified Metric View on the
Results for <Metric View> page. This path
accepts parameters that let you specify which
Metric View to open and which information to
display.
Results for
<Metric View>
page
Metrics/Results
Drill Through
page
Results/DrillThrough Opens the specified Metric View on the Drill

Through page. This path accepts parameters
that let you specify which Metric View to open

and which information to display.
Manage
Scorecards
Scorecard
Designer
Scorecard
Displays the Scorecards page. This path does

not accept any parameters.
Scorecard/Design
Displays the Design Scorecard page for the

specified scorecard. This path accepts a
parameter that lets you specify which
scorecard to open.
Scorecard Viewer Scorecard/View
Displays the View Scorecard page for the

specified scorecard. This path accepts a
parameter that lets you specify which
scorecard to open.
Manage KPIs
Serves as the path for providing access to the

Manage KPIs functionality. The path accepts
parameters that let you customize the URL.
Scorecard/KPI
Parameters for the Design Page URL

The Design page URL lets you construct a hyperlink that will open a Metric View on the
Design page. The base URL, meridium://Metrics/Designer, accepts one parameter that
lets you specify which cube to open on the Design page.
Parameter
Name
Description
CubeView
Specifies the Metric View that The Entity Key of the

you want to open on the
Metric View that you
Design page.
want to open.
Accepted Value(s)
Notes
This parameter
is required.
Examples of the Design Page URL
meridium://Metrics/Designer?CubeView=1234567
Opens the Metric View with the Entity Key 1234567 on the Metrics Design page.
Parameters for the Results for <Metric

View> Page URL
The URL for the Metrics Results for <Metric View> page, meridium://Metrics/Results,
accepts the parameters described in the following table. This URL lets you construct a
hyperlink that will open a Metric View on the Results for <Metric View> page.
Parameter
Name
CubeView
Mode
Path
Description
Accepted Value(s)
Notes
You must define either the

The Entity Key of the
CubeView parameter or the
Metric View that you want Path parameter to specify
to access.
which Metric View you
want to open.
A value of 0 (zero) will
display the Graph tab. A
value of 1 (one) will
Specifies whether
display the Table tab. Note
to display the
0
that if you omit this
Table tab or the
parameter, the Graph tab
Graph tab on the
1
will be displayed by
Results for
default.
<Metric View>
page.
Specifies the
Metric View that
you want to
access.
Specifies the
Metric View that
you want to
access.
The Catalog path and file

name of the Metric View
that you want to open.
You must define either the

Path parameter or the
CubeView parameter to
specify which Metric View
to open.
Slices
The desired slice. The

values for the Slices
Specifies which
parameter use the syntax
slices you want to [A].[B].[C]... to indicate
apply to the Metric the slice dimension in the
View.
cube hierarchy. See the
examples for more
information.
You can specify multiple

values for the Slices
parameter, separating each
with a comma. Note that
you can use the Slices
parameter to apply to a
cube slices that are not
saved with the Metric View
itself.
Examples of the Results for <Metric

View> Page URL
meridium://Metrics/Results?CubeView=1234567
Opens the Metric View identified by the Entity Key 1234567 on the Results for <Metric
View> page. The Graph tab is selected by default.
meridium://Metrics/Results?CubeView=1234567&Mode=1
Opens Metric View 1234567 on the Results for <Metric View> page, where the Table tab
is selected by default.
meridium://Metrics/Results?CubeView=1234567&Slices=[Customers].[All
Customers].[USA].[WA],[Yearly Income].[All Yearly Income].[$10K - $30K]
Opens Metric View 1234567 on the Results for <Metric View> page, and applies the
slices Slices=[Customers].[All Customers].[USA].[WA] and [Yearly Income].[All Yearly
Income].[$10K - $30K].
meridium://Metrics/Results?Path=Public\Meridium\Modules\Metrics
Manager\Pump Failures
Opens on the Results for <Metric View> page the Pump Failures View, which is stored in
the Catalog folder \\Public\Meridium\Modules\Metrics Manager.
Parameters for the Drill Through Page

URL
The URL for the Drill Through page, meridium://Metrics/DrillThrough, accepts
parameters that let you specify which View to open and which information to display.
Parameter Name
Description
Accepted Value(s)
Notes
This parameter is
required. You must
Specifies the
The Entity Key of define the
Metric View whose
the Metric View CubeViewDrillThrough
CubeViewDrillThrough Drill Through
that you want to parameter and the Page
results you want to
access.
parameter to specify
access.
where to open the
Metric View.
This parameter is
required. You must
define the Page
parameter and the
CubeViewDrill
Through parameter to
specify where to open
the Metric View.
Page
Specifies the page

that you want to Drill Through
access.
MemberCollection
The desired
members. The
values for the
This parameter is
MemberCollection
Specifies the
required. You can
parameter use the
members whose
specify multiple values
syntax [A].[B].
Drill Through
for the
[C]...to indicate the
results you want to
MemberCollection
member dimension
access.
parameter, separating
in the cube
each with a period.
hierarchy. See the
examples for more
information.
Example of the Drill Through Page URL
meridium://METRICS/RESULTS/DRILLTHROUGH?
Page=DrillThrough&CUBEVIEWDRILLTHROUGH=64251796271&MemberCo
llection=[Measures].[Internet Sales-Sales Amount],[Employee].[Department
Name].[All Employees]
Opens the Drill Through page, displaying the Drill Through results for the specified
Metric View and members.
Parameters for the Linked Views URL

The URL for the Linked Views page, meridium://Metrics/LinkedViews, accepts a
parameter that lets you specify the Metric View for which you want to access the Linked
Views page.
Parameter
Name
Description
Path
Specifies the View for which The Catalog path and file
This
you want to access the
name of the View for which parameter is
Linked Views page.
to access linked views.
required.
Accepted Value(s)
Notes
Examples of the Linked Views URL
meridium://Metrics/LinkedViews?Path=Public\Meridium\Modules\Metrics
Manager\Pump Failures
Displays the Linked Views page for the Pump Failures View, which is stored in the
Catalog folder \\Public\Meridium\Modules\Metrics Manager.
Parameters for the Scorecard Designer

URL
The URL for the Design Scorecard page, meridium://Scorecard/Design, accepts the
parameter described in the following table.
Parameter
Name
Description
EntityKey
Specifies which Scorecard The Entity Key of the

you want to open.
desired Scorecard.
Accepted Value(s)
Notes
This parameter is
required.
Examples of the Scorecard Designer

URL
meridium://Scorecard/Design?EntityKey=2775406
Opens in the Design Scorecard page the Scorecard with the Entity Key 2775406.
Parameters for the Scorecard Viewer

URL
The URL for the View Scorecard page, meridium://Scorecard/View, accepts the parameter
described in the following table.
Parameter
Name
Description
EntityKey
Specifies which Scorecard The Entity Key of the

you want to open.
desired Scorecard.
Accepted Value(s)
Notes
This parameter is
required.
Examples of the Scorecard Viewer URL
meridium://Scorecard/View?EntityKey=2775406
Opens in the View Scorecard page the Scorecard with the Entity Key 2775406.
Parameters for the Manage KPIs URL

The URL for the Manage KPIs functionality, meridium://Scorecard/KPI, accepts the
parameters described in the following table. Note that a link constructed from the path
alone will open the Key Performance Indicators page, which displays a list of all the
KPIs in the database.
Parameter
Name
EntityKey
Image
Description
Accepted
Value(s)
The Entity
Specifies the KPI Key of the
that you want to KPI that you
open.
want to
view.
Dial
Specifies to
display the KPI Trend
dial, trend chart,
or trend data for Data
Notes
This parameter can be used in conjunction
with either the Page or Image parameter.
Used alone, this parameter will simply
limit the list of KPIs displayed on the Key
Performance Indicators page.
This parameter should be used in
conjunction with the EntityKey parameter,
which specifies the KPI whose dial you
want to view. This parameter is unique in
that it does not create a standard link.
the specified KPI.
Page
Specifies whether
View
to display the
specified KPI in
Edit
view or edit
mode.
Rather, it displays the image of the actual

KPI component, which is linked to the KPI
itself. This URL is useful for displaying on
a Home Page the image of a KPI
component, which will provide access to
the associated KPI.
This parameter should be used in

conjunction with the EntityKey parameter,
which specifies which KPI you want to
view or edit.
Examples of the Manage KPIs URL
meridium://Scorecard/KPI
Opens the Key Performance Indicators page, which displays a list of all the KPIs that
exist in the database.
meridium://Scorecard/KPI?Page=View&EntityKey=1234567
Opens the KPI identified by the Entity Key 1234567 in the View KPI page.
meridium://Scorecard/KPI?Page=Edit&EntityKey=1234567
Opens the KPI identified by the Entity Key 1234567 in the KPI Editor page.
meridium://Scorecard/KPI?EntityKey=1234567&Image=Dial
Displays an image of the meter for the KPI identified by the Entity Key 1234567.
Clicking the dial image will display the associated KPI on the View KPI page.
Slice
A filter that allows you to specify a subset of data that you want to analyze. Slices can be
added to a Metric View to filter the data that is displayed so that a more specific subset of
data can be examined.
Overview of Root Cause Analysis

The Meridium APM Root Cause Analysis (RCA) module lets you conduct a root cause
analysis, which allows you to track and analyze causes of equipment and location
failures. When you create an RCA Analysis, you are using Meridium APM Framework
Tools to facilitate a standard process that is based on the PROACT for Meridium
methodology.
Note: The RCA module is based on the PROACT RCA Methodology and Software,
Copyright 1996 - 2004, RCI-Reliability Center Incorporated. All rights reserved. Used
with Permission.
When a piece of equipment or location in your facility fails, there could be any number of
causes that led up to the failure. If you investigate the causes, you might find that each
failure stems from another higher-level cause. If this root cause remains unidentified, the
failures will likely persist.
For instance, consider an example of a car that has had trouble starting every month for
the past three months. In this case, you might determine that:
In the first month, the cold weather caused the failure.

In the second month, the battery was low.
In the third month, the fuel in the tank was low.
If you were to conduct a root cause analysis on the car, you may find that while each
month's failure had its own apparent cause, the root cause of each failure was that a spark
plug needed to be replaced.
To help you identify the root causes of failures in your facility, you can assemble an RCA
Analysis Team that will:
Collect data relevant to the failure.
Analyze the data.
Develop hypotheses about the root cause.
Develop recommendations for preventing the failure from occurring or lessen the
impact of the failure in the future.
Implement recommended solutions.
Track implemented solutions and re-evaluate them if necessary. D
What is PROACT for Meridium?

PROACT for Meridium is a methodology that is used in the RCA module and allows you
to conduct a root cause analysis. The PROACT acronym stems from the following steps,
where we have capitalized the letters that make up the acronym:
PReserve: Team members gather and record information (i.e., failure data) about a
piece of equipment's or location's failure.
Order: The Principal Analyst:
Defines the goals of the RCA Analysis.
Assembles the team members who will conduct the RCA Analysis.
Analyze: Team members review and analyze the available information and then
record any conclusions.
Communicate: Team members submit to the decision makers in the organization

their hypotheses about the cause of the failure and their recommendations for
solutions to the failure.
Track: Team members track the success of the solutions that were implemented. A
re-evaluation can be performed, if necessary.
You can use these steps as a guideline for conducting a root cause analysis in the RCA
module, which consists of creating the data in Meridium APM that is necessary to
complete these five steps of the PROACT for Meridium methodology and implement
successful solutions.
Note: These steps do not need to be completed in the exact order that they are listed
above. It is important, however, that all steps of the methodology be completed. For more
information, see the workflow for conducting a root cause analysis.
What is a Root Cause Analysis?

A root cause analysis is the process of analyzing equipment and locations failures down
to their root cause, which can include but is not limited to deficiencies in management
systems and in the piece of equipment or location itself.
In the Meridium APM Framework, an RCA Analysis is the combination of an RCA
Analysis record and a group of records that are linked to it that store all the information
necessary for the team to identify a root cause for a piece of equipment's or location's
failure. The Root Cause Analysis module provides an interface that you can use to create
an RCA Analysis, using the steps in the PROACT for Meridium methodology to facilitate
the completion of a root cause analysis.
When the RCA Analysis is complete, it can be published and made available to users who
are not members of the analysis team, allowing them to view the results using Meridium
APM Framework Tools.
RCA System Requirements

The Root Cause Analysis license is required to take advantage of RCA functionality. In
addition, your system must contain the basic Meridium APM system architecture.
perform some configuration tasks specifically for the RCA module.
Root Cause Analysis Data Model

The Root Cause Analysis data model uses families to represent the various components
of an RCA Analysis, as defined by the standard, accepted PROACT for Meridium
methodology. Meridium APM leverages its fundamental entity and relationship family
infrastructure to store data related to an RCA Analysis.
Each RCA Analysis is represented at the root level by an RCA Analysis record. The RCA
Analysis record can be linked to an RCA Event record through the RCA Analysis
Relationship. RCA Event records can, in turn, be linked to RCA Failure Mode records,
RCA Sequence Node records, and so on for all components of the RCA Analysis.
Together, the root RCA Analysis record and all the records that are linked to it, either
directly or indirectly, make up the RCA Analysis.
The following image shows the entity families and relationship families that are used to
create an RCA Analysis.
Note: RCA Recommendation records can be linked to any Equipment record and any
Functional Location record. They may or mat not be the same Equipment or Functional
Location records that are linked to the RCA Analysis record.
The Root Cause Analysis Best Practice specifies that you will create RCA Analyses either
for equipment or locations. Either option may be valid, depending upon the analysis.
Throughout the RCA documentation, we assume that you are following the Meridium
APM best practice and storing your equipment and location information in Equipment
and Functional Location Records. Additionally, we assume that you are following the
RCA Best Practice and linking your RCA Analysis records to either Equipment or
Functional Location records.
In addition to the relationships that appear in this image, records in the following families
can be linked to records in the RCA Reference Document family through a relationship
definition on the Has Reference Documents family:
RCA Analysis
RCA Critical Success Factor
RCA Event
RCA Failure Mode
RCA Preserve Item
RCA Recommendation
RCA Team Member
RCA Tracking Item
RCA Verification
Additionally, the following families are used by the RCA module but are not related to
any other family in the data model:
The RCA Image family is used to display an image of the Event Diagram and the
Logic Tree in the Comprehensive Analysis Report
The Alert family is used to send alert emails.
About Analysis States

The state of an RCA Analysis record is stored in the State field and is represented by a
value of 0, 1, or 2. The State field is not included on any of the baseline datasheets that
exist for the RCA Analysis family. The state of an RCA Analysis is determined by actions
that you take in the RCA module. When you perform an action (e.g., publish an analysis),
the value in the State field changes automatically, which transitions the analysis from one
state to another. The default value is 0. After an RCA Analysis is published, the value
changes to 1. After an RCA Analysis is produced from an existing analysis (i.e., as a
template), the value changes to 2. On the Manage Analyses page, the numeric values are
translated into text via code that exists in the Meridium APM system.
RCA Analyses can have one of the states in the following list. The number in parentheses
indicates the value in the State field that corresponds to each state. Only the name of the
state will appear on the Manage Analyses page. The numbers are not displayed in Root
Cause Analysis:
In Progress (0): Indicates that an RCA Analysis has not yet been completed. Only
Meridium APM users who are members of the RCA Analysis Team and members
of the MI PROACT Administrator Security Group can view and modify an RCA
Analysis via the My PROACT page when it is in the In Progress state. RCA
Analyses will remain in the In Progress state until the Principal Analyst publishes
the analysis. Additionally, a Published RCA Analysis that is unpublished will

return to the In Progress state.
Published (1): Indicates that an RCA Analysis has been completed. After the RCA
Analysis is complete, the Principal Analyst can publish the analysis, which will
assign the Published state to the analysis and populate the Date Published field in
the RCA Analysis record with the date on which it was published. When an RCA
Analysis is published, Meridium APM users, regardless of whether they are
members of the analysis team or not, will have read-only access to the RCA
Analysis as long as they have the following security permissions:
View privileges to all RCA Analysis families, including the RCA Analysis
Relationships and RCA System Relationships families.
Insert privileges on the RCA Analysis family.
Update privileges on the RCA Image family.
If a Published RCA Analysis is unpublished, the RCA Analysis will return to the In
Progress state, but the value in the Date Published field will not be updated until the
analysis is published again.
Template (2): Indicates that an RCA Analysis has been produced from an existing
analysis using the Produce Template link. RCA Analyses in the Template state are
identical to RCA Analyses that are in the In Progress state, except that they do not
have an analysis team defined.
Super Users, members of the MI PROACT Administrators Security

Group, and Principal Analysts can transition analyses to in the Template
state.
Note: Principal Analysts can create RCA Analysis Templates only if the Template
Creation Permissions setting has been enabled.
Only Super Users and members of the MI PROACT Administrators

Security Group can modify an RCA Analysis that is in the Template state.
Defining When a Root Cause Analysis

Should Be Performed
Before you begin conducting a root cause analysis using the Root Cause Analysis
module, members of your organization should determine which events require further
investigation through a root cause analysis. This involves defining criteria that
standardizes when a root cause analysis should always be performed.
The root cause analysis criteria should be defined according to the needs and resources
within your organization. For instance, the criteria can be based strictly on the data
collected in Failure records. For example, the criteria might be that a root cause analysis
is automatically performed when a piece of equipment fails more than two times in a 12month period. The criteria can also be less restrictive, allowing an area manager or
reliability engineer to initiate a root cause analysis even if a failure does not meet the
standard criteria.
Regardless of the specific criteria that you use, your goal should be to define criteria that
will allow personnel to know when a root cause analysis should always be conducted,
ensuring that failure events are analyzed in a consistent and methodical way.
Steps in Developing an RCA Analysis

After you have configured the RCA module, members of your organization must define
the general criteria that dictate when an RCA Analysis should be performed. When a
piece of equipment or location in your facility meets this criteria, you should perform an
RCA Analysis according to the steps in the PROACT for Meridium methodology using
the Root Cause Analysis module.
The following list outlines the steps in the PROACT for Meridium methodology and the
corresponding tasks that you should complete in Meridium APM to develop an RCA
Analysis.
1. Order the analysis: Use the New Analysis Builder to complete the initial steps
required for the RCA Analysis. When you are finished, an RCA Analysis record is
created. Using the New Analysis Builder, you will:
1.
Select the Equipment or Functional Location record on which the RCA

Analysis is based.
Select the members of the RCA Analysis Team.
Select or add Critical Success Factors to the RCA Analysis.
Select or modify the Team Charter.
2. Preserve failure data: Create RCA Preserve Item records and assign them to team
members.
Note: While the PROACT acronym lists the Preserve step first, the order in which you
perform the associated task in Meridium APM differs.
3. Analyze the data: Create an Event Diagram and a Logic Tree diagram to provide a
visual representation of the data that was collected. Using the diagrams, you can
analyze the data, develop hypotheses, and verify hypotheses. When you develop
and verify hypotheses, you will create the corresponding RCA Hypothesis and
RCA Verification records.
4. Communicate findings and recommendations: Update the RCA Analysis record,
create RCA Recommendation records, and generate reports to communicate the
team's conclusions to the decision makers in your organization.
5. Track and reevaluate results: Using RCA Tracking Item records to track the
success or failure of the solutions that were implemented. If necessary, reevaluate
and modify the team's recommendations.
About This Example

This section of the documentation provides topics that correspond to each step in the
workflow for developing an RCA Analysis. In each topic, the workflow for creating a
Root Cause Analysis will be illustrated through examining the recurring failure(s) of a
cooling water pump. The following topics appear in this section of the documentation and
are intended to be read in order:
Defining the criteria for when an RCA Analysis should be performed.

Ordering the analysis.
Preserving failure event data.
Analyzing data.
Communicating findings and recommendations.
Tracking results.
Note: The information contained in these topics assumes that you are the user who will
be performing the associated step in Root Cause Analysis and that all RCA administrative
tasks have been completed.
Defining When an Analysis Should Be

Performed: An Example
Before you can begin conducting an RCA Analysis, you need to establish the criteria that
standardizes when a Root Cause Analysis should be performed. For example, the
manager of the plant where the cooling water pump exists might specify criteria as:
If any pump fails one or more times per week for more than two successive
weeks, regardless of the cost for repairs, an RCA study should be conducted.
If any pump fails catastrophically (e.g., causes they system to shut off), an RCA
Analysis should be conducted.
-or-
Now, assume that in January 2012, the bearing temperature alarm on the outboard
bearing of a cooling water pump sounded. By the time the operator arrived, the motor
temperature had increased and caused the system to shut off, resulting in loss of
production. According to the criteria that was developed, these conditions dictate that an
RCA Analysis should be performed. The first step is to order the analysis.
Ordering the Analysis: An Example
After the cooling water pump failure meets the criteria for requiring an RCA Analysis,
the first step is to order the analysis. The user who will serve as the Principal Analyst can
complete this step by using the New Analysis Builder to initiate the development of the
RCA Analysis for the recurring failures of the cooling water pump.
To order the analysis for our example:
1. Access the New Analysis Builder.
2. When the New Analysis Builder appears, the PROACT Analysis Datasheet screen
is displayed, where you would define the RCA Analysis record, as shown in the
following image.
In the Frequency of Failures text box, the number 1 represents the number of failures that
occurred for the cooling water pump.
3. When you click the Next button, the Linked Assets screen will appear, where you
can search for the desired Equipment or Functional Location record and select it.
4. You will then click the Next button to display the Select Team Members screen,
where you can define the RCA Analysis Team by selecting the names of the users
who would contribute a wide range of expertise to the team. In this case, you
would select:
The analyst, Suzie Jones, to help gather information surrounding the
failure.
The mechanic, Pete Handy, because he will repair the cooling water pump.
The engineer, Bob Speck, because he is an expert on systems and safety

guidelines.
The following image shows the Select Team Members screen after the RCA Analysis
Team has been selected. The Principal Analyst is Jane Doe, who is an expert on
facilitating team discussion and documenting discussion notes.
5. On the Select CSF screen, you can accept the default Critical Success Factors or
create new ones. For this example, you want to accept the default Critical Success
Factors, so select each Critical Success Factor in the Available CSF grid and
proceed to the next screen.
6. On the Enter Team Charter screen, you can type your own Team Charter or accept
the default Team Charter. For this example, you want to accept the default Team
Charter and modify it so that it appears as the following image shows.
7. After you define the Team Charter, you can click the Finish button to exit the New
Analysis Builder and begin preserving the failure data for the RCA Analysis.
After you click the Finish button, the RCA Analysis record and all initial information for
the RCA Analysis is saved, and the Preserve Failure Data page appears.
An Example of Preserving Failure Event

Data
After you have ordered the RCA Analysis, you can begin preserving failure event data,
which consists of creating RCA Preserve Item records that contain a data-collection task
that should be completed by the team member to whom the record is assigned. Each task
can be categorized according to the 5 P's (i.e., Parts, Paper, People, Position, Paradigms),
which indicates the type of data that should be collected.
To preserve failure event data for our example:
On the Preserve Failure Data page, create RCA Preserve Item records and assign
them to the team members who will complete the task specified in the record. For
this example, you should create RCA Preserve Item records that contain the
information as it appears in each of the following tables.
RCA Preserve Item 1

Field
Value(s)
Assign To
Pete Handy
Data Category
Parts
Data to Collect
The pieces of the cooling water pump that could have

caused the pump to overheat.
Collection
Strategy
Document (pictures and observations) the condition of the

components of the pump.
Date Due
1/8/2012
Send Alert on
Due Date?
True
Days Before Due 1

Date to Be
Notified
Frequency of
Alert After Due
Date
Daily
This is a reminder to gather and document the pieces of the

Alert Email Body pump that could have caused the pump to overheat and
report back to the team.
Completed?
No
Date Completed
RCA Preserve Item 2

Field
Value(s)
Assign To
Suzie Jones
Data Category
Paper
Data to Collect
Standard operating procedures and frequent failure

information
Collection
Strategy
Research
Date Due
1/9/2012
Send Alert on
Due Date?
True
Days Before Due

Date to Be
1
Notified
Frequency of
Alert After Due
Date
Daily
This is a reminder to gather the standard operating

Alert Email Body procedures and frequent failure information and report
back to the team.
Completed?
No
Date Completed
RCA Preserve Item 3

Field
Value(s)
Assign To
Bob Speck
Data Category
People
Data to Collect
Operating procedures used by those who maintain the

pump.
Collection
Strategy
Interview the floor operators who are assigned to the

pump.
Date Due
1/10/2012
Send Alert on
Due Date?
True
Days Before Due

Date to Be
1
Notified
Frequency of
Alert After Due
Date
Daily
This is a reminder to interview operators assigned to the

Alert Email Body pump and document their operating procedures and report
back to the team.
Completed?
No
Date Completed
RCA Preserve Item 4

Field
Value(s)
Assign To
Bob Speck
Data Category
Position
Data to Collect
Environment surrounding the pump.
Collection
Strategy
Tools, pictures, diagrams
Date Due
1/10/2012
Send Alert on
Due Date?
True
Days Before Due

Date to Be
1
Notified
Frequency of
Alert After Due
Date
Daily
Alert Email Body
This is a reminder to investigate the environment where

the pump exists and report back to the team.
Completed?
No
Date Completed
RCA Preserve Item 5
Field
Value(s)
Assign To
Jane Doe (Principal Analyst)
Data Category
Paradigms
Data to Collect
Common assumptions made when a pump fails.
Collection
Strategy
Research and interview.
Date Due
1/10/2012
Send Alert on
Due Date?
False
Completed?
No
Date Completed
After each team member has collected the data that is specified in the RCA Preserve Item
record, they should record their findings for the rest of the team through artifacts,
including Reference Document records and hard copies of documents. After all the RCA
Preserve Item records have been completed, the team can begin to analyze the data.
Analyzing Data: An Example

After the team has preserved the failure data, the team can begin to analyze the data. To
help you visualize the event and organize the team's hypotheses, you should create an
Event Diagram and a Logic Tree to facilitate and organize the team's analysis.
To analyze failure event data for our example:
1. Access the Event Diagram page, and define the failure event by creating an RCA
Event record. For this example, you would complete the RCA Failure Event
datasheet as the following image shows.
2. Diagram the events that led up to and immediately followed the failure event. For
this example, you would create the Event Diagram as shown in the following
image. The team should note the trend in the failures that occurred in the past. In
this way, the team may be able to identify a pattern in the events prior to the RCA
Analysis that may indicate the underlying cause(s) for these failures.
3. Diagram each failure mode in detail. For this example, you would create a Logic
Tree like the one shown in the following image.
In the Logic Tree in this image, you can see that two Failure Mode nodes are linked to the
Failure Event node, and multiple Hypothesis nodes are linked to the Motor Tripped due
to high temperature Failure Mode node.
4. Now that several likely hypotheses have been introduced, the team will need to
rule out hypotheses. To rule out a hypothesis or prove a hypothesis, the hypothesis
will need to be tested against the data that is available to the team (i.e., the failure
event data and the team of experts).
The Principal Analyst should create RCA Verification records and assign them to team
members who will be responsible for completing the associated task. The following
image shows an example of an RCA Verification record that contains a task to test the
Mechanical hypothesis. The record is assigned to the team member Pete Handy, the
mechanic.
The task defined in this RCA Verification record instructs Pete Handy to inspect the
wiring for the cooling water pump to ensure that the problem was not electrical, but
mechanical.
5. When a hypothesis has been tested using the task specified in the RCA
Verification record, the state of the associated RCA Hypothesis record should be
set to True if the hypothesis is true or Not True if the hypothesis is not true. For
example, the following image shows the Logic Tree after Pete Handy has
completed the RCA Verification record to which he was assigned. Pete Handy
concluded that the wiring did not the cause the pump to overheat, so the problem
must be mechanical.
After the state of the Mechanical RCA Hypothesis record is set to True, the team can
continue down the logic tree until they identify the root cause. Causes can be further
identified as physical, human, or latent. For example, the following image shows the
Logic Tree after ALL the RCA Verification records have been completed. The team has
concluded that inadequate accountability of workers has led to insufficient lubricant
being applied to the outboard bearing, which caused the motor's temperature to increase
and the pump to overheat.
In this case, the root cause for the pump failure would be identified as latent (i.e.,
inadequate accountability of workers), which lead to human (i.e., too little applied) and
physical (i.e., lubrication issue) causes. Now that a hypothesis has been verified and the
root cause has been determined, you can create RCA Recommendation records to
communicate your findings on how to prevent this failure in the future.
Communicating Findings and

Recommendations: An Example
Now that the team has determined the root cause of the cooling water pump failure to be
inadequate accountability of workers, you will want to record your findings and create
RCA Recommendation records. After recommendations have been implemented, you can
share the results of the RCA Analysis with others.
To communicate findings and recommendations for our example:
1. On the RCA Communicate datasheet for the example RCA Analysis, complete the
Mechanism and Acknowledgments fields as appropriate. In the following image,
the Mechanism and Acknowledgements fields are outlined in red, and the
datasheet is completed as it should be for this example.
2. After the RCA Communicate datasheet has been completed, you can recommend
actions and propose them for implementation. In this case, the team has decided
that requiring workers to document and report performed maintenance will make
them accountable for procedures performed, and will reduce the risk of a failure
in the future. To propose this recommendation, you would create an RCA
Recommendation record as shown in the following image.
3. On the RCA Recommendation datasheet, on the Alert tab, you can schedule an
alert email to be sent to the team member responsible for completing the
implementation of the recommendation. To do so, you would complete the fields
on the Alert tab for REC-1376 as the shown in the following image.
4. After an RCA Recommendation record has been created, the RCA Analysis is
almost complete. If desired, you can run reports based on the information that was
gathered during the RCA Analysis and even publish the RCA Analysis to
distribute the information to others.
After the recommended action has been implemented, you will need to continue tracking
the success of the recommended solution.
Tracking for Results: An Example

After the RCA Analysis findings have been communicated and the recommendation has
been implemented, the team will want to track the effectiveness of the recommendation
to see if the new report has prevented the cooling water pump from failing thus far.
Tracking for results involves creating RCA Tracking Item records, scheduling the
Tracking Evaluations in the Meridium APM Schedule Manager, and modifying the
existing recommendation or creating a new one based on the discoveries that are made
through reevaluation.
To keep track of the success of the implemented recommendations for our example:
1. Create RCA Tracking Item records and assign them to the team member(s)
responsible for tracking the recommendation. An email message will be sent to
the team member if the values in the Count and Cost field are exceeded. In this
case, you would create an RCA Tracking Item record as shown in the following
image.
The value 2 in the Count field indicates that if the number of Failure records linked to the
Equipment record Pump exceeds two, the alert email will be sent to Bob Williams. Note
also that in the Cost field, the value 45 indicates that if the sum of the failure cost exceeds
$10,000, the alert email will be sent to Bob Williams.
In this case, the cooling water pump has not incurred any failures since the
recommendation was implemented.
2. The recommendation should continue to be tracked by a member of the RCA
Analysis Team through RCA Tracking Item records and the Schedule Manager.
At this point, the RCA Analysis is considered complete, and you can publish the RCA
Analysis and share reports with individuals outside of the RCA Analysis Team.
About the RCA Analysis Example

In this area of the documentation, we list the specific data used in the example RCA
Analysis. This information is provided for your reference.
Note: In these topics, we list only the fields that contain a value. In the case of numeric
fields, this includes fields that contain a value of zero (0). Fields that contain NO value
are not listed here.
The following topics contain details on the specific data in our example RCA Analysis:
Example Data in the RCA Analysis Record

Example Data in the RCA Critical Success Factor Records
Example Data in the RCA Event Record
Example Data in the RCA Failure Mode Records
Example Data in the RCA Hypothesis Records
Example Data in the RCA Logic Gate Records
Example Data in the RCA Preserve Item Records
Example Data in the RCA Recommendation Record
Example Data in the RCA Sequence Node Records
Example Data in the RCA Team Member Records
Example Data in the RCA Tracking Item Record
Example Data in the RCA Verification Record
Example Data in the Equipment Record
Example Data in the RCA Analysis

Record
Like all RCA Analyses, the example RCA Analysis contains one RCA Analysis record.
The following values exist in that record.
Field
Description
Analysis
Description
An analysis to determine the root cause of the pump overheating.
Analysis
Name
Cooling Water Pump
Analysis
Type
Mechanical
Charter
To identify the root causes of the cooling water pump failure. This
includes identifying deficiencies in or lack of management systems.
Appropriate recommendations for root causes will be communicated to
the management for rapid resolutions.
Comments
Comments
Equipment
Pump
ID
End Date
1/15/2012
Event
Narrative
Investigate what caused the motor temperature in the water pump to

increase and overheat.
Frequency
Start Date
1/6/2012
Example Data in the RCA Critical

Success Factor Records
The example RCA Analysis has six RCA Critical Success Factor records, which represent
the default CSFs. Each RCA Critical Success Factor record contains a different value in
the Critical Success Factor field. Each bullet in the following list displays the value that
exists in one of these RCA Critical Success Factor records:
A cross-functional section of plant personnel/experts will participate in the

analysis.
A disciplined RCFA approach will be utilized.
A measurement process will be used to track the progress of approved

recommendations.
All analysis hypothesis will be verified or disproven.
Management agrees to fairly evaluate the analysis team findings and

recommendations.
No one will be disciplined for honest mistakes.
Example Data in the RCA Event Record

The example RCA Analysis contains one RCA Event record. The following values exist
in that record.
Field
Description
Notes
Event End
1/15/2012
Date
None
Event ID
The Event ID field is populated automatically

with the date the record is created and is disabled
so that value cannot be changed. If you choose to
re-create this example RCA Event record, your
Event ID value will be different from the value
listed here.
RCA-9/18/2012
Event Start
1/6/2012
Date
Label
None
Overheating in Pump 1 None
Investigate the cause

Long
of a cooling water
None
Description pump to overheat and
shut down the system.
Example Data in the RCA Failure Mode

Records
The example RCA Analysis has four RCA Failure Mode records. The following values
exist in those records.
RCA Failure Mode Record ID

No Spare Parts
Values Specified
Label: No Spare Parts
Motor tripped due to high temperature.
Description: No spare parts caused the

pump to be out of commission for a longer
amount of time.
Label: Motor tripped due to high
temperature.
Description: The motor shut off because the
temperature became too hot and the system
was shut down.
Example Data in the RCA Hypothesis

Records
The example RCA Analysis has multiple RCA Hypothesis records. The following chart
displays the values for these records, in the order they appear in the Logic Tree.
Note: The ID fields are automatically populated and if you choose to reproduce this
example, your ID values might be different from the values listed here.
RCA Hypothesis Record ID
Values Specified
Level 1
Label: Mechanical
Descriptions: The increase in temperature
was due to a mechanical failure.
Mechanical
Confidence Factor: Likely (3)

State: Hypothesis True
ID: Hyp-365
Label: Electrical
Electrical
Descriptions: The increase in temperature
was due to an electrical failure.
Confidence Factor: Possibly True (2)

State: Hypothesis Not True
ID: Hyp-362
Level 2
Label: Outboard bearing
Descriptions: The outboard bearing had a
mechanical problem.
Outboard bearing
Confidence Factor: Highly Likely (4)

State: Hypothesis True
ID: Hyp-364
Label: Inboard bearing
Descriptions: The inboard bearing had a
mechanical problem.
Inboard bearing
Confidence Factor: Somewhat True (1)

ID: Hyp-363
Level 3
Label: Erosion
Descriptions: The outboard bearing eroded
after overuse.
Erosion

ID: Hyp-367
Label: Corrosion
Corrosion
Descriptions: The outboard bearing
corroded and was rusty.

ID: Hyp-361
Label: Fatigue
Descriptions: The outboard bearing was
overheated due to a weakness of materials.
Fatigue

ID: Hyp-368
Level 4
Label: Misalignment
Descriptions: The outboard bearing was not
aligned correctly.
Misalignment

ID: Hyp-369
Label: Loose Bolts
Descriptions: Bolts were loose and caused
the outboard bearing to become loose.
Loose Bolts

ID: Hyp-370
Label: Lubrication Issue
Lubrication Issue
Descriptions: The outboard bearing was not
receiving the right amount of lubrication.
State: Cause Physical

ID: Hyp-371
Level 5
Label: Leak
Descriptions: The lubricant was leaking
from the pump.
Leak

ID: Hyp-372
Label: Too much applied
Descriptions: There was too much lubricant,
causing, the bearing to operate too quickly
and overheat.
Too Much Applied

ID: Hyp-373
Label: Too little applied
Descriptions: There was not enough
lubricant, causing friction and an increase in
temperature.
Too Little Applied

State: Cause Human
ID: Hyp-374
Level 6
Label: Poor training
Poor training
Descriptions: Workers were not properly
training on applying lubricant to the
bearing.
ID: Hyp-375
Label: Inadequate Procedures Documented
Descriptions: Workers are referencing
procedure documentation that is not clear.
Inadequate Procedures Documented

ID: Hyp-376
Label: Worker Fatigue
Descriptions: Workers are overworked and
are not able to perform at an acceptable
level.
Worker Fatigue

State: Cause Physical
ID: Hyp-377
Label: Inadequate Accountability of
Workers
Descriptions: Workers are not being held
accountable for the maintenance procedures
they are required to perform.
Inadequate Accountability of Workers

State: Cause Latent
ID: Hyp-378
Example Data in the RCA Logic Gate

Records
The example RCA Analysis contains four RCA Logic Gate records, which represent
Logic Gate nodes and are used in the Logic Tree. These Logic Gate nodes must be
enabled to be seen on the Logic Tree.
In the following table, the Logic Gates are numbered as they appear in the Logic Tree
from left to right. For each RCA Logic Gate record, the table displays the value in the
Gate Type field of the RCA Logic Gate record and identifying information about the
records (e.g., RCA Failure Mode) to which it is linked.
RCA Logic
Gate Record
Value Specified Linked To
Gate Type: Or
RCA Failure Mode: Motor tripped due to

high temperature
RCA Hypothesis: Mechanical
RCA Hypothesis: Electrical

high temperature
RCA Hypothesis: Mechanical
RCA Hypothesis: Inboard Bearing
RCA Hypothesis: Outboard Bearing

high temperature
RCA Hypothesis: Outboard Bearing
RCA Hypothesis: Corrosion
RCA Hypothesis: Erosion
RCA Hypothesis: Fatigue

high temperature
Gate Type: Or
Gate Type: Or
Gate Type: Or
Gate Type: Or
RCA Hypothesis: Fatigue
RCA Hypothesis: Loose Bolts
RCA Hypothesis: Lubrication Issue
RCA Hypothesis: Misalignment

high temperature
RCA Hypothesis: Lubrication Issue
RCA Hypothesis: Leak
RCA Hypothesis: Too Little Applied
RCA Hypothesis: Too Much Applied

high temperature
RCA Hypothesis: Too Little Applied
RCA Hypothesis: Inadequate Accountability

of Workers
RCA Hypothesis: Inadequate Procedures

Documented
RCA Hypothesis: Poor Training
RCA Hypothesis: Worker Fatigue
Gate Type: Or
Example Data in the RCA Preserve Item

Records
The example RCA Analysis contains five RCA Preserve Item records. The following
values exist in those records.
RCA Preserve Item

Record ID
Values Specified
Linked To
Data Category: Paper

Data to Collect: Standard
operating procedures and
frequent failure
information.
Collection
Strategy: Research
Date Due: 1/9/2012
Paper-Standard operating
procedures and frequent
failure information.
Send Alert on Due

Date?: True
The RCA Team Member
Days Before Due Date to be record for Suzie Jones.
Notified: 1 (Days)
Frequency of Alert After
Due Date: Daily
Alert Email Body: This is a
reminder to gather the
standard operating
procedures and frequent
failure information and
Completed?: No
Data Category: Paradigms
Paradigms-Common
assumptions made when a
pump fails.
The RCA Team Member

Data to Collect: Common record for Jane Doe.
assumptions made when a
pump fails.
Collection Strategy:
Research and interview.
Date Due: 1/10/2012
Sent Alert on Due Date:
False
Completed: No
Data Category: Parts
Data to Collect: The pieces
of the cooling water pump
that could have caused the
pump to overheat.
Document (pictures and
observations) the condition
of the components of the
pump.
Date Due: 1/8/2012
Parts-The pieces of the
Send Alert on Due Date?:
cooling water pump that
The RCA Team Member
True
could have caused the pump
record for Pete Handy.
to overheat.
Days Before Due Date to be
Notified: 1 (Days)
Due Date: Daily
reminder to gather and
document the pieces of the
pump that could have caused
the pump to overheat and
Completed?: No
Data Category: People
People-Operating procedures
The RCA Team Member
used by those who use the
Data to Collect: Operating record for Bob Speck.
pump.
procedures used by those
who maintain the pump.
Interview the floor
operators who are assigned
to the pump.
Date Due: 2/10/2012

Send Alert on Due Date?:
True
Notified: 1 (Days)
Due Date: Daily
reminder to interview
operators assigned to the
pump and document their
operating procedures and
Completed?: No
Data Category: Position
Position-Environment
surrounding the pump
Data to Collect:
Environment surrounding
the pump.
Collection Strategy: Tools,
pictures, diagrams.
Date Due: 1/10/2012
Send Alert on Due
Date?: Yes
Notified: 1 (Days)
Due Date: Daily
reminder to investigate the
environment where the
pump exists and report
back to them.
The RCA Team Member

record for Bob Speck.
Completed?: No
Example Data in the RCA

Recommendation Record
The example RCA Analysis contains one RCA Recommendation record. The following
values exist in that record.
Field
Description
Alert Responsibility
Party When Due?
True
Assigned To Name
Suzie Jones
Author Name
Jane Doe
Business Impact
Production (PRODUCTION)
Cause
Inadequate accountability of workers.
Cause Type
Cause Latent
Days Before Date To Be

4
Alerted
Final Approver Name
Jane Doe
Frequency of Alert
After Due Date
Daily
Implementation Alert
Text
You have less than 4 days to complete the new required

report.
Mandatory Date
2/28/2012
RCA Analysis ID
Cooling Water Pump
Recommendation
Description
This report will require workers to document each time they

perform a routine procedure, which will hold them
accountable for pump maintenance.
Recommendation
Headline
Create a new performed maintenance report.
Recommendation ID
REC-1376
Recommendation
Priority
Medium (Medium)
Required Equipment
Status
On-Line (ON-LINE)
Reviewer Name
Jane Doe
Status
Created (CREATED)
Target Completion Date Monday, February 20, 2012
Example Data in the RCA Sequence

Node Records
The example RCA Analysis has nine RCA Sequence Node records, which are displayed
on the Event Diagram. For each RCA Sequence Node record, the following table lists the
type of node and the values that exist in the RCA Sequence Node record.
Type of Node
Values
Label: Pump place into service
Start/Finish
Event Start Date: 1/1/2011 12:00 AM
Event End Date: 1/1/2011 12:00 AM
Label: Cooling water pump turned on daily
Process

Label: Bearing Temperature Alarm sounded
Operation
Label: Pump Overheated
Operation
Label: System shut down
Operation
Label: Decided to perform an analysis
Decision
Label: RCA Study began
Start/Finish
Example Data in the RCA Team

Member Records
The example RCA Analysis contains four RCA Team Member records. For each RCA
Team Member record, the following table lists the value in the Member Type field in the
RCA Team Member record and the first and last name in the Human Resource record to
which it is linked.
Value Specified
Linked To Human Resource Record
Principal Analyst
Jane Doe
Member
Suzie Jones
Member
Pete Handy
Member
Bob Speck
Example Data in the RCA Tracking

Item Record
The example RCA Analysis contains one RCA Tracking Item record. The following
values exist in that record.
Field
Description
Active
True
Start Date
3/1/2012
Count
Cost
10,000
Alert
Williams, Bob
Message Subject Cooling Water Pump Improvement

Message Text
Cooling water pump 1 has failed and needs to be re-evaluated.
Example Data in the RCA Verification

Record
The example RCA Analysis contains two RCA Verification records. The following values
exist in that record.
RCA Verification Record ID

Inspect wiring to make sure the cause was
not electrical.
Values Specified
Due Date: 1/10/2012
Method: Inspect wiring to make sure the
cause was not electrical.
Completed: False
Due Date: 1/10/2012
Perform a metallurgical analysis to

determine why the bearing failed.
Method: Perform a metallurgical analysis to

determine why the bearing failed.
Completed: False
Example Data in the Equipment Record

The example RCA Analysis contains one Equipment record. The following value exists
in that record.
Equipment ID: Pump
Accessing Root Cause Analysis

To access Root Cause Analysis:
Elimination, and then click Root Cause Analysis.
The Root Cause Analysis Start Page appears.
Aspects of the Root Cause Analysis Start

Page
The Root Cause Analysis Start Page provides links to features that are available in Root
Cause Analysis. You can click any link to access the corresponding feature.
The PROACT Start Page contains the following links:
My PROACT: Displays the My PROACT page, where you can track unpublished
RCA Analyses in which you are a member of the RCA Analysis Team. To access
the feature, you must be:
A member of the MI PROACT Administrator Security Group.
-or1.
o
A member of the MI PROACT Team Member Security Group.
-or1.
o
A Super User
If you are not, when you click this link, a message will appear, indicating that you do not
have the necessary permissions.
Principal Analyst's View: Displays the PA PROACT page, where you can view
and manage all unpublished RCA Analyses in which you are the Principal
Analyst. To access this feature, you must be:
You must be a member of the MI PROACT Administrator Security Group.
-or1.
o
-or1.
o
A Super User.
New Analysis Builder: Displays the New Analysis Builder, which guides you stepby-step through the initial steps required for developing a new RCA Analysis. To
access this feature, you must be:
-or1.
o
-or1.
o
A Super User.
Manage Analyses: Displays the Manage Analyses page, where you can view a list
of all existing RCA Analyses. To access this feature, you must be:
-or1.
o
-or1.
o
A member of the MI PROACT Viewer Security Group.
-or1.
o
A Super User.
have the necessary permissions. After you click this link, you will be granted access only
to the features allowed by your specific family-level privileges.
Administrative Tools: Displays the Administrative Functions page, where you can
perform administrative tasks for Root Cause Analysis. This link appears only if
you are a Super User or a member of the MI PROACT Administrator Security
Group.

Deploying and configuring the RCA module 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 RCA on
top of the basic Meridium APM system architecture.

are marked as Required if you must perform the step to take advantage of RCA
functionality.
Step Task
1
Optional
Review the RCA data model to
This task is necessary only if
determine which relationship
you store equipment and
definitions you will need to
location information in
modify to include your custom
families other than the
equipment and location
baseline Equipment and
families. Modify any
relationship definitions as
needed via the Configuration
Assign Security Users to one or Required
more RCA Security Groups via
the Configuration Manager
application.
Optional
Specify the Team Charter that
will appear in the New Analysis
Builder by default when you
create a new RCA Analysis.
Optional
Specify the Critical Success
Factors that will appear in the
New Analysis Builder by
default when you create a new
RCA Analysis.
Users will not be able to access

RCA unless they belong to an
RCA Security Group.
Define the Tracking Evaluation Optional

Query.

you do not want to use the
baseline query, which is defined
by default.
Create a scheduled item to

enable Tracking Evaluations.
You can do so via the Meridium
APM Framework application.
A default Team Charter exists in

the baseline Meridium APM
database and will be used if you
do not define one of your own.
Default Critical Success Factors
exist in the baseline Meridium
APM database and will be used
if you do not define one of your
own.
Required
A scheduled item must be
created via the Meridium APM
Schedule Manager to run your
Tracking Evaluation query on a
regular basis.
Optional
7
Specify whether Principal

Analysts will be allowed to
create RCA Analysis
Templates.
Modify queries that are

configured by default to return
Equipment and Functional
Location records.
By default, only Super Users

and members of the MI
PROACT Administrator
Security Group are allowed to
create RCA Analysis Templates.
You can, however, specify that
you want to allow Principal
Analysts to create RCA
Analysis Templates.
Optional
you are using families other
than the baseline Equipment and
Functional Location families to
store your equipment and
location data.
Upgrade Workflow
are upgrading:
V3.5.1
V3.5.0 SP1 LP
V3.5.0
V3.4.5
Upgrading RCA From V3.5.1 to

V3.6.0.0.0
RCA will be upgraded from V3.5.1 to V3.6.0.0.0 automatically when you upgrade the
required.
Upgrading RCA From V3.5.0 SP1 LP to

V3.6.0.0.0
RCA 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.
Upgrading RCA From V3.5.0 to

V3.6.0.0.0
required.
Upgrading RCA from V3.4.5 to

V3.6.0.0.0
required.
About RCA Security

To use RCA, a Meridium APM Security User must be a Super User or a member of one
of the following Security Groups:
MI PROACT Administrator: Allows access to ALL RCA features, including

administrative features.
MI PROACT Team Member: Allows access to all RCA features, except the
administrative features. The Administrative Tools link on the PROACT Start Page
will appear only to Security Users who are Super Users or belong to the MI
PROACT Administrator Security Group.
MI PROACT Viewer: Allows view-only access to the RCA module. Members of
the MI PROACT Viewer Security Group will be able to view existing analyses
but will not be able to create or modify them. When a Security User belongs to the
MI PROACT Viewer Security Group, only the Manage Analyses link on the
PROACT Start Page will be functional.
Each of these Security Groups has a set of family-level privileges associated with it,
which are needed in order to provide access to the records used throughout RCA. Access
to RCA features, however, is not granted through privileges alone but through
membership in these groups and the privileges associated with them. Granting RCA
family-level privileges at the Security User level or through a custom Security Group will
not provide access to RCA.
Throughout the RCA documentation, when we explain how to perform a certain task, we
assume that the user is a member of the Security Group that allows access to that task.
Note: In addition to assigning Security Users to these Security Groups, you will need to
grant users family-level privileges to any custom family that participates in a relationship
with a baseline RCA family.
About Root Cause Analysis Security

Privileges
In addition to the family-level privileges that must be granted to users via the
Configuration Manager application, in RCA, permission to perform certain tasks is
granted based upon a user's role on a given RCA Analysis team. There are two types of
RCA Analysis Team members:
Principal Analyst: The member of the RCA Analysis Team who is responsible for
facilitating and coordinating the RCA Analysis. The user who completes the
initial steps required for an RCA Analysis is automatically designated the
Principal Analyst by default. You can designate a different team member as the
Principal Analyst if needed. For a given RCA Analysis, the Principal Analyst can:
View, modify, copy, delete, and publish the RCA Analysis.
Copy, delete, and unpublish the RCA Analysis.
Note: Published RCA Analyses cannot be modified by any user, including the Principal
Analyst. If needed, the Principal Analyst can unpublish the RCA Analysis, modify it, and
then republish it.
Create RCA Analysis Templates from the RCA Analysis.
Note: Principal Analysts can create RCA Analysis Templates only if permission to do so
has been granted through the Template Creation Permissions setting on the
Administrative Functions page.
Analysis Team Member: Any user who is a member of an RCA Analysis Team.
Analysis team members who have Meridium APM user accounts can view any
unpublished RCA Analysis to which they belong. Team members can modify the
RCA Analysis information, the Logic Tree, and the Event Diagram but cannot
modify the RCA Analysis Team.
Note: The preceding descriptions of Root Cause Analysis roles assume that the user has
FULL privileges to ALL RCA families.
In addition to RCA Analysis Team members, a Meridium APM user who is not a member
of the RCA Analysis Team can view a read-only copy of any published RCA Analysis as
long as that user has View privileges to all RCA Analysis families, including the RCA
Analysis Relationships and RCA System Relationships families. That user will also need
additional Insert privileges on the RCA Analysis family and Update privileges on the
RCA Image family.
RCA Security Groups

The following Security Groups are provided for RCA:
MI PROACT Administrator
MI PROACT Team Member
MI PROACT Viewer
Membership in these Security Groups provides Security Users with access to RCA. The
baseline privileges for these Security Groups are listed in the following table. Note,
however, that access to RCA is not granted through these privileges but through
membership in these Security Groups.
MI PROACT
Administrator
MI PROACT
Team Member
MI PROACT
Viewer
Equipment
View
View
View
Functional Location
View
View
View
Human Resource
View, Update, Insert
View, Update,
Insert
View
Notification
View, Update,
Insert, Delete
View, Update,
Insert, Delete
View
RCA Analysis
View, Update,
Insert, Delete
View, Update,
Insert, Delete
View
RCA Build List Item
View, Update,
Insert, Delete
View, Update,
Insert, Delete
View
View, Update,
Insert, Delete
View, Update,
Insert, Delete
View
RCA Event
View, Update,
Insert, Delete
View, Update,
Insert, Delete
View
Family
RCA Failure Mode
View, Update,
Insert, Delete
View, Update,
Insert, Delete
View
RCA Hypothesis
View, Update,
Insert, Delete
View, Update,
Insert, Delete
View
RCA Logic Gate
View, Update,
Insert, Delete
View, Update,
Insert, Delete
View
RCA Preserve Item
View, Update,
Insert, Delete
View, Update,
Insert, Delete
View
RCA Recommendation
View, Update,
Insert, Delete
View, Update,
Insert, Delete
View
RCA Sequence Node
View, Update,
Insert, Delete
View, Update,
Insert, Delete
View
RCA Team Member
View, Update,
Insert, Delete
View, Update,
Insert, Delete
View
RCA Tracking Item
View, Update,
Insert, Delete
View, Update,
Insert, Delete
View
RCA Verification
View, Update,
Insert, Delete
View, Update,
Insert, Delete
View
Reference Document
View, Update,
Insert, Delete
View, Update,
Insert, Delete
View
RCA Image
View, Update,
Insert, Delete
View, Update,
Insert, Delete
View, Update,
Insert
Security User
View
View
View
Has Recommendations
View, Update,
Insert, Delete
View, Update,
Insert, Delete
View
Has Reference Documents
View, Update,
Insert, Delete
View, Update,
Insert, Delete
View
Is a User
View, Update,
Insert
View
Group Assignment
View, Update,
Insert
View
Production Event Has RCA

Analysis
View, Update,
Insert, Delete
View, Update,
Insert, Delete
View
RCA Analysis Has Asset
View, Update,
Insert, Delete
View, Update,
Insert, Delete
View
RCA Analysis Relationships
View, Update,
Insert, Delete
View, Update,
Insert, Delete
View
RCA System Relationships
View, Update,
Insert, Delete
View, Update,
Insert, Delete
View
RCA Tracking Item

Relationships
View, Update,
Insert, Delete
View, Update,
Insert, Delete
View
User Assignment
View, Update,
Insert
View
Equipment Has Equipment
View
View
View
Functional Location Has

Equipment
View
View
View
Functional Location Has

Functional Location(s)
View
View
View
A Note About RCA Team Member Roles

RCA security is somewhat unique because Security Group membership is used in
conjunction with a user's role within a given analysis to determine what that user can and
cannot do with that analysis. Each analysis has:
A Principal Analyst who can perform all functions related to the analysis.
Analysis team members, who can perform most functions related to analysis but
are restricted from performing some tasks that are reserved for the Principal
Analyst.
Viewers, who can only view the analysis after it has been published.
Permissions granted through these roles will override access granted through RCA
Security Group membership. This means, for example, that some functions may be
restricted for members for the MI PROACT Administrator Security Group when they are
working with an analysis in which they are not the Principal Analyst.
For a complete description of the functions that are allowed and not allowed based on a
user's role within an analysis, see the RCA Help. Note that privileges granted through
roles are done through data filters that are defined on the baseline Analysis family for
RCA Analyses.
Accessing the Administrative Functions

Page
Note: To access the Administrative Functions page, you must be a Super User or a
member of the MI PROACT Administrator Security Group.
To access the Administrative Functions page:
In the Meridium APM Framework application, on the Root Cause Analysis Start
Page, click the Administrative Tools link.
The Administrative Functions page appears.
Aspects of the Administrative Functions

Page
The Administrative Functions page contains the following sections, which allow you to
perform various administrative functions for the RCA module:
Default Team Charter

Default Critical Success Factors
Select Tracking Evaluation Query
Template Creation Permissions
At the bottom of the page, the following buttons appear:
Save: Saves the changes that were made to the settings on the Administrative
Functions page and then displays the Root Cause Analysis Start Page.
Cancel: After displaying a confirmation message, saves or discards your changes
depending upon your response and then displays the Root Cause Analysis Start
Page.
The Administrative Functions page contains one task menu: Common Tasks.
Default Team Charter Section

The following image shows the Default Team Charter section of the Administrative
Functions page.
The Default Team Charter section contains a text box, were you can specify the Team
Charter that will appear by default when you click the Default Team Charter button on
the Enter Team Charter screen in the New Analysis Builder. A Team Charter is provided
in the baseline Meridium APM database. You can use the baseline Team Charter or
specify a custom Team Charter.
Default Critical Success Factors Section

The following image shows the Default Critical Success Factors section of the
The Default Critical Success Factors section contains a list of the Critical Success
Factors (CSFs) that will appear by default in the Available CSF section on the Select
CSF screen in the New Analysis Builder. Below the list of default CSFs, the following
buttons appear:
Edit: Displays the selected default CSF on the Critical Success Factor dialog box,
where you can modify the text as desired. This button is enabled only when a row
is selected in the list.
Add: Displays a blank Critical Success Factor dialog box, where you can define a
new default CSF.
Delete: Displays a confirmation message and then deletes the selected default
CSF. This button is enabled only when a row is selected in the list.
Select Tracking Evaluation Query

The following image shows the Select Tracking Evaluation Query section of the
The Select Tracking Evaluation Query section contains a text box that stores the path to
the query that returns the number and costs of failures that have occurred for a given
piece of equipment or location after a specific date. Based upon this information, you can
send a Tracking Item notification email to the recipient specified in the RCA Tracking
Item record.
By default, the Select Tracking Evaluation Query text box contains the Catalog path to
the Tracking Evaluation Query that is provided in the baseline Meridium APM database,
Tracking Evaluation Query, which is stored in the Catalog folder
\\Public\Meridium\Modules\RCA.
Below the Select Tracking Evaluation Query text box, the following buttons appear:
Browse: Displays the Open Query window, where you can navigate to a different
query.
Clear: Removes the value that appears in the Select Tracking Evaluation Query
text box.
Template Creation Permissions

The following image shows the Template Creation Permissions section of the
The Template Creation Permissions section contains a check box that lets you determine
whether or not Principal Analysts will be allowed to create RCA Analysis Templates. By
default, this check box is cleared, indicating that only Super Users and members of the
MI PROACT Administrator Security Group will be allowed to create RCA Analysis
Templates. You can select the check box to also allow Principal Analysts to create RCA
Templates.
Common Tasks Menu
The Common Tasks menu on the Administrative Functions page one option:
Help: Displays the context-sensitive Help topic for the Administrative Functions
page.
About the Team Charter

The Team Charter is a statement that defines the goal that the RCA Analysis Team wants
to achieve through conducting an RCA Analysis. The RCA Analysis Team can refer to the
Team Charter throughout the analysis to determine if the goal is being achieved. A Team
Charter is provided in the baseline Meridium APM database and appears in the Default
Team Charter section of the Administrative Functions page. The following image
shows the Team Charter that is defined in the baseline Meridium APM database as it
appears on the Administrative Functions page.
When you complete the initial steps required for a new RCA Analysis via the New
Analysis Builder, you will be prompted to specify the Team Charter on the Enter Team
Charter screen. This screen displays the Team Charter that is defined in the Default Team
Charter section on the Administrative Functions page (shown in the previous image). The
following image shows the Enter Team Charter screen in the New Analysis Builder.
On the Enter Team Charter screen in the New Analysis Builder, you can choose to:
Accept the default Team Charter

Modify the default Team Charter.
Create a new Team Charter.
Modifying the Default Team Charter
The following instructions provide details on modifying the Team Charter that will be
displayed in the New Analysis Builder by default. When you modify the baseline Team
Charter, the text that you specify will be saved in place of the baseline text.
To modify the default Team Charter:
1. In the Meridium APM Framework application, on the Administrative Functions
page, in the Default Team Charter text box, modify the text as desired.
2. At the bottom of the page, click the Save button.
Your changes are saved, and the Root Cause Analysis Start Page appears.
About Critical Success Factors

Critical Success Factors (CSFs) are elements of a Root Cause Analysis that indicate
whether or not the RCA Analysis effort has been successful. The RCA Analysis effort is
considered to be successful if the RCA Analysis Team adheres to and meets the standards
defined by the Critical Success Factors (CSFs). The RCA Analysis Team can define CSFs
that are specific to a given RCA Analysis or that are more generic to the work process.
When you create an RCA Analysis via the New Analysis Builder, you will be prompted
to select the CSFs for the analysis on the Select CSF screen. You can choose from a list of
Critical Success Factors that appears in the Available CSF section on that screen. This list
contains the CSFs that are defined in the Default Critical Success Factors section on the
Administrative Functions page. Throughout this documentation, we refer to the CSFs that
appear in this list as default CSFs.
A list of default CSFs is provided with the baseline RCA module and is displayed on the
Administrative Functions page. If desired, an administrative user can customize the list of
default CSFs. The following image shows the baseline default CSFs as they appear in the
Default Critical Success Factors section on the Administrative Functions page.
In the New Analysis Builder, on the Select CSF screen, you can:
Use the default CSFs that are displayed in the Available CSF section.
Define your own custom CSFs via the Custom CSF text box.
-or-
The following image shows the Select CSF screen as it appears in the New Analysis
Builder.
Creating New Default Critical Success

Factors
You can create default CSFs that are specific to a certain RCA Analysis or that are
generic to any RCA Analysis. After you create a new default CSF, it will appear in the:

Available CSF list on the Select CSF screen in the New Analysis Builder.
The following instructions provide details on creating a new default Critical Success
Factor via the Administrative Functions page.
To create a new default Critical Success Factor:
page, in the Default Critical Success Factors section, click the Add button.
The Critical Success Factor dialog box appears.
2. In the text box, type the text that defines the Critical Success Factor.
The Critical Success Factor dialog box closes, and the new default CSF appears in the
list in the Default Critical Success Factors section.
4. At the bottom of the Administrative Functions page, click the Save button.
Modifying Existing Default Critical

Success Factors
The following instructions provide details on modifying default CSFs via the Default
Critical Success Factors section on the Administrative Functions page.
You can modify a default CSF to make it more relevant to a specific RCA Analysis, or
you can modify a default CSF to make it generic to your work process. After you modify
a default CSF, your changes will appear in the:
Available CSF list on the Select CSF screen of the New Analysis Builder.
To modify an existing default Critical Success Factor:

page, in the list in the Default Critical Success Factors section, select the row
containing the default CSF that you want to modify.
2. Click the Edit button.

The Critical Success Factor dialog box appears, displaying the text that is currently
defined for the default CSF that you selected.
3. Modify the text as desired.

The Critical Success Factors dialog box closes, and your changes appear in the list in the
Default Critical Success Factors section on the Administrative Functions page. In the
following image, the selected row contains a default CSF that was modified.
5. At the bottom of the Administrative Functions page, click the Save button
Deleting Default Critical Success

Factors
If desired, you can delete a default CSF that you do not want use for any RCA Analyses.
When you delete a default CSF, it will be removed from the:
Available CSF list on the Select CSF screen in the New Analysis Builder.
To delete a default Critical Success Factor:

page, in the list in the Default Critical Success Factors section, select the row
containing the default CSF that you want to delete.
A confirmation message appears, asking if you really want to delete the default CSF.
The selected default CSF is deleted and removed from the list in the Default Critical
Success Factors section.
4. At the bottom of the Administrative Functions page, click the Save button,
About Tracking Evaluations

Tracking Evaluations are scheduled items that you can create in the Meridium APM
Schedule Manager and use to track the success of a recommendation that was
implemented as the result of an RCA Analysis. Tracking Evaluations are executed at
regular intervals as determined by the Schedule Manager. When the Tracking Evaluation
is executed, if certain conditions are met, a Tracking Item notification will be sent via
email to a specified recipient, notifying the recipient that the recommendation requires
reevaluation.
The Meridium APM system will use the query that is specified in the Select Tracking
Evaluation Query section on the Administrative Functions page to return the number and
costs of failures that have occurred for a given piece of equipment or location after a
specific date. The baseline RCA product provides a query for this purpose, Tracking
Evaluation Query, which is stored in the Catalog folder
The baseline Tracking Evaluation Query returns the number and costs of failures that
have occurred for a given piece of equipment or location after a specific date. This
information is stored in records in the baseline Equipment, Functional Location, and
Work History families. If you are following the Meridium APM Best Practice and using
Equipment and Functional Location records to store your equipment and location
information and Work History records to store your failure information, you should not
need to modify this query.
When the Tracking Evaluation scheduled item is executed, the Meridium APM system
will run the query that is specified on the Administrative Functions page and retrieve the
failure count and cost data for the Equipment or Functional Location record that is linked
to a given RCA Tracking Item record. The Meridium APM system will compare the
results of the query against the reevaluation criteria stored in the Start Date, Count, and
Cost fields in the RCA Tracking Item record. If the criteria are exceeded, a Tracking Item
notification email will be sent to the recipient specified in the Alert field in the RCA
Tracking Item record.
Note: Recommendations will continue to be tracked in this way until the value in the
Start Date field in the RCA Tracking Item record is updated or until the Active check box
in the RCA Tracking Item record is cleared.
If you are following the Meridium APM Best Practice, to enable complete Tracking
Evaluation functionality, you will at least need to create a Tracking Evaluation scheduled
item in the Meridium APM Schedule Manager. If you are not following the Meridium
APM Best Practice, in addition to creating the scheduled item, you will also need to
create your own Tracking Evaluation query and define it on the Administrative Functions
page.
Creating the Tracking Evaluation

Scheduled Item
In Root Cause Analysis, you can create an RCA Tracking Item record that contains
criteria that defines when an implemented recommendation for a piece of equipment or
location requires reevaluation. When the criteria stored in the RCA Tracking Item record
is met, an email message will be sent to the specified user.
To enable this functionality, you will need to create a scheduled item in the Meridium
APM Schedule Manager to run that query on a regular basis to determine whether or not
the criteria have been met. When the scheduled item is executed, if the Tracking
Evaluation query returns results that exceed the criteria defined in RCA Tracking Item
records, an email message will be sent to the responsible team member.
To create a scheduled item that will execute tracking evaluations for Root Cause
Analysis:
1. Launch the Meridium APM Schedule Manager and log in.
2. On the Scheduled Items window, click the Add New... link.
The Choose a Meridium Assembly window appears.
3. Select the file Meridium.RCA.dll, and click the Open button.

The Schedule PROACT Tracking Evaluation dialog box appears, displaying the Task tab.
4. Select the Recurring item check box, and then select the frequency for the
execution. The frequency that you select will determine how often the criteria is
examined to see if it has meet the conditions specified in the RCA Tracking Item
record.
5. Click the User tab.
6. On the User tab, type the user ID of a user who has at least View permissions to
the Catalog folder where the Tracking Evaluation query is stored and to the
families that are included in the query.
7. In the Password text box, type the password associated with the user ID that you
specified in the previous step.
8. Click OK.
The scheduled item is saved and appears in the Scheduled Items window.
Specifying the Tracking Evaluation

Query
If you do not want to use the baseline Tracking Evaluation Query, you can specify a
custom Tracking Evaluation Query to track the success of a recommendation that was
implemented as the result of an RCA Analysis.
To specify the Tracking Evaluation query that you want to use:
page, in the Select Tracking Evaluation Query section, click the Browse button.
The Open Query dialog box appears.
2. Navigate to the desired query, and then click the Open button.
The path and file name of the query appears in the Select Tracking Evaluation Query
field.

Defining Template Creation Permissions

By default, only Super Users and members of the MI PROACT Administrator Security
Group are allowed to create RCA Analysis Templates. You can, however, also specify that
you want to allow Principal Analysts to create RCA Analysis Templates.
To specify whether or not Principal Analysts will be allowed to create RCA Analysis
Templates:
1. In the Meridium APM Framework application, access the Administrative
Functions page, and scroll down to the Template Creation Permissions section.
2. If you want RCA users to be allowed to create RCA Analysis Templates from any
RCA Analysis for which they are the Principal Analyst, select the check box.
-orIf you do not want Principal Analysts to be allowed to create RCA Analysis Templates,
clear the check box. By default, the check box is cleared.
Note: Regardless of whether this check box is selected or cleared, Super Users and
members of the MI PROACT Administrator Security Group will be allowed to create an
RCA Analysis Template from any RCA Analysis. Additionally, RCA users serving the
Analysis Team Member role in an analysis will not be allowed to create RCA Analysis
Templates.
About Configuring Queries for Custom

Families
If you have defined equipment and location information the baseline Equipment and
Functional Location families and defined failure information in the Work History family,
you will be able to use the baseline RCA queries without performing any configuration
tasks.
If you have defined this information in families outside of these baseline families, you
will need to modify existing queries in order to perform certain tasks in the Root Cause
Analysis module. These queries are stored in the following folder in the Meridium APM
Catalog: \\Public\Meridium\Modules\RCA.
The following queries will need to be configured to incorporate non-baseline families:
Get Equipment Family Key Query

Get Functional Location Family Key Query
Functional Location from Asset Query
Tracking Evaluation Query
Note: The queries Select Query-Does Not Have Equipment and Select Query- Has
Equipment were previously used to identify equipment and location families, but now the
Meridium APM system identifies equipment and location families using the RCA Has
Asset relationship. These queries still exist in the Catalog folder
\\Public\Meridium\Modules\RCA but are not used and do not need to be modified to use
custom families.
Customizing Family Key Queries

If you are using non-baseline families to store equipment and location information, you
will need to modify the Get Equipment Family Key and Get Functional Location Family
Key queries to use your custom families and fields.
The baseline Get Equipment Family Key query returns the following fields from the
Equipment family:
FMLY_KEY
Equipment Technical Number
In an RCA Recommendation record, when you search for a record using the Equipment
ID field, the Meridium APM system uses this query to populate the Search In list with the
value Equipment automatically. This query is also used to populate the Technical Number
field automatically. If you are using a non-baseline family to store information about
equipment, you will need to modify the query to return the Family Key of the family that
you use to store equipment data. You can also modify the query to populate the Technical
Number field in an RCA Recommendation record with a value that you use to identify
equipment.
The baseline Get Functional Location Family Key query returns the following fields from
the Functional Location family:
FMLY_KEY
In an RCA Recommendation record, when you search for a record using the Functional
Location ID field, the Meridium APM system uses this query to populate the Search In
list with the value Functional Location automatically. If you are using a non-baseline
family to store location information, you will need to modify the query to return the
Family Key of the family that you use to store location data.
Customizing the Functional Location

from Asset Query
If you are using non-baseline families to store equipment and location information, you
will need to modify the Functional Location from Asset query to use your custom
families and fields.
The baseline Functional Location from Asset query returns the following fields:
From the Equipment Family: The ENTY_KEY field. The following prompt is
defined for the this field.
((? :n :caption='Equipment Key'))
From the Functional Location Family: The ENTY_ID and ENTY_KEY fields.
In an RCA Recommendation record, if the Equipment record you selected using the
Equipment ID field is linked to a Functional Location record, the Meridium APM system
uses this query to populate the Functional Location ID field in the RCA Recommendation
record automatically. If you are using non-baseline families, you will need to modify the
query to return the Record ID and Entity Key of records that belong to the family that
you use to store location data.
Customizing the Tracking Evaluation

Query
If you are using non-baseline families to store equipment, location, and failure
information, you will need to modify this query to use your custom families and fields.
The baseline query contains a union statement and, therefore, can be modified via the
SQL code only. Alternatively, you can create a new query in the Meridium APM
Framework application. Custom families must follow the same guidelines used for
baseline families.
The following elements are returned from the baseline families using the baseline
Tracking Evaluation Query. The Equipment and Functional Location families are related
to the Work History family via the Has Work History relationship.
Equipment family or Functional Location family: The ENTY_KEY field. The

following prompt is defined for the ENTY_KEY field:
((? :n :caption= 'ENTITY_KEY' :id=ENTY_KEY))
If you are using a non-baseline family, you will need to provide the ENTY KEY of your
custom family and add the baseline prompt.
Work History family: The ENTY_KEY, Total Cost, and Event Start Date fields.
The following prompt is defined for the Event Start Date field.
(>(? :d :caption='START_DATE' :id=START_DATE))
If you are using a non-baseline event family, you will need to add fields that you can use
as Count, Cost, and Date columns. The following list contains information on how the
criteria in each column are used by the Meridium APM system:
Count: Used to count the number of failures that the piece of equipment or
location has incurred since the start date that is specified in the RCA
Tracking Item record. The Count column must have the alias Count
defined for it.
Cost: Used to calculate the total cost of the failures that the piece of
equipment or location has incurred since the start date that is specified in
the RCA Tracking Item record. The Cost column must have the alias Cost
defined for it.
Date: Used to compare the date on which the failures occurred to the start
date that is specified in the RCA Tracking Item record. The Date column
must contain the baseline prompt.
If you modify the baseline Tracking Evaluation Query or create a custom one, you will
need to specify that query as the default query on the Administrative Functions page.
About Navigating the RCA Module

Within the Meridium APM Framework application, the RCA module provides the
following navigational tools:
A start page with links that provide access to the main features of RCA. You can
use these links to develop an RCA Analysis.
A Site Map that you can use to navigate within the RCA module. The Site Map
indicates your current location and shows the typical path for arriving there. To
access a previous page, you can click its hyperlinked name in the Site Map.
Using the RCA Site Map

The Site Map in RCA allows you to navigate from the current page to other pages in
RCA. The RCA link, which provides access to the Root Cause Analysis Start Page, will
always be available. Links to other pages may also be available, depending upon your
location in the application. You can click any link that is available to access the
corresponding page.
The following image shows an example of what the Site Map looks like on the Analysis
page. A red outline has been added to the image to highlight the Site Map.
About Ordering Analyses

After all of the Root Cause Analysis administrative tasks have been completed, you can
order the analysis. Ordering the analysis consists of completing the following steps via
the New Analysis Builder:
Create the RCA Analysis record.

Link the RCA Analysis record to the desired Equipment or Functional Location
records.
Define Critical Success Factors (CSFs).
Define the Team Charter.
Set up the RCA Analysis Team.
The user that completes these tasks will be added to the RCA Analysis Team
automatically as the Principal Analyst. If desired, after completing these steps, you can
designate a different team member as the Principal Analyst.
Note: You can define CSFs, the Team Charter, and the RCA Analysis Team outside of the
New Analysis Builder, if needed. For more information, see the related topics in this
section of the documentation.
Accessing the New Analysis Builder
You can access the New Analysis Builder in various ways, depending on the page that you
are currently viewing in Root Cause Analysis.
To access the New Analysis Builder:
If you are on the Root Cause Analysis Start Page, click the New Analysis
Builder link.
If you are on the PA PROACT page (i.e., the Principal Analyst's View), on the
Common Tasks menu, click the New Analysis link.
If you are on the My PROACT page, on the Common Tasks menu, click the New
Analysis link.
If you are on the Manage Analyses page, on the Common Tasks menu, click the
Create Analysis link. From the Manage Analyses page, you can also copy an
existing RCA Analysis to create a new one or use an RCA Analysis Template to
create a new RCA Analysis.
The New Analysis Builder appears, displaying a new RCA Analysis record.
After you access the New Analysis Builder, you will need to proceed through the builder
and supply information on each screen in order to create a new analysis.
Developing a New RCA Analysis

To create a new RCA Analysis using the New Analysis Builder:
1. Access the New Analysis Builder.
The New Analysis Builder appears, displaying RCA Analysis Datasheet screen.
2. On the Analysis Details tab, enter values in the available fields. The Analysis
Name field is required and must be unique.
The Link Assets screen appears.
4. At the bottom of the Link Assets screen, click the Link Assets button.
The Find Asset window appears.
5. Perform a search to find the Equipment records that you want to link to the RCA
Analysis record.
6. In the search results, select the rows that contain the desired records, and then
click the Select button.
The Select an Asset screen returns to focus.
Each Equipment record you selected is linked to the RCA Analysis record and appears on
the Linked Assets screen. The Record ID column is populated with the Record ID of the
Equipment record that you selected from the list, and the Family column is populated
with Equipment.
7. Click the Link Assets button again.
The Find Asset window appears.
8. Perform a search to find the Functional Location records that you want to link to
the RCA Analysis record.
9. In the search results, select the rows that contain the desired records, and then
The Select an Asset screen returns to focus.
Each Functional Location record you selected is linked to the RCA Analysis record and
appears on the Linked Assets screen. The Record ID column is populated with the Record
ID of the Functional Location record that you selected from the list, and the Family
column is populated with Functional Location.
The Select Team Members screen appears.
Note: The New Analysis Builder displays a list of available members with a Human
Resource record already defined in the Meridium APM database. If you want to add a
team member whose name does not appear in the list, you must first create a Human
Resource record for the user outside of the New Analysis Builder. You can then add the
user to the team via the Team page.
11. In the Available Members list, select the users that you want to add to the RCA
Analysis Team, and click the
button. The user who creates the RCA
Analysis is added automatically to the RCA Analysis Team as the Principal
Analyst. Note also that you can filter the list of users by typing criteria in the
Search Text box and clicking the Search button.
Hint: You can add members to the RCA Analysis Team via the drag-and-drop method or
by double-clicking a user.
The selected users appear in the Selected Team Members list.
Hint: If needed, you can use the
button, the drag-and-drop method, or the doubleclick method to remove selected team members from the Selected Team Members list.
12. When you are finished adding members to the list, click the Next button.
The Select CSF screen appears.
13. In the Available CSF list, select the desired Critical Success Factors (CSFs). The
list contains the CSFs that an administrative user has pre-configured for use with
RCA Analyses. You can select any CSF from the list by double-clicking it or by
using the drag-and-drop method to add it to the Selected CSF list.
The selected CSFs appear in the Selected CSF list.
14. If you want to add a custom CSF to the RCA Analysis, type the appropriate text in
the Custom CSF text box, and then click the Add CSF button.
The new CSF appears in the Selected CSF list. You can add as many custom CSFs you
like.
Hint: If needed, you can remove a CSF from the Selected CSF list by double-clicking it
or by using the drag-and-drop method to add it back to the Available CSF list.
15. When you have finished selecting the CSFs that you want to include in the
analysis, click the Next button.
The Enter Team Charter screen appears.
16. On the Enter Team Charter screen, you can:
Create a custom Team Charter by typing the Team Charter in the text box
in the Enter Team Charter section.
-or1.
Use the default Team Charter that an administrative user has defined by
clicking the Default Team Charter button. The Default Team Charter
dialog box appears.
Click the Accept button to use the default Team Charter. You can then modify the default
Team Charter in the text box in the Enter Team Charter section, if desired.
17. When you are finished defining the Team Charter, on the Enter Team Charter
screen, click the Finish button.
The new RCA Analysis is created and saved, and the Preserve Failure Data page appears.
From the Preserve Failure Data page, you can begin the next step of the RCA Analysis by
creating RCA Preserve Item records and linking them to the RCA Analysis record.
About Equipment, Locations, and RCA

Analyses
You can link Equipment and Functional Location records to an RCA Analysis record. You
should link all Equipment and Functional Location records related to the RCA Analysis
in order to keep a full record of the equipment and locations that are impacted by the
RCA Analysis results.
You can link only Equipment records, only Functional Location records, or both types of
records simultaneously to an RCA Analysis record. Consider the following examples.
1. You want to run an RCA Analysis on a pump, which is always located in the same
place. You link the pump's Equipment record to the RCA Analysis record.
2. You want to run an RCA Analysis on an incident that occurred at a specific plant
and you aren't sure which pump was involved. You link the plant's Functional
Location record to the RCA Analysis record.
3. You want to run an RCA Analysis on a pump that was previously located in
another plant and has been installed in a new plant. You link both the pump's
Equipment record (which is already linked to the new plant's Functional Location
record) and the old plant's Functional Location record to the RCA Analysis
record.
4. You want to run an RCA Analysis involving multiple pumps that are all
experiencing similar failures. You link multiple Equipment records to the same
RCA Analysis record.
You can link Equipment or Functional Location records to the RCA Analysis record when
you complete the initial steps required for an RCA Analysis, or you can link Equipment
or Functional Location records to an existing RCA Analysis record via the Manage
Assets page.
For existing RCA Analysis records, Equipment or Functional Location records can be
managed from the Manage Assets page, where you can:
Link Equipment or Functional Locations records to an RCA Analysis.

View Equipment or Functional Location records that are currently linked to an
RCA Analysis.
Unlink Equipment or Functional Location records from an RCA Analysis.
Accessing the Manage Assets Page

To access the Manage Assets page:
On the Analysis page, on the Manage Assets menu, click the Manage Assets link.
The Manage Assets page appears, displaying a list of Equipment or Functional Location
records that have been linked to the RCA Analysis record for the current analysis.
Aspects of the Manage Assets Page

The Manage Assets page displays a list of Equipment and Functional Location records
that are linked to the RCA Analysis record associated with the current RCA Analysis.
The grid on the Manage Assets page contains the Record ID and family of each record
that is linked to the RCA Analysis record. For Equipment records, the Record ID column
is populated with the Record ID of the linked Equipment record, and the Family column
is populated with Equipment. For Functional Location records, the Record ID column is
populated with the Record ID of the linked Functional Location record, and the Family
column is populated with Functional Location. By default, linked records will be listed
alphabetically, first by the Family column, and then by the Record ID column.
The Manage Assets page contains the following task menus:
Manage Assets
Common Tasks
PReserve
Order
Analyze
Communicate
Track
Manage Assets Menu

The Manage Assets menu on the Manage Assets page contains the following link:
Manage Assets: Displays the Manage Assets page, where you can link, view, and
unlink Equipment and Functional Location records associated with the current
RCA analysis.
Common Tasks Menu

The Common Tasks menu on the Manage Assets page contains the following links:
Link to Assets: Displays the Asset Finder window, where you can search for the
Equipment or Functional Location records that you want to link to the RCA
Analysis record.
View Linked Assets: Displays the selected Equipment or Functional Location
records in the Record Manager. This link is enabled only if the current RCA
Analysis is already linked to an Equipment or Functional Location record.
Unlink Assets: Displays a confirmation message, asking if you really want to

unlink the selected Equipment or Functional Location records from the current
RCA Analysis and then deletes the link between the RCA Analysis record and the
Equipment or Functional Location records. This link is enabled only if the current
RCA Analysis is already linked to an Equipment or Functional Location record.
Send To: Displays a submenu of options that let you provide a link to the current
page on your desktop (create shortcut), in email message, or on a Home Page.
Help: Displays the context sensitive help topic for the Manage Assets page.
PReserve Menu
The PReserve menu on the Manage Assets page contains the following link:
Preserve Records: Displays the Preserve Failure Data page, where you can view
and manage RCA Preserve Item records for the current RCA Analysis.
Order Menu
The Order menu on the Manage Assets page contains the following links:
Critical Success Factors: Displays the Critical Success Factors page.

Team Charter: Displays the Team Charter dialog box, where you can view and
modify the Team Charter.
Team: Displays the Team page, where you can view and manage Human Resource
records for the members of the RCA Analysis Team.
Analyze Menu
The Analyze menu on the Manage Assets page contains the following links:
Event Diagram: Displays the Event Diagram page, where you can view and
modify the Event Diagram for the current RCA Analysis.
Logic Tree: Displays the Logic Tree page, where you can view and modify the
Logic Tree for the current RCA Analysis.
Communicate Menu
The Communicate menu on the Manage Assets page contains the following links:
Communicate Records: Displays the Communicate Records page, where you can
view, modify, and send Communicate records and RCA Recommendation records.
Reports: Displays the Reports List page, where you can view and manage reports
based on the data from the current RCA Analysis.
Track Menu
The Track menu on the Manage Assets page contains the following link:
Track: Displays the Analysis Tracking Items page, where you can view and
manage the RCA Tracking Item records for the current RCA Analysis.
Linking Equipment and Functional

Location Records to RCA Analysis
Records
The following instructions provide details on linking an Equipment or Functional
Location record to an existing RCA Analysis record.
To link an Equipment record or Functional Location record to an existing RCA Analysis
record:
1. Access the Manage Assets page.
2. On the Common Tasks menu, click the Link to Assets link.
The Asset Finder window appears.
3. Perform a search to find the Equipment or Functional Location record you want to
link to the RCA Analysis record.
4. In the search results list, select the Equipment or Functional Location records that
you want to link to the RCA Analysis record.
5. Click the Select button.
The Asset Finder window closes, and the selected Equipment or Functional Location
records appear on the Manage Assets page and are now linked to the RCA Analysis
record.
Opening Equipment and Functional

Location Records Linked to RCA
Analysis Records
To open the Equipment or Functional Location records that are currently linked to an
RCA Analysis:
2. In the grid, select the rows containing the Equipment or Functional Location
records that you want to open.
Hint: Alternatively, if you only want to open one Equipment or Functional Location
record, you can click the hyperlinked Record ID of the record you want to view.
3. On the Common Tasks menu, click the View Linked Assets link.
The Record Manager appears, displaying the selected Equipment and Functional
Location records.
If you selected more than one record, multiple records will appear in Record Manager.
The first record that you selected in the grid on the Manage Assets page will be expanded
in the Record Explorer pane and displayed in the datasheet area. The rest of the records
appear collapsed in the Record Explorer pane.
Unlinking Equipment or Functional

Location Records from RCA Analysis
Records
To unlink an Equipment or Functional Location record from an RCA Analysis record:
2. Select the Equipment and Functional Location records you want to unlink from
the analysis by selecting one or more rows in the Manage Assets grid.
3. On the Common Tasks menu, click the Unlink Assets link.
A confirmation message appears, asking if you really want to delete the link.
4. Click OK.
The links between the selected Equipment and Functional Location records and the RCA
analysis record are deleted, and the Equipment and Functional Location records no longer
appear in the list on the Manage Assets page.
About CSFs
Critical Success Factors (CSFs) are elements of an RCA Analysis that allow the analysis
team to evaluate whether or not the analysis effort has been successful. The RCA
Analysis effort is considered to be successful if the analysis team adheres to and meets
the standards defined by the CSFs.
RCA uses two types of CSFs.
Default CSFs: RCA Critical Success Factors that are available for use in all RCA
Analyses. Default CSFs are stored as system preferences and appear on the
Administrative Functions page and in the New Analysis Builder. Default CSFs are
not stored in a record until they are added to an RCA Analysis. When a Default
CSF is added, a new RCA Critical Success Factor record is created and populated
automatically with the Default CSF text, then linked to the RCA Analysis record.
Custom CSFs: RCA Critical Success Factor records that are linked to a specific
RCA Analysis record. When Custom CSFs are created for an RCA Analysis, a
new RCA Critical Success Factor record is created and linked to the RCA
Analysis record.
A baseline set of Default CSFs is provided with the RCA module and appear on the
Administrative Functions page, where an administrative user can modify them and define
their own Default CSFs. All Default CSFs (baseline and custom) will be available for
selection in the New Analysis Builder when you create an RCA Analysis.
Additionally, you can define Custom CSFs for each RCA Analysis. Custom CSFs are
defined for a single RCA Analysis and stored in RCA Critical Success Factor records.
You can define custom CSFs via the New Analysis Builder and the Critical Success
Factors page.
All RCA Critical Success Factor records for the current RCA Analysis are displayed on
the Critical Success Factor page. An RCA Critical Success Factor record exists for each
CSF that is linked to an RCA Analysis record.
Accessing the Critical Success Factors

Page
To access the Critical Success Factors page:
On the Analysis page, on the Order menu, click the Critical Success Factors link.
The Critical Success Factors page appears, displaying a list of CSFs that have been
created for the current RCA Analysis.
Aspects of the Critical Success Factors

Page
The Critical Success Factors page displays a list of Critical Success Factors that have
been created for the current RCA Analysis.
The Critical Success Factors page contains the following task menus:
Manage Assets
Common Tasks
PReserve
Order
Analyze
Communicate
Track
Manage Assets Menu

The Manage Assets menu on the Critical Success Factors page contains the following
link:
RCA analysis.
Common Tasks Menu

The Common Tasks menu on the Critical Success Factors page contains the following
links:
New CSF: Displays the CSF Details page, where you can create a new RCA
Critical Success Factor record.
Edit CSF: Displays the CSF Details page, where you can modify the selected
RCA Critical Success Factor record.
Delete CSF: After displaying a confirmation message, deletes the selected RCA
Critical Success Factor record.
Spell Check: Displays the Spell Check dialog box, which allows you to perform a
spell check operation on the text and character fields in records belonging to the
current RCA Analysis.
Help: Displays the context sensitive help topic for the Critical Success Factors
page.
PReserve Menu
The PReserve menu on the Critical Success Factors page contains the following link:
Order Menu
The Order menu on the Critical Success Factors page contains the following links:
Critical Success Factors: Displays the Critical Success Factors page. This link is
available on other pages in Root Cause Analysis.
records for the members of the RCA Analysis Team.
Analyze Menu
The Analyze menu on the Critical Success Factors page contains the following links:
Communicate Menu
The Communicate menu on the Critical Success Factors page contains the following
links:
Track Menu
The Track menu on the Critical Success Factors page contains the following link:
Creating a New RCA Critical Success

Factor Record
The following instructions provide information on creating a new RCA Critical Success
Factor record from the Critical Success Factors page.
To create a new RCA Critical Success Factor record for an RCA Analysis:
1. On the Critical Success Factors page, on the Common Tasks menu, click the New
CSF link.
The CSF Details page appears, displaying a new RCA Critical Success Factor record.
2. In the Value(s) column, type the details of the CSF, or click the
button to
enter the details using the Text Editor, which is shown in the following image.
3. On the Common Tasks menu, click the Save CSF link.
The RCA Critical Success Factor record is created and linked automatically to the RCA
Analysis record for the current RCA Analysis, and the Critical Success Factors page
appears.
Viewing or Modifying the Details of a

Critical Success Factor
To view or modify the details of a CSF:
1. On the Critical Success Factors page, in the list of RCA Critical Success Factor
records, click the hyperlink for the record whose details you want to view or
modify.
The CSF Details page appears, displaying the details of the selected CSF.
2. In the Value(s) column, modify the text as desired. You can click the
button
to modify the text using the Text Editor, which is shown in the following image.
3. On the Common Tasks menu, click the Save CSF link.

Your changes are saved, and the Critical Success Factors page appears.
Deleting Critical Success Factors

To remove a Critical Success Factor from the RCA Analysis:
1. On the Critical Success Factors page, in the Critical Success Factors list, select
the row containing the CSF that you want to delete.
2. On the Common Tasks menu, click the Delete CSF link.

A confirmation message appears, asking if you really want to delete the CSF.
The CSF is removed from the RCA Analysis, the link between the RCA Critical Success
Factor record and the RCA Analysis record is removed, and the CSF no longer appears in
the list on the Critical Success Factors page.
About the Team Charter

The Team Charter defines the goal that the RCA Analysis Team wants to achieve by
developing an RCA Analysis. The baseline RCA module contains a default Team Charter
that you can modify and use as desired. An administrative user will specify the default
Team Charter that can be accessed in the New Analysis Builder when you create the RCA
Analysis. You can modify the default Team Charter as desired.
After you have defined a Team Charter for the RCA Analysis, you can view and modify it
via the Order menu on most pages in Root Cause Analysis by clicking the Team Charter
link.
Modifying the Team Charter

The following instructions provide details on modifying the Team Charter for an RCA
Analysis.
To modify the Team Charter for an RCA Analysis:
1. On the Analysis page, on the Order menu, click the Team Charter link.
The Team Charter dialog box appears, displaying the current Team Charter. If the Team
Charter was not modified when the initial steps required for an RCA Analysis were
completed, the default text will be displayed in the text box.
2. Modify the existing text or type new text as desired.

Your changes are saved, and the Team Charter dialog box closes.
About the RCA Analysis Team

The RCA Analysis Team is the group of individuals who will complete the steps required
for a comprehensive RCA Analysis. Security permissions in Root Cause Analysis are
based upon family-level privileges and a user's role within a given RCA Analysis. Root
Cause Analysis users who are members of the RCA Analysis Team will have one of the
following RCA Analysis team member roles:
Principal Analyst: The user who is responsible for facilitating and coordinating
the RCA Analysis.
Analysis Team Member: Any user who is a member of an RCA Analysis Team.
When you add new members to the RCA Analysis Team, an RCA Team Member record
is created automatically and linked to the RCA Analysis record and the individual's
Human Resource record. If the same team member is linked to multiple analyses, an
RCA Team Member record will exist for each RCA Analysis team in which they are a
member. The RCA Team Member record stores the RCA Analysis Team member's role
(i.e., Team Member or Principal Analyst). A given team member's role determines the
security privileges that the user has in Root Cause Analysis.
You can add Meridium APM users and non-Meridium APM users to the RCA Analysis
Team.
Meridium APM users will have an existing Meridium APM Security User account
and an associated Human Resource record that is created automatically when the
Security User account is created.
Non-Meridium APM users will not have a Meridium APM Security User account.
To add a non-Meridium APM user to the RCA Analysis Team, you first need to
create a Human Resource record for that user. You can do so via the Team page in
Root Cause Analysis or using Meridium APM Framework Tools.
Note: A Meridium APM Security User record is required for logging in to the Meridium
APM Framework application and using Root Cause Analysis. RCA Analysis team
members who do not have a Security User account may participate in and contribute to
the analysis but will not be able to use the application.
After you add a new team member to the RCA Analysis Team, that user will inherit the
security privileges associated with the user's team member role (e.g., Principal Analyst).
Accessing the Team Page

You can access the Team page via the Order menu on any of the following pages:
Analysis page
Preserve Failure Data page
Preserve Record Details page
Critical Success Factors page
Event Diagram page
Logic Tree page
To access the Team page:
On the Order menu, click the Team link.
The Team page appears, displaying a list of the users who are members of the RCA
Analysis Team for the current RCA Analysis.
Aspects of the Team Page

The Team page displays a list of all the members of the RCA Analysis Team for the
The values that appear in each column on the Team page are stored in the team member's
Human Resource record and RCA Team Member record. The following information
appears for each team member in the list:
Name: The name of the team member. This value is stored in the Human
Resource record.
Security Privilege: The role assigned to the team member. The team member who
is the Principal Analyst is assigned Principal security privileges. All other team
members are assigned Member security privileges. This value is stored in the
RCA Team Member record.
Title: The job title of the team member. This value is stored in the Human
Resource record.
Facility Name: The name of the facility that the team member represents. This
value is stored in the Human Resource record.
Business Unit: The business unit within the facility that the team member
represents. This value is stored in the Human Resource record.
Phone No.: The phone number for the team member. This value is stored in the
Human Resource record.
E-mail Address: The email address for the team member. This value is stored in
the Human Resource record.
Note: You can customize the display of the team member grid in several ways including,
adding additional columns, sorting columns, and filtering the list.
On the Team page, you can:
View and modify the contents of team members' Human Resource records.
Add new team members to the RCA Analysis Team.
Delete team members.
The Team page contains the following task menus:
Manage Assets
Common Tasks
Manage Human Resources
PReserve
Order
Analyze
Communicate
Track
Associated Pages
Note: Items appear on the Associated Pages menu only if Associated Pages have been
configured for the RCA Analysis family.
Manage Assets Menu

The Manage Assets menu on the Team page contains the following link:
RCA analysis.
Common Tasks Menu

The Common Tasks menu on the Team page contains the following links:
New Team Member: Displays the Find Team Member window, where you can
search the Human Resource family for the record associated with the user that
you want to add as a new team member. This link is enabled only if you are a
member of the MI PROACT Administrator Security Group, a Super User, or the
Principal Analyst for the current RCA Analysis.
Delete Team Member: Removes the selected RCA Analysis Team member from
the RCA Analysis Team after displaying a confirmation message. This link is
enabled only if the row containing a team member's name is selected and you are
a member of the MI PROACT Administrator Security Group, a Super User, or the
Principal Analyst for the current RCA Analysis.
Change Principal Analyst: Changes the selected user to the Principal Analyst role
after displaying a confirmation message. This link is enabled only if a row
containing a team member's name is selected and you are a member of the MI
PROACT Administrator Security Group, a Super User, or the Principal Analyst
for the current RCA Analysis.
Help: Displays the context-sensitive help topic for the Team page.
Manage Human Resources Menu
The Manage Human Resources menu on the Team page contains the following links:
Edit Selected User: Displays the User Details page, where you can view and
modify the Human Resource record associated with the selected team member.
This link is enabled only if a row containing a team member's name is selected
and you are a member of the MI PROACT Administrator Security Group, a Super
User, or the Principal Analyst for the current RCA Analysis.
New User: Displays the User Details page, where you can define a Human
Resource record for a non-Meridium APM user and add them to the RCA
Analysis Team. This link is enabled only if you are a member of the MI PROACT
Administrator Security Group, a Super User, or the Principal Analyst for the
PReserve Menu
The PReserve menu on the Team page contains the following link:
Order Menu
The Order menu on the Team page consists of the following links:
Critical Success Factors: Displays the Critical Success Factors page.

records for the members of the RCA Analysis Team. This link is available on
other pages in Root Cause Analysis.
Analyze Menu
The Analyze menu on the Team page contains the following links:
Communicate Menu
The Communicate menu on the Team page contains the following links:
Track Menu
The Track menu on the Team page contains the following link:
About Adding New Team Members to

the RCA Analysis Team
Two options appear on the Team page that let you add a new member to the RCA
Analysis Team:
New Team Member: Use this option if you want to add to the RCA Analysis Team
a user who already has a Human Resource record. This option appears as a link on
the Common Tasks menu.
New User: Use this option if you want to add to the RCA Analysis Team a user
who does not have an existing Human Resource record. This option appears as a
link on the Manage Human Resources menu.
Note: If a Team Member will need to perform tasks within the RCA module, in addition
to the Human Resource record, the Team Member must also have a Security User record.
Using the Meridium APM Framework, you can promote a Human Resource record to a
Security User record.
Adding Team Members Who Already

Have Human Resource Records
The following instructions provide details on adding a person to the RCA Analysis Team
who already has a Human Resource record. If the person who you want to add to the
RCA Analysis Team does not have a Human Resource record, you will need to create the
Human Resource record and automatically add the person to the RCA Analysis Team.
Note: A given Human Resource record can be added to the RCA Analysis Team only
once.
To add a person to the RCA Analysis Team who already has a Human Resource record:
1. Access the Team page.
The Team page appears, displaying a list of existing team members.
2. On the Common Tasks menu, click the New Team Member link.
The Find Team Member window appears. The Search In list contains the Human
Resource family by default and cannot be changed.
3. Perform a search in the Human Resources family to locate the desired team
member.
The search results appear.
4. In the results list, select the row containing the desired team member, and then
The selected person is added to the list of team members. An RCA Team Member record
is created for that user automatically and linked to that user's Human Resource record and
to the RCA Analysis record for the current RCA Analysis.
Note: A given Human Resource record cannot be added to the RCA Analysis Team more
than once. If you try to add a team member who is already listed on the Team page, a
message appears, indicating that the person is already a member of the RCA Analysis
Team.
Creating New Users and adding them to

the Analysis Team
A person who does not have a Human Resource record can be added to an RCA Analysis
Team, provided that you create a new Human Resource record for that person. The
following instructions provide details on creating a Human Resource record and
automatically adding the person to the RCA Analysis Team.
To create a new Human Resource record and add it to the RCA Analysis Team
automatically:
1. On the Team page, on the Manage Human Resources menu, click the New User
link.
The User Details page appears, displaying the MI Human Resource datasheet.
2. In the Last Name field, type the last name of the team member. This field is
required.
3. Complete the remaining fields on the datasheet as desired.
4. On the Common Tasks menu, click the Save User link.
The new Human Resource record is saved, the Team page appears, displaying that person
in the list of team members for the current RCA Analysis, and an associated RCA Team
Member record is created for that user automatically and linked to that user's Human
Resource record and the RCA Analysis record for the current RCA Analysis.
Viewing the Human Resource Record

for Existing Team Members
Only members of the MI PROACT Team Member Security Group or MI PROACT
Administrator Security Group can view the contents of Human Resource records.
To view the Human Resource record for an existing team member:
On the Team page, in the list of team members, click the hyperlink associated
with the team member whose Human Resource record you want to view.
The Proact page appears, displaying the Human Resource record for the selected team
member. The fields are read-only.
Modifying Human Resource Records for

Existing Team Members
Only Members MI PROACT Administrator Security Group, Super Users, or the Principal
Analyst can modify the contents of a Human Resource record.
To modify the Human Resource record for a team member:
1. On the Team page, select the row containing the team member whose Human
Resource record you want to modify.
On the Manage Human Resources menu, click the Edit Selected User link.
The User Details page appears, displaying the Human Resource record for the selected
team member.
2. Modify the fields as needed.

3. On the Common Tasks menu, click the Save User link.
Your changes are saved, and the Team page appears.

Note: If you modify the Last Name, First Name, or Middle Initial field, after you save the
record, your changes will not be displayed in the grid on the Team page immediately.
Your changes ARE saved in the Human Resource record. The next time that you access
the Team page or the Human Resource record for the user, you will see your changes.
Changing the Principal Analyst

To change the Principal Analyst for an RCA Analysis, you must be a Super User, a
member of the MI PROACT Administrator Security Group, or the existing Principal
Analyst.
To change the Principal Analyst for a RCA Analysis:
1. On the Team page, select the row containing the team member that want to make
the new Principal Analyst.
2. On the Common Tasks menu, click the Change Principal Analyst link.
A message appears, asking if you really want the selected team member to become the
new Principal Analyst.
The user's RCA Team Member record and the value in the Security Privilege column is
updated to reflect the change.
Deleting Team Members from the

Analysis
The following instructions provide details on deleting a team member from an RCA
Analysis Team. When you delete a team member from the RCA Analysis Team, you are
deleting the associated RCA Team Member record only. The associated Human Resource
record is not deleted.
If a team member is linked to one or more RCA Preserve Item records, RCA
Verifications, or RCA Recommendation records, when the team member is deleted from
the RCA Analysis Team, the items that were previously assigned to that team member
will appear on the PA PROACT page for the Principal Analyst to re-assign to other team
members.
To delete a team member from the RCA Analysis Team:
1. On the Team page, select the row containing the team member that you want to
delete.
2. On the Common Tasks menu, click the Delete Team Member link.
A message appears, asking if you really want to delete the team member.
The team member is deleted from the RCA Analysis Team.
About Preserving Failure Data

In an RCA Analysis, preserving failure data involves collecting a wide range of
information related to the equipment or location failure that the team will analyze. The
collected data is stored in RCA Preserve Item records, which contain task-related data for
the collection of the failure data. In this way, RCA Preserve Item records are essentially
tasks assigned to the team member who should collect the failure data specified in the
record by a certain date. For example, an RCA Preserve Item record may contain a task to
collect all the broken pieces of a piece of equipment.
Using the Preserve Failure Data page, you can create new RCA Preserve Item records
or modify existing RCA Preserve Item records for the current RCA Analysis. After the
tasks defined in the RCA Preserve Item records are complete, the team can begin to
analyze the data that was collected.
The 5 P's
When you create a RCA Preserve Item record, the type of data that you want a member of
the RCA Analysis Team to collect is identified by one of the following categories, known
as the 5 P's:
People: Indicates that human witnesses should be questioned about the incident.
Witnesses might include the person who is responsible for the maintenance of the
piece of equipment or location associated with the failure event, the operator, or
even the stock room attendant.
Parts: Indicates that physical pieces of the equipment should be collected (i.e., the
broken pieces). This may also include collecting a functional piece of equipment
to test against the broken one.
Paper: Indicates that any data or information that exists about the piece of
equipment or location should be gathered. This could include recent performance
reports, schedules, Meridium APM data, specifications, and so on.
Position: Indicates that the environment in which the piece of equipment or

location exists should be documented and considered. This could include, for
example, the temperature of the room at the time of the incident or the proximity
of one piece of equipment or location to another.
Paradigms: Indicates that any trends or common assumptions about the cause of
the incident should be noted. The intent of noting these paradigms is to remove
this assumption from the investigation (i.e., remove any bias from the analysis).
On the RCA Preserve Failure Data Item datasheet, in the Data Category box, you can
type or select one of the 5 P's. The following image shows the list of the of the 5 P's. A
red outline has been added to the image to highlight these values.
Accessing the Preserve Failure Data

Page
To access the Preserve Failure Data page:
On the Analysis page, on the PReserve menu, click the Preserve Records link.
The Preserve Failure Data page appears, displaying a list of the RCA Preserve Item
records that are associated with the current RCA Analysis.
From the Preserve Failure Data page, you can click a link to view the details for any
RCA Preserve Item record. If no RCA Preserve Item records have been created for the
current RCA Analysis, a message is displayed, indicating that there are no RCA Preserve
Item records associated with the current RCA Analysis.
Aspects of the Preserve Failure Data

Page
The Preserve Failure Data page displays a list of the RCA Preserve Item records that
exist for a given RCA Analysis.
For each RCA Preserve Item record, the following information appears:
Data To Collect: A specific description of the data that should be collected, as

specified in the Data Category column. Each description listed in the Data to
Collect column is a hyperlink that you can click to view the RCA Preserve Item
record on the Preserve Failure Details page.
Data Category: The type of data that should be collected about the problem that
you want to analyze: People, Parts, Paper, Position, or Paradigms.
Collection Strategy: A description of the way in which the data should be

collected (e.g., acquire production logs from a line supervisor).
Date Due: The deadline for collecting the failure data.
Date Completed: The date when the data collection was completed.
Team Member: The team member responsible for completing the task specified in
the RCA Preserve Item record.
On the Preserve Failure Data page, you can perform tasks related to the RCA Analysis
by using the options available on the task menus: Manage Assets, Common Tasks,
PReserve, Order, Analyze, Communicate, Track, and Associated Pages.
Note: If one or more RCA Preserve Item records exits for the RCA Analysis, the
Associated Pages menu displays items that have been configured for the RCA Preserve
Item family via the URL Manager. If no items have been configured or if items have been
configured but an RCA Preserve Item record does not exist, the Associated Pages menu
will be empty.
Manage Assets Menu

The Manage Assets menu on the Preserve Failure Data page contains the following link:
RCA analysis.
Common Tasks Menu

The Common Tasks menu on the Preserve Failure Data page contains the following
links:
New Record: Displays the Preserve Record Details page, where you can create an
RCA Preserve Item record.
Copy Record: Copies the selected RCA Preserve Item record.
Edit Record: Displays the Preserve Record Details page, where you can modify
the selected RCA Preserve Item record.
Delete Record: Displays a confirmation message, asking if you really want to

delete the record, and then deletes the selected RCA Preserve Item record.
Send Record: Allows you to send a link to the selected RCA Preserve Item record
to an email recipient.
Send To: Displays a submenu with options that let you send a link to the current
page to your desktop (create shortcut), an email recipient, or a Home Page.
Help: Displays the context-sensitive Help topic for the Preserve Failure Data
page.
PReserve Menu
The PReserve menu on the Preserve Failure Data page contains the following link:
Preserve Records: Displays the Preserve Failure Data page, which lists existing
RCA Preserve Item records for the current RCA Analysis.
Order Menu
The Order menu on the Preserve Failure Data page contains the following links:
Critical Success Factors: Displays the Critical Success Factors page, which
displays existing RCA Critical Success Factor records that are linked to the
Team Charter: Displays the Team Charter dialog box, which contains the Team
Charter for the current RCA Analysis.
Team: Displays the list of Team page, where you can view the RCA Team
Members records that are linked to the current RCA Analysis.
Analyze Menu
The Analyze menu on the Preserve Failure Data page contains the following links:
Event Diagram: Displays the Event Diagram page for the current RCA Analysis.
If this is the first time that you have accessed the Event Diagram page for the
current RCA Analysis, the RCA Event dialog box will appear automatically so that
you can define the failure event.
Logic Tree: Displays the Logic Tree page for the current RCA Analysis, where
you can organize the process of analyzing the issue to evaluate the root cause of
the failure event. If this is the first time that you have accessed the Logic Tree
page for the current RCA Analysis, the RCA Event dialog box will appear
automatically so that you can define the failure event for the current RCA
Analysis.
Communicate Menu
The Communicate menu on the Preserve Failure Data page contains the following links:
Communicate Records: Displays the Communicate Records page for the current
RCA Analysis, where you can create RCA Recommendation records that are
linked to it.
Reports: Displays the Reports List page, where you can view a list of reports that
have been configured for Root Cause Analysis.
Track Menu
The Track menu on the Preserve Failure Data page contains the following link:
Track: Displays the Analysis Tracking Items page, where you can view, modify,
and create RCA Tracking Item records that are linked to the current RCA
Analysis.
Accessing the Preserve Record Details

Page
The Preserve Record Details page lest you view the details of an RCA Preserve Item
record. You can access the Preserve Record Details page via the following methods:
Create a new RCA Preserve Item record.
Open an existing RCA Preserve Item record.
-or-
Aspects of the Preserve Record Details

Page
The Preserve Record Details page displays the contents of a single RCA Preserve Item
record on the RCA Preserve Failure Data Item datasheet.
Above the datasheet, the Assign To list appears and contains the names of the users who
are currently assigned to the RCA Analysis Team. You can select a name from the list to
assign this person as the owner of the task that is defined in the RCA Preserve Item
record.
The following image shows what the Preserve Record Details page looks like after you
create a new RCA Preserve Item record.
The Preserve Record Details page contains the same task menus that appear on the
Preserve Failure Data page. The Common Tasks menu, however, contains different links.
Common Tasks Menu

The Common Tasks menu on the Preserve Record Details page contains the following
links:
Save Record: Saves the current record.

current page on your desktop (create shortcut), in email message, or on a Home
Page.
Help: Displays the context-sensitive Help topic for the Preserve Record Details
page.
Creating a New RCA Preserve Item

Record
Any team member can create an RCA Preserve Item record for a given RCA Analysis.
You can create a new RCA Preserve Item record from scratch, as described in the
following instructions, or you can copy an existing RCA Preserve Item record to create a
new record.
You can create multiple RCA Preserve Item records for one RCA Analysis using different
data categories. You can use the 5 P's in the Data Category list to categorize the type of
data that should be collected.
To create an RCA Preserve Item record for an RCA Analysis:
1. On the Preserve Failure Data page, on the Common Tasks menu, click the New
Record link.
The Preserve Record Details page appears.
2. In the Assign To list, select the team member to whom the task will be assigned.
3. Complete the details of the RCA Preserve Item record as desired.
4. On the Common Tasks menu, click the Save Record link.
The RCA Preserve Item record is saved, and the Preserve Failure Data page appears.
Modifying Existing RCA Preserve Item

Records
Only the Principal Analyst and members of the RCA Analysis Team can modify RCA
Preserve Item records that belong to a given RCA Analysis.
To modify an existing RCA Preserve Item record:
1. On the Preserve Failure Data page, in the Data to Collect cell, click the hyperlink
for the RCA Preserve Item record that you want to modify.
2. Modify the details of the RCA Preserve Item record as desired.

The RCA Preserve Item record is updated and saved, and the Preserve Failure Data page
appears.
Linking Reference Document Records to

Existing Preserve Item Records
If desired, you can link additional information to an RCA Preserve Item record. For
example, if the data category for the RCA Preserve Item record is Paper, you may want
to link the associated reference documents to the record. You can do so by linking
Reference Document records to RCA Preserve Item records.
Note: You cannot link a Reference Document record to an RCA Preserve Item record
when it is first created. The reference documents icon is enabled only after you have
saved the RCA Preserve Item record.
To link a Reference Document record to an RCA Preserve Item record:
1. Access the RCA Preserve Item record to which you want to link a Reference
Document record.
The Preserve Record Details page appears, displaying the details of the selected record.
2. At the top of the datasheet, click the reference documents icon.

The standard Reference Documents window appears.
3. Add the desired Reference Document records to the RCA Preserve Item record.
The Preserve Record Details page returns to focus.
Copying an RCA Preserve Item Record

to Create a New Record
When you copy an existing RCA Preserve Item record, a new Preserve Item record is
created and populated automatically with data from the source record. Only the Principal
Analyst and members of the RCA Analysis Team can copy an RCA Preserve Item record
for an RCA Analysis for which they are a member of the RCA Analysis Team.
To create a new RCA Preserve Item record by copying an existing one:
1. On the Preserve Failure Data page, select the row containing the record that you
want to copy.
2. On the Common Tasks menu, click the Copy Record link.
The Preserve Record Details page appears, displaying a copy of the RCA Preserve Item
record you selected. The values in all fields are populated automatically with data from
the source record.
3. Modify the fields on the RCA Preserve Failure Data Item datasheet as needed.
The RCA Preserve Item record is saved to the database and linked to the RCA Analysis
record for the current RCA Analysis. The Preserve Failure Data page appears, displaying
the record in the Preserve Failure Data list.
Deleting an RCA Preserve Item Record

Only the Principal Analyst and members of the RCA Analysis Team can delete a RCA
Preserve Item record from a given RCA Analysis.
To delete an RCA Preserve Item record:
1. On the Preserve Failure Data page, select the row containing the record that you
want to delete.
1. On the Common Tasks menu, click the Delete Record link.

A confirmation message appears, asking if you really want to delete the record.
The record is removed from the Preserve Failure Data list and is deleted from the
database.
About Analyzing Data

In an RCA Analysis, analyzing data involves compiling the information that has been
collected thus far in the RCA Analysis and representing it visually in order to facilitate
discussion. Event Diagrams and Logic Trees let you represent visually the events that are
associated with an piece of equipment's or location's failure and the cause-and-effect
relationships that may have led to a failure event.
You can create an Event Diagram on the Event Diagram page and a Logic Tree on the
Logic Tree page. In both diagrams, you can add nodes to the Failure Event node that
represent components of the RCA Analysis. For example, if you define the Failure Event
node as a fire, in the Event Diagram you can add to the Failure Event node upstream
nodes that depict the chain of events that preceded the failure event. Additionally, in the
Logic Tree, you would add to the Failure Event node downstream nodes that represent all
the possible causes for the failure event.
What is a Failure Event?

The failure event is a short description of the problem that you and your team are
analyzing. Your team could be analyzing a failure event that is comprised of several
failures over a specified period of time, or one failure (e.g., a larger event, such as a fire).
The first time that you access the Event Diagram page or the Logic Tree page for a given
RCA Analysis, you will be prompted to define the failure event in an RCA Event record,
which will be used as the Failure Event node. The following image shows an example of
a completed RCA Event record.
Each RCA Analysis will have one Failure Event node, which will always appear at the
root level of the Logic Tree hierarchy and as the first node in the Event Diagram. For
example, the following image shows the Failure Event node as it appears in the Logic
Tree in our Cooling Water Pump example.
You cannot remove the Failure Event node from the Logic Tree or the Event Diagram.
You can modify the RCA Event record, if desired.
What's the Difference Between an Event

Diagram and a Logic Tree?
The following image shows an Event Diagram that was created using the Event Diagram
page. The Event Diagram can depict the cause-and-effect of events that led to the failure
event and post-failure activities. In other words, the Event Diagram provides a way for
the RCA Analysis Team to view and organize the chain of events prior to the failure event
and identify possible work process issues.
The following image shows a Logic Tree that was created using options on the Logic
Tree page. The Logic Tree can depict, starting with the failure event, possible causes and
hypotheses related to the event itself. In other words, the Logic Tree provides a way for
the RCA Analysis Team to organize and record discussion points on the possible causes
of the failure event.
Overview of the Event Diagram and

Logic Tree Data Model
An Event Diagram and a Logic Tree consist of an RCA Event record and all the records
that are linked to it directly or indirectly. For example, after you define the failure event,
you can create RCA Failure Mode records to link to the RCA Event record, and then you
can link RCA Hypothesis records to the RCA Failure Mode records, and so on.
The following image shows the entity families and relationship families that are used to
create an Event Diagram and a Logic Tree in Root Cause Analysis. The Logic Tree and
the Event Diagram share an RCA Event record. The RCA Sequence Node family is used
only by the Event Diagram. All of the other families are used by the Logic Tree.
Records in the RCA Logic Gate family can be linked to other records in the RCA Logic
Gate family. Additionally, records in the RCA Sequence Node family can be linked to
other records in the RCA Sequence Node family.
In addition to the relationships that appear in the image, records in the following families
can be linked to records in the RCA Reference Document family through a relationship
definition on the Has Reference Documents family:
RCA Event
RCA Hypothesis
RCA Logic Gate
Defining the Failure Event
The first time that you access the Event Diagram page or the Logic Tree page for a given
RCA Analysis, the RCA Event dialog box will appear, where you can create an RCA
Event record. When you create an RCA Event record, you are also defining the associated
Failure Event node. After you create a Failure Event node, you cannot delete it via Root
Cause Analysis, but you can modify the RCA Event record, if necessary. Only one RCA
Event record can be defined for each RCA Analysis.
Note: If you previously accessed the Logic Tree page or the Event Diagram page and
defined a Failure Event node, you will not see the RCA Event dialog box prompting you
to define it again. Instead, you will see the Failure Event node in the main display area
(i.e., the design canvas or Logic Tree section). The following instructions assume that this
is your first time accessing the Event Diagram page or the Logic Tree page for the current
RCA Analysis.
To define the failure event for the RCA Analysis:
1. On the Analysis page, on the Analyze menu, click the Event Diagram or Logic
Tree link.
The RCA Event dialog box appears.
3. Populate the fields on RCA Failure Event datasheet as desired.

The RCA Event record is created and linked automatically to the RCA Analysis record
for the current RCA Analysis. The Failure Event node appears in the diagram canvas on
the Event Diagram page or in the Logic Tree section on the Logic Tree page.

Existing Failure Event Records
If desired, you can create a new Reference Document record to link to the Failure Event
record for the current RCA Analysis. You can also search for an existing Reference
Document record and link it to the Failure Event record for the selected RCA Analysis.
The following instructions assume that you want to create a new Reference Document
record.
Note that you will not be able to add a reference document to a Failure Event record upon
creation. The reference document icon is enabled only after you have saved the Failure
Event record.
To link a Reference Document record to the Failure Event record:
1. Access the datasheet for the desired RCA Event record.
At the top of the datasheet, click the reference documents icon.

2. Add the desired Reference Document records to the Failure Event record.
The Reference Documents window closes, and the Event Diagram page returns to focus.
Accessing the Event Diagram Page

About Accessing the Event Diagram Page
You can access the Event Diagram page via the Analyze menu on any of the following
pages:
Analysis page
Event Diagram page
Logic Tree page
If an RCA Event record has already been created and linked to the current RCA Analysis,
the Event Diagram will be displayed on the Event Diagram page, as shown in the
following image.
If an RCA Event record has not yet been created for the current RCA Analysis, the RCA
Event dialog box will appear, prompting you to define information for the failure event.
Note: If the RCA Analysis was created from a Production Event record in the PLA
module, several of the fields in the RCA Event record will be populated automatically
with values from that Production Event record.
Accessing the Event Diagram Page

To access the Event Diagram page:
On the Analyze menu, click the Event Diagram link.
Either the Event Diagram page or the RCA Event dialog box appears, depending upon
whether or not an RCA Event record has been created for the current RCA Analysis.
Aspects of the Event Diagram Page

The Event Diagram page consists of the sections shown in the following image.
Numbered labels have been added to the image to identify the sections on the page.
The Event Diagram page consists of the following sections, as identified by the
numbers in the preceding image:
1. Diagram canvas: An interactive drawing interface upon which you can build a
diagram that represents the order of events that occurred leading up to and
immediately after the failure event. You can right-click the diagram canvas to
display a shortcut menu, containing options that let you modify the way the Event
Diagram page looks.
2. Available Nodes Palette pane: Contains a group of icons that you can use to
diagram the events. You can add nodes from the Available Nodes Palette to the
diagram canvas on the Event Diagram page. When you add any type of node to
the Event Diagram, you are creating an RCA Sequence Node record in the
database and linking it to the RCA Analysis record for the current RCA Analysis.
The RCA Sequence Node record contains information related to the event for
which you are creating the associated node.
You can hide or display the Available Nodes Palette pane via the Event Diagram menu by
clicking the Hide Node Palette or Show Node Palette link, as appropriate. Additionally,
you can reposition the palette by clicking the title bar and dragging it to the desired
location.
Note: When two nodes are connected, a link between the two records is immediately
created within the database. If a node is moved within the diagram, the links between the
records are updated accordingly.
The following table describes the nodes in the Available Nodes Palette section.
This node
Can be used to represent...

A single step or an entire sub-process within a larger
process.
A printed document or report.
Material or information entering or leaving the system,
such as customer order (input) or a product (output).
A decision or branching point.
A step that marks the starting or ending point of the

event.
Hint: The descriptions in this table describe the generic, intended use of these nodes. You
can use the nodes according to the needs of your organization.
3. Selected Node Datasheet section: Displays the contents of the RCA Sequence
Node record for the selected node. The following fields are available in the RCA
Sequence Node record:
Label: A description of the event that the node represents, as you want it to
appear in the Event Diagram.
Long Description: A detailed description of the event. You can click the
button to type the description in the Text Editor.
Event Start Date: The date the event started. You can type or select the
date on which the event started.
Event End Date: The date the event ended. You can type or select the
date on which the event ended.
You can select any node in the diagram to view the associated datasheet for that node.
You can hide or display the Selected Node Datasheet section via the Event Diagram
menu by clicking the Hide Data Sheet or Show Data Sheet link, as appropriate.
Additionally, you can reposition the Selected Node Datasheet section by clicking the title
bar and dragging it to the desired location.
4. Task Menu pane: Displays the Manage Assets menu, Common Tasks menu, the
Event Diagram menu, the PReserve menu, the Order menu, the Analyze menu,
the Communicate menu, and the Track menu, which you can use to navigate
throughout Root Cause Analysis to perform various tasks.
Manage Assets Menu
The Manage Assets menu on the Event Diagram page contains the following link:
RCA analysis.
Common Tasks Menu

The Common Tasks menu on the Event Diagram page contains the following links:
Page.
Help: Displays the context-sensitive Help topic for the Event Diagram page.
Event Diagram Menu
The Event Diagram menu on the Event Diagram page contains the following links:
Export Event Diagram: Displays the Export Event Diagram dialog box, where
you navigate to a location where you can export the current Event Diagram as an
image file.
Full Screen: Maximizes the Meridium APM window and hides the frame around
the diagram canvas (including the task menu pane), and displays only the Event
Diagram, the Selected Node Datasheet pane and the Available Nodes Palette. To
return to the regular view, right-click the diagram canvas, and clear the Full
Screen option.
Hide Data Sheet: Lets you hide the Selected Node Datasheet section. When you
hide the datasheet, a Show Data Sheet link will appear on the Event Diagram
menu in place of the Hide Data Sheet option.
Hide Node Palette: Lets you hide the Available Nodes Palette section. When you
hide the palette, a Show Node Palette link will appear on the Event Diagram
menu in place of Hide Node Palette option.
PReserve Menu
The PReserve menu on the Event Diagram page contains the following link:
Preserve Records: Displays the Preserve Failure Data page, which lists the
existing RCA Preserve Item records that are linked to the current RCA Analysis.
Order Menu
The Order menu on the Event Diagram page contains the following links:
Critical Success Factors: Displays the Critical Success Factors page, which lists
the existing RCA Critical Success Factor records that are linked to the RCA
Analysis record for the current RCA Analysis.
Team Charter: Displays the Team Charter dialog box, which contains the defined
Team Charter for the current RCA Analysis.
Team: Displays the Team page, which lists the RCA Team Member records that
are linked to the RCA Analysis record for the current RCA Analysis.
Analyze Menu
The Analyze menu on the Event Diagram page contains the following links:
Logic Tree: Displays the Logic Tree page for the current RCA Analysis.
Communicate Menu
The Communicate menu on the Event Diagram page contains the following links:
view, modify, and send RCA Analysis records and RCA Recommendation
records.
Track Menu
The Track menu on the Event Diagram page contains the following link:
Track: Displays the Analysis Tracking Items page, where you can add, edit, or
delete RCA Tracking Item records for the current RCA Analysis.
Using the Shortcut Menu in the

Diagram Canvas
To access the shortcut menu in the diagram canvas:
Right-click anywhere in the design canvas.
The shortcut menu appears.
The following options on the shortcut menu let you modify the way the Event Diagram
page appears.
Zoom: Displays a submenu of options that let you change the magnification at
which you are viewing the Event Diagram. When you select a magnification from
the submenu, the design canvas refreshes and displays the Event Diagram at the
specified magnification.
Full Screen: Maximizes the Meridium APM window and hides the frame around
the diagram canvas (including the task menu pane), and displays only the Event
Diagram, the Selected Node Datasheet pane and the Available Nodes Palette.
When this option is selected, a check mark appears to the left of the option. To
return to the regular view, right-click the diagram canvas and clear the Full Screen
option.
Toggle Options: Hides the Selected Node Datasheet pane and the Available Nodes
Palette. To hide this pane individually, you can use the Hide Data Sheet and Hide
Node Palette options on the Event Diagram task menu.
About Creating a New Event Diagram

The Event Diagram page provides tools that you can use to create the Event Diagram: a
visual representation of the events that led up to and immediately followed the failure
event. From the Event Diagram page, you can view and modify an existing Event
Diagram or create a new Event Diagram.
Building the Event Diagram consists of the following steps:
1. Defining the failure event.
2. Adding desired nodes to the Event Diagram.
3. Adding the node connectors to the Event Diagram.
Adding Node to the Event Diagram

To add a node to the Event Diagram:
1. In the Available Nodes Palette section, click the icon that represents the type of
node you want to add, and drag it to the desired location on the diagram canvas.
Note: A plus sign (+) appears next to the pointer to indicate that the new node can be
linked to the existing node.
After you release the mouse button, the RCA Event Diagram dialog box appears,
displaying the RCA Sequence Node datasheet.
2. Provide values in the fields on the datasheet, as needed.

The RCA Sequence Node record is saved and linked automatically to the RCA Analysis
record for the current RCA Analysis, and the associated node appears in the diagram
canvas on the Event Diagram page.
Connecting Sequence Nodes

You can create connections between the nodes in the Event Diagram to establish a
relationship between the nodes. Each node in the diagram canvas has two ports that are
used for connecting nodes to another node. Each port is designated by a circle on the
right and left of the node. You can create as many connections as you need to build the
Event Diagram. More than one connector can be attached to the same port of a node,
allowing you to create parallel events. As you connect the nodes to build the Event
Diagram, links are created between the items using a predecessor-successor relationship
definition that exists between them.
Note: The predecessor is the node that precedes the node that is currently selected in the
Event Diagram. The successor is the node that succeeds the node that is currently selected
in the Event Diagram.
To connect nodes in an Event Diagram:
1. On the Event Diagram page, in the diagram canvas, click the circle on the node
from which you want to initiate the connection, also known as the predecessor
node.
2. Press and hold your mouse button down, and drag your pointer to the port of the
successor node. As you drag your pointer, a line appears.
3. When your pointer touches the port of the successor node, release the mouse
button.
An arrow appears, connecting the two nodes, and a link between the two records is
automatically created.
Viewing and Modifying the Record

Associated with Each Node
To view and modify the record associated with a given node:

1. On the Event Diagram page, In the design canvas, click the node whose datasheet
you want to view.
The associated datasheet appears in the Selected Node Datasheet section at the bottom of
the page, and the selected node is highlighted in green.
2. Modify the record as desired.

3. At the top of the datasheet, click the Save icon.
Cutting, Copying, and Pasting Nodes

After you create various nodes in your Event Diagram, you can cut, copy, and paste them
as needed throughout the Event Diagram. Copying multiple nodes also copies any
connectors between the nodes, as long as the connectors are selected when you perform
the copy function. Cutting a single node in the middle of the Event Diagram also cuts
successor nodes and as any connectors between them.
Hint: If you do not want to cut successor nodes along with a predecessor node, you
should remove the connector between them before cutting the predecessor node.
To cut or copy a node in the Event Diagram:
1. On the Event Diagram page, in the design canvas, right-click the node that you
want to cut or copy, and on the shortcut menu, click the Cut or Copy option.
Note: If you select the Cut option and the node has successor nodes, the successor nodes
will also be cut.
2. Navigate to the area on the Event Diagram canvas that you want to paste the node,
right-click and select the Paste option from the shortcut menu.
The node is pasted to the Event Diagram canvas. If you chose to copy the node, a new
RCA Sequence Node record is created for the pasted node.
Deleting Nodes from the Event Diagram

If desired, you can remove a node from the Event Diagram. When you delete a node from
the Event Diagram, you are deleting the associated RCA Sequence Node record and any
links to the associated RCA Sequence Node record.
Hint: If you do not want to delete successor nodes, you should remove the connectors
before deleting the predecessor node. If you delete a predecessor node without first
deleting the connector between it and the successor nodes, the records associated with the
successor nodes will also be deleted.
To delete a node from the Event Diagram:
1. On the Event Diagram page, in the design canvas, right-click the node, and on the
shortcut menu, click Delete.
A message appears, explaining that deleting the node will also delete all of its successors
and asking if you really want to delete the node.
The RCA Sequence Node record is deleted along with any Sequence Node records
associated with the successor nodes, and the predecessor node and any successor node(s)
no longer appear in the diagram canvas.
Deleting Node Connectors
When you delete a connector between two given nodes in the Event Diagram, you are
deleting the link between the two records.
To delete a connector from an Event Diagram:
1. On the Event Diagram page, in the diagram canvas, click the desired connector to
select it.
2. Press the Delete key.

A message appears, asking if you really want to delete the connector.
The connector is deleted from the Event Diagram. The Meridium APM system also
updates the record links for each node when one or more connectors attached to the node
are deleted.
Displaying the Event Diagram on a Full

Screen
Displaying an Event Diagram on a full screen can be useful for showing the Event
Diagram in a presentation. The following instructions provide details on displaying the
Event Diagram on a full screen.
To display the Event Diagram on a full screen:
On the Event Diagram page, on the Event Diagram menu, click the Full Screen
link.
The Event Diagram appears on a full screen. All of the options available from the rightclick menus in normal mode are also available in the full screen mode.
-orRight-click the diagram canvas, and then click Full Screen.
To return to normal mode from the full screen mode:
Press the Esc key.
-orRight-click the diagram canvas, and then click Full Screen.
Hiding or Displaying the Selected Node

Datasheet Section
To hide the Selected Node Datasheet section:
On the Event Diagram task menu, click the Hide Data Sheet link.
The Selected Node Datasheet Section is removed from the Event Diagram page.
To display the Selected Node Datasheet section:
On the Event Diagram task menu, click the Show Data Sheet link.
The Selected Node Datasheet Section appears on the Event Diagram page.
Hiding and Displaying the Available

Nodes Palette Section
To hide the Available Nodes Palette section:
On the Event Diagram page, on the Event Diagram task menu, click the Hide
Node Palette link.
The Available Nodes Palette section is removed from the Event Diagram page.
To display the Available Nodes Palette section:
On the Event Diagram page, on the Event Diagram task menu, click the Show
Node Palette link.
The Available Nodes Palette section appears on the Event Diagram page.
Exporting the Event Diagram

If desired, you can export the Event Diagram as an image and save it to another location,
such as your local hard drive. You can export the Event Diagram in any of the following
image formats:
Bitmap (.BMP)
Graphic Interchange Format (.GIF)
Joint Photographic Experts Group (.JPG)
Portable Network Graphics (.PNG)
Tag Image File Format (.TIF)
The following instructions assume that you have already created an Event Diagram for
the RCA Analysis.
To export the Event Diagram:
1. On the Event Diagram page, on the Event Diagram menu, click the Export Event
Diagram link.
The Export Event Diagram dialog box appears.
2. Navigate to the location to which you want to save an image of the Event
Diagram.
3. In the File Name text box, type the desired file name.
4. In the Save as type list box, select the desired file type.

The Event Diagram is saved as an image to the specified location.
What is a Logic Tree?

A Logic Tree is an organizational tool that you can use to diagram all the possible causes
of a failure event. The structure of the Logic Tree is hierarchical so that you can easily
reference which event caused what effect. Each cause or effect is represented by a labeled
icon, called a node.
There are four types of nodes: Failure Event, Failure Mode, Hypothesis, and Logic Gate.
Each node has an associated record, which participates in a predecessor-successor
relationship. For example, each Failure Mode node that appears in the Logic Tree has an
associated RCA Failure Mode record that is linked to the root RCA Event record.
Additionally, for each Hypothesis node that appears in the Logic Tree, an associated RCA
Hypothesis record exists that is linked to the predecessor RCA Failure Mode record and
the root RCA Event record. Additionally, when you add a node to the Logic Tree, a link is
created between the record for that node and the RCA Analysis record.
The following image illustrates the basic structure of the Logic Tree. For more
information on each level of the Logic Tree, click the hyperlinked name on the associated
node in the image.
Accessing the Logic Tree Page

You can access the Logic Tree page via the Analyze menu on any of the following pages:
Analysis page
Event Diagram page
Logic Tree page
If an RCA event record has already been created and linked to the current RCA Analysis,
the Logic Tree page will appear, displaying the current Logic Tree.
If an RCA Event record has not yet been created for the current RCA Analysis, the RCA
Event dialog box will appear, prompting you to define the failure event.
Note: If the RCA Analysis was created from a Production Event record in the PLA
module, several of the fields in the RCA Event record will be populated automatically
with values from that Production Event record.
To access the Logic Tree page:
On the Analyze menu, click the Logic Tree link.
The Logic Tree page or RCA Event dialog box will appear, depending upon whether or
not an RCA Event record has been created for the current RCA Analysis.
Aspects of the Logic Tree Page

The Logic Tree page consists of the sections shown in the following image. Numbered
labels have been added to the image to identify the sections on the page.
The Logic Tree page consists of three sections:

1. Diagram canvas: The main display area where you can build the Logic Tree
diagram. You can right-click the diagram canvas to display a shortcut menu,
containing options that let you modify how the Logic Tree page looks.
2. Options pane: Contains the following tabs:
o
Palette: Contains icons that represent the nodes that you can use to build a
Logic Tree.
Properties: Displays the details of the record for the node that is currently
selected in the diagram canvas.
Find Nodes: Lets you search the Logic Tree for a specific node.
Verifications: Displays a list of the RCA Verification records related to the

hypothesis node that is currently selected.
1.
o
Incomplete Verifications: Displays a list of RCA Hypothesis records that

are linked to RCA Verification records for which there is no outcome. You
can filter this list to display RCA Hypothesis records that are not linked to
RCA Verification records.
Build List: Displays the current build list, which is a list of potential RCA
Hypothesis records that you can later select to add to the Logic Tree.
Tree Appearance: Provides you with options to change the appearance of

the Logic Tree.
3.
Task menu pane: Contains the following task menus that provide options that let
you perform tasks associated with the RCA Analysis:
o
Manage Assets
Tree Tasks
PReserve
Order
Analyze
Communicate
Track
Aspects of the Options Pane

The Options pane on the Logic Tree page contains tabs, which contain options that you
can use to perform tasks associated with the Logic Tree and the Analyze step of the RCA
Analysis.
The Options pane contains the following tabs:
Palette: Contains icons that represent the nodes that you can use to build a Logic
Tree. You can drag icons from the palette and drop them on the diagram canvas to
add them to the Logic Tree. The Palette tab is displayed by default when you first
access the Logic Tree page.
Properties: Displays the datasheet for the node that is currently selected in the
diagram canvas. You can view and modify the details for the selected nodes on the
datasheet. The following image shows an example of a completed datasheet on

the Properties tab.
Find Nodes: Lets you search the Logic Tree for a specific node. You can doubleclick the desired node from the search results, and the Meridium APM system will
locate the node in the Logic Tree and select it. The following image shows the
Find Nodes tab.
Verifications: Displays a list of the RCA Verification records related to the

Hypothesis node that is currently selected. The following image shows the
Verifications tab.
From this tab, you can:

1.
o
Select an RCA Verification record to modify.
Create a new RCA Verification record. The New button is enabled only
when a Hypothesis node is selected in the diagram canvas.
Delete an existing RCA Verification record for a selected hypothesis. The

Delete button is enabled only when a Hypothesis node is selected in the
Logic Tree.
Note: RCA Verification records are can be created only for Hypothesis nodes.
Incomplete Verifications: Contains options that you can use to filter the list of
RCA Hypothesis records to locate those that are not linked to RCA Verification
records or that are linked to incomplete RCA Verification records. The following
image shows an example of the Incomplete Verifications tab, where the Show All
option is selected.
The Incomplete Verifications tab contains the following options:

1.
No Verifications: Displays a list of RCA Hypothesis records for which no

RCA Verification records exist.
Incomplete Outcome: Displays a list of RCA Hypothesis records for which

RCA Verification records exist but are incomplete (i.e., the Outcome field
in the RCA Verification record is empty).
Show All: Displays a list containing both types of RCA Hypothesis

records.
Print button: Displays the Preview window from which you can print the
list of RCA Hypothesis records.
Build List: Contains a list of Hypothesis nodes that have not yet been added to the
Logic Tree. On the Build List tab, you can add, modify, and delete Hypothesis
nodes and import existing Hypothesis nodes to later add to the Logic Tree. The
following image shows an example of the Build List tab, which contains a list of
Hypothesis nodes.
Tree Appearance: Provides you with options that you can use to change the
appearance of the Logic Tree. The following image shows the Tree Appearance
tab.
From the Tree Appearance tab, you can:

1.
o
Zoom in and zoom out on the Logic Tree.
Change the style of the lines that connect the nodes.
Change the color of the Logic Tree window.
Adjust the number of levels and nodes displayed on the Logic Tree.
Change the font color and size of the node labels.
Manage Assets Menu

The Manage Assets menu on the Logic Tree page contains the following link:
RCA analysis.
Tree Tasks Menu

The Tree Tasks menu on the Logic Tree page contains the following links:
All Verifications: Displays the All Verifications dialog box, which displays all
verifications (i.e., hypotheses) that belong to the current RCA Analysis. You can
use this dialog box to send records in an email message or print records.
Settings: Displays a submenu that contains the following options:
Show Logic Gates: Displays on the Palette tab in the Options section the
logic gates that you can use to connect nodes (i.e., And and Or) and
reveals the logic gates that the Meridium APM system adds to the Logic
Tree automatically.
Auto Arrange: Automatically arranges the nodes so that the nodes and the
connector lines appear organized as you add nodes and connector lines to
the Logic Tree. If this option is selected (as indicated by the check mark to
the left of the option), you will not be able to move the nodes manually.
o
Rearrange: Rearranges the nodes and the connector lines so that they
appear organized after you have manually moved and added nodes and
connector lines to the Logic Tree. This option is disabled when the Auto
Arrange option is selected.
Note: Unlike the other options on the submenu, a check mark does not appear to the left
of the Rearrange option after you select it.
Vertical View: Displays the Failure Event node at the top of the diagram
canvas with the Logic Tree cascading down. This is the default display
setting.
Horizontal View: Displays the Failure Event node at the left of the
diagram canvas with the Logic Tree cascading across the page to the right.
Overview Map: Displays the Overview Map window, which displays the Logic
Tree from an overview perspective, where you can use your pointer to zoom in on
specific areas. This option is useful when the Logic Tree is larger than the display
area.
Full Screen: Maximizes the Meridium APM Framework window, hides the frame
around the diagram canvas (including the task menu pane), and displays only the
Event Diagram, the Selected Node Datasheet pane, and the Available Nodes
Palette.
Toggle Options: Hides or displays the Options section.
current RCA Analysis..
Export Tree: Displays the Export Logic Tree dialog box, where you can select a
location and image file type and then export the Logic Tree.
Page.
Print Preview: Displays the Print Preview window, which shows you a preview of
the Logic Tree as it will appear on the printed page.
Print: Displays the Print dialog box, where you can specify the printer settings,
and then print the Logic Tree.
Help: Displays the context-sensitive Help topic for the current page.
PReserve Menu
The PReserve menu on the Logic Tree page contains the following link:
Preserve Records: Displays the Preserve Failure Data page, which lists the
existing RCA Preserve Item records for the current RCA Analysis.
Order Menu
The Order menu on the Logic Tree page contains the following links:
displays the CSFs associated with the selected RCA Analysis.
Team Charter: Displays the Team Charter dialog box, which displays the Team
Charter that is currently defined for the RCA Analysis. You can modify the Team
Charter using this option, and then click the Save button.
Team: Displays the Team page, which contains a list of Team Members that
belong to the current RCA Analysis.
Analyze Menu
The Analyze menu on the Logic Tree page contains the following links:
Communicate Menu
The Communicate menu on the Logic Tree page contains the following links:
Communicate Records: Displays the Communicate Records page, which contains

the RCA Communicate datasheet and a list of RCA Recommendation records that
are linked to the current RCA Analysis.
Reports: Displays the Reports List page, which contains a list of reports that have
been configured for use with Root Cause Analysis.
Track Menu
The Track menu on the Logic Tree page contains the following link:
Track: Displays the Analysis Tracking Items page, which contains a list of RCA
Tracking Item records that are linked to the current RCA Analysis.
Using the Shortcut Menu in the

Diagram Canvas
To access the shortcut menu in the diagram canvas:
Right-click anywhere in the diagram canvas.
About the options on the shortcut menu:

The following options are available on the shortcut menu in the diagram canvas that let
you modify the way the Logic Tree page appears.
Zoom: Displays a submenu of options that let you change the magnification at
which you are viewing the Event Diagram. When you select a magnification from
the submenu, the design canvas refreshes and displays the Event Diagram at the
specified magnification.
Tree Settings: Displays a submenu of options that correspond to the options

displayed on the submenu for the Settings link on the Tree Tasks menu. These
options include the following.
Show Logic Gates: Displays on the Palette tab in the Options section
the logic gates that you can use to connect nodes (i.e., And and Or),
and reveals the logic gates that are added automatically to the Logic
Tree. The Meridium APM system adds an Or node to the Logic Tree
by default. If you want to add an And node, you will need to do so
manually.
Auto Arrange: Automatically arranges the nodes so that the nodes and the
connector lines appear organized as you add nodes and connector lines to
the Logic Tree. If this option is selected (as indicated by the check mark to
the left of the option), you will not be able to manually move the nodes.
Rearrange: Rearranges the nodes and the connector lines so that they
appear organized after you have manually moved and added nodes and
connector lines to the Logic Tree. This option is disabled when the Auto
Arrange option is selected. A check mark does not appear to the left of the
Rearrange option after you select it.
Vertical View: Displays the Logic Tree with the event at the top of the
diagram canvas cascading down. This is the default display setting.
Horizontal View: Displays the Logic Tree with the event to the left of the
diagram canvas cascading across the page to the right.
Full Screen: Maximizes the Meridium APM Framework window and hides the
frame around the diagram canvas (including the task menu pane), and displays
only the Event Diagram, the Selected Node Datasheet pane and the Available
Nodes Palette. When this option is selected, a check mark appears to the left of
the option. To return to the regular view, right-click the diagram canvas and clear
the Full Screen option.
Toggle Options: Hides the Selected Node Datasheet pane and the Available Nodes
Palette. To hide the panes individually, you can use the Hide Data Sheet and Hide
Node Palette options on the Event Diagram task menu.
Workflow for Creating a New Logic

Tree
The Logic Tree page provides tools that you can use to create a Logic Tree. From the
Logic Tree page you can view and modify an existing Logic Tree or create a new Logic
Tree.
Building the Logic Tree consists of completing the following steps:
1. Defining the Failure Event node.
2. Adding Failure Mode nodes to the Logic Tree.
3. Adding Hypothesis nodes to the Logic Tree.
4. Adding RCA Verification records to Hypothesis nodes.
5. Adding Logic Gate nodes to the Logic Tree.
6. Setting the states and causes of the hypotheses.
What is a Failure Mode?

A failure mode is a possible cause associated with the failure event. The failure mode is
represented by a node, called the Failure Mode node, which appears below the Failure
Event node. When you add a Failure Mode node to the Logic Tree, you are defining the
RCA Failure Mode record. When you define an RCA Failure Mode record, a link is
created between the RCA Failure Mode record and the root RCA Event record and
between the RCA Failure Mode record and the RCA Analysis record.
The following image shows an example of a completed RCA Failure Mode datasheet.
The RCA Failure Mode datasheet consists of the following fields:
Label: A description of the failure mode as you want it to appear on the Logic
Tree.
Description: A detailed description of the Failure Mode. You can click the
button to display the Text Editor.
Failure Mode nodes exist on the second level of the tree, under the Failure Event node.
Multiple Failure Mode nodes can be linked to the Failure Event node. The following
image shows an example of how a Failure Mode node will look in the Logic Tree.
A given failure event can have multiple failure modes. For example, the image shows the
failure modes from our Cooling Water Pump failure example. The Failure Event node
(i.e., the overheated pump) is associated with the following Failure Mode nodes:
No Spare Parts. There were no spare parts when the pump overheated, which
caused the pump to be down for a longer amount of time and a greater loss of
production. This failure mode did not cause the failure, so there are no hypotheses
associated with it, but it is included as part of the failure event.
Motor tripped due to high temperature. This failure was the cause of the
overheated pump event. There are additional hypotheses associated with this node
so that the cause of the event can be determined.
Adding Failure Mode Nodes to the Logic

Tree
To add a Failure Mode node to a Logic Tree, you can either create a new RCA Failure
Mode record or import an existing RCA Failure Mode record. The following instructions
assume that you want to create a new RCA Failure Mode record.
To add a Failure Mode node to the Logic Tree:
1. In the Options pane, on the Palette tab, click and drag the Failure Mode icon to
the Failure Event node in the diagram canvas and then release the mouse button to
drop the Failure Mode in the desired location. A plus sign appears to indicate
when you have chosen a valid location.
-orRight-click the Failure Event node in the diagram canvas, and on the shortcut menu, click
Add Failure Mode.
The New Logic Tree Item dialog box appears.
2. Complete the fields on the RCA Failure Mode datasheet as desired.

The RCA Failure Mode record is saved and automatically linked to the RCA Event record
and the RCA Analysis record. The Failure Mode node also appears on the Logic Tree
below the Failure Event node.
If necessary, you can add additional Failure Mode nodes by repeating these steps. You
can also modify the RCA Failure Mode record properties on the datasheet. After you have
finished defining the Failure Mode nodes, the next step in building the Logic Tree is to
define Hypotheses.
What is a Hypothesis?
By definition, a hypothesis is a tentative assumption intended to explain certain facts or
observations. Within the context of an RCA Analysis, a hypothesis represents a theory
about the root cause of a failure event.
In the Logic Tree, a hypothesis is represented by a Hypothesis node, which is defined in
an associated RCA Hypothesis record. Hypothesis nodes can appear below Failure Mode
nodes and other Hypothesis nodes in the Logic Tree. When you add a Hypothesis node to
the Logic Tree, a link is created between the RCA Hypothesis record and the RCA
Analysis record. A link is also created between the RCA Hypothesis record and either the
RCA Failure Mode record or the predecessor RCA Hypothesis record.
The following image shows an example of a completed RCA Hypothesis datasheet.
The RCA Hypothesis datasheet contains the following fields:
Label: A description of the hypothesis as you want it to appear on the Logic Tree.
Description: A detailed description of the hypothesis.
Confidence Factor: A value that indicates the probability that the hypothesis is
true. The list contains values that range from Not True (0) to True (5). You can
choose ONE of the six values. If you select a value in this field, the value that you
select will appear in brackets to the right of the hypothesis name in the Logic
Tree.
State: The state of the Hypothesis node, which is set to Hypothesis by default.
You can choose from the following states:
Hypothesis
Hypothesis True
Hypothesis Not True
Cause Human
Cause Latent
Cause Physical
Note: For more information on Hypothesis node states, see the Hypothesis States section
of this Help system.
The following image shows an example of how a Hypothesis node and the associated
RCA Hypothesis record will look in the Logic Tree when it is first created.
To the right of the label that you assign to the Hypothesis node, a number appears,
indicating the level of confidence that the team has in the hypothesis being true. After a
given RCA Hypothesis record has been created, the team can create an RCA Verification
record to test the hypothesis. The team will then change the state of the RCA Hypothesis
record according to the results of the RCA Verification record.
You can define multiple Hypothesis nodes for any RCA Failure Mode record or RCA
Hypothesis record, meaning that one cause could have been caused by something else.
For example, a lubrication issue may cause a cooling water pump to overheat, but that
lubrication issue was caused by an operator who did not apply enough lubricant, which
was caused by inadequate accountability of workers. In this case, the lubrication issue is a
physical cause, too little lubrication applied is a human cause, and the latent root cause is
the inadequate accountability of workers. The following image shows how this scenario
would appear in the Logic Tree.
About Hypothesis States

RCA Hypothesis records are assigned a state that indicates the validity of the hypothesis.
When a Hypothesis node is first created, it is assigned the Hypothesis state by default.
After the hypothesis has been tested through the completion of an RCA Verification
record, the state of the Hypothesis node can then be changed to True or Not True. If a
hypothesis is proven to be incorrect, after you change the Hypothesis state to Not True,
you are finished working with that hypothesis. If a hypothesis is proven to be true and
you change the Hypothesis State to True, you can:
Create additional RCA Hypothesis records that provide further information on a

root cause and link them to the RCA Hypothesis record.
Create RCA Verification records to test the additional hypotheses, determine if the
hypotheses are true or not true, and then change the state of the associated RCA
Hypothesis records accordingly.
Create additional RCA Verification records to test the hypothesis to further

identify the root cause as physical, human, or latent.
-or-
After the root cause has been identified, you can change the state of the associated RCA
Hypothesis record to indicate your conclusions (i.e., Cause Human, Cause Latent, or
Cause Physical).
When you change the state of a Hypothesis node, the node icon changes to indicate the
new state. The following table describes all the possible states of an RCA Hypothesis
record and how the associated Hypothesis node will appear in the Logic Tree.
Hypothesis
Node
Hypothesis
State
Description
For example, the team

may determine that:
Hypothesis
The hypothesis is proposed and

no conclusions can be drawn at
may have failed due to a
this point. This is the default
pressure leak.
state.
Hypothesis
True
The hypothesis has been tested

and proven to be correct.
failed due to a pressure
Further conclusions can be
leak.
drawn.
Hypothesis
Not True
The hypothesis has been tested

and proven to be incorrect. No
did not fail due to a
further conclusions can be
pressure leak.
drawn.
Cause
Human
The operator failed to

The hypothesis has been proven
increase the pressure
correct and further testing has
when it reached the
revealed that the root cause of
critical level, therefore
the Failure Event was caused by
causing a pressure leak
human interaction.
and the failure.
The hypothesis has been proven

correct and further testing has Management failed to
revealed that the root cause of adhere to the
the Failure Event was caused by recommended safety
flaw(s) in procedure or the
guidelines for the piece
system that caused incorrect
of equipment, thus the
Cause Latent decisions to be made. This is
operator failed to
often due to poor data or
increase the pressure
communication between
when it reached the
individuals within the
critical level, causing the
organization. In the vast
pressure leak and the
majority of events, there will be failure.
at least one latent cause.
Cause
The hypothesis has been proven The seals on the
Physical
pressure relief valve are

correct, and further testing has
worn and require
revealed that the root cause of
replacement, which
the Failure Event was caused by
caused the pressure leak
a physical piece of equipment.
and the failure.
Adding Hypothesis Nodes to the Logic

Tree
Hypothesis nodes are always on the third level of the tree or later, attached either to a
Failure Mode node or another Hypothesis node. After you have created the Failure Event
node and the corresponding Failure Mode node(s), you can add Hypothesis nodes to the
Failure Mode nodes and Hypothesis nodes as desired to help the team determine the
cause of the event.
You can add a Hypothesis node to the Logic Tree by creating a new RCA Hypothesis
record or by importing an existing RCA Hypothesis record and the associated Hypothesis
node. The following instructions provide details on defining a new Hypothesis node and
adding it to the Logic Tree.
To create a new Hypothesis node and add it to the Logic Tree:
1. On the Logic Tree page, In the Options pane, on the Palette tab, click and drag a
Hypothesis icon to the Failure Mode node or Hypothesis node in the diagram
canvas and then release the mouse button to drop the Hypothesis node in the
desired location. A plus sign (+) appears to indicate when you have chosen a valid
location.
-orOn the Logic Tree page, right-click the Failure Mode node or Hypothesis node in the
diagram canvas, and on the shortcut menu, click Add Hypothesis.
2. Define the RCA Hypothesis record as desired.

The Hypothesis node appears in the Logic Tree and a link is created between the RCA
Hypothesis record and the RCA Analysis record and between the RCA Hypothesis record
and the RCA Failure Mode record or another RCA Hypothesis record.
If necessary, you can add additional Hypothesis nodes by repeating these steps. You can
also modify the hypothesis properties via the datasheet.
About the Build List Tab

The Build List tab appears in the Options pane on the Logic Tree page and contains a list
of potential Hypothesis nodes that have been defined by an RCA Analysis Team.
You can create new RCA Hypothesis records and add them to list on the Build List tab,
and you can select a hypothesis from the Build List tab and add the associated Hypothesis
node to the Logic Tree.
Adding a New Hypothesis to the Build

List Tab
The following instructions provide details on creating a new RCA Hypothesis record and
adding it to the Build List tab.
To create a new RCA Hypothesis record and add it to the Build List tab:
1. On the Logic Tree page, In the Options pane, click the Build List tab.
The Build List tab appears.
If RCA Hypothesis records exist that are linked to the current RCA Analysis but do not
appear in the Logic Tree, they will appear in the list.
2. In the text box below the label Enter a Hypothesis below, then click the Add
button, type a description of the new Hypothesis node as want it to appear on the
Logic Tree.
The description for the new hypothesis appears in the Build List of potential hypotheses.
This list will be retained until you add the associated Hypotheses nodes to the Logic Tree.
Importing a Hypothesis and Adding it to

the Build List Tab
The following instructions provide details on importing an RCA Hypothesis record from
an existing RCA Analysis and adding it the Build List tab.
Note: Importing an RCA Hypothesis record in this way adds it only to the Build List tab.
If you want to add the Hypothesis node to the Logic Tree, you will need to do so
manually or import the Hypothesis node and add it to the Logic Tree.
To import a Hypothesis node to the Build List tab:
1. On the Logic Tree page, In the Options pane, on the Build List tab, click the
Search button.
The Search Tool window appears.
2. In the Search Text box, type the search criteria for the analysis that is associated
with the Hypothesis node that you want to import and add to the Build List tab.
Hint: You can type the % (percent sign) in the Search Text field as a wild card character,
allowing you to search on all items stored in the database.
3. Select the check boxes that apply to the type(s) of analysis for which you want to
search, Templates and/or Published Analyses. Note that the Templates and
Published Analyses check boxes are selected by default. If you want search only
for Templates or only for Published Analyses, clear the appropriate check box.
4. Select the Match Case? check box if you want to return items that match exactly
the case of the keyword you entered in the Search Text box.
Note: To return all search criteria to their default values, click the Reset button. This will
clear the Search Text box, reselect the Templates and Published Analyses check boxes,
and clear the Match Case? check box.
5. Click the Search button.
The Meridium APM system searches the database for existing analyses that match the
analysis type you selected and whose Label field contains the value that you typed in the
Search Text box.
The results appear in the grid in the Search Results section on the Search Tool window.
6. Select the desired analyses in the list.

7. Click the Select button.
The Hypothesis node(s) associated with the selected analyses are imported and appear in
the Build List tab.
Adding Hypotheses from the Build List

Tab to the Logic Tree
The following instructions provide details on adding hypothesis nodes from Build List tab
to the Logic Tree using the drag-and-drop method.
To add a Hypothesis node from the Build List tab to the Logic Tree:
1. On the Logic Tree page, in the Options pane, on the Build List tab, select the row
containing the desired hypothesis.
2. Drag the selected hypothesis to the desired location in diagram canvas. A plus
sign (+) will appear to indicate that you have selected a valid location. You should
only add a Hypothesis node to a Failure Mode node or another Hypothesis node.
Note: If you try to attach a hypothesis to the Failure Event node, the Meridium APM
system will create a new Failure Mode node instead of a new Hypothesis node.
3. Release your mouse button to drop the hypothesis in the selected location.
The New Logic Tree Item dialog box displays the RCA Hypothesis datasheet.
4. If desired, you can modify the fields on the datasheet.

Your changes are saved, and the new Hypothesis node appears on the Logic Tree in the
specified location.
Modifying an Existing Hypothesis on the

Build List Tab
The following instructions provide details on modifying an existing item on the Build
List tab in the Options pane of the Logic Tree page.
To modify an existing item on the Build List tab:
containing the item that you want to edit.
2. Click the Edit button.

The Hypothesis dialog box appears.
3. Modify the text for the hypothesis as desired.

Your changes are saved and the item in the Build List reflects those changes.
Deleting a Hypothesis from the Build

List Tab
The following instructions provide details on deleting a hypothesis from the Build List
tab in the Options pane of the Logic Tree page.
To delete a hypothesis from the Build List tab:
containing the item that you want to delete.

A confirmation message appears, asking if you really want to delete the item.
The item is removed from the list on the Build List tab.
Deleting All Hypotheses from the Build

List Tab
The following instructions provide details on deleting all of the hypotheses from the Build
List tab in the Options pane of the Logic Tree page.
To delete all hypotheses from the Build List tab:
1. On the Logic Tree page, in the Options pane, on the Build List tab, click the Clear
List button.
A confirmation message appears, asking if you really want to delete the entire list.
The list on the Build List tab is cleared.
Changing the State of an RCA

Hypothesis Record
When an RCA Hypothesis record is created, the state is set to Hypothesis by default.
Each RCA Hypothesis record can then be tested and proven True or Not True and the
Hypothesis State can be changed accordingly.
To change the state of an RCA Hypothesis record:

1. On the Logic Tree page, in the diagram canvas, right-click the Hypothesis node
whose state you want to change.
2.
On the shortcut menu, point to State, and then click the desired state. You can
choose:
True if the hypothesis has been confirmed.
Not True if the hypothesis has been ruled out.
Note: After you determine a hypothesis to be true, you can identify the root cause.
Identifying the Root Cause for

Hypotheses Proven True
After you determine a hypothesis to be true and change its state accordingly, you can
continue testing the hypothesis through RCA Verification records to identify the root
cause of the Failure Event.
If a hypothesis is proven correct, the RCA Analysis team should continue testing all the
other hypotheses before testing further to determine the root cause. For example, the team
may find that Hypothesis-A is true and that the cause was physical. If the RCA Analysis
is prematurely ended the here because the solution seems evident, the team may fail to
consider other causes. If other causes are not identified as possibilities, no additional
action will occur and the failure event is likely to occur again.
To specify the root cause for a hypothesis:
On the Logic Tree page, in the diagram canvas, right-click the Hypothesis node
whose root cause you want to specify, point to State, and then click the desired
cause. You can choose one of the following causes:
Cause - Physical
Cause - Human
Cause - Latent
After you select a cause:
The hypothesis is outlined in a red square.
A red line is drawn to show the path to failure.
The icon used to identify the Hypothesis node changes to indicate the
specific cause.
The team can communicate their findings to the decision makers in your
organization.
About Importing Existing Failure

Modes and Hypotheses
As you are building out the Logic Tree for an RCA Analysis, you have the option of
defining new Failure Mode and Hypothesis nodes from scratch or importing them from
the Logic Trees of other RCA Analyses.
You can import existing Failure Mode and Hypothesis nodes via the Search Tool window,
which allows you to find Failure Mode and Hypothesis nodes that exist in other RCA
Analyses.
You can use the Search Tool window to define criteria for searching for Failure Mode and
Hypothesis nodes to import.
When you import a node into the Logic Tree, any subnodes that belong to it are also
added to the Logic Tree. For example, if you import a Failure Mode that is associated
with three Hypothesis nodes, the Failure Mode node and ALL of its Hypothesis nodes
will be added to your Logic Tree.
Note: Hypothesis nodes can also be added to the Build List tab by importing them into the
Logic Tree.
Aspects of the Search Tool Window

The Search Tool window allows you to search for existing Failure Mode and Hypothesis
nodes.
The Search Tool window contains the following items:
Search Text text box: Identifies the value that you want to find within the Label
field of RCA Event, RCA Failure Mode, and RCA Hypothesis records. For
example, if you type Pump Failure, the search results will return all RCA Event,
RCA Failure Mode, and RCA Hypothesis records with the value Pump Failure in
the Label field.
Analysis Search Text text box: Identifies the value that you want to find within the
Name field of RCA Analyses whose nodes you want to import. For example, if
you want to import a Failure Mode node that belongs to an RCA Analysis with the
value Pump Analysis in the Name field, you would type Pump Analysis in this
text box.
Note: The Search Text text box and Analysis Search Text text boxes can be used
independently or in conjunction with one another. For example, if you are looking for
Pump Failure Failure Modes from any analysis, you would type Pump Failure in the
Search Text text box and leave the Analysis Search Text text box empty. If you are
looking for all the Failure Modes in the Pump Analysis RCA Analysis, you would leave
the Search Text text box empty and type Pump Analysis in the Analysis Search Text text
box. If you are looking for a Pump Failure Failure Mode node in the Pump Analysis RCA
Analysis, you would type Pump Failure in the Search Text text box and type Pump
Analysis in the Analysis Search Text text box.
Templates check box: Indicates whether or not you want to search the Meridium
APM database for RCA Analysis Templates that contain the values that you typed
in the Search Text text box and Analysis Search Text text box. This check box is
selected by default.
Published Analyses check box: Indicates whether or not you want to search the
Meridium APM database for Published RCA Analyses that contain the values that
you typed in the Search Text text box and Analysis Search Text text box. This
check box is selected by default.
Match Case? check box: Indicates whether or not you want the search to be casesensitive. This check box is cleared by default, meaning that the search will not be
case-sensitive.
Search button: Runs the search using the specified criteria.
Reset button: Clears any values in the Search Text and Analysis Search Text text
boxes and resets the check boxes to their default states.
Search Results section: Displays the search results that are returned for the
selected search parameters.
Select: Imports the search results that are selected in the Search Results section
into the Logic Tree.
Cancel: Closes the Search Tool window.
Children check box: Indicates whether or not you want the Search Results section
to display child Hypothesis nodes.
Note: Even if the Children check box is selected, you cannot select child nodes
independently of their parent nodes.
Verifications check box: Indicates whether or not you want to import RCA
Verification records. If you select this check box and then select in the search
results a Hypothesis record that is linked to an RCA Verification record, values
from the following fields in that RCA Verification record will be copied to a new
RCA Verification record, which is created automatically and linked to the
Hypothesis record that is created from the imported Hypothesis node:
Method
Send Alert on Due Date?
Alert Email Text fields
Note: The Verifications check box is enabled only if the Children check box is selected.
About the Search Results Section

When you use the Search Tool window to import a Failure Mode or Hypothesis node into
a Logic Tree, the results from the search are displayed in the Search Results section. The
results are displayed in a hierarchy that contains images and text that identify the items
that are returned in the search results. You can select the check boxes to the left of the
items in the search results that you want to import into the Logic Tree.
The following table lists the items that appear in the search results, the icons that are used
to represent each item, and any additional information about those items.
Item
RCA Analysis
Icon Notes
RCA Analyses always appear on the first level of the hierarchy. For
each RCA Analysis, the label that appears in the search results is
the value in the Analysis Name field in the RCA Analysis record for
that analysis. The RCA Analysis is displayed in the search results

for the purpose of grouping the items that belong to that analysis.
While you can select the check box to the left of an RCA Analysis,
you cannot import an RCA Analysis into the Logic Tree. If you
select the check box to the left of an RCA Analysis, all of the
children will be selected automatically and imported into the Logic
Tree.
Failure Event
Failure Events always appear on the second level of the hierarchy,

directly below the RCA Analysis to which they belong. For each
Failure Event, the label that appears in the search results is the
value in the Label field of the RCA Event record for that Failure
Event. While you can select the check box to the left of the Failure
Event, you cannot import a Failure Event into the Logic Tree. If
you select the check box to the left of a Failure Event, nothing will
be imported.
Failure Mode
In the hierarchy, Failure Modes appear below the Failure Event to

which they belong. For each Failure Mode, the label that appears in
the search results is the value in the Label field of the RCA Failure
Mode record for that Failure Mode. If you select the check box to
the left of a Failure Mode, it will be imported into the Logic Tree.
Hypothesis
Hypotheses always appear directly below the Failure Mode to

which they belong. For each Hypothesis, the label that appears in
the search results is the value in the Label field of the RCA
Hypothesis record for that Hypothesis. If you select the check box
to the left of a Hypothesis, it will be imported into the Logic Tree.
Specifying Search Text Only

In the following example, suppose you are building a Logic Tree for an RCA Analysis
about a malfunctioning cooling water pump. You are looking for Failure Modes or
Hypotheses for a Failure Event where a cooling water pump overheated in a similar way.
To search for a Failure Mode or Hypothesis for a Failure Event that involves overheating,
you would search for overheating in the Search Text text box. The following image shows
what the search results would look like, assuming that the example RCA Analysis has
been published and that there are no other published analyses or templates.
In this image, because the text overheating appears in the Search Text text box, the search
results display the Failure Event Overheating In Pump 1. In addition, the hierarchy
displays:
The RCA Analysis to which the Failure Event belongs, Cooling Water Pump.
The Failure Modes that belong to the Failure Event. These failure modes are:
No spare parts.
If you were to select the Children check box, the search results would look like this:
In this image, because the Children check box is selected, the following Hypotheses
appear:
Mechanical
Electrical
Note: You cannot select a child node independent of its parent node.
Specifying Analysis Search Text Only

about a malfunctioning cooling water pump. You are looking for Failure Modes or
Hypotheses for a Failure Event where a cooling water pump overheated in a similar way,
and you know there has been another RCA Analysis published about a similar
malfunction.
In this case, you would use the Analysis Search Text text box to search for Failure Modes
and Hypotheses that belong to that specific analysis. The following image shows what the
search results would look like, assuming that the RCA Analysis Cooling Water Pump has
In this image, because the text Cooling Water Pump appears in the Analysis Search Text
text box, the search results display the published RCA Analysis Cooling Water Pump and
the hierarchy beneath it. The hierarchy displays:
The Failure Event Overheating in Pump 1 and Failure Modes that belong to it.
These Failure Modes are:
No Spare Parts.
Each Failure Mode and the Hypotheses that belong to it. The Hypothesis nodes
are:
Mechanical
Electrical
Outboard Bearing
Inboard Bearing
Erosion
Corrosion
Fatigue
Misalignment
Loose Bolts
Lubrication Issue
Leak
Too Much Applied
Too Little Applied
Poor Training
Inadequate Procedures Document
Worker Fatigue
Inadequate Accountability of Workers
Note: In this case, because the entire RCA Analysis was returned in the search results,
you can select a child node independent of its parent node.
Specifying Search Text and Analysis

Search Text
about a cooling water pump that has malfunctioned due to a lubrication issue. You are
looking for Hypotheses for this particular Failure Mode, and you know there has been an
RCA Analysis published about a similar malfunction.
In this case, you would use both the Search Text text box and the Analysis Search Text
text box to search for a Hypothesis whose Label field contains the word Lubrication and
is part of the RCA Analysis Cooling Water Pump. The following image shows what the
search results would look like, assuming that the RCA Analysis Cooling Water Pump has
In this image, because the text Lubrication appears in the Search Text text box, the search
results display the Hypothesis node Lubrication. In addition, because the text Cooling
Water Pump appears in the Analysis Search Text text box, the search results display only
the Failure Modes or Hypotheses that belong to the published RCA Analysis Cooling
Water Pump. Therefore, the hierarchy displays the Hypotheses node Lubrication with the
following additional Hypothesis nodes that exist below Lubrication in the hierarchy:
Leak
Too Much Applied
Too Little Applied
Performing the Import Operation

To import existing Failure Mode and Hypothesis nodes:
1. On the Logic Tree page, in the diagram canvas, right-click the parent node whose
child node you want to import, and on the shortcut menu, click Import.
The Search Tool window appears.
For the node that you right-clicked, the value that is stored in the Label field in the
corresponding record appears in the Search Text text box. In the preceding image, the
Search Tool window was accessed from the Failure Mode node whose Failure Mode
record contains the value Leaks in the Label field.
2. If desired, in the Search Text text box, type the name of the parent node that
contains the child nodes that you want to import.
Hint: You can use the percent sign (%) as a wild card in the Search Text text box,
allowing you to search on all items stored in the database.
3. If desired, in the Analysis Search Text text box, type the name of the RCA
Analysis that contains the nodes that you want to import.
4. If you do not want to search RCA Analysis templates, clear the Templates check
box.
5. If you do not want to search published analyses, clear the Published Analyses
check box.
6. If you want the search to be case-sensitive, select the Match Case? check box.
7. Click the Search button.
The results appear in the Search Results section in a hierarchical view of the items that
meet the specified criteria.
Hint: If desired, you can double-click the name of the item to view the associated
datasheet.
8. In the Search Results section, select the check boxes next to the nodes that you
want to import.
9. If you want to view and import child nodes (e.g., the Hypothesis nodes that exist
for a given Failure Mode node), select the Children check box at the bottom of the
Search Results section.
The child nodes appear in the hierarchy, where you can select the check box next to the
nodes that you want to import, along with the parent node or nodes.
10. If you want to import RCA Verification records, select the Verifications check box
at the bottom of the display area.
11. When you have made the desired selections, click the Select button to import the
selected items.
The Search Tool window closes, and the selected nodes appear in the diagram canvas and
are linked to the selected Failure Event node.
What is a Verification?
A verification is a task to prove or disprove a hypothesis. An RCA Verification record
contains the task-related information necessary to verify a hypothesis. RCA Verification
records are assigned to team members, similarly to the way in which RCA Preserve Item
records are assigned. For example, if you wanted to verify whether a pump overheated
because of a mechanical or electrical problem, you would need to inspect the pump's
wiring. The following image shows an example of an RCA Verification record.
The following fields are available on the RCA Verification datasheet:
Method: The method used to prove that a hypothesis is true or not true (e.g., Data
analysis, lube oil analysis, stress analysis, visual inspection, interviews). You can
click the button to display the Text Editor.
Outcome: The actual results of the verification method. For instance, an outcome
can be a set of lab results or a report to prove or disprove the hypothesis in
question. This field is populated when the assigned team member has completed
the verification process. You can click the button to display the Text Editor.
Due Date: The date by which the verification of the selected hypothesis should
occur. In the Due Date cell, type or select the date on which the verification is
due.
Send Alert on Due Date?: Select this check box if you want to send to the team
member in the Assign To field an email message on the date specified in the Due
Date field.
Days Before Due Date to be Notified: The number of days before the date
specified in the Due Date field that an alert will be sent to the assigned team
member in the Assign To field. If you do not want an alert to be sent to the team
member before the due date, enter the value 0.
Frequency of Alert After Due Date: How often you want an alert to be sent to the
assigned team member after the date specified in the Due Date field. If you do not
want an alert sent to be sent to the team member after the due date, select Never
from the list.
Alert Email Text: Enabled if you selected the Send Notification on Due Date?
check box. Type the body of the email message that will be sent to the assigned
team member.
Completed?: Defaults to No when you create an RCA Verification record. This

field can be changed to Yes when the assigned team member has completed the
verification process.
RCA Verification records are linked to RCA Hypothesis records and the RCA Team
Member record for the team member to whom the record is assigned. RCA Verification
records do not have an associated node in the Logic Tree. You can send a link to the RCA
Verification record to the team member who is responsible for completing the verification
task.
Adding a New Verification to a

Hypothesis Node
Each hypothesis is proven true or not true by creating and linking RCA Verification
records to that RCA Hypothesis record. A verification is a test that you will conduct to
prove or disprove (i.e., verify) a hypothesis.
To create a new RCA Verification record for a selected RCA Hypothesis record:
1. In the Logic Tree, select the Hypothesis node that you want to verify.
2. In the Options pane, click the Verifications tab.
Any existing RCA Verification records that are linked to the selected Hypothesis node
appear on the Verifications tab.
3. Click the New button.
Note: Since RCA Verification records are associated only with RCA Hypothesis records,
the New button is disabled until you select a Hypothesis node in the Logic Tree.
The Verification Properties dialog box appears, displaying the RCA Verification
datasheet.
4. Complete the fields on the Verification datasheet, as desired.

5. In the Assign To list, select a team member to whom you want to assign to the
RCA Verification record.

The RCA Verification record is saved and linked to the RCA Analysis record and the
RCA Hypothesis record. If you selected the Send Alert on Due Date check box, an Alert
record that is associated with the RCA Analysis is created automatically. The Alert record
then creates a scheduled item in the Schedule Manager, and an email message is sent to
the specified recipient on the due date.
Copying and Pasting an RCA

Verification Record
You can create a copy of an RCA Verification record and assign the new record to the
same Hypothesis node or a different Hypothesis node as the source record.
To copy an RCA Verification record:
1. In the Logic Tree, select the Hypothesis node that is linked to the Verification
record you want to copy.
2. In the Options pane, click the Verifications tab.
3. In the grid, select the RCA Verification record that you want to copy, and click the
Copy button.
4. To paste the copy of the RCA Verification record to the same Hypothesis node,
click the Paste button.
-orTo paste the copy of the RCA Verification record to a different Hypothesis node, select
the desired Hypothesis node and click the Paste button on the Verifications tab for that
node.
The Verification Properties dialog box appears.
5. Modify the fields in the Verification Properties dialog box as needed.

The copy of the RCA Verification record appears on the Verifications tab and is linked to
the Hypothesis record.
Finding Hypothesis Nodes with No

Verifications or Incomplete
Verifications
RCA Verification records are considered complete when the Outcome field is populated
with a value. The Meridium APM system keeps a log of all incomplete RCA Verification
records that are linked to RCA Hypothesis records in a given RCA Analysis.
On the Logic Tree page, in the Options pane, on the Incomplete Verifications tab, you can
view a list of RCA Hypothesis records that are not linked to any RCA Verification record
or whose RCA Verification records are incomplete.
To find RCA Hypothesis records without RCA Verification records or with Incomplete
RCA Verification records:
1. In the Options pane, click the Incomplete Verifications tab.
The Incomplete Verifications tab appears.
The Show All option is selected by default so the list contains RCA Hypothesis records
that are not linked to any RCA Verification records or whose RCA Verification records
are incomplete.
2. Filter the list to view the desired hypothesis. You can choose one of the following:
No Verifications
Incomplete Outcome
Show All
3. Select the row containing the RCA Hypothesis record that you want to identify in
the Logic Tree.
The associated Hypothesis node is outlined in blue in the diagram canvas.
What is a Logic Gate?

Root Cause Analysis provides an option that you can use to add logic gates to the Logic
Tree to define a connection between nodes. A logic gate is defined in an RCA Logic Gate
record and is represented in the Logic Tree by a Logic Gate node. You can use Logic
Gate nodes to add Boolean logic between nodes (i.e., AND and OR statements).
The AND Logic Gate is represented by the

Gate is represented by the
symbol in the Logic Tree. The OR Logic
symbol in the Logic Tree.
Adding a Logic Gate node between other nodes in the Logic Tree indicates a conditional
relationship between the nodes, which you can define in the description fields in the RCA
Logic Gate record. These conditional relationships are defined in logical statements (e.g.,
if B is true, then A is true).
To add a Logic Gate node to the Logic Tree, you will need to enable logic gates and
create an RCA Logic Gate record. There are two types of RCA Logic Gate records: AND
and OR. This value is stored in the Gate Type field in the RCA Logic Gate record and
determines the text that is displayed on the Logic Gate node (i.e., AND or OR). The
default Gate Type value in an RCA Logic Gate record is OR.
You can add a Logic Gate node to...
Failure Mode nodes linked to Hypothesis nodes.

Hypothesis nodes linked to other Hypothesis nodes.
Logic Gate nodes linked to other Logic Gate nodes or Hypothesis nodes.
You cannot add a Logic Gate node to the Failure Event node (i.e., between Failure Mode
nodes). A given predecessor node can have only one Logic Gate node.
When you add a Logic Gate node to a node in the Logic Tree, a link is created between
the RCA Logic Gate record and the record associated with the node to which you added
the Logic Gate node and also between the RCA Logic Gate record and the RCA Analysis
record. The following fields are available in the RCA Logic Gate record:
Short Description: The connection that the Logic Gate node defines.
Long Description: The logical statement that the Logic Gate node defines.
Gate Type: The type of logic gate: AND or OR.
Example of Logic Gate Nodes

Assume you want to indicate in the Logic Tree that Failure Mode is true only if
Hypothesis 1 and Hypothesis 2 or Hypothesis 2A is true.
You would organize the nodes in the Logic Tree as shown in the following image.
Enabling Logic Gates

To enable the use of Logic Gate nodes within a Logic Tree:
On the Tree Tasks menu, click the Settings link, and on the shortcut menu, click
the Show Logic Gates option.
Note: If the Show Logic Gates option is enabled, a check mark will appear to the left of
the option.
The Logic Gate nodes appear on the Palette tab in the Options pane.
Adding a Logic Gate to the Logic Tree
Before you can add a Logic Gate node to the Logic Tree, you will need to enable logic
gates.
To add a Logic Gate node to the Logic Tree:
1. On the Logic Tree page, In the Options pane, on the Palette tab, click and drag the
AND or OR icon to the desired node in the diagram canvas. Release the mouse
button to drop the node in the desired location. A plus sign appears to indicate
when you have chosen a valid location.
-orRight-click the node to which you want to add the Logic Gate node, and then on the
shortcut menu, click Add Logic Gate.
2. Complete the fields on the RCA Logic Gate datasheet as desired.

3. Click OK.
The Logic Gate node is added to the Logic Tree. A link is created between the RCA
Analysis record and the RCA Logic Gate record and between the RCA Logic Gate record
and the record associated with the node to which you added the Logic Gate node.
Changing the Gate Type of a Logic Gate

The following instructions provide details on changing the gate type of a Logic Gate in
the diagram canvas on the Logic Tree page.
To change the type of a Logic Gate node that appears in the Logic Tree:
1. On the Logic Tree page, In the diagram canvas, double-click the Logic Gate node
whose gate type you want to change.
The Properties tab appears in the Options pane, displaying the RCA Logic Gate datasheet
for the selected Logic Gate node.
2.
Click the Gate Type field to expand the Gate Type list, and select the desired
logic gate.
3. Click the Save current record icon.

Hint: You can also change the gate type for a Logic Gate node by right-clicking the Logic
Gate node whose gate type you want to change (i.e., OR to AND, or AND to OR), and on
the shortcut menu, point to State, and then click the desired type of gate.
Viewing and Modifying Existing Logic

Tree Node Records
A node is any object within the Logic Tree. For example, Failure Mode nodes have an
associated RCA Failure Mode record that is linked to the RCA Event record. There are
several ways to view the record associated with a Logic Tree node, and you can modify
the values in the record at any time. Throughout this documentation, we refer to the
information contained in the record for a Logic Tree node as its properties.
To view and modify the properties for a Logic Tree node, use any of the following
methods:
On the Logic Tree page, in the Options pane, click the Properties tab, and then
click the Logic Tree node whose properties you want to view or modify.
On the Logic Tree page, in the diagram canvas, right-click the Logic Tree node
whose properties you want to view or modify, and on the shortcut menu, click
Properties.
On the Logic Tree page, in the diagram canvas, double-click the Logic Tree node
whose properties you want to view or modify.
The datasheet for the selected record appears in the Options pane on the Properties tab.
When you are finished modifying the properties of the Logic Tree node, at the top of the
datasheet, click the Save current record icon,
and your changes will be saved.
Note: In addition to modifying the properties of a node using the previous instructions,
you can modify the label of any node by clicking the label on the diagram canvas and
making your changes there. If you modify a label in this way, after you navigate off the
node label, your changes will be saved automatically.
Expanding and Collapsing Logic Tree

Nodes
You can collapse or expand nodes in the Logic Tree to hide or reveal related nodes. You
can collapse or expand all nodes simultaneously, or you can collapse or expand nodes
individually. The following instructions provide details on collapsing and expanding all
Logic Tree nodes and individual Logic Tree nodes.
A minus sign (-) on a Logic Tree node indicates that the node is expanded,
revealing its successor nodes.
A plus sign (+) on a Logic Tree node indicates that the node is collapsed, hiding
its successor nodes.
No plus sign (+) or minus sign (-) on a Logic Tree node indicates that the node
has no successors to hide or reveal.
To collapse ALL child Logic Tree nodes that appear after a parent Logic Tree node:
On a predecessor Logic Tree node (e.g., Failure Mode node or Failure Event
node), click the collapse icon as indicated by the minus sign.
The Logic Tree collapses. The minus sign now appears as a plus sign, indicating that the
tree is collapsed.
To expand ALL successor Logic Tree nodes that appear after a predecessor Logic Tree
node:
Right-click the desired predecessor Logic Tree node, and on the shortcut menu,
click Expand All.
Note: If there are no successor nodes associated with a selected node, the Expand All
option will not appear on the menu.
The Logic Tree expands all the nodes that appear below a predecessor node in the Logic
Tree.
To expand Logic Tree nodes individually:
Select the desired Logic Tree node, and click the plus sign, indicating that the
node contains successor nodes.
The next level of the Logic Tree displays the node associated with the selected node. The
plus sign now appears as a minus sign, indicating that the Logic Tree node is fully
expanded.
Finding Nodes in the Logic Tree

You can locate specific nodes within the Logic Tree by searching for text that matches the
label on the node.
To locate nodes in the Logic Tree:
1. On the Logic Tree page, in the Options pane, select the Find Nodes tab.
The Find Nodes tab appears, displaying blank search fields.
2. In the Search Text box, type the text that you want to search for in the records
associated with the Logic Tree node.
Note: The search is not case sensitive.
3. Click the Find button to display the search results.
The Meridium APM system searches the Label field in the records associated with the
Logic Tree nodes for the text that you entered. The results appear in the text box below
the Search Text box.
If there are no nodes in the Logic Tree that meet the search criteria, a message appears,
indicating that no results match your search criteria. If this message appears, click OK to
close the message and return to the Find Nodes tab.
4. On the Find Nodes tab, in the list of results, locate the desired node.
5. Double-click the desired node.
The selected node appears outlined in blue in the diagram canvas.
If the selected node is hidden in the diagram canvas (e.g., if its predecessor node is
collapsed), the Logic Tree will expand automatically to reveal the selected node.
Manually Arranging Nodes Within the

Logic Tree
Disabling Automatic Arrangement
By default, the Meridium APM system automatically arranges the presentation of the
nodes on the Logic Tree. You can accept this default setting and allow the Meridium
APM system to control the display of the Logic Tree, or you can disable this feature and
manually rearrange the location of the nodes.
Before you can begin manually arranging the nodes in the Logic Tree, you will need to
disable the Auto Arrange option.
To disable this Auto Arrange option:
On the Logic Tree page, on the Tree Tasks menu, click the Settings link, and on
the submenu, click the Auto Arrange option to clear the check mark that appears
to the left of the option.
Note: If you disable the Auto Arrange option, manually change the location of the nodes,
and then reselect the Auto Arrange option, the system will over-ride all of the manual
changes and apply the system defaults to the Logic Tree.
Arranging Nodes Manually

To manually arrange nodes in the Logic Tree:
On the Logic Tree page, on the diagram canvas, click and drag the desired node to
the desired location in the Logic Tree.
You can click the plus symbol or minus symbol on a node to expand and collapse the
nodes that appear below the selected node.
Note also, that if you click the Rearrange option on the Settings menu on the Tree Tasks
menu, the Logic Tree will display the nodes that you manually arranged in a more logical
way. For example, if you arrange the Logic Tree nodes as shown in the following image:
...and then you click the Rearrange option, the Logic Tree will be displayed as shown in
the following image.
Sending Links to Verification Records to

Team Members
On the Logic Tree page, you can select and send links to RCA Verification records to
multiple analysis team members at the same time. To send links to RCA Verification
records to team members, you must be a member of the RCA Analysis Team for the
current RCA Analysis, and you must have an email address defined in your Meridium
APM Security User record. Additionally, an email address must exist in the recipient's
Meridium APM Security User record.
To send links to RCA Verification records to team members:
1. On the Logic Tree page, on the Tree Tasks menu, click the All Verifications link.
The All Verifications dialog box appears, displaying a list of all existing RCA Verification
records associated with the current RCA Analysis.
2. On the All Verifications dialog box, click the Send Records button.
The Email List of Items dialog box appears, displaying a list of the existing RCA
Verification records in the current RCA analysis.
Note: If you do not currently have an email address defined in your Meridium APM
Security User record, a message will appear, indicating that you do not have an email
address. You will need to enter a valid email address in your Meridium APM Security
User record before you can continue.
3. Select the RCA Verification record whose link you want to send via email. You
can click the Select All button to select all the analyses or the Deselect All button
to clear all selections.
4. In the Subject text box, type the subject of the email message.
5. In the Message Text box, type the text of the email message.
Note: The Person Responsible field displays the list of team members to whom the
message will be sent.
6. Click the Send button.
The email message(s) containing a hyperlink to the selected RCA Verification record is
sent, and a message appears, indicating that the message has been sent.
Note: If the Security User record for the specified recipient does not contain an email
address, a message will appear, indicating that the email could not be sent because the
recipient does not have an email address defined. You will need to type a valid email
address in the Security User record for the recipient before you can send an email
message to that person.
7. Click OK to close the confirmation message.
8. Click the Close button to close the Email List of Items dialog box.
Cutting, Copying, and Pasting Logic

Tree Nodes
After you create various nodes in your Logic Tree, you can cut, copy, and paste them as
needed throughout the Logic Tree.
To cut or copy a Logic Tree node:
On the Logic Tree page, in the diagram canvas, right-click the Logic Tree node
that you want to cut or copy, and on the shortcut menu, click the Copy or Cut
option.
If you are copying a Logic Tree node that has successor nodes, a message
appears, asking if you also want to copy the successor nodes. Click the
Yes button to copy the successor nodes, or click the No button to copy the
predecessor node and leave the successor nodes.
Note: When you copy a Hypothesis node, if the RCA Hypothesis record is linked to RCA
Verification records, the verifications for that Hypothesis node will also be copied. When
you paste the Hypothesis node, new RCA Hypothesis and RCA Verification records will
be created and will contains the same information as the source records.
If you are cutting a Logic Tree node that has successor nodes, the
successor nodes will also be cut.
If the selected Logic Tree node does not have successor nodes, the
selected node is copied to the clipboard.
To paste a copied node:
On the Logic Tree page, in the diagram canvas, right-click the node onto which
you want to paste the copied node, and on the shortcut menu, click Paste.
If the selected node is a valid location to paste the copied or cut node, the
nodes that were copied or cut appear in the levels below the selected node.
If the selected node is not a valid location to paste the copied or cut node,
nothing happens. You will need to select a different location to paste the
node(s).
Managing Reference Document Records

for Logic Tree Nodes
In some cases it may be necessary to attach additional information to nodes in the Logic
Tree. You can do so by creating a Reference Document record and linking it to the record
for the desired node.
To manage Reference Document records for nodes in the Logic Tree:
1. On the Logic Tree page, in the diagram canvas, double-click the node to which
you want to add a reference document.
The associated record appears on the Properties tab in the Options pane. The following
image is an example of an RCA Hypothesis datasheet as it appears on the Properties tab
when you double-click a Hypothesis node.

3. Configure reference documents as desired.
Deleting Nodes from the Logic Tree

When you delete a node from the Logic Tree, the associated record is deleted from the
database. Any node except the Failure Event Node can be deleted from a Logic Tree.
To delete a node from the Logic Tree:
1. On the Logic Tree page, in the diagram canvas, right-click the node that you want
to delete.
A highlighted square appears around the node, indicating that the node has been selected,
and a shortcut menu appears.
2. On the shortcut menu, click Delete.

-ORPress the Delete key.
A message appears, asking if you really want to delete the selected node and its successor
nodes (if any).
3. Click the Yes button to delete the selected node and its successors (if any).
The record associated with the node is deleted from the database, and the node no longer
appears in the Logic Tree.
Additionally, the link that existed between the record associated with the deleted node
and the node to which it was linked are removed.
Changing the Tree View

When you begin creating a Logic Tree, the tree is displayed vertically by default. If
desired, you can view the Logic Tree horizontally. For example, the following image
shows a Logic Tree that is displayed using the default setting:
...and this image shows the same Logic Tree after the view has been changed to
horizontal:
To change the tree view:
1. On the Logic Tree page, on the Tree Tasks menu, click the Settings link.
A submenu appears, displaying a list of options that let you modify the settings on the
Logic Tree.
A bullet appears to the left of the Horizontal View or Vertical View option to indicate the
current setting.
2. Click the option that corresponds to the view that you want to apply to the Logic
Tree (i.e., Horizontal or Vertical).
The Logic Tree is displayed using the selected view.
Displaying the Logic Tree on a Full

Screen
The full screen view of the Logic Tree is useful for showing the Logic Tree in a
presentation.
To display the Logic Tree on a full screen:
On the Logic Tree page, on the Tree Tasks menu, click the Full Screen link.
The Logic Tree appears on a full screen. All of the options available from the right-click
menus in normal mode are also available in the full screen mode.
To return to normal mode from the full screen mode:
Press the Esc key.
-orRight-click the Logic Tree diagram, and clear the Full Screen option.
Zooming In and Out on the Logic Tree

You can adjust the size of the Logic Tree diagram by zooming in and out on the Logic
Tree.
To zoom in and out of the Logic Tree:
1. On the Logic Tree page, in the Options pane, click the Tree Appearance tab.
The Tree Appearance tap appears, displaying tree appearance options that can be
modified.
Note: You can also right-click the diagram canvas, point to Zoom, and click the desired
percentage on the submenu.
2. Click the Zoom indicator, and drag it to the right or left to adjust the view size as
desired.
The view becomes larger or smaller as appropriate.
Applying a Different Line Style

You can change the style type of the lines that join the nodes on the Logic Tree. The style
is set to Bezier by default.
To change the line style:
modified.
2. Expand the Line Style list, and select a different line style. You can select any of
the following options:
Orthogonal
Rounded
Straight
The line style is applied to the Logic Tree, and the system saves the Logic Tree with the
selected line style. The next time that you view the Logic Tree for the current RCA
Analysis, the selected style appears.
Changing the Color of the Logic Tree

Section
The default color of the diagram canvas is white. If desired, you can change the color of
the diagram canvas.
To change the color of the diagram canvas:
modified.
2. In the Window Color field, click the

The Color dialog box appears.
button.
3. Select the color that you want to use for the background from the color palette, or
specify a custom color, and click OK.
The diagram canvas is displayed using the selected color.
Changing the Spacing for Levels and

Nodes
The following instructions provide details on changing the spacing between the levels
and individual nodes in the Logic Tree.
To change the spacing for levels and nodes:
modified.
2. In the Spacing section, in the Levels field, use the

The default setting is 90.
buttons to select a number.
3. In the Spacing section, in the Nodes field, use the

The default setting is 90.
buttons to select a number.
Changing the Size and Color of the Font

If desired, you can change the color and size of the text displayed in the Logic Tree.
To change the font color:
modified.
2. In the Node Label section, click the

The Color dialog box appears.
button in the Font Color field.
3. Select the desired font color from the color palette, or specify a custom color, and
click OK.
The text is displayed using the selected font color.
To change the font size:
modified.
2. In the Node Label section, expand the Font Size list, and select a number. The
default setting is 8.
The text is displayed using the selected font size.
Resetting the Logic Tree to Display

Default Settings
If desired, after you have changed the appearance of the Logic Tree, you can reset the
Logic Tree and display it using the default settings. The following image shows the
default appearance settings for the Logic Tree.
To return the Logic Tree to its default appearance:

2. On the Tree Appearance tab, click the Default button.
A confirmation message appears, asking if you really want to reset the Logic Tree to its
default appearance.
The Logic Tree is displayed using the default appearance settings.
Accessing the Overview Map

The Overview Map is useful when you are working with a large Logic Tree. The
Overview Map displays an aerial view of the Logic Tree so that you can quickly locate
and zoom in on specific sections of the Logic Tree.
To display the Overview Map window and use it to work with the Logic Tree:
On the Logic Tree page, on the Tree Tasks menu, click the Overview Map link.
The Overview Map window appears.
The Logic Tree appears in a box in the upper left corner of the Overview Map window.
The box that appears around the Logic Tree indicates the scope of the area that is
currently magnified in the diagram canvas. You can move the magnifying box to various
locations on the tree and the diagram canvas will display that portion of the tree.
You can resize the window by clicking the frame and dragging it to the desired size. To
close the Overview Map window, click the X button in the upper-right corner of the
window. After you close the Overview Map window, the area that you were magnifying
will continue to be displayed in the diagram canvas.
Using the Overview Map

The Overview Map is a tool that you can use to quickly locate specific areas of the Logic
Tree, magnify them, and then modify them as desired. You can use your pointer to change
the size of the magnifying box to select the areas on the Logic Tree that you want to
magnify.
For example, you can change the size of the magnifying box to only display one node at a
time, which lets you navigate around the Logic Tree, while seeing only the magnified
node in the diagram canvas.
For example, the following image shows the Overview Map window when it was first
accessed via the Tree Tasks menu.
This image shows the Overview Map window after it changed the size of the magnifying
box:
...and this image shows a node that is highlighted in the Overview Map as it appears in
the diagram canvas:
The size of the magnifying box determines the magnification that is applied to the area
that appears inside the box. The smaller the box, the greater the magnification level,
meaning the image will appear larger in the diagram canvas (taking up more screen
space). The larger the box, the lower the magnification level, meaning the image will
appear smaller.
Additionally, when you pause on the lines that define the magnifying box, your pointer
looks like the following image, which indicates that you can move the magnifying box.
When your pointer looks like the following image, it indicates that you can draw your
own magnifying box.
To draw a magnifying box on the Overview Map window:

1. Point to an area on the Overview Map window (other than the lines that define the
current magnifying box).
Your pointer appears as an arrow.
2. Press and hold your mouse button, and drag the pointer to the desired size.
As you drag the pointer, a box appears and grows larger or smaller with your
movements.
3. Release the mouse button when the magnifying box is the desired size (i.e.,
magnification).
The magnifying box that you drew appears in the Overview Map. You can move the
magnifying box around the Logic Tree in the Overview Map to magnify that area in the
diagram canvas. The diagram canvas displays the selected area at the magnification level
that corresponds to the size of the magnifying box.
Note: You cannot re-size a magnifying box after it has been drawn. If you want to change
the size of a magnifying box, you will need to draw a new magnifying box.
To select areas on the Logic Tree that you want to magnify:
1. Pause on the magnifying box.
Your pointer appears as a four-way arrow.
2. Press and hold your mouse button, and drag your pointer until the magnifying box
is in the desired location in the Logic Tree.
The diagram canvas displays the selected area at the magnification level that corresponds
to the size of the magnifying box.
Exporting Logic Trees
You can export a Logic Tree as an image and save it to another location, such as your
local hard drive.
The exported image will match the current expanded/collapsed state of the Logic
Tree. For example, the image will display each node as it is shown in the tree at
the time of the export. Expanded nodes will be expanded; collapsed nodes will be
collapsed.
Regardless of the zoom factor that is currently applied to the Logic Tree, the
entire tree will be included in the image, even if it part of the tree is cut off at the
time you perform the export. The zoom factor will, however, affect the size of the
image that is exported.
To export a Logic Tree:

1. On the Logic Tree page, on the Tree Tasks menu, click the Export Tree link.
The Export Logic Tree dialog box appears.
2. Navigate to the location to which you want to save an image of the tree.
3. In the File Name text box, type a name for the file.
4. In the Save as type list box, select the desired file type. You can choose from:
Bitmap (.BMP)
Graphics Interchange Format (.GIF)
Joint Photographic Experts Group (.JPG)
Portable Network Graphics (.PNG)
Tag Image File Format (.TIF)

The Logic Tree is saved to the selected location as the selected image type.
About Communicating Findings and

Implementing Recommendations
After the RCA Analysis Team has successfully identified the root cause of the equipment
or location failure, the next step involves communicating the team's findings and
proposing recommendations to the appropriate individuals within your organization. To
do so, you can use the Communicate Records page to:
Complete the fields on the RCA Communicate datasheet to define the failure
mechanism and acknowledge those who participated in the RCA Analysis but
who were not members of the RCA Analysis Team.
Create RCA Recommendation records and link them to the RCA Analysis record.
RCA Recommendation records contain proposed solutions called
recommendations that identify the changes in work processes that can be used to
avoid or prepare for future failures.
Generate reports to communicate the team's findings. These reports can be
published and distributed to other members of your organization.
After you have successfully communicated the team's findings and the proposed
recommendations have been approved, the recommendations should then be implemented
within the organization.
After the recommendations have been implemented, the team should continue to track the
success of the implemented solution through RCA Tracking Item records.
Accessing the Communicate Records

Page
You can access the Communicate Records page via the Communicate menu on any of the
following pages:
Analysis page.
Preserve Failure Data page.
Critical Success Factors page.
Event Diagram page.
Logic Tree page.
To access the Communicate Records page:
On the Communicate menu, click the Communicate Records link.
The Communicate Records page appears.
Overview of the Communicate Records

Page
The Communicate Records page consists of:
The RCA Communicate datasheet for the RCA Analysis record, as shown in the
following image.
This datasheet appears at the top of the page and contains fields that allow you to
complete the RCA Analysis record. The RCA Communicate datasheet contains the same
fields as the RCA Analysis datasheet with two exceptions: the Mechanism field and the
Acknowledgments field. You should complete these fields on the RCA Communicate
datasheet to communicate the results of the RCA Analysis.
The Recommendations section, which appears at the bottom of the page and
displays a list of RCA Recommendation records that are associated with the RCA
Analysis. The following image shows an example of the Recommendations
section.
You can use RCA Recommendation records to record and track the progress of
recommendations. For each RCA Recommendation record, the following information
appears:
Recommendation Headline: A short description of the recommendation.
Assigned To: The name of team member who is responsible for the
completing the solution outlined in the RCA Recommendation record.
Target Completion Date: The date by which the recommendation should

be implemented.
Implemented Date: The date on which the recommendation was

completed. This field will be populated with a value only for
recommendations that have been completed.
For tracking purposes, the Assigned To, Target Completion Date, and the Implemented
Date columns are color-coded according to due date:
Yellow: Indicates that the RCA Recommendation record is due in two

weeks or less. When the row containing a RCA Recommendation record is
colored yellow, the value in the Target Completion Date column is within
14 days of the current date.
Red: Indicates that the RCA Recommendation record is overdue. When

the row containing the RCA Recommendation record is colored red, the
value in the Target Completion Date column is on or before the current
date.
Green: Indicates that the RCA Recommendation record has been

completed.
No color: Indicates that the RCA Recommendation record does not meet
any of the conditions described above.
In addition, the Communicate Records page provides the following task menus, which
give you access to functions associated with the RCA Analysis: Manage Assets,
Common Tasks, PReserve, Order, Analyze, Communicate, Track, and Associated Pages.
Note: Items appear on the Associated Pages menu only if they have been configured for
the RCA Analysis family.
Manage Assets Menu

The Manage Assets menu on the Communicate Records page contains the following link:
RCA analysis.
Common Tasks Menu

The Common Tasks menu on the Communicate Records page contains the following
links:
New Recommendation: Displays the Recommendation Details page, where you

can create a new RCA Recommendation record to link to the current RCA
Analysis.
Copy Recommendation: Creates a copy of the selected record on the
Recommendation Details page, where you can modify the recommendation and
save it to the current RCA Analysis.
Delete Recommendation: After displaying a confirmation message, deletes the

selected RCA Recommendation record. This link is enabled only when an RCA
Recommendation record is selected in the Recommendations section at the bottom
of the page.
Page.
Help: Displays the context-sensitive Help topic for the Communicate Records
page.
PReserve Menu
The PReserve menu on the Communicate Records page contains the following link:
RCA Preserve Item records for the current RCA Analysis.
Order Menu
The Order menu on the Communicate Records page contains the following links:
displays existing RCA Critical Success Factor records that are linked to the
modify the Team Charter for the current RCA Analysis.
Team: Displays the Team page, where you can view and modify the RCA Team
Analyze Menu
The Analyze menu on the Communicate Records page contains the following links:
Event Diagram: Displays the Event Diagram page, where you can create an Event
Diagram for the current RCA Analysis.
Logic Tree: Displays the Logic Tree page, where you can create a Logic Tree
diagram for the current RCA Analysis.
Communicate Menu
The Communicate menu on the Communicate Records page contains the following links:
linked to it.
have been configured for Root Cause Analysis.
Track Menu
The Track menu on the Communicate Records page contains the following link:
Track: Displays the Analysis Tracking Items page, where you can view a list of
RCA Tracking Item records that are linked to the current RCA Analysis.
Completing the RCA Communicate

Datasheet
The Communicate Records page displays the RCA Communicate datasheet, which is one
of the datasheets available for the RCA Analysis family. The RCA Communicate
datasheet lets you record details about a completed RCA Analysis. You will need to
complete the RCA Communicate datasheet after a root cause has been determined.
The following fields are unique to the RCA Communicate datasheet and you should
complete these fields to communicate the results of the team's analysis:
Mechanism: A brief description of the failure mechanism that was involved in the
failure event that was analyzed, including the root causes that were found as a
result of the RCA Analysis. This description outlines the "links of the chain" that
led to the event.
Acknowledgements: A list of people who are not members of the RCA Analysis
Team but who contributed expertise to the RCA Analysis. You may want to
include, for example, the company name and the name and position of each
person who contributed to the development of the hypotheses, root cause, and
recommendations for the pump failure that was analyzed.
To complete the RCA Communicate datasheet:

1. Access the Communicate Records page.
The Communicate Records page appears, displaying the RCA Communicate datasheet. A
red outline has been added to the following image to highlight the RCA Communicate
datasheet.
2. On the RCA Communicate datasheet, complete the Mechanism and

Acknowledgements fields as desired.
3. On the datasheet toolbar, click the Save current record icon.
Viewing and Modifying Values on the

RCA Communicate Datasheet
If desired, you can view and modify the values on the RCA Communicate datasheet.
To view and modify values on the RCA Communicate datasheet for an RCA Analysis:
1. Access the Communicate Records page.
The Communicate Records page appears, displaying the RCA Communicate datasheet at
the top of the page. A red outline has been added to the following image to highlight the
RCA Communicate datasheet.
Note: When you access the Communicate Records page, the RCA Communicate
datasheet is displayed by default. If desired, you can select a different datasheet in the
Datasheet list to modify.
2. Modify the values in the fields as desired.
3. At the top of the datasheet, click the Save current record icon.
What is a Recommendation?
A recommendation is a suggested solution for preventing or lessening the impact of
future failures for the piece of equipment or location that the RCA Analysis Team is
analyzing, such as making changes to maintenance schedules or providing additional
training to operators. The RCA Analysis Team should develop these solutions based on
the evidence that was collected and the conclusions that were drawn in the Preserve and
Analyze steps of the RCA Analysis.
RCA Recommendation records store the details of the team's recommendation and
provide functionality that lets you send alert emails to the team member responsible for
implementing the recommendation. In this way, RCA Recommendation records represent
tasks assigned to team members. The following image is an example of a completed RCA
Recommendation datasheet, which stores the data that makes up an RCA
Recommendation record.
After the recommendation is completed, the value in the Status field of the RCA
Recommendation record can be marked as Implemented. The success of the implemented
recommendation, however, should continue to be tracked. If the piece of equipment or
location continues to fail after the recommendation has been implemented, the RCA
Recommendation record can be flagged for reevaluation.
About Equipment, Locations, and RCA

Recommendations
The details of the recommendations and the progress associated with getting the
recommendation approved and implemented can be tracked using fields in RCA
Recommendations records. When you create an RCA Recommendation record, a link is
created between the RCA Recommendation record and the RCA Analysis record. You can
then choose to link the RCA Recommendation record to an Equipment or Functional
Location record. Depending on the nature of the recommendation, RCA
Recommendation records may or may not be linked to the same Equipment and
Functional Location records that are linked to the RCA Analysis record.
For example, suppose you created an RCA Analysis for a piece of equipment called
Pump 1 that was shutting down more frequently than normal. You find that the pump is
one of several pumps that are more than 10 years old. You create an RCA
Recommendation record to increase inspection rounds for Pump 1. Although the RCA
Analysis was performed for Pump 1, another similar pump, Pump 2, is the same age. You
can create a new RCA Recommendation record and populate the value in the Equipment
ID field to Pump 2 so that the same recommendation can be applied.
Furthermore, if the Equipment record Pump 1 is already linked to the Functional
Location record Row 12, you can change the value in the Functional Location ID field of
the RCA Recommendation record from Row 12 to reflect a higher level Functional
Location record, such as Statesville Plant. This value can serve as an indicator that pumps
located at the Statesville Plant are older than other plants, which is more relevant than the
information that Pump 1 is located in a certain row.
Workflow for Proposing and

Implementing Recommendations
RCA Analysis and the fields in the RCA Recommendation record facilitate the following
general workflow for proposing and implementing recommendations:
1. After a hypothesis is proven true and a root cause is identified, the RCA Analysis
Team discusses possible solutions.
2. After a recommendation has been developed, the analysis team creates an RCA
Recommendation record from the analysis. When the RCA Recommendation
record is created, the value in the Status field is Created by default.
3. The Analysis Team defines the details of the recommendation in the RCA
Recommendation record. If the recommendation is specific to a piece of
equipment or location, the Analysis Team can define values in the Equipment ID
and Functional Location ID fields to link the RCA Recommendation record to the
Equipment or Functional Location records that represents that equipment and
locations.
4. After the RCA Recommendation record is created to track the progress of the
recommendation, an RCA Analysis Team member proposes the recommended
solution to the decision makers in your organization using the details stored in the
RCA Recommendation record.
5. Your organization make decisions about the recommendation (e.g., approve or
reject), and the necessary fields (including the Status field) in the RCA
Recommendation record are updated to reflect these decisions.
6. After a recommendation has been approved (i.e., the value in the Status field is
changed to Approved), it should be implemented within your organization. Alert
emails can be scheduled and sent to the team member responsible for
implementing the recommendation.
7. In order to implement the recommendation, you can create a work request in a
maintenance management system (e.g., an SAP Notification, an Oracle EBS eAM
Work Request ) by setting the value in the Create Work Request field in the RCA
Recommendation record to True.
8. After the recommendation is implemented, the value in the Status field in the
RCA Recommendation record should be changed to Implemented, and the RCA
Recommendation record is considered complete.
Note: This step is part of the Tracking and Reevaluating Analysis Results step in an RCA
Analysis.
8. If the piece of equipment or location continues to fail, the RCA Recommendation
record should be flagged for reevaluation via the Alert tab on the RCA
Recommendation datasheet.
9. The team should meet to discuss the implemented recommendation, propose new
recommendations, amend the original recommendations, and so on until an
implemented solution prevents the piece of equipment or location from failing in
the same manner that triggered the RCA Analysis.
Creating RCA Recommendation

Records
After the RCA Analysis Team has developed a recommended solution for preventing
future failures of the piece of equipment or location, a team member should create an
RCA Recommendation record to store the details of the recommendation.
To create a new RCA Recommendation record:

1. On the Communicate Records page, on the Common Tasks menu, click the New
Recommendation link.
The Recommendation Details page appears, displaying the RCA Recommendation
datasheet. The General Information tab is selected by default.
2. On the General Information tab, enter the appropriate values into the available
fields. The Target Completion Date and Assigned To Name fields are required.
3. If the recommendation is specific to a piece of equipment or location, define
values in the Equipment ID and Functional Location ID fields to link the RCA
Recommendation record to the Equipment or Functional Location records that
represent that piece of equipment or location.
1.
o
If a recommendation is specific to an piece of equipment, you should

define a value in the Equipment ID field first. If the Equipment record you
choose is linked to a Functional Location record, the Functional Location
ID field will be populated automatically with the value in the Functional
Location field of that Equipment record.
If the Equipment record is not linked to a Functional Location record or

you want to define a different Functional Location record, you can then
define a value in the Functional Location ID field.
Note: If you define a value in the Functional Location ID field before you define a value
in the Equipment ID field, it may be overwritten when you define a value in the
Equipment ID field.
If you want to schedule a recommendation alert email to be sent to a specified recipient,
click the Alert tab, and enter the appropriate information on the datasheet.
4. On the Common Tasks menu, click the Save Recommendation link.
The RCA Recommendation record is saved to the database and linked to the RCA
Analysis record for the current RCA Analysis, and the Communicate Records page
appears.
Copying RCA Recommendation

Records
After the RCA Analysis Team has recorded proposed solutions for a piece of equipment
or location in an RCA Recommendation record, the RCA Recommendation record can be
copied and linked to other Equipment or Functional Location records that identify
equipment and locations that require the same actions to be taken. You can also copy an
RCA Recommendation record and modify it in order to create a second RCA
Recommendation record for the same piece of equipment or location.
To copy an RCA Recommendation record:
1. On the Communicate Records page, select an RCA Recommendation record that
you wish to copy from the Recommendations grid.
2. On the Common Tasks menu, and click the Copy Recommendation link.
The Recommendation Details page appears, displaying a copy of the RCA
Recommendation record you selected. The values in all fields displayed on the General
Information and Alert tabs are copied except for the Recommendation ID field, which is
populated automatically with a unique ID, and the Recommendation Description field.
2. Modify the fields on the RCA Recommendation datasheet as needed.

3. If you want to apply the recommendation to another piece of equipment or
location, define values in the Equipment ID and Functional Location ID fields to
link the RCA Recommendation record to the Equipment or Functional Location
records that represent that piece of equipment or location.
1.
o
If a recommendation is specific to a piece of equipment, you should define

a value in the Equipment ID field first. If the Equipment record you
choose is linked to a Functional Location record, the Functional Location
ID field will be populated automatically with the value in the Functional
Location field of that Equipment record.
If the Equipment record is not linked to a Functional Location record or

you want to define a different Functional Location record, you can then
define a value in the Functional Location ID field.
Note: If you define a value in the Functional Location ID field before you define a value
in the Equipment ID field, it may be overwritten when you define a value in the
Equipment ID field.
The RCA Recommendation record is saved to the database and linked to the RCA
Analysis record for the current RCA Analysis, and the Communicate Records page
appears.
Opening an Existing RCA

After an RCA Recommendation record has been created, you can open the record to view
and modify the contents. At least the team member responsible for implementing the
recommendation will need to update the RCA Recommendation record with current
information. For example, if a recommendation is rejected by management, the Status
field should be updated to reflect this decision.
To open an existing RCA Recommendation record:
On the Communicate Records page, in the Recommendations section, in the

Recommendation Headline column, click the link associated with the RCA
Recommendation record that you want to view.
The selected RCA Recommendation record appears on the Recommendation Details

page, where you can view and modify the record as desired.
Aspects of the Recommendation Details

Page
The Recommendation Details page displays the details of an RCA Recommendation
record. When you open an existing RCA Recommendation record or create a new RCA
Recommendation record, it appears on the Recommendation Details page. The main
display area contains the RCA Recommendation datasheet, which contains the General
Information and Alerts tabs. You can use the fields in the datasheet to record information
associated with the RCA Recommendation record.
The task menu pane on the Recommendation Details page contains the same task menus
as the Communicate Records page:
Manage Assets
Common Tasks
PReserve
Order
Analyze
Communicate
Track
Associated Pages
Note: The Associated Pages menu on the Recommendation Details page displays links
only if they have been configured for the RCA Recommendation family via the URL
Manager.
Deleting RCA Recommendation

Records
To delete a RCA Recommendation record:

1. On the Communicate Records page, in the Recommendations area, select the row
that contains the RCA Recommendation record that you want to delete.
2. On the Common Tasks menu, click the Delete Recommendation link.
A confirmation message appears, asking if you really want to delete the record.
3. Click the Yes button to delete the selected record.
The selected record is deleted from the database and no longer appears in the
Recommendations section. Additionally, the link that existed between the RCA
Recommendation record and the RCA Analysis record is removed.
About RCA Reports

The RCA baseline module provides a set of baseline reports that display data from RCA
Analyses. You can access these reports via the Reports List page. If desired, you can also
create your own custom reports and make them available from the Reports List page.
Accessing the List of RCA Reports

You can access the list of RCA reports via the Communicate menu on any of the
following pages:
Analysis page
Team page
Event Diagram page
Logic Tree page
Analysis Tracking Items page
To access the list of RCA reports:
On the appropriate page, on the Communicate menu, click the Reports link.
The Reports List page appears, displaying a list of links to all the available RCA reports.
Overview of the Reports List Page

The Reports List page is divided into two sections:
Master Report: Displays the Catalog caption, formatted as a hyperlink, of the

main report Comprehensive Analysis Report. You can click the link to run this
report, which is stored in the Catalog folder
\\Public\Meridium\Modules\RCA\SSRS along with the subreports that support the
main report.
Note: To ensure that you will be able to run the report, you should not delete or rename
any of the reports or queries that exist by default in the folder
\\Public\Meridium\Modules\RCA\SSRS.
Individual Reports: Displays the Catalog captions of all reports that exist in the
Catalog folder \\Public\Meridium\Modules\RCA as links. This list includes any
baseline reports provided with the Root Cause Analysis product and any custom
reports that you have saved in this location.
You can click any hyperlink on the Reports List page to open the associated report on the
Report Viewer page, where all standard reporting functionality will be available to you.
The Reports List page contains the following task menus:
Manage Assets
Common Tasks
PReserve
Order
Analyze
Communicate
Track
Manage Assets Menu

The Manage Assets menu on the Reports List page contains the following link:
RCA analysis.
Common Tasks Menu

The Common Tasks menu on the Reports List page contains the following links:
Page.
Help: Displays the context-sensitive Help topic for the Reports List page.
PReserve Menu
The PReserve menu on the Reports List page contains the following link:
RCA Preserve Item records for the current analysis.
Order Menu
The Order menu on the Reports List page contains the following links:
displays existing RCA Critical Success Factor record that are linked to the current
RCA Analysis.
Team: Displays the list of Team page, where you can view the RCA Team
Analyze Menu
The Analyze menu on the Reports List page contains the following links:
Event Diagram: Displays the Event Diagram page. If this is the first time that you
have accessed the Event Diagram page for a given RCA Analysis, the RCA Event
dialog box will appear automatically so that you can define an RCA Event record
and link it to the current RCA Analysis.
you can organize the process of analyzing the issue to evaluate the possible causes
of the failure being analyzed.
Communicate Menu
The Communicate menu on the Reports List page contains the following links:
linked to it.
Reports: Displays the Reports List page. This link is available on other pages in
Root Cause Analysis that let you navigate to the Reports List page.
Track Menu
The Track menu on the Reports List page contains the following link:
Track: Displays the Analysis Tracking Items page. This link is available on other
pages in Root Cause Analysis that let you navigate to the Analysis Tracking Items
page.
About Opening an RCA Report

You can open any of the following RCA reports from the Report List page:
The baseline comprehensive report.
Any baseline topic-specific report.
Any customized report that exists in the following Catalog folder:

Opening the Comprehensive Analysis

Report
The Comprehensive Analysis Report is comprised of multiple subreports. When you open
the report, you can select which subreports you want to display and which ones you do
not.
To open the Comprehensive Analysis Report, you must have View privileges to all
families included in the underlying queries and datasets. You will must also have View
and Update privileges to the RCA Image family.
Note: If this is the first time the Comprehensive Analysis Report has been opened by
ANY user, that user must have View, Update, and Insert privileges to the RCA Image
family to view the report.
To open the Comprehensive Analysis Report:
1. On the Reports List page, click the hyperlinked caption of the Comprehensive
Analysis Report.
The Comprehensive Analysis Report dialog box appears.
The Comprehensive Analysis Report dialog box contains multiple options, which
correspond to subreports that can be included in the Comprehensive Analysis Report. All
of the options are selected by default. You can modify these selections as desired. The
options that are selected will persist for the current user, which means if you clear any of
the check boxes, the next time that you access the report, your previous selections will be
retained.
2. Clear the check box next to any item that you want to exclude from the report.
The following table describes the options that are displayed in the Comprehensive
Analysis Report dialog box and the corresponding section in the report.
Window Option
Report Section
Preserve
A description of the Preserve stage of a Root Cause

Analysis.
Data Collection
A list of the RCA Preserve Item records that are included

in the RCA Analysis.
Data Collection File

Links
A list of the Reference Document records that are linked to

the RCA Preserve Item records that are included in the
RCA Analysis.
Order
A description of the Order stage of a Root Cause Analysis.
Team Member
A list of the RCA Analysis Team members.
Critical Success
Factors
A description of the analysis Team Charter, a list of the

critical success factors that are included in the RCA
Analysis, and a list of the important dates associated with
the RCA Analysis.
Analyze
A description of the Analyze stage of a Root Cause
Analysis.
Event Diagram
An image of the Event Diagram.
Logic Tree
An image of the Logic Tree.
Verification Log
A list of the RCA Verification records, which are included


Verification File Links the RCA Verification records, which are included in the
RCA Analysis.
Communicate
A description of the Communicate stage of a Root Cause

Analysis.
Event and Cause

Summaries
A description of the event that is being analyzed and a

description of the team's findings. These descriptions
reflect the values in the Event Narrative and Mechanism
fields of the RCA Analysis record.
Executive Summary
A list of the RCA Recommendation records that are
Recommendations
included in the RCA Analysis.

Recommendation File
the RCA Recommendation records that are included in the
Links
RCA Analysis.
Acknowledgements
A description of the acknowledgements included in the

RCA Analysis. This description reflects the value in the
Acknowledgements field, which appears on the RCA
Communicate datasheet on the Communicate Records
page.
Track
A description of the Track stage of a Root Cause Analysis.
Tracking Items
Summary
A list of the RCA Tracking Item records that are included

Analysis-At-A-Glance A description of the Overview section of the report.

An overview of the RCA Analysis, including:
Overview
The name of the RCA Analysis.

The Principal Analyst.
The analysis start date.
The estimated completion date.
The estimated cost of the event.
The number of items that have been created,

completed or assigned to RCA Analysis Team
Members (e.g., RCA Preserve Item records).
3. If you want to include Reference Documents in the report, click the Reference
Documents link.
Note: The check box to the left of the Reference Documents link will be selected if one or
more reference documents are already included in the report. You can click the Reference
Documents link to see which ones are already included.
The Select Reference Documents dialog box appears.
4. In the list of available references documents, select the check box to the left of
any reference document that you want to include in the report. If a reference
document is already included in the report, the check box to the left of its
Document ID will already be selected. You can select the check box in the upper,
left corner of the grid to include ALL reference documents. The list contains
Reference Document records that are linked to any of the following records in the
RCA Analysis:
RCA Analysis
RCA Event
RCA Failure Mode
RCA Hypothesis
RCA Logic Gate
RCA Preserve Item
RCA Recommendation
RCA Team Member
RCA Tracking Item
RCA Verification
Note: Only image files with the file extensions JPEG, BMP, GIF, and PNG are supported
by the Comprehensive Analysis report. If other types of reference documents are
associated with the analysis, they will not be displayed in the list. Of no reference
documents are available, the list will be empty.
5. Click OK.
The Select Reference Documents dialog box closes, and the Comprehensive Analysis
dialog box returns to focus.
6. Click OK.
The report is generated and appears in the Report Viewer.
Opening an Individual Report

To open an individual report:
On the Reports List page, in the Individual Reports section, click the hyperlinked
caption of the desired report.
The report you selected appears in the Report Viewer.
About Available Reports

The baseline RCA module provides the following types of baseline reports for use with
the RCA product:
Comprehensive: The Comprehensive Analysis Report includes information about

the entire RCA Analysis. You can customize the data that appears in the report to
display data associated with all stages of the RCA Analysis. The Comprehensive
Analysis Report is stored in the following folder in the Meridium APM
Catalog: \\Public\Meridium\Modules\RCA\SSRS.
Important: This report report is built from the queries and reports stored in the SSRS
folder. You should not change the name of the SSRS Catalog folder, the name or content
of any item within the folder, or remove from the folder any item that is being used by the
comprehensive report. Modifying or moving any of these items could cause the
Comprehensive Analysis Report to stop working.
Individual: Multiple reports that display data associated with specific areas of an
RCA Analysis. The individual reports are stored in the Meridium APM Catalog
folder \\Public\Meridium\Modules\RCA. Keep in mind that the Reports List page
displays all reports that are stored in the RCA folder.
Note: All items in the Public folder are also available in the corresponding Baseline
folder. Throughout this documentation, however, we refer to items in the Public folder.
Components of the Comprehensive

Analysis Report
The Comprehensive Analysis Report contains the following components:
Cover Page
Topics Included in this Report
Preserve (5 P's)
Data Collection
Data Collection File Links
Order
Team Members
Charter
Critical Success Factors
Analyze
Event Diagram
Logic Tree
Verification Logs
Verification Log File Links
Communicate
Event Summary
Summary of Findings
Executive Summary Recommendations
Recommendation File Links
Acknowledgements
Track
Tracking Item Summary
Analysis-At-A-Glance
PROACT RCA Analysis-At-A-Glance Overview
Cover Page
The cover page of the Comprehensive Analysis Report displays introductory information
for the Comprehensive Analysis Report. The cover page is always included in the
Comprehensive Analysis Report. The cover page cannot be excluded from the report.
The following image shows an example of the cover page as it appears in the
Comprehensive Analysis Report for the example RCA Analysis. The cover page displays
the name of the report, which is always Comprehensive Analysis Report, and the
following information:
Analysis Name: The name of the RCA Analysis. This value is stored in the
Analysis Name field of the RCA Analysis record.
Principal Analyst: The name of the Principal Analyst. This value is stored in the
First Name and Last Name fields of the Human Resource record that is linked to
the RCA Team Member record that contains the value Principal Analyst.
Printed: The date on which the report was generated.
Topics Included in this Report

The Topics Included in this Report section of the Comprehensive Analysis Report
displays the titles of the sections that are included in the Comprehensive Analysis Report,
much like a table of contents. The titles of the sections correspond to the check boxes that
you select on the Comprehensive Analysis Report dialog box. The Topics Included in
this Report section will always be included in the Comprehensive Analysis Report and
cannot be excluded from the report.
The following image shows an example of the Topics Included in this Report section as it
appears in the Comprehensive Analysis Report for the example RCA Analysis.
Note: In this image, all possible sections for the Comprehensive Analysis Report appear
in the list because ALL the check boxes were selected on the Comprehensive Analysis
Report dialog box.
Preserve (5P's)
The Preserve (5P's) section of the Comprehensive Analysis Report displays a description
of the PReserve step of a Root Cause Analysis. This section will be included in the report
when you select the Preserve check box on the Comprehensive Analysis Report dialog
box.
The following image shows an example of the Preserve (5P's) section as it appears in the
Comprehensive Analysis Report for the example RCA Analysis.
Data Collection
The Data Collection section of the Comprehensive Analysis Report displays information
that is stored in each RCA Preserve Item record that is linked to the RCA Analysis record.
It also displays information stored in the Human Resource record that is linked to the
RCA Team Member record that is linked to each RCA Preserve Item record. This section
will be included in the report when you select the Data Collection check box on the
Comprehensive Analysis Report dialog box.
The following image shows an example of the Data Collection section as it appears in the
The following table lists each item in the Data Collection section and the corresponding
RCA Preserve Item or Human Resource record field whose data is displayed in the
report.
Report Column
Record Family
Record Field
Category
RCA Preserve Item
Data Category
Data
RCA Preserve Item
Data to Collect
Strategy
RCA Preserve Item
Collection Strategy
Team Members
Human Resource
First Name, Last Name
Date
RCA Preserve Item
Date Due
Completed?
RCA Preserve Item
Completed?
Data Collection File Links

The Data Collection File Links section of the Comprehensive Analysis Report displays a
list of the Reference Document records that are linked to the RCA Preserve Item records
that are linked to the RCA Analysis record. This section will be included in the report
when you select the Data Collection File Links check box on the Comprehensive
Analysis Report dialog box.
The following image shows an example of the Data Collection File Links section as it
would appear in a Comprehensive Analysis Report.
The following table lists each item in the Data Collection File Links section and the
corresponding RCA Preserve Item, Human Resource, or Reference Document record
field whose data is displayed in the report.
Report Column
Record Family
Record Field
Category
RCA Preserve Item
Data Category
Data
RCA Preserve Item
Data to Collect
Team Members
Human Resource
Document Path
Reference Document
Document Path
ID
Reference Document
ID
Order
The Order section of the Comprehensive Analysis Report displays a description of the
Order step of a Root Cause Analysis. This section will be included in the report when you
select the Order check box on the Comprehensive Analysis Report dialog box.
The following image shows an example of the Order section as it appears in the
Team Members
The Team Members section of the Comprehensive Analysis Report displays information
that is stored in Human Resource records that are linked to RCA Team Member records
that are linked to the RCA Analysis record. This section will be included in the report
when you select the Team Members check box on the Comprehensive Analysis Report
dialog box.
The following image shows an example of the Team Members section as it appears in the
Note: In order for a team member's information to appear in the Comprehensive Analysis
Report, in addition to the Human Resource record, the Team Member must also have a
Security User record. Using the Meridium APM Framework, you can promote a Human
Resource record to a Security User record.
The following table lists each item in the Team Members section and the corresponding
Human Resource record field whose data is displayed in the report.
Report
Item
Record Field Notes
Principal
Analyst
First Name,
Last Name
These values are stored in the Human Resource record that is

linked to the RCA Team Member record that contains the
value Principal Analyst.
Name
First Name,
Last Name
None
Facility
Facility
None
E-mail
Email
Address
None
Phone
Phone1
None
Charter
The Charter section of the Comprehensive Analysis Report displays the value that is
stored in the Charter field of the RCA Analysis record. This section will be included in
the report when you select the Critical Success Factors check box on the Comprehensive
The following image shows an example of the Charter section as it appears in the

The Critical Success Factors section of the Comprehensive Analysis Report displays
information that is stored in RCA Critical Success Factor records and important dates that
are stored in the RCA Analysis record (e.g., the start date and publish date). This section
will be included in the report when you select the Critical Success Factors check box on
the Comprehensive Analysis Report dialog box.
The following image shows an example of the Critical Success Factors section, outlined
in red, as it appears in the Comprehensive Analysis Report for the example RCA
Analysis.
The following table lists each item in the Critical Success Factors section and the
corresponding RCA Critical Success Factor or RCA Analysis record field whose data is
displayed in the report.
Report Item
Record Family
Record Field
CSF
Analysis Start Date
RCA Analysis
Start Date
Analysis End Date
RCA Analysis
End Date
Date Published
RCA Analysis
Date Published
Comments
RCA Analysis
Comments
Analyze
The Analyze section of the Comprehensive Analysis Report displays a description of the
Analyze step of a Root Cause Analysis. This section will be included in the report when
you select the Analyze check box on the Comprehensive Analysis Report dialog box.
The following image shows an example of the Analyze section as it appears in the
Event Diagram
The Event Diagram section of the Comprehensive Analysis Report displays an image of
the Event Diagram that exists for the RCA Analysis. This section will be included in the
report when you select the Event Diagram check box on the Comprehensive Analysis
Report dialog box.
The following image shows an example of the Event Diagram section as it appears in the
Logic Tree
The Logic Tree section of the Comprehensive Analysis Report displays an image of the
Logic Tree that exists for the RCA Analysis. This section will be included in the report
when you select the Logic Tree check box on the Comprehensive Analysis Report dialog
box.
The following image shows an example of the Logic Tree section as it appears in the
Verification Logs
The Verification Logs section of the Comprehensive Analysis Report displays information
that is stored in each RCA Verification record and the RCA Hypothesis record that is
linked to an RCA Verification record. It also displays information stored in the Human
Resource record that is linked to the RCA Team Member record that is linked to the RCA
Verification record. This section will be included in the report when you select the
Verification Logs check box on the Comprehensive Analysis Report dialog box.
The following image shows an example of the Verification Logs section as it appears in
the Comprehensive Analysis Report for the example RCA Analysis.
The following table lists each item in the Verification Log section and the corresponding
RCA Verification, RCA Hypothesis, or Human Resource record field whose data is
Report Column
Record Family
Record Field
Hypothesis
RCA Hypothesis
ID
Description
RCA Hypothesis
Description
Team Member
Human Resource
Verification Method
RCA Verification
Method
Outcome
RCA Verification
Outcome
Verification Log File Links

The Verification Log File Links section of the Comprehensive Analysis Report contains a
list of the Reference Document records that are linked to the RCA Verification records
that are linked to the RCA Analysis record. It also displays information stored in the
Human Resource record that is linked to the RCA Team Member record that is linked to
the RCA Verification record. This section will be included in the report when you select
the Verification Log File Links check box on the Comprehensive Analysis Report dialog
box.
The following image shows an example of the Verification Log File Links section as it
The following table lists each item in the Verification Log File Links section and the
corresponding RCA Verification, Human Resource, or Reference Document record field
whose data is displayed in the report.
Report Column
Record Family
Record Field
Method
RCA Verification
Method
Team Members
Human Resource
Document Path
Reference Document
Document Path
ID
Reference Document
ID
Communicate
The Communicate section of the Comprehensive Analysis Report displays a description
of the Communicate step of a Root Cause Analysis. This section will be included in the
report when you select the Communicate check box on the Comprehensive Analysis
Report dialog box.
The following image shows an example of the Communicate section as it appears in the
Event Summary
The Event Summary section of the Comprehensive Analysis Report displays the value
that is stored in the Event Narrative field in the RCA Analysis record. This section will be
included in the report when you select the Event and Cause Summaries check box on the
The following image shows an example of the Event Summary section as it appears in the
Summary of Findings
The Summary of Findings section of the Comprehensive Analysis Report displays the
value that is stored in the Mechanism field of the RCA Analysis record. This field is
labeled Summary of Findings on the RCA Communicate datasheet. This section will be
included in the report when you select the Event and Cause Summaries check box on the
The following image shows an example of the Summary of Findings section as it appears
in the Comprehensive Analysis Report for the example RCA Analysis.
Executive Summary Recommendations

The Executive Summary Recommendations section of the Comprehensive Analysis
Report displays information that is stored in RCA Recommendation records that are
linked to the RCA Analysis record. This section will be included in the report when you
select the Executive Summary Recommendations check box on the Comprehensive
The following image shows an example of the Executive Summary Recommendations
section as it appears in the Comprehensive Analysis Report for the example RCA
Analysis.
The following table lists each item in the Executive Summary Recommendations section
and the corresponding RCA Recommendation record field whose data is displayed in the
report.
Report Column
Record Field
Root Cause
Cause
Type
Cause Type
Recommendation
Recommendation Headline
Team Members
Assigned To Name, Assigned To User ID
Target Completion Date
Implemented Date
Implemented Date
Recommendation File Links

The Recommendation File Links section of the Comprehensive Analysis Report contains
a list of the Reference Document records that are linked to the RCA Recommendation
records that are linked to the RCA Analysis record. This section will be included in the
report when you select the Recommendation File Links check box on the Comprehensive
The following image shows an example of the Recommendation File Links section as it
The following table lists each item in the Recommendation File Links section and the
corresponding RCA Recommendation or Reference Document record field whose data is
Report Column
Record Family
Record Field
Cause
RCA Recommendation Cause
Team Members
RCA Recommendation Assigned To Name, Assigned To User ID
Document Path
Reference Document
Document Path
ID
Reference Document
ID
Acknowledgements
The Acknowledgements section of the Comprehensive Analysis Report displays the value
that is stored in the Acknowledgments field in the RCA Analysis record. This section will
be included in the report when you select the Acknowledgements check box on the
The following image shows an example of the Acknowledgements section as it appears in
the Comprehensive Analysis Report for the example RCA Analysis.
Track
The Track section of the Comprehensive Analysis Report displays a description of the
Track step of a Root Cause Analysis. This section will be included in the report when you
select the Track check box on the Comprehensive Analysis Report dialog box.
The following image shows an example of the Track section as it appears in the
Tracking Item Summary

The Tracking Item Summary section of the Comprehensive Analysis Report contains
information that is stored in an RCA Tracking Item record and the Equipment or
Functional Location record that is linked to the RCA Tracking Item record. This section
will be included in the report when you select the Tracking Item Summary check box on
the Comprehensive Analysis Report dialog box.
The following image shows an example of the Tracking Item Summary section as it
would appear in the Comprehensive Analysis Report.
The following table lists each item in the Tracking Items Summary section and the
corresponding RCA Tracking Item record whose data is displayed in the report.
Report Column
Record Family
Record Field
Related Equipment
Equipment or Functional Location
Record ID
Start Date
RCA Tracking Item
Start Date
Count
RCA Tracking Item
Count
Cost
RCA Tracking Item
Cost
Analysis-At-A-Glance
The Analysis-At-A-Glance section of the Comprehensive Analysis Report contains an
introduction to the PROACT RCA Analysis-At-A-Glance Overview section, which
includes information such as the names of the RCA Analysis Team members and the
status of Communicate stage of the RCA Analysis. This section will be included in the
report when you select the Analysis-At-A-Glance check box on the Comprehensive
The following image shows an example of the Analysis-At-A-Glance section as it appears
in the Comprehensive Analysis Report for the example RCA Analysis.
About the PROACT RCA Analysis-AtA-Glance Overview
The PROACT RCA Analysis-At-A-Glance Overview section of the Comprehensive

Analysis Report displays a summary of the RCA Analysis. This section includes the
following subsections:
Analyze and Team Data: Contains summary information about the RCA Analysis.
Assets: Contains information about the Equipment and Functional Location
records that are linked to the RCA Analysis record.
Status of Preserve, Status of Analyze, and Status of Communicate: Contain the

number of items that have been created, completed, or assigned to RCA Analysis
Team Members.
The PROACT RCA Analysis-At-A-Glance Overview section will be included in the report
when you select the Overview check box on the Comprehensive Analysis Report dialog
box.
Analysis and Team Data Subsection

The following image shows an example of the Analysis and Team Data subsection of the
PROACT RCA Analysis-At-A-Glance Overview section for the example RCA Analysis.
The following table lists each item in the Analysis and Team Data subsection and the
corresponding record field whose data is displayed in the report.
Report Item
Record
Family
Record
Field
Notes
Analysis Name RCA Analysis
Analysis
Name
Principal
Analyst
These values are stored in the Human

First Name, Resource record that is linked to the RCA
Last Name Team Member record that contains the value
Principal Analyst.
Human
Resource
Team Members Human
None
First Name, None
Resource
Team Charter
Last Name
RCA Analysis Charter
None
RCA Critical
Critical Success
Success
CSF
Factors
Factor
None
Start Date
RCA Analysis Start Date
None
Estimated
Completion
Date
RCA Analysis End Date
None
Estimated Cost
RCA Analysis Cost
of Event
None
Assets Subsection
The following image shows an example of the Assets subsection of the PROACT RCA
Analysis-At-A-Glance Overview section for the example RCA Analysis.
The following table lists each item in the Assets subsection and the corresponding record
Report
Column
Record
Family
Record Field Notes
Equipment Equipment ID This column contains the Record ID of each

Record ID or Functional or Functional Equipment or Functional Location record that is
Location
Location ID linked to the RCA Analysis record.
Family
None
None
This field is populated automatically with the

name of the family to which the piece of
equipment or location belongs. If it belongs to
the Equipment family, this field will be

populated automatically with Equipment. If it
belongs to the Functional Location family, this
field will be populated automatically with
Functional Location.
Status of Preserve, Analyze, and

Communication Subsections
The following image shows an example of the Status of Preserve, Status of Analyze, and
Status of Communicate subsections of the PROACT RCA Analysis-At-A-Glance
Overview section for the example RCA Analysis.
The following table lists each item in the Status of Preserve, Status of Analyze, Status of
Communicate subsections and the corresponding record field whose data is displayed in
the report.
Report Item
Description
Notes
Status of Preserve
Number of Data
Collection Tasks
Assigned
The total number of RCA

Preserve Item records
None
linked to the RCA
Analysis record.
Number of Data
Collection Tasks
Completed
The number of RCA

Preserve Item records
that contain the value
True in the Completed?
field.
None
% of Data Collection The percentage of RCA None

Tasks Completed
Preserve Items
records that contain the
value True in the

Completed? field.
Status of Analyze
Number of
Hypothesis

Hypothesis records that
None
are linked to the RCA
Analysis record.

Number of
Verification records that
None
Verification Assigned are linked to RCA
Hypothesis records.
Number of
Verification
Completed
The number of RCA

None
contain the value True in
the Completed? field.
% of Verification
Completed
The percentage of RCA

None
contain the value True in
the Completed? field.
Status of Communicate
Number of Root
Causes Identified
Number of
Recommendations
Approved
Created
Pending
Review
Reviewed
The number of RCA

Hypothesis records that
contain the value Cause None
Human, Cause - Latent,
or Cause - Physical in the
State field.
The number of RCA
If there are no records that contain a
Recommendation records certain value in the Status field, they do
that contain a certain
not appear in the report. For example, if
value (e.g., Created) in an RCA Recommendation record
the Statue field.
contained the value Reviewed in the
Status field, the value Reviewed would
appear under the Number of
Recommendations field, and the number
1 would appear next to it. If there are no
RCA Recommendation records with the
Rejected
Superseded
In Progress
Implemented
value Reviewed in the Status field, the

value Reviewed does not appear under
the Number of Recommendations field.
Analysis Summary Report

The Analysis Summary report displays summary information that is stored in the RCA
Analysis record. The report is divided into the following sections:
Analysis Data: Contains general information about the analysis.

Location Data: Contains information about the location of the piece of equipment
being analyzed.
Equipment Data: Contains information about the piece of equipment that is being
analyzed.
The name of the analysis, which is stored in the Analysis Name field in the RCA Analysis
record, is displayed at the top of the Analysis Summary report. The following table lists
each item in the report and the corresponding RCA Analysis record field whose data is
Note: The Location Data and Equipment Data sections exist in the Analysis Summary
report so that you can view this information in analyses where it existed in previous
releases. In the current product, the Manage Assets page allows you to link Equipment
and Functional Location records to the RCA Analysis record. Asset information is no
longer stored in fields in the RCA Analysis record, which are used to populate values in
the Analysis Summary report. You can view information in Equipment and Functional
Location records that are linked to the RCA Analysis record using the Assets subsection
of the PROACT RCA Analysis-At-A-Glance Overview section in the Comprehensive
Analysis report.
Report Item
RCA Analysis Field
Analysis Data
Analysis Type
Analysis Type
Cost of Event
Cost
Frequency
Frequency
Acknowledgements
Acknowledgements
Event Mechanism
Mechanism
Analysis Start Date
Start Date
Analysis End Date
End Date
Location Data
Plant Location
Plant Location
Division
Division
Functional Location
Functional Location
Unit
Unit
Equipment Data
Asset Category
Asset Category
Asset Class
Asset Class
Asset Type
Asset Type
Asset ID
Asset ID
Manufacturer
Manufacturer
Cause Report
The Cause report displays information that is stored in RCA Hypothesis records that are
linked to the RCA Analysis record and contain a value of Cause - Physical, Cause Latent, or Cause - Human in the State field. This information is displayed in two different
formats:
The Types of Causes graph.
A table below the graph.
The following image displays the Types of Causes graph. The x-axis displays the types of
cause (i.e., human, physical, and latent). The y-axis displays the number of RCA
Hypothesis records that contain a cause in the State field and exist in the Logic Tree for
the RCA Analysis.
The table below the graph displays information related to each RCA Hypothesis record
that is linked to the RCA Analysis record.
The following table lists each item in the Cause report and the corresponding RCA
Hypothesis record field whose data is displayed in the report. A row exists for each RCA
Hypothesis record and is categorized by the cause state (i.e., physical, latent, or human),
which is stored in the State field of the RCA Hypothesis record.
Report Column
RCA Hypothesis Field
Hypothesis
ID
Hypothesis Description
Description
Confidence Factor
Confidence Factor
Logic Tree Summary Report
The Logic Tree Summary report consists of two parts:
The Logic Tree Summary By Node Type graph.

A table that displays the information in the graph.
The following image displays the Logic Tree Summary By Node Type graph. The x-axis
displays the hypothesis state of the node, which is stored in the State field of each
corresponding RCA Hypothesis record. The y-axis displays the number of nodes that
exist in the Logic Tree for each type of state.
The table below the graph contains the same information in a chart form. In this case, the
values in the Node State column are equivalent to the Hypothesis State values in the
graph, and the values in the Node Count column are equivalent to the Total Number on
Logic Tree values in the graph. The value in the Total row is the total number of nodes
that exist in the Logic Tree with a value in the State field in the corresponding RCA
Hypothesis record.
Verification Report
The Verification report displays information that is stored in each RCA Verification
record and the RCA Hypothesis record that is linked to an RCA Verification record. It
also displays information stored in the Human Resource record that is linked to the RCA
Team Member record that is linked to the RCA Verification record. The report includes
each RCA Verification record that is linked to the RCA Analysis record.
record, is displayed at the top of the Verification report. The following table lists each
item in the report and the corresponding RCA Verification, RCA Hypothesis, or Human
Resource record field whose data is displayed in the report.
Report Column
RCA Verification or RCA Hypothesis record Record Field
Hypothesis
RCA Hypothesis
ID
Verification Method RCA Verification
Method
Outcome
RCA Verification
Outcome
Responsible
Human Resource
First Name, Last

Name
Due Date
RCA Verification
Due Date
Recommendation Report
The Recommendation report displays information that is stored in each RCA
Recommendation record that is linked to an RCA Analysis record.
record, is displayed at the top of the Recommendation report. The following table lists
each item in the report and the corresponding RCA Recommendation record field whose
data is displayed in the report.
Report Column
RCA Recommendation Field
Recommendation
Recommendation Headline
Assigned To
Assigned to Name
Status
Status
Completed?
Completed
Completion Date
Implemented Date
Team Member Report

The Team Member report displays information that is stored in an RCA Team Member
record and the Human Resource record that is linked to the RCA Team Member record.
The report includes each RCA Team Member record that is linked to the RCA Analysis
record.
record, is displayed at the top of the Team Member report. The following table lists each
item in the report and the corresponding RCA Team Member or Human Resource record
Report Field
RCA Team Member or Human Resource record
Record Field
Team Member Type RCA Team Member
Type
Job Title
Human Resource
Job Title
Company
Human Resource
Company
Site
Human Resource
Site Code
Facility
Human Resource
Facility
Business Unit
Human Resource
Business Unit
Country
Human Resource
Country
Address
Human Resource
Address1
City
Human Resource
City
State
Human Resource
State
Zip Code
Human Resource
Postal Code
Email
Human Resource
Email Address
Phone
Human Resource
Phone1
Preserve Items Report - Group by

Category
The Preserve Items - Group by Category report displays information that is stored in each
RCA Preserve Item record that is linked to an RCA Analysis record and information
stored in the Human Resource record that is linked to an RCA Team Member record that
is linked to the RCA Preserve Item record. This report displays information for each
preserve item in an analysis according to the value in the Data Category field (e.g.,
paper) in the RCA Preserve Item record.
The name of the analysis, which is stored in the Analysis Name field in the RCA
Analysis record, is displayed at the top of the Preserve Items - Group By Category report.
The following table lists each item in the report and the corresponding RCA Preserve
Item or Human Resource record field whose data is displayed in the report.
Report Item
RCA Preserve Item or Human Resource

record
Record Field
Data to Collect
RCA Preserve Item
Data to Collect
Collection
Strategy
RCA Preserve Item
Collection Strategy
Due Date
RCA Preserve Item
Date Due
Completed?
RCA Preserve Item
Completed?
Responsible
Human Resource
First Name, Last

Name
Preserve Items Report - Group by Team

Member
The Preserve Items - Group by Team Member report displays information that is stored in
each RCA Preserve Item record that is linked to an RCA Analysis record. This report
displays information for each RCA Preserve Item record according to the RCA Team
Member to whom the preserve item is assigned. Each Team Member (e.g., Analyst) is
identified in the report by the value stored in the Last Name and First Name fields of the
Human Resource record that is linked to the RCA Team Member record that is linked to
the RCA Preserve Item record.
The name of the analysis, which is stored in the Analysis Name field in the RCA
Analysis record, is displayed at the top of the Preserve Items - Group by Team Member
report. The following table lists each item in the report and the corresponding RCA
Preserve Item record field whose data is displayed in the report.
Report Item
RCA Preserve Item Field
Data to Collect
Data to Collect
Collection Strategy
Collection Strategy
Due Date
Date Due
Completed?
Completed?
Data Category
Data Category
About Tracking and Reevaluating

Analysis Results
After your team's findings have been communicated successfully to the appropriate
individuals in your organization, the next step in the PROACT workflow is to track the
effectiveness of your recommendations through RCA Tracking Item records. The goal of
tracking recommendations is to make sure that the recommendation that was

implemented has produced the desired results. Depending on the results, you may need to
reevaluate the solution that was implemented to address the underlying issues.
During the tracking process, the team should decide on a set of conditions on which
reevaluation notifications should be based. The Principal Analyst should specify these
conditions in the associated fields in the RCA Tracking Item record. These notifications
should be based on event criteria.
Criteria that is event-based includes a number of failure events and/or the failure cost that
the piece of equipment or location has incurred after the implementation of a
recommendation. When the criteria defined in the RCA Tracking Item record is exceeded,
the RCA Tracking Item record will be updated automatically to a Reevaluate status, and
an email reminder will notify the responsible party to reexamine the recommendation.
Accessing the List of Existing RCA

Tracking Item Records
You can access the Analysis Tracking Items page via the Track menu on any of the
following pages:
Analysis page
Team page
Event Diagram page
Logic Tree page
Reports List page
To access the list of existing tracking items:
On the appropriate page, on the Track menu, click the Track link.
The Analysis Tracking Items page appears, displaying the list of existing RCA Tracking
Item records for the current RCA Analysis. If no records exist, a message appears in the
workspace instead, indicating that there are no RCA Tracking Item records linked to the
current RCA Analysis. The following image shows what the Analysis Tracking Items
page looks like when it contains RCA Tracking Item records.
Aspects of the Analysis Tracking Items

Page
The Analysis Tracking Items page displays a list of all the RCA Tracking Item records
that are linked to the RCA Analysis record for the current RCA Analysis.
For each item, the following information appears:
Start Date: The date on which the evaluation will begin. This value appears as a
hyperlink, which you can click to view the contents of the corresponding RCA
Is Active?: A check box that indicates whether the tracking item is active or
inactive. You can select this check box to indicate that the RCA Tracking Item
record is active.
Count: The number of failures that can occur before a revaluation email is sent to
the users whose names are selected in the Alert List field in the corresponding
RCA Tracking Item record. You can think of this number as the expected number
of failures that will occur after the associated recommendation has been
implemented. Once this number is reached, a notification will be sent to the users
whose names appear in the Alert List field.
Cost: The failure cost that must be exceeded for a reevaluation email to be sent to
the users whose names are selected in the Alert List field in the corresponding
RCA Tracking Item record. You can think of this number as the expected cost for
maintenance and failure of the piece of equipment that will occur after the
associated recommendation has been implemented. Once this number is reached,

a notification will be sent to the users whose names appear in the Alert List field.
Equipment: The Equipment ID for the piece of equipment that is being tracked.
The Analysis Tracking Items page contains the following task menus:
Manage Assets
Common Tasks
PReserve
Order
Analyze
Communicate
Track
Associated Pages
Note: The Associated Pages menu will contain links only if they have been defined for
the RCA Tracking Item family via the URL Manager.
Manage Assets Menu

The Manage Assets menu on the Analysis Tracking Items page contains the following
link:
RCA analysis.
Common Tasks Menu

The Common Tasks menu on the Analysis Tracking Items page contains the following
links:
New Item: Displays the Tracking Item Details page, which contains a blank
datasheet that you can use to create a new RCA Tracking Item record to link to the
RAC Analysis record for the current RCA Analysis.
Edit Item: Opens the selected RCA Tracking Item record on the Tracking Item
Details page, where you can view and modify its contents.
Copy Item: Creates a copy of the selected RCA Tracking Item record on the
Tracking Item Details page, where you can modify the RCA Tracking Item record
and save it to the current RCA Analysis.
Delete Item: After asking for confirmation, deletes the selected RCA Tracking
Item record.
Page.
Help: Displays the context-sensitive Help topic for the Analysis Tracking Items
page.
PReserve Menu
The PReserve menu on the Analysis Tracking Items page contains the following link:
Preserve Records: Displays the Preserve Failure Data page, which displays the
list of existing RCA Preserve Item records for the current analysis.
Order Menu
The Order menu on the Analysis Tracking Items page contains the following links:
displays the list of existing RCA Critical Success Factor records that are linked to
the RCA Analysis record for the current RCA Analysis.
Team: Displays the Team page, where you can view the list of RCA Team
Members records that are linked to the RCA Analysis record for the current RCA
Analysis.
Analyze Menu
The Analyze menu on the Analysis Tracking Items page contains the following links:
Event Diagram: Displays the Event Diagram page. The first time that you access
the Event Diagram page for a given RCA Analysis, the RCA Event dialog box will
appear automatically so that you can define an RCA Event record and link it to
the current RCA Analysis. Otherwise, the Event Diagram page appears,
displaying the event diagram for the current RCA Analysis.
you can create a logic tree diagram to represent the possible causes of the event
being analyzed.
Communicate Menu
The Communicate menu on the Analysis Tracking Items page contains the following
links:
create RCA Recommendation records to represent recommendations for the
have been configured for the Root Cause Analysis module.
Track Menu
The Track menu on the Analysis Tracking Items page contains the following link:
Track: Displays the current page. This link is available on other pages in Root
Cause Analysis and lets you navigate to the Analysis Tracking Items page.
Accessing the Tracking Item Details

Page
You can access the Tracking Item Details page via the following methods:
Create a new RCA Tracking Item record.
Open an existing RCA Tracking record.
-or-
Aspects of the Tracking Item Details

Page
The Tracking Item Details page displays the contents of a single RCA Tracking Item
record on the RCA Tracking Item Details datasheet.
Above the datasheet, the Related Equipment text box appears, which contains the Record
ID of the Equipment or Functional Location record to which the RCA Tracking Item
record is linked. If the RCA Tracking Item record is not linked to an Equipment or
Functional Location record, this text box will be empty.
To the right of the Related Equipment text box, the Search button appears, which you can
click to search for an Equipment or Functional Location record to link to the current RCA
The following image shows what the Tracking Item Details page looks like when you
create a new RCA Tracking Item record.
The Tracking Items Details page contains the same task menus that appear on the
Analysis Tracking Items page.
Note: The Associated Pages menu on the Tracking Item Details page contains links only
if they have been defined for the RCA Tracking Item family and you are viewing an
existing RCA Tracking Item record.
Creating New RCA Tracking Item

Records
You can create RCA Tracking Item records and set up tracking notifications as a part of
the reevaluation process. In the RCA Tracking Item record, you will define the:
User to whom the notification will be sent.

Time interval or event-based conditions that should be met before the notification
can be sent.
Note: For notifications to work properly, an administrative user must create the Tracking
Evaluation scheduled item in the Meridium APM Schedule Manager.
When you create an RCA Tracking Item record, a link is created automatically between
the RCA Tracking Item record and the RCA Analysis record. In addition, you will need to
specify the Equipment or Functional Location record that represents the piece of
equipment or location that you are analyzing. When you do so, a link is created
automatically between the RCA Tracking Item record and the specified Equipment or
Functional Location record.
To create a new Tracking Item record:

1. On the Analysis Tracking Items page, on the Common Tasks menu, click the New
Item link.
The Tracking Item Details page appears, displaying a new RCA Tracking Item record.
2. On the RCA Tracking Item Details datasheet, complete the fields as desired. The
following fields are required:
1.
o
Start Date
Alert
Message Subject
Message Text
3. On the Common Tasks menu, click the Save this Item link.
The RCA Tracking Item record is saved to the database. At this point, you can link an
Equipment or Functional Location record to the RCA Tracking Item record.
Linking Equipment or Functional

Location Records to RCA Tracking
Item Records
Once you save a RCA Tracking Item record to the database, you can link an Equipment
or Functional Location record to that RCA Tracking Item record. Only one Equipment or
Functional Location Record can be linked to each RCA Tracking Item record.
To link an Equipment or Functional Location record to an RCA Tracking Item record:
1. Open the RCA Tracking Item record to which you want to link the Equipment or
Functional Location record.
2. Above the datasheet, click the Search button.
The Find Equipment window appears, and the Search In list contains the Equipment and
3. Perform a search to locate the desired record.
4. In the search results, select row containing the Equipment or Functional Location
record that you want to link to the RCA Tracking Item record, and click the Select
button.
The Find Equipment window closes, and the Record ID of the selected record appears in
the Related Equipment text box, indicating that the RCA Tracking Item record is linked
to the record with that Record ID.
Viewing the Contents of RCA Tracking

Item Records
To view the contents of an RCA Tracking Item record:
On the Analysis Tracking Items page, in the row representing the RCA Tracking
Item record whose contents you want to view, in the Start Date cell, click the
hyperlinked start date.
The Tracking Item Details page appears, displaying the contents of the selected record.
Modifying Existing RCA Tracking Item

Records
To modify the RCA Tracking Item record:
1. Open the RCA Tracking Record whose contents you want to modify.
2. Modify the contents of the record as desired.
Your changes are saved to the database, and the Analysis Tracking Items page appears.
Copying RCA Tracking Item Records

You can copy an RCA Tracking Item record in order to create the same tracking item for
similar equipment and locations related to an RCA Analysis.
To copy an RCA Tracking Item record:
1. On the Analysis Tracking Items page, select an RCA Tracking Item that you wish
to copy from the Tracking grid.
2. On the Common Tasks menu, click the Copy Item link.
The Tracking Item Details page appears, displaying a copy of the RCA Tracking Item
record you selected. The values in all of the fields on the RCA Tracking Item Details
datasheet are copied except for the value in the Related Equipment text box.
3. Link an Equipment or Functional Location record to the RCA Tracking Item

record.
4. Modify the rest of the contents in the RCA Tracking Item Details datasheet as
desired.
Your changes are saved to the database, and the Analysis Tracking Items page appears.
Deleting RCA Tracking Item Records

To delete an existing RCA Tracking Item record:
1. On the Analysis Tracking Items page, in the list of RCA Tracking Item records,
select the row representing the RCA Tracking Item that you want to delete.
2. On the Common Tasks menu, click the Delete Item link.

A confirmation message appears, asking if you really want to delete the item.
The record is removed from the list of RCA Tracking Item records and deleted from the
Meridium APM database.
About the Spell Check Feature

You can use the spell check feature to search for spelling errors in a Root Cause Analysis.
When you use the spell check feature, the Meridium APM system checks the spelling of
the values in text and character fields of the following records within an RCA Analysis:
RCA Preserve Item

RCA Sequence Node
RCA Logic Gate
RCA Failure Mode
RCA Hypothesis
RCA Verification
RCA Build List Item
RCA Recommendation
RCA Tracking Item
RCA Analysis
If a word in a field is misspelled according to the language specified for the spell check
feature, the Meridium APM system will display alternative words that you can choose to
use in place of the misspelled word.
Note: Fields containing HTML or XML tags will be ignored by the spell check feature.
The Spell Check feature is accessible via the Spell Check link, which is located on the
Tree Tasks menu on the Logic Tree page and the Common Tasks menu on the following
pages:
Preserve Failure Data

Team
Event Diagram
Communicate Records
Reports List
Analysis Tracking Items
Note: For unpublished analyses, the Spell Check link is always enabled. For published
analyses, it is disabled on all pages except the Communicate Records and the
Recommendation Details pages. It is enabled on these pages for published analyses only
if you are a Super User, a member of the MI PROACT Administrator Security Group, or
the Principal Analyst for the analysis.
Checking the Spelling in an Analysis

To use the spell check feature:
1. On the Common Tasks menu, click the Spell Check link.
The Spell Check dialog window appears.
2. To start checking the spelling in the analysis, click the Start button.
Note: When you start the spell check operation, the currently selected dictionary will be
used automatically. If this is the first time you have accessed the spell check feature, the
Meridium APM system will automatically select a dictionary that corresponds to your
Meridium APM Culture setting, if one is available. If a dictionary is not available for
your Meridium APM Culture setting or you do not have a Meridium APM Culture setting
defined, the English dictionary will be used. You can change the language by clicking the
Options button.
If one or more misspelled words are found, the Word Not Found dialog box appears,
displaying the misspelled word, the family of the misspelled word, and the number of
records that are being checked in the RCA Analysis. If NO misspelled words are found,
the Spelling dialog box appears, notifying you that the check is complete.
3. If the spell check feature finds misspelled words, click one of the following
buttons on the Word Not Found dialog box:
Ignore: Ignores the selected word and continues to the next misspelled
word.
Ignore All: Ignores all instances of the selected word in the analysis and
continues to the next misspelled word.
Change: Replaces the selected word with a word you select from the
Possible Alternatives list.
Change All: Replaces all instances of this word in the analysis with a word
you select from the Possible Alternatives list.
Add: Adds the selected word to the dictionary. After you add the word to
the dictionary, it will no longer be considered misspelled, and the spell
check feature will continue to the next misspelled record.
Cancel: Cancels the spell check and closes the Word Not Found dialog
box.
Options: Displays the Spelling Options dialog box, where you can specify
a new language for the dictionary.
When the spell check process is complete, the Spelling dialog box appears.
4. Click OK. The Spell Check dialog box returns to focus. If you are done using the
spell check feature, click the Close button.
Specifying a Language for the

Dictionary
When you initiate the spell check operation, a dictionary will be selected for you by
default. The first time you access the spell check feature, the Meridium APM system will
automatically select the dictionary associated with your Meridium APM Culture setting
(if one is available). If a dictionary is not available for your Meridium APM Culture
setting or you do not have a Meridium APM Culture setting defined, the English
dictionary will be used. If desired, you can modify the default dictionary selection. If you
do so, that language will be selected automatically the next time you access the spell
check feature.
To specify the language to be used by the spell check feature:

1. On the Spell Check window or the Word Not Found window, click the Options
button.
The Spelling Options dialog box appears.
2. Click one of the available options from the Choose the language you would like to
use when performing spell checking.
3. Click OK.
The language you selected will now be used by default each time you access the spell
check feature.
Accessing the My PROACT Page

The My PROACT page which contains a list of the in-progress (unpublished) RCA
Analyses to which you belong and lists of all assigned task items, including RCA
Preserve Item records, RCA Verification records, and RCA Recommendation records.
To access the My PROACT page:
On the Root Cause Analysis Start Page, click the My PROACT link.
The My PROACT page appears.
Aspects of the My PROACT Page
The My PROACT page displays a list of all of the unpublished RCA Analyses where you
are a member of the RCA Analysis Team. It provides you with a central location for
viewing the list of the RCA Analyses and the assigned open task items associated with
those RCA Analyses. When an RCA Analysis is in progress, only the team members and
the Principal Analyst can view the associated data. An example of the My PROACT page
is shown in the following image.
The My PROACT page consists of two sections:
The Analyses in Progress section displays following columns of information for

each RCA Analysis:
Analysis Name: The name assigned to the RCA Analysis. You can click
the hyperlinked analysis name to view the associated RCA Analysis
record.
Note: The Analysis Name field is locked in the first position on the grid.
1.
Long Description: A description of the RCA Analysis.
Start Date: The start date of the RCA Analysis.
End Date: The date when the RCA Analysis has been completed, if
applicable.
You can click the hyperlinked analysis name to view the details of the RCA Analysis.
The Preserve Items, Verifications, and Recommendations tabs section appear at

the bottom of the My PROACT page to let you view and manage all RCA
Preserve Item records, RCA Verification records, and RCA Recommendation
records that are assigned to you. To view the details for a particular type of item,
click the corresponding tab:
Preserve Items: Displays a list of all incomplete RCA Preserve Item

records for the RCA Analyses to which you belong. RCA Preserve Item
records will be displayed as they are created and assigned.
Verifications: Contains a list of the incomplete RCA Verification records

for the RCA Analyses to which you belong. RCA Verification records will
be displayed as they are created and assigned.
Recommendations: Contains a list of the RCA Recommendation records

for the RCA Analyses to which you belong. Recommendations will be
displayed as they are created and assigned.
Additionally, each tab displays the number of items that appear in the list on that tab. The
items in the list on each tab are color-coded according to due date for easy tracking:
1.
No color (the default white background): The item is due two weeks or
more from the current date.
Yellow: The item is due within two weeks of the current date.
Red: The item is due today or is overdue.
Green: The item has been completed.
Note: After an RCA Analysis is published, assigned items associated with it are removed
from the Preserve Items, Verifications, and Recommendations tabs.
The My PROACT page contains the following task menus that provide access to Root
Cause Analysis functions: Common Tasks and Other Tasks.
Common Tasks Menu
The Common Tasks menu on the My PROACT page contains the following links:
New Analysis: Displays the New Analysis Builder, which will guide you step-bystep through the initial steps required for a new RCA Analysis.
Page.
Help: Displays the context-sensitive Help topic for the My PROACT page.
Other Tasks Menu
The Other Tasks menu on the My PROACT page contains the following link:
Manage Analyses: Displays the Manage Analyses page, where you can view all of
the analyses of which you are member, regardless of the state.
Viewing the Details of an Analysis

From the My PROACT page, you can view the details of any RCA Analysis that appears
in the list of existing RCA Analyses.
To view the details of an analysis:
On the My PROACT page, in the Analyses in Progress list that appears at the top
of the page, click the hyperlinked name of the RCA Analysis whose RCA
Analysis record you want to view.
The Analysis page appears.
Viewing the Details of a Preserve Item

From the My PROACT page, you can view the details for any RCA Preserve Item record
that is listed on the Preserve Items tab at the bottom of the page.
To view the details of an RCA Preserve Item record:
1. On the My PROACT page, in the Preserve Items, Verifications, and
Recommendations tabs section, click the Preserve Items tab to view a list of RCA
Preserve Item records.
2. In the list of RCA Preserve Items, in the Data Category column, click the
hyperlinked value for the record that you want to view.
Viewing the Details of an RCA

Verification Record
On the My PROACT page, you can view the details for any RCA Verification record that
is listed on the Verifications tab at the bottom of the page. An RCA Verification record
will appear on the Verifications tab only if it assigned to you.
To view the details of an RCA Verification record:
1. On the My PROACT page, in the Preserve Items, Verification, and
Recommendations tab section, click the Verifications tab to view a list of RCA
Verification records.
2. In the list of RCA Verification records, in the Verification Method column, click
the hyperlinked value for the record that you want to view.
The RCA Verification dialog box appears.
Viewing the Details of an RCA

On the My PROACT page, you can view the details for any RCA Recommendation
record that is listed on the Recommendations tab at the bottom of the page.
To view the details of an RCA Recommendation record:
1. On the My PROACT page, in the Preserve Items, Verifications, and
Recommendations tabs section, click the Recommendations tab to view a list of
RCA Recommendation records.
2. In the list of RCA Recommendation records, in the Description column, click the
hyperlinked value for the record that you want to view.
The Recommendation Details page appears.
About the Principal Analyst's View

The Principal Analyst facilitates, organizes, and manages the RCA Analysis process. In
Root Cause Analysis, when a user completes the initial steps required for an RCA
Analysis, that user is designated automatically as the Principal Analyst. Each RCA user
has access to the Principal Analyst's view for the RCA Analyses they have initiated via
the New Analysis Builder. The PA PROACT page displays the Principal Analyst's view.
Via the PA PROACT page, you can review all tasks assigned to all team members for any
RCA Analysis that you have initialized. If you have not completed the initial steps
required for an active RCA Analysis, your PA PROACT page will be empty. When you
select an RCA Analysis from the list, the open items (e.g., RCA Preserve Item records,
RCA Verification records, RCA Recommendation records) associated with the selected
RCA Analysis appear on a series of tabs. You can select a items on each tab to view the
current status of the item.
In addition, on the PA PROACT page, you can create notifications to alert team members
of overdue RCA Preserve Item records and RCA Verification records. You can also send
notifications to the team member who is responsible for an RCA Recommendation
record.
Items with blank assignments will be listed on the PA PROACT page to allow you to
track the items. If a team member is removed from the RCA Analysis, any item that was
previously assigned to the deleted team member (e.g., RCA Verification record) will be
displayed on the PA PROACT page, where you can reassign those items to another team
member.
Accessing the PA PROACT Page

From the PA PROACT page, you can view the list of RCA Analyses for which you are
currently serving as the Principal Analyst. In addition, you can view and manage the tasks
associated with the RCA Analysis (e.g., RCA Preserve Item records, RCA Verification
records, and RCA Recommendation records) and the team members to whom the tasks
are assigned.
To access the PA PROACT page:
On the Root Cause Analysis Start Page, click the Principal Analyst's View link.
The PA PROACT page appears.
Aspects of the PA PROACT Page

The PA PROACT page displays a list of RCA Analyses for which you are currently
serving as the Principal Analyst. In addition, on the PA PRAOCT page, you can view and
manage the tasks associated with the RCA Analysis (e.g., RCA Preserve Item records,
RCA Verification records, and RCA Recommendation records) and the team members to
whom the tasks are assigned.
The PA PROACT page consists of two sections:
The Analyses in Progress section contains a list of active analysis for which you
are currently serving as the Principal Analyst. By default, the following analysis
properties are shown for each analysis that appears in the list.
Analysis Name: The name assigned to this analysis. Click an Analysis

Name to view the summary for the selected analysis.
Note: This field is locked in the first position on the grid.
Long Description: A description of the analysis.
Start Date: The start date of the analysis and the time are listed in this
field.
End Date: The end date of the analysis and the time are listed in this field.
The Preserve Items, Verifications, and Recommendations tab section appears

below the list of analyses. Each tab contains a list of items that are linked to the
analyses in the Analyses in Progress list. Only the unpublished analyses to which
the Principal Analyst is assigned will appear in the list.
The following tabs are displayed:

1.
Preserve Items: Displays a list of the RCA Preserve Item records

associated with the selected analysis.
Verifications: Displays a list of the RCA Verification records associated

with the selected analysis.
Recommendations: Display a list of the RCA Recommendation records

associated with the selected analysis.
The items in the list on each tab are color-coded according to due date for easy tracking:
1.
No color (the default white background): The item is due two weeks or
more from the current date.
Yellow: The item is due within two weeks of the current date.
Red: The item is due today or is overdue.
Green: The item has been completed.
Items with blank assignments will be listed on the PA PROACT page to allow the
Principal Analyst to track the items. If a team member is deleted, the analysis task (the
RCA Preserve Item Record, RCA Verification Record, or RCA Recommendation record)
that was previously assigned to the deleted team member will appear on the PA PROACT
page. The Principal Analyst can then re-assign those items to another team member.
Common Tasks Menu
The Common Tasks menu on the PA PROACT page contains the following links:
New Analysis: Displays the New Analysis Builder, which will guide you step-bystep through the initial steps required for a new RCA Analysis.
Page.
Help: Displays the context-sensitive Help topic for the PA PROACT page.
Other Tasks Menu
The Other Tasks menu on the PA PROACT page contains the following links:
Send Records: Allows the Principal Analyst to send an email message to the RCA
Analysis Team member who is responsible for an overdue item (an RCA Preserve
Item record or an RCA Verification record) that is being tracked.
Manage Analyses: Displays the Manage Analyses page, where you can view all of
the analyses of which you are member, regardless of the state.
Viewing the Details of an In-Progress

RCA Analysis
To view the details of an in-progress RCA Analysis:
1. On the PA PROACT page, in the Analyses in Progress section, select the row
containing the RCA Analysis for which you want to display the details.
2. Click the hyperlinked name of the RCA Analysis in the Analysis Name column.
Viewing Assigned Incomplete RCA

Preserve Item Records
You can view the RCA Preserve Item records assigned for a selected unpublished RCA
Analysis for which you are the Principal Analyst.
To view an RCA Preserve Item record:
1. On the PA PROACT page, in the Analyses in Progress section, click the row
containing the RCA Analysis for which you want to display items.
2. Click the Preserve Items tab at the bottom of the page.
All of the RCA Preserve Item records for the selected RCA Analysis appear in the list on
the Preserve Items tab. A color is assigned to each RCA Preserve Item record according
to the due date.
The following details are displayed for each Preserve Item in the list.
Data Category: A data collection procedure based on five categories,

called the 5 P's, provides a guide for organizing data that is relative to the
problem that the RCA Analysis Team wishes to analyze.
Collection Strategy: A description of the exact manner in which the data

will be collected. An example of a strategy for collecting data could be
acquiring production logs from a line supervisor.
Person Responsible: The name of the team member to whom this task is
assigned.
Due Date: The deadline for collecting the failure data.
Date Completed: The date on which the task was completed. This field is
automatically populated when the assigned team member has finished
collecting the data for the RCA Preserve Item record.
3. Click the hyperlinked value in the Data Category column that corresponds to the
record that you want to view or modify.
The RCA Preserve Item record appears on the Preserve Record Details page.

Your changes are saved to the database and the PA PROACT page reappears.
Viewing and Modifying Assigned RCA

Verification Records
You can view the RCA Verification records that are linked to a selected unpublished RCA
Analysis for which you are the Principal Analyst. From the Verifications tab, you can
select an RCA Verification record that you want to review.
To view assigned RCA Verification records:
2. In the Preserve Items, Verifications, and Recommendations tabs section, click the
Verifications tab.
All the RCA Verification records for the selected RCA Analysis appear in the list on the
Verifications tab. A color is assigned to each RCA Verification record according to the
due date.
The following details are displayed for each RCA Verification record in the list:
Verification Method: The method utilized to prove that a hypothesis is true

or not true (e.g., Data analysis, lube oil analysis, stress analysis, visual
inspection, interviews).
Person Responsible: The name of the team member to whom this task is
assigned.
Due Date: The deadline when the verification should be completed.
Date Completed: The date on which the verification is completed. This

field is automatically populated when the assigned team member has
completed the verification process.
3. Click the hyperlinked value in the Verification Method column that corresponds to
the record that you want to view or modify.
The RCA Verification dialog box appears, displaying the RCA Verification datasheet.

5. Click the Save button to save your changes.
Your changes are saved and the PA PROACT page reappears.
Viewing and Modifying Assigned RCA

Recommendation Records
You can view the RCA Recommendation records assigned for a selected unpublished
RCA Analysis for which you are the Principal Analyst.
To view and modify assigned RCA Recommendation records:
2. Click the Recommendations tab to select it.
All of the Recommendations for the selected RCA Analysis appear in the list on the
Recommendations tab. The system assigns a color to each RCA Recommendation record
according to the due date.
The following details are displayed for each RCA Recommendation record in the list:
Description: A brief description of the recommendation.
Person Responsible: The name of the team member assigned to this

record.
Due Date: The deadline when the recommendation should be

implemented.
Date Completed: Populated when the assigned team member has

implemented the recommendation.
3. Click the hyperlinked value in the Description column associated with the record
that you want to view or modify.
The Recommendation Details page appears, displaying the selected RCA
Recommendation record.

Your changes are saved to the database and the PA PROACT page reappears.
About Sending Email to Team Members

Root Cause Analysis provides the Principal Analyst with the ability to send an email
message to the RCA Analysis Team member who is responsible for an item, such as an
RCA Preserve Item record or an RCA Verification record. The Principal Analyst can
select and send email messages about multiple items to multiple RCA Analysis Team
members at the same time. Using this feature allows the Principal Analyst to facilitate the
participation of team members and manage the administrative responsibilities of
collecting the data.
Note: To use this feature, team members must have an email address defined in their
Meridium APM Human Resource record. In addition, Microsoft Outlook or the SMTP
Server must be configured properly. Additionally, the user who is sending the records and
the user who is receiving the records must belong to the same RCA Analysis Team.
Using the PA PROACT page, you can:
Send email message about RCA Preserve Item records.

Send email messages about RCA Verification records.
The Principal Analyst can also send an email message about a recommendation to the
RCA Analysis Team member who is responsible for that RCA Recommendation record.
The functionality for sending an email message about an RCA Recommendation record is
available via the datasheet for the RCA Recommendation record.
Sending Email About RCA Preserve

Item Records
To send an email message about an RCA Preserve Item record:
1. On the PA PROACT page, in the Analyses in Progress section, select the row
containing the desired RCA Analysis.
Preserve Items tab.
3. On the Other Tasks menu, click the Send Records link.
Note: If you are an RCA Analysis Team member but do not have an email address
defined in your Meridium APM Human Resource record, a message will appear,
indicating that the current user does not have an email address defined. You can define an
email address by modifying your Human Resource record.
Preserve Item records associated with the selected RCA Analysis.
4. Click the rows containing the records about which you want to send an email
message.
5. In the Subject text box, type the subject of the email message(s).
6. In the Message Text text box, type the text of the email message.
The Meridium APM system sends the email messages containing hyperlinks to the
selected RCA Preserve Item record(s) and displays a confirmation message.
9. On the Email List of Items dialog box, click the Close button to close the Email
List of Items dialog box.
Sending Email about RCA Verification

Records
To send an email message about RCA Verification records:
containing the desired RCA Analysis.
Verifications tab.
3. On the Other Tasks menu, click the Send Records link.
Verification records associated with the selected RCA Analysis.
4. Select the rows containing the records about which you want to send an email
message.
5. In the Subject text box, type the subject of the email message.
6. In the Message Text text box, type the text of the email message.
The Meridium APM system sends the email messages containing hyperlinks to the
selected RCA Verification record(s) and displays a confirmation message.
9. On the Email List of Items dialog box, click the Close button to close the Email
List of Items dialog box.
Accessing the Manage Analyses Page

The Manage Analyses page lets you view a list of unpublished RCA Analyses, RCA
Analysis Templates, and published RCA Analyses. From the Manage Analyses page, you
can also view the details of an existing RCA Analysis and perform various tasks
associated with RCA Analyses.
The following instructions provide details on accessing the Manage Analyses page via the
Root Cause Analysis Start Page. You can also access the Manage Analyses page via the
Other Tasks menu on any of the following pages:
My PROACT page
PA PROACT page
Analysis page
To access the Manage Analyses page:
On the Root Cause Analysis Start Page, click the Manage Analyses link.
The Manage Analyses page appears.
Aspects of the Manage Analyses Page

The Manage Analyses page displays unpublished RCA Analyses, RCA Analysis
Templates, and published RCA Analyses. By default, the list of existing RCA Analyses is
grouped by state so that you can distinguish between analysis states (i.e., In Progress,
Published, and Template). You can click any RCA Analysis in the list to view the details
on the Analysis page.
For each RCA Analysis in the list, the Manage Analyses page displays the following
information:
Analysis Name: The name of the RCA Analysis.

Long Description: A description of the RCA Analysis.
Analysis Type: The analysis type: Mechanical, Operational, Quality, or Safety.
Asset ID: If you are analyzing equipment, the ID of the selected piece of
equipment.
Start Date: The start date of the RCA Analysis.
The Manage Analyses page contains one task menu: Common Tasks.
Common Tasks Menu
The Common Tasks menu on the Manage Analyses page contains the following links:
Create Analysis: Displays the New Analysis Builder, which will guide you stepby-step through the initial steps required for a new RCA Analysis.
Copy Analysis: Displays a confirmation message, asking if you really want to
develop a new RCA Analysis based on the selected RCA Analysis and then copies
the RCA Analysis.
Delete: Displays a confirmation message, asking if you really want to delete the
selected RCA Analysis and then deletes the RCA Analysis. Only the Principal
Analyst or a member of the MI PROACT Administrator Security Group can
delete an RCA Analysis.
Publish: Displays a confirmation message, asking if you really want to publish

the selected RCA Analysis and then publishes it. Only the Principal Analyst or a
member of the MI PROACT Administrator Security Group can publish an RCA
Analysis. When an RCA Analysis is published, the system grants all Meridium
APM Security users read-only access to the RCA Analysis, regardless of whether
they are included on the RCA Analysis Team or not.
Unpublish: Displays a confirmation message, asking if you really want to revoke

the publication of the selected RCA Analysis, and then unpublishes a published
RCA Analysis. Only the Principal Analyst or a member of the MI PROACT
Administrator Security Group can revoke the publication of an RCA Analysis.
Produce Template: Displays a confirmation message, asking if you really want to

create an RCA Analysis Template based on the selected RCA Analysis and then
creates a template. This link is enabled only if:
You are logged in as a Super User or a member of the MI PROACT

Administrator Security Group.
-or
You are the Principal Analyst of the currently selected RCA Analysis and
the Template Creation Permissions setting has been enabled.
Page.
Help: Displays the context-sensitive Help topic for the Manage Analyses page.
About Copying Existing Analyses

You can make a copy of any existing RCA Analysis to create a new RCA Analysis. This
may be useful if you need to conduct multiple RCA Analyses with similar information.
For example, another facility may have completed an RCA Analysis on a piece of
equipment that you also have in your facility.
You can make a copy of any RCA Analysis regardless of the state of the analysis. This
means that you can copy an analysis that is in the In Progress, Published, or Template
state.
When you copy an RCA Analysis to develop a new RCA Analysis, the New Analysis
Builder appears, where you can define a new RCA Analysis record. Any of the following
items that exist in the original RCA Analysis will be copied to the new RCA Analysis:
RCA Preserve Item records. The values in the record remain the same except:
The value in the Date Due field is set to 30 days after the date the copy is
performed.
The Completed? field is set to the default value NO.
The Date Completed field is disabled and the value is cleared.
The Logic Tree and any associated records (e.g., Hypothesis, Failure Mode). The
values in these records remain the same.
RCA Verification records. The values in the record remain the same except:
The Outcome field is cleared.
The Due Date field is set to 30 days after the date the copy is performed.
The Completed? field is set to the default value No.
The Date Completed field is disabled and the value is cleared.
Event Diagram and any associated records (i.e., RCA Sequence Node records).
The values in these records remain the same.
Copying an Existing Analysis to Develop

a New Analysis
To create a new analysis based on an existing analysis:
1. On the Manage Analyses page, in the list of existing RCA Analyses, select the
row containing the RCA Analysis on which you want to base the new RCA
Analysis.
2. On the Common Tasks menu, click the Copy Analysis link.
A confirmation message appears, asking if you really want to develop a new RCA
Analysis based on the selected RCA Analysis.
The New Analysis Builder appears, displaying the RCA Analysis datasheet.
4. Complete the steps in the New Analysis Builder. You must at least define a unique
Analysis ID for the new RCA Analysis. If you are creating the RCA Analysis
based on a template, keep in mind that templates do not have team members
defined for them, so you will also want to set up the RCA Analysis Team.
5. When you have completed all the steps, click the Finish button.
The initial steps required for a new RCA Analysis are complete and saved, and the
Preserve Failure Data Records screen appears. If there were RCA Preserve Item records
linked to the original RCA Analysis record, those items will appear in the list.

RCA Analysis Records
If desired, you can link existing Reference Document record to the RCA Analysis record
or create a new Reference Document record to link to it. The following instructions
provide details on linking Reference Document records to an RCA Analysis record.
To link Reference Document records to an RCA Analysis record:
1. On the Root Cause Analysis Start Page, click the Manage Analyses link.
The Manage Analyses page appears.
2. Click the hyperlinked name of the RCA Analysis record to which you want to link
a Reference Document record.
The Analysis page appears, displaying the RCA Analysis Details datasheet for the
selected RCA Analysis.

The Reference Documents window appears.
4. Add the desired Reference Document records to the RCA Analysis record.
Your changes are saved, and the Analysis page returns to focus.
Creating RCA Analysis Templates

An RCA Analysis Template is an RCA Analysis that is in the Template state. RCA
Analysis Templates are the same as other RCA Analyses except that they do not have
team members assigned to them and they are always in the Template state (i.e., they
never become published). RCA Analysis Templates can be created either from RCA
Analyses in either the Published or Unpublished state and can be used for creating new
RCA Analyses.
Only certain users can manage RCA Analysis Templates.
Super Users and members of the MI PROACT Administrator Security Group can
create RCA Analysis Templates.
Additionally, RCA users can create RCA Analysis Templates from the RCA
Analysis in which they are the Principal Analyst if the check box Allow users to
create RCA Analysis Templates from the Analyses in which they are the Principal
Analyst is selected on the Administrative Functions page.
Only Super Users and members of the MI PROACT Administrator Security
Group can modify or delete RCA Analysis Templates, regardless of who has
created them.
To create an RCA Analysis Template:

row containing the RCA Analysis that you want to use to create the template. You
can select either a published or an unpublished RCA Analysis.
2. On the Common Tasks menu, click the Produce Template link.
Note: This link is enabled only if you have permission to create RCA Analysis Templates
for the selected RCA Analysis.
A confirmation message appears, asking if you really want to create the template.
The New Analysis Name dialog box appears.
By default, the text box contains the name of the RCA Analysis that you selected along
with the prefix Template.
4. In the text box, type a name for the RCA Analysis Template to distinguish it from
the original RCA Analysis.
Note: If you attempt to save an RCA Analysis Template with a name that is already being
used by a RCA Analysis or RCA Analysis Template, an error message will appear,
warning you that the name already exists and prompting you to enter another name.
5. Click OK.
The Manage Analyses page displays the new RCA Analysis Template in the list. You can
click the hyperlinked Analysis ID to view or modify the template on the Analysis page.
Note: Any Meridium APM user that has View privileges to the RCA Analysis can view
RCA Analysis Templates. Only members of the MI PROACT Administrator Security
Group and Super Users can modify RCA Analyses in the Template state.
Publishing an Analysis
After an RCA Analysis has been completed, the Principal Analyst can publish it. When an
the RCA Analysis is in the Published state, it will be read-only to all users, including the
team members and the Principal Analyst. If changes must be made to a published
analysis, the Principal Analyst can unpublish it, make the necessary changes, and the
republish.
Note: While most components of a published analysis cannot be modified, RCA
Recommendation records in a published analysis can be edited. Changes are allowed to
the RCA Recommendation records because modifications may be necessary to facilitate
the implementation of those recommendations.
Published RCA Analyses are useful because they can be viewed by all users, facilitating
the transfer of knowledge to other people in your organization.
To publish an unpublished analysis:
1. On the Manage Analyses page, in the list of analyses, select the row containing
the RCA Analysis that you want to publish.
2. On the Common Tasks menu, click the Publish link.
A message appears, asking if you really want to publish the RCA Analysis.

The state of the RCA Analysis changes from Unpublished (In Progress) to Published and
the Date Published field on the RCA Analysis record is populated with the date on which
the analysis was published.
Unpublishing an Analysis
After an RCA Analysis has been completed, it can be published so that other users can
view it. With the exception of RCA Recommendation records, when an RCA Analysis is
in the Published state, the components of that analysis cannot be modified. If you need to
make changes to the RCA Analysis after it has been published, or if you decide that you
do not want it to be viewed by others, you can unpublish it.
Note: Only a member of the MI PROACT Administrator Security Group, the Principal
Analyst, or a Super User can unpublish an RCA Analysis.
To unpublish a published RCA Analysis:
row containing the published RCA Analysis that you want to unpublish.
2. On the Common Tasks menu, click the Unpublish link.
A message appears, asking if you really want to unpublish the RCA Analysis.
The state of the RCA Analysis changes from Published to Unpublished (In Progress).
Deleting an RCA Analysis or Analysis

Template
The following instructions provide details on deleting a published RCA Analysis, an

unpublished RCA Analysis, or an RCA Analysis Template. When you delete an RCA
Analysis, the RCA Analysis record is deleted along with all the records that are linked to
the RCA Analysis record except for the:
RCA Recommendation records.
Note: When you delete an RCA Analysis that has RCA Recommendation records
associated with it, a message will appear, providing you with the option to delete the
associated RCA Recommendation records or not.
RCA Tracking Item records that are linked to Equipment or Location records.
To delete an RCA Analysis or RCA Analysis template:

row containing the RCA Analysis or RCA Analysis Template that you want to
delete.
2. On the Common Tasks menu, click the Delete link.
A confirmation message appears, asking if you really want to delete the analysis.
If RCA Recommendation records are associated with the analysis, a message appears,
asking if you also want to delete those records.
4. Click the Yes or No button, as desired.
The selected items are deleted from the database, and the analysis no longer appears in
the list on the Manage Analyses page.
Accessing the Analysis Page

Individual RCA Analyses appear on the Analysis page, where you can manage all the
information associated with that specific RCA Analysis. You can access the Analysis page
from the following main places:
PA PROACT page
Manage Analyses page
My PROACT page
Each page that appears in the previous list is accessible from the Root Cause Analysis
Start Page.
To access the Analysis page:
On the PA PROACT page, in the list that appears at the top of the page, click the
hyperlinked name of the RCA Analysis that you want to view.
On the Manage Analyses page, in the list of analyses, click the hyperlinked
analysis name of the RCA Analysis that you want to view.
On the My PROACT page, in the list that appears at the top of the page, click the
hyperlinked name of the RCA Analysis that you want to view.
-or-
-or-
Aspects of the Analysis Page

The Analysis page displays a datasheet that contains all the information associated with a
given RCA Analysis. The specific fields that appear will depend on how your system has
been configured.
Note: The RCA Analysis Detail datasheet is set as the default datasheet on the Analysis
page. While viewing the Analysis page, you can select another datasheet by choosing the
desired datasheet from the Datasheet list. If you select a different datasheet, however, the
next time you access the Analysis page, the default datasheet will be displayed again.
You can click the Plant & Equipment Info tab to view information about the piece of
equipment or location that is associated with the RCA Analysis. If desired, you can
modify the fields on this datasheet.
Note: If you make any changes to any of the information on the datasheet, you can click
the Save button on the Common Tasks menu to save your changes.
At the bottom of the page, the following read-only information appears:
Number of Team Members: The number of team members assigned to the current
RCA Analysis.
Number of Preserve Items: The number of RCA Preserve Item records that are
linked to the current RCA Analysis.
Number of Critical Success Factors: The number of CSFs that are associated with
the current RCA Analysis.
From the Analysis page, you can perform tasks related to the RCA Analysis using the
available task menus: Manage Assets, PReserve, Order, Analyze, Communicate, Track,
and Associated Pages.
Note: Links appear on the Associated Pages menu only if they have been configured for
the RCA Analysis family via the URL Manager.
Manage Assets Menu

The Manage Assets menu on the Analysis page contains the following link:
RCA analysis.
PReserve Menu
The PReserve menu on the Analysis page contains the following link:
Preserve Records: Displays the list of existing RCA Preserve Item records that are
linked to the current RCA Analysis.
Order Menu
The Order menu on the Analysis page contains the following links:
Critical Success Factors: Displays the list of existing CSFs that are associated
with the current RCA Analysis.
Team Charter: Displays the team charter that is currently defined for the RCA
Analysis.
Team: Displays the list of team members that are associated with the current RCA
Analysis.
Analyze Menu
The Analyze menu on the Analysis page contains the following links:
Communicate Menu
The Communicate menu on the Analysis page contains the following links:
linked to it.
contain details about the current RCA Analysis.
Track Menu
The Track menu on the Analysis page contains the following link:
Track: Displays the Analysis Tracking Items page, where you can view the RCA
Tracking Item records that are linked to the current RCA Analysis.
About the Catalog Items Used by

PROACT Reports
The Catalog folders \\Public\Meridium\Modules\RCA and
\\Public\Meridium\Modules\RCA\SSRS contain items that are used to support RCA
reports. The Catalog items used by the Comprehensive Analysis Report are located in the
SSRS folder, and the catalog items used by the individual reports are located in the RCA
folder. The following topics explain the Catalog items that are used by these reports.
Note: A copy of the catalog items used by the individual reports also exists in the SSRS
folder, but the Meridium APM systems does not use these items.
Catalog Items Used by the

Comprehensive Analysis Report
The following table lists the name and description of the subreports that are used to
generate the Comprehensive Analysis Report, any queries that support the subreports, and
the Comprehensive Analysis Report sections that the subreports and supporting queries
are used to generate.
Subeport Name
AAAGPage
Behavior and
Usage
Supporting Query
Provides an
None
introduction to the
PROACT RCA
Analysis-At-A-
Comprehensive
Analysis Report
Section
Analysis-At-AGlance
Glance Overview
section.
AAAGReview
Provides a
summary of the
RCA Analysis,
which includes
data such as the
name of the RCA
Analysis, the
name of the
Principal Analyst,
the start date, and
the estimated
completion date.
HypothesisCount
RecommendationMatrix Query
RootCauseCountTaskAssignedCount
Query
TaskAssignedCount Query
TaskCompletedCount Query
VerificationAssignedCount
VerificationCompletedCount
PROACT RCA
Analysis-At-AGlance Overview
Acknowledgements
Displays the value

that exists in the
Acknowledgments
field on the RCA
None
Communicate
datasheet of the
RCA Analysis
record.
Acknowledgeme
AnalzyePage
Provides
information about
the Analyze step None
of a Root Cause
Analysis.
Analyze
CommunicatePage
Provides
information about
the Communicate None
step of a Root
Cause Analysis.
Communicate
Comprehensive Report
Provides
necessary input
for the
None
Comprehensive
Analysis Report.
None
Cover
Provides basic
analysis
information, such
as the Analysis
Name, Principal Cover Query
Analyst, and the
date on which the
report was
generated.
Cover Page
CSF
Provides a list of
the Critical
Success Factors
CSF Query
that are defined
for the RCA
Analysis.
Critical Success
Factors
CSFMain
Provides the
charter and the
Critical Success
Factors that are
defined for the
RCA Analysis.
DataCollection
Provides a list of
the RCA Preserve
Item records that DataCollection Query
are included in the
RCA Analysis.
Data Collection
DataCollectionFileLink
Provides a list of
the RCA Preserve
Item records that DataCollectionFileLink Query
are included in the
RCA Analysis.
Data Collection
File Links
EventDiagram
Provides an image
of the Event
Diagram that
EventDiagramImage Query
exists for the RCA
Analysis
Event Diagram
EventSummary
CSF Query
Provides
None
information stored
in the Event
Charter
Critical
Success
Factors
Event
Summary
Summary
Narrative and the

Mechanism fields
of the RCA
record.
of Findin
LogicTree
Provides an image
of the Logic Tree
LogicTreeImage Query
that exists for the
RCA Analysis.
Logic Tree
OrderPage
Provides
information about
the Order step of a None
Root Cause
Analysis.
Order
PreservePage
Provides
information about
the Preserve step None
of a Root Cause
Analysis.
Preserve (5 P's)
Provides a list of
the Reference
Document records
that are linked to
RecommendationFileLinks the RCA
RecommendationFileLinks Query
Recommendation
records that are
included in the
RCA Analysis.
Recommendation
File Links
Provides a list of
the RCA
Recommendation
RecommendationSummary
None
records that are
included in the
RCA Analysis.
Executive
Summary
Recommendation
Provides a list of
the titles of the
sections that are
None
included in the
Comprehensive
Analysis Report.
Topics Included i
this Report
TableOfContent
TeamMemberPrincipal
Identifies the
Principal Analyst
and identifying
information from
the associated
TeamMemberPrincipal Query
Human Resource
record (e.g., name
and contact
information).
Team Members
TeamMembers
Provides a list of
the team members
who belong to the
RCA Analysis
Team, including
various
identifying
TeamMember Query
information from
the associated
Human Resource
records (e.g.,
name and contact
information).
Team Members
TrackingSummary
Provides
information from
the RCA Tracking
Item records that Tracking Query
are linked to the
RCA Analysis
record.
Tracking Item
Summary
TrackPage
Provides
information about
the Track step of a None
Root Cause
Analysis.
Track
VerificationFileLinks
Provides a list of VerificationFileLink Query

the Reference
Document records
that are linked to
the RCA
Verification
records that are
Verification Log
File Links
included in the
RCA Analysis.
VerificationLogs
Provides a list of
the RCA
Verification
Verification Query
records that are
included in the
RCA Analysis.
Each supporting query that is listed in this table contains a prompt on the ENTY_KEY
field of the RCA Analysis family. When you run a report from the Reports List page, the
ENTY_KEY of the RCA Analysis record associated with the current RCA Analysis is
passed automatically to the prompt. After the ENTY_KEY is passed, the results for the
current RCA Analysis are displayed. If you run an RCA report or query from the Catalog,
however, you will need to supply the ENTY_KEY for an RCA Analysis record manually
to retrieve results.
Catalog Items Used by the Individual

Reports
The following table provides a description of the baseline individual RCA reports. Each
report is built upon a supporting query or dataset that is stored in the same folder as the
report itself. Each report is a formatted view of the corresponding query or dataset. For
additional details on the data that is included in the report, you can run the query itself.
Report Name
Supporting Query
Behavior and Usage
Analysis Summary
Report
Analysis Summary
Query
Provides a summary of the information

that is stored in a given RCA Analysis
record, including information about the
piece of equipment or location associated
with the RCA Analysis.
Analyze - Cause
Report
Analyze - Cause
Query
For a given RCA Analysis, provides a list

of the associated RCA Hypothesis records
whose State field contains the value Cause
Verification Logs
Human, Cause Latent, or Cause Physical.

Provides a summary of the RCA
Hypothesis records that exist in the Logic
Tree of a given RCA Analysis. This report
includes a graph that provides a visual
Analyze - Logic Tree Analyze - Logic Tree representation of the number of RCA
Summary Report
Summary Query
Hypothesis records that are designated as
Cause Human, Cause Latent, and Cause
Physical and a count of the total number of
RCA Hypothesis records not designated as
any "cause."
Provides a list of the RCA Verification
records that are associated with an RCA
Analyze - Verification Analyze - Verification
Analysis record, including the outcome of
Report
Query
each verification and the name of the RCA
Hypothesis record to which it is linked.
Provides a list of the RCA
Recommendation records that are
associated with an RCA Analysis,
including the name of the team member to
whom the RCA Recommendation record is
assigned and information about the due
date and status of the recommendation.
Communicate Recommendation
Report
Communicate Recommendation
Query
Order - Team
Member Report
Provides a list of the team members who

belong to an RCA Analysis Team,
Order - Team Member including various identifying information
Query
from the associated Human Resource
record (e.g., name and contact
information).
Preserve - Preserve
Preserve - Report
Items Report - Group
Query
by Category
Provides a list of the RCA Preserve records

that are linked to an RCA Analysis,
grouped according to the following Data
Categories: Parts, Paper, People, Position,
Paradigms.
Preserve - Preserve
Preserve - Report
Items Report - Group
Query
by Team Member
Provides a list of the RCA Preserve records

that are linked to an RCA Analysis record,
grouped according to the team member
who is responsible for the item.
Each supporting query contains a prompt on the ENTY_KEY field of the RCA Analysis
family. When you run a report from the Reports List page, the ENTY_KEY of the RCA
Analysis record associated with the current RCA Analysis is passed automatically to the
prompt. After the ENTY_KEY is passed, the results for the current RCA Analysis are
displayed. If you run an RCA report or query from the Catalog, however, you will need to
supply the ENTY_KEY for an RCA Analysis record manually to retrieve results.
RCA Analysis
RCA Analysis records store basic information about an RCA Analysis created to track
and analyze causes of equipment and location failures. The following table provides an
alphabetical list and description of the fields that exist for the RCA Analysis family and
appear by default on the RCA Analysis and RCA Analysis Detail datasheets. The
information in the table reflects the baseline state and behavior of these fields. This list is
not comprehensive.
Note: The fields on the Plant & Equipment Info tab exist on the RCA Analysis Detail
datasheet so that you can view this information in analyses where it existed in previous
releases. In the current product, the Manage Assets page allows you to link Equipment
and Functional Location records to the RCA Analysis record, and you no longer need to
view equipment and location information on the RCA Analysis Detail datasheet. If you
do not want to see the Plant & Equipment Info tab by default, in Meridium APM
Configuration Manager you can change the default datasheet for the RCA Analysis
family to the RCA Analysis datasheet, which does not contain the Plant & Equipment
Information tab.
Field
Analysis
Name
Datasheet
Caption
Analysis
Name
Data
Type
Description
Behavior and Usage Datasheets
A value that
identifies the
Root Cause
Analysis
Character record
throughout
the Meridium
APM
product.
RCA
Analysis;
RCA
Analysis
Detail:
Analysis
Details Tab

list of the following
values:
Analysis Type
Analysis
Type
The type of
RCA
Character Analysis you
are
conducting.
Mechanical
Operational
Quality
RCA
Analysis;
Safety
RCA
Analysis
Environmental
Detail:
Analysis
Electrical
Details Tab
Human
You can select the

value that defines the
type of analysis you are
performing.
Asset
Category
Asset Class
Asset ID
Equipment
Category
The category You can type a value in

of equipment this field to describe
Character associated
the piece of equipment
with the RCA identified in the Asset
analysis.
ID field.
RCA
Analysis
Detail:
Plant &
Equipment
Tab
Equipment
Class
The class of You can type a value in

equipment
this field to describe
analysis.
ID field.
RCA
Analysis
Detail:
Plant &
Equipment
Tab
Equipment
ID
A unique
You can type in this
value that
field the name of the
identifies the piece of equipment you
piece of
are analyzing.
Character equipment on Alternatively, you can
which the
link Equipment records
analysis is
to the RCA Analysis
being
record via the Manage
performed. Assets page.
RCA
Analysis
Detail:
Plant &
Equipment
Tab
Asset Type
Charter
Comments
Cost
Date
Published
Equipment
Type
The type of You can type a value in

equipment
analysis.
ID field.
RCA
Analysis
Detail:
Plant &
Equipment
Tab
Text
This value is populated

automatically with the
The purpose
charter you entered on RCA
of and
the Enter Team Charter Analysis;
requirements
RCA
screen of the New
associated
Analysis Builder. If the Analysis
with
full charter does not fit Detail:
conducting
Analysis
in the field, you can
the RCA
Details Tab
Analysis.
click the
button to
see the full text.
Comments
Text
Any
additional
information
about the
current
analysis.
Cost
The
estimated
cost of the
You can type a value in
Number
failure
this field.
event(s) you
are analyzing.
Charter
Date
Published
Date
RCA
You can specify
comments by clicking Analysis;
RCA
the
button and
Analysis
entering comments in Detail:
the Comments dialog Analysis
box.
Details Tab

The date on
When the RCA
which the
Analysis is published,
RCA
this field is updated
Analysis was
published.
published date.
RCA
Analysis;
RCA
Analysis
Detail:
Analysis
Details Tab
RCA
Analysis;
RCA
Analysis
Detail:
Analysis
Details Tab
Division
End Date
Event
Narrative
Frequency
Functional
Location
Division
The division
of the
equipment on
which the
Character
RCA
identified in the Asset
Analysis is
ID field.
being
performed.
RCA
Analysis
Detail:
Plant &
Equipment
Tab
Date
RCA
Analysis;
The end date
RCA
of the
You can select a date
Analysis
analysis, if using the Calendar tool.
Detail:
applicable.
Analysis
Details Tab
Event
Narrative
Text
RCA
Analysis;
Information
You can type a
RCA
about the
description of the event Analysis
equipment
in this field.
Detail:
failure.
Analysis
Details Tab
Frequency
The number
of times the
Number equipment
this field.
failure
occurred.
RCA
Analysis;
RCA
Analysis
Detail:
Analysis
Details Tab
Functional
Location
You can type in this

The location
field the name of the
containing
location that you are
the piece of
analyzing.
equipment on
Alternatively, you can
Character which you
link Functional
are
Location records to the
performing
RCA Analysis record
the RCA
via the Manage Assets
Analysis.
page.
RCA
Analysis
Detail:
Plant &
Equipment
Tab
End Date
Long
Description
Analysis
Text
Description
RCA
A brief
Analysis;
description of You can click the
RCA
the current button and enter text in Analysis
the Analysis
RCA
Detail:
Description dialog box. Analysis
Analysis.
Details Tab
The
manufacturer
of the piece
of equipment
Manufacturer Manufacturer Character
on which you
are
performing
the analysis.
Plant
Location
Start Date
Unit
Plant
Location
The plant
where the
Character equipment
failure
occurred.

the manufacturer of the
piece of equipment
identified in the Asset
ID field.
RCA
Analysis
Detail:
Plant &
Equipment
Tab
You can type a value in RCA

Analysis
the plant location of the Detail:
piece of equipment
Plant &
identified in the Asset Equipment
ID field.
Tab
RCA
Analysis;
The start date
RCA
of the
Analysis
using the Calendar tool.
analysis.
Detail:
Analysis
Details Tab
Start Date
Date
Unit
The ID of the
unit where
the piece of
equipment
for which you
Character
the unit of the piece of
are
equipment identified in
conducting
the Asset ID field.
the RCA
analysis
exists.
RCA
Analysis
Detail:
Plant &
Equipment
Tab
RCA Event
RCA Event records store basic information about a failure event. The following table
provides an alphabetical list and description of the fields that exist for the RCA Event
family and appear by default on the RCA Failure Event datasheet. The information in the
table reflects the baseline state and behavior of these fields. This list is not
comprehensive.
Field
Data
Type
Description
If the RCA Analysis was created from a

Production Event record, this field will be
The end date of the populated automatically with the value in
failure event, if
the End Date field of that Production
applicable.
Event record. Otherwise, you can define
this value manually when you create the
RCA Event record.
Event End
Date
Date
Event ID
The ID for the

Character
failure event.
Event Start
Date
Date
Label
Behavior and Usage
The Event ID field is populated

automatically with RCA-[Current Date]
and is disabled.

populated automatically with the value in
The start date of the
the Start Date field of that Production
failure event.
RCA Event record.

The name of the
failure event as you
want it to appear
Character
the Headline field of that Production Event
for the Failure
record. Otherwise, you can define this
Event node in the
value manually when you create the RCA
diagram.
Event record.
Long
Text
Description
A detailed
description of the
failure event.

the Description field of that Production

RCA Event record.
Short
A brief description This field does not appear on the RCA
Character
Description
of the failure event. Failure Event datasheet by default.
RCA Preserve Item

RCA Preserve Item records store information about tasks assigned to team members to
collect failure data by a certain date. The following table provides an alphabetical list and
description of the fields that exist in the RCA Preserve Item family and appear by default
on the RCA Preserve Item datasheet. The information in the table reflects the baseline
state and behavior of these fields.
Field
Collection
Strategy
Datasheet Data Type

Caption
Collection
Strategy
Text
Description
A description of
the way in
which the data
should be
collected (e.g.,
acquire
production logs
from a line
supervisor).
Data
Category
On the RCA Preserve Item

datasheet, you can click the
button to define this value
manually via the Collection
Strategy dialog box.
You can choose Yes or No

depending on the status of the
data collection. When you set
this value to Yes, the Date
Completed field will be
populated automatically with the
current date.
This field contains a list of the
Character The type of data following values representing
you want a team
A value that
specifies
whether or not
Completed? Completed? Character
the data
collection is
completed.
Data
Category
Behavior and Usage
the 5 P's:
member to
collect.
People
Parts
Paper
Position
Paradigms
You can select the option that

defines the type of data that
should be collected.
Data To
Collect
Data To
Collect
A description of
On the Preserve Failure Data
the data that will
page, the text that is specified in
be collected for
this cell will appear as a
Character the category that
hyperlink you can click to
you selected in
access the RCA Preserve Item
the Data
record.
Category field.
Date
Completed
Date
Completed
Date
When the Completed? field is

The date on
set to True, the Date Completed
which the data- field will be populated
collection was automatically with the current
completed.
date and time. You can modify
the date if necessary.
Date Due
Date Due
Date
The deadline for

You can select a date using the
collecting the
Calendar tool.
data.
Days Before Days Before

Due Date to Due Date to Number
be Notified be Notified
Frequency
After Due
Frequency
After Due
The number of
days prior to the
due date that an
alert message is
sent to the team
member to
whom the
record is
assigned.
Character The frequency

after the due
This field is enabled only when

the Send Alert on Due Date?
field is set to True. Then this
field is required. You must enter
a numeric value in this field, or
an error message will appear.
The units for this field are
automatically set to Days.
the Send Alert on Due Date?
field is set to True. Then this
field is required. This field

contains a list of the following
values:
Date to be
Notified
date that an alert

message will be
sent to the team
member to
whom the
record is
assigned.
Date to be
Notified
Never
Daily
Weekly
Monthly
Yearly

defines how frequently an alert
should be sent after the due date
of the RCA Preserve Item
record.
On the RCA Preserve Item
datasheet, you can click the
Notification Alert Email

Text
Email Body Body
The body of the

alert that will be
sent via email.
Send
Send Alert
Notification
on Due
on Due
Date?
Date?
This field is enabled when there

is a value in the Due Date field.
A value that
When this field is set to True,
specifies
when you save the RCA
whether or not Preserve Item record, an Alert
an alert email record will be created
message will be automatically in the Meridium
sent to the team APM database and a Scheduled
member to
Item will be created
whom the
automatically in the Schedule
record is
Manager. The Alert record that
assigned.
was created automatically will
not be linked automatically to
Logical
button to define this value

manually via the Alert Email
Body dialog box.
RCA Recommendation
RCA Recommendation records store details of a recommendation and the progress
associated with getting the recommendation approved and implemented. The following
table provides an alphabetical list and description of the fields that exist for the RCA
Recommendation family. The information in the table reflects the baseline state and
behavior of these fields. This list is not comprehensive.
Field
Datasheet
Caption
Date Type
Description
Alert Assignee
When Due?
Analysis ID
The ID of the
RCA Analysis
RCA Analysis ID Character associated with
the
recommendation.
Asset ID
Equipment ID
Assigned to
Name
Assigned to
Name
Datasheet
If this field is set to

An option that
True, the Meridium
lets you send an APM system will send
RCA
alert to the person an alert to the person in
Recommendation
responsible for the Assigned to Name
Tab
implementing the field on the date
recommendation. defined in the Target
Completion Date field.
Alert
Responsible
Party When
Due?
Logical
Behavior and Usage
The Record ID
for the
Equipment
Character Record
associated with
the
recommendation.
Character The name of the

person
responsible for
ensuring the
This field is
automatically populated
RCA
when an RCA
Recommendation
Recommendation
General Informati
record is linked to an
Tab
RCA Analysis record,
and is disabled.
You can define this
field by clicking the
button and
RCA
searching for the
Recommendation
desired Equipment
General Informati
record, selecting it, then
Tab
clicking OK to link it to
the RCA
Recommendation
record.
You can select a team
member from a list of
current RCA Analysis
RCA
Recommendation
General Informati
Tab
recommendation
Team Members.
is implemented.
Author Name
Author Name
The name of the

person proposing
Character
the
recommendation.
The impact to the

manufacturing
process during
Business Impact Business Impact Character
the
recommendation
implementation.
Cause
Cause Type
Completed
Completion
Comments

Team Members.
You can choose this
value from a list of the
following options:
RCA
Recommendation
General Informati
Tab
RCA
Safety
Recommendation
Environmental
General Informati
Tab
Production
Economic
Cause
A description of
the cause of the
problem the
Character
recommendation
has been created
to fix.
You can choose from a

list of RCA Hypothesis
records that you have
identified as causes in
the Logic Tree for the
RCA Analysis.
RCA
Recommendation
General Informati
Tab
Cause Type
This field is disabled

The type of cause
and populated
of the problem
the
Character
value in the State field
recommendation
of the RCA Hypothesis
has been created
record identified in the
to fix.
Cause field.
RCA
Recommendation
General Informati
Tab
Completed
Close-Out
Comments
Logical
You can set this value None

Indicates that the
to True to indicate that
recommendation
this recommendation is
is complete.
complete.
Text
This field is required if

Details about the
the value in the Status
completed
field is Rejected or
recommendation.
Superseded.
RCA
Recommendation
General Informati
Tab
Date
The date the
RCA
Creation Date
Creation Date
This field is disabled
and populated
automatically with the Recommendation
recommendation
date on which the RCA General Informati
was created.
Recommendation
Tab
record was created.
Create SAP
Notification?
Date Reviewed
Create Work
Request?
Date Reviewed
Logical
If the SAP Interfaces

module has been
implemented and this
field is set to True,
when the RCA
Recommendation
record is saved, a
Creates an SAP
notification will be
Notification for
created in SAP, and the
the corresponding
Work Reference
recommendation.
Request, Work Request
Equipment, and Work
Request Functional
Location fields will be
populated with values
from the corresponding
notification.
Date
The date the

recommendation
status was
changed to
Reviewed.
RCA
Recommendation
General Informati
Tab

current date when the None
Status field is updated
to Reviewed.
The numbers of
days prior to the
Days before Due Days before Due
target date that
Date to be
Date to be
Number
the email
Notified
Alerted
message should
be sent.
This field is enabled

only when the Alert
RCA
Responsible Part When
Recommendation
Due? field is set to
Alert Tab
True. Then the field is
required.
Equipment
Technical
Number
When you select a

RCA
value in the Equipment Recommendation
ID field, this field is
General Informati
populated automatically Tab
with the value in the
Equipment Technical
Number field of the
associated Equipment
Technical
Number
Character The technical

number of the
piece of
equipment for
which the
recommendation
is being made.
record.
Final Action
Taken
Final Approver
Name
You can define this

None
The actions taken field manually by
to implement the typing a description of
recommendation. final actions in this
field.
Final Action
Taken
Text
Final Approver
Name
The name of the

person ultimately
responsible for
Character approving the
recommendation
and the
associated cost.

Team Members.
RCA
Recommendation
General Informati
Tab

only when the value in
the Alert Responsible
Part When Due? field is
True, in which case this
field is required, and
you can choose a value
from the list of
The frequency
following values:
Frequency of
Frequency of
RCA
after the target
Alert After Due Alert After Due Character
Recommendation
date that the alert
Never
Date
Date
Alert Tab
will be resent.
Daily
Functional
Location ID
Functional
Location ID
Weekly
Monthly
Yearly
Character The Record ID of This value is populated RCA

the Functional
automatically if a
Recommendation
Location record Functional Location
General Informati
that is either
record exists and is
Tab
linked to the
linked to the Equipment
Equipment record record that appears in
that appears in
the Equipment ID field.
the Equipment ID You can also click the
field or linked
button to search
separately to the
for the desired
RCA
Functional Location
record, select it, then
Recommendation click OK to link it to
record.
the RCA
Recommendation
record.
Hypothesis ID
Hypothesis
The ID of the
None
hypothesis
automatically if the
Number associated with RCA Recommendation
the corresponding record is linked to an
RCA Analysis. RCA Analysis record.
Implementation Implementation
Text
Alert Text
Alert Text
Text the user can

add that will be
sent in the body
of the alert to the You can type the text
assignee to
you wish to appear in
remind them the the Alert email.
recommendation
must be met by
the target date.
Implemented
Date
Date
The date the

recommendation
was
implemented.
Date
The date by
RCA
which the
You can select a date Recommendation
recommendation
using the Calendar tool. General Informati
must be
Tab
implemented.
Implemented
Date
Mandatory Date
Mandatory Date

automatically when the
RCA Recommendation
record is implemented.
When this occurs, the
field becomes disabled.
Background
You can type any
information about
Recommendation Recommendation
necessary background
Character why the
Basis
Basis
information in this
recommendation
field.
is being made.
RCA
Recommendation
Alert Tab
RCA
Recommendation
General Informati
Tab
RCA
Recommendation
General Informati
Tab
None
Recommendation Recommendation Date

Closure Date
Closure Date
The date the

recommendation automatically with the
status is changed current date when the
value in the status field

to Implemented,
is changed to
Rejected, or
Implemented, Rejected,
Superseded.
or Superseded.
You can type a
A detailed
description of the
description of the
recommendation in this
recommendation.
field.
RCA
Recommendation
General Informati
Tab
You can type a brief

A brief summary
summary of the
Character of the
Headline
Headline
recommendation in this
recommendation.
field.
RCA
Recommendation
General Informati
Tab

automatically with a
The Record ID unique name (e.g.,
for the RCA
REC_888) when the
Character
ID
ID
Recommendation recommendation is
record.
created. You can
change this value if
desired.
RCA
Recommendation
General Informati
Tab
You can chose from a

A value that
represents the
values:
priority or
criticality level of
High
Character
Priority
Priority
the
Medium
recommendation
for
Low
implementation.
RCA
Recommendation
General Informati
Tab
Text
Description
Description
Reevaluate?
Reevaluate?
Logical
Reevaluation
Reevaluation
Text
Alert Body Text Alert Body Text
Indicates whether
If the value is set to
team members
True, an alert will be RCA
should evaluate
sent to users specified Recommendation
the
in the Reevaluation
Alert Tab
recommendation
Notification List field.
again.
The message text This field is enabled

RCA
in the body of the only when the
Recommendation
reevaluation alert, Reevaluate? field is set Alert Tab
which will be
to True. Then the field
sent to users in is required.
the reevaluation
notification list.
Reevaluation
Reevaluation
Notification List Alert List
Reevaluation
Date
Required
Equipment
Status

only when the
Reevaluate? field is set
Individuals that
RCA
to True. Then the field
Character will be sent to the
Recommendation
is required. You can
reevaluation alert.
Alert Tab
select from a list of
names with Human
Resource records.

The date on
only when the
which an alert is
Reevaluate? field is set RCA
sent out to tell the
to True. Then the field Recommendation
alert recipient to
is required. You can
Alert Tab
re-evaluate the
select a date using the
recommendation.
Calendar tool.
Reevaluation
Date
Date
Required
Equipment
Status

The operating
status the piece of values:
equipment must
be under, in order
On-line
Character
for the
Off-line
recommendation
to be
Not Applicable
implemented.
The name of the

person
responsible for
Reviewer Name Reviewer Name Character
reviewing and
endorsing the
recommendation.

Team Members.
RCA
Recommendation
General Informati
Tab
RCA
Recommendation
General Informati
Tab
This value does n

appear on the data
The ID of the
by default.
Status Changed Status Changed
user who last
Character
automatically when the
By
By
changed value in
Status field is updated.
the Status field.
The name of the

This field is populated This value does n
Status Changed Status Changed
person who last
Character
automatically when the appear on the data
by Name
by Name
changed the
Status field is updated. by default.
Status field.
Status Date
Status
Status Date
Status
Date
Character
The date the

Status field was
most recently
changed.
The status of the

recommendation.
This value does n

This field is populated appear on the data
automatically with the by default.
current date when the
Status field is updated.
values:
Created
Pending Review
Reviewed
Rejected
Superseded
In Progress
Implemented
RCA
Recommendation
General Informati
Tab
When the record is

created, the field set
populated automatically
to Created, but can be
modified if needed.
The date the

RCA
Target
Target
recommendation
Recommendation
Date
using the Calendar tool.
Completion Date Completion Date
is intended to be
General Informati
implemented.
Tab
This value does n
The ID of the
This field is populated appear on the data
by default.
Work Order
Work Order
work order
automatically after a
Character
Number
Number
arising from the notification has been
work request.
created in SAP.
Work Request
Equipment
Work Request
Equipment
The Record ID of
the Equipment in
SAP that is
Character associated with
notification has been
the SAP
created in SAP.
Notification that
was created.
RCA
Recommendation
General Informati
Tab
Work Request
Functional
Location
Work Request
Functional
Location
The Record ID of
the Functional
Location in SAP
Character that is associated
notification has been
with the SAP
created in SAP.
Notification that
was created.
Work Request
Reference
Work Request
Reference

The ID of the
Character
SAP Notification. notification has been
created in SAP.
RCA Tracking Item

RCA Tracking Item records store a set of conditions on which reevaluation notifications
should be based. The following table provides an alphabetical list and description of the
fields that exist for the Tracking Item family and appear by default on the RCA Tracking
Item Details datasheet. The information in the table reflects the baseline state and
Field
Datasheet Data Type Description

Caption
Indicates whether
the RCA Tracking
Item record is
included in the
tracking and
reevaluation process
(i.e., active).
Active
Active
Logical
Cost
Cost
Number The failure cost that

must be met for a
revaluation email to
be sent to the user
Behavior and Usage
When you create a new RCA

Tracking Item record, the Active
field is set to True by default.
You set the value to False to
indicate that the record is
inactive.
Tracking Item record, you can
manually type a value in this
field, but the value must be
RCA
Recommendation
General Informati
Tab
RCA
Recommendation
General Informati
Tab
numeric, or an error message

specified in the Alert
will appear when you move to
field.
another field.
The number of
failures that must
occur before a
Number reevaluation email is
sent to the user
specified in the Alert
field.

Tracking Item record, you can
manually type a value in this
field, but the value must be
numeric, or en error message
will appear when you move to
another field.
Count
Count
Message
Subject
The text that you

You can manually type the
Message
that want to appear
Character
subject of the email message in
Subject
in the subject line of
this field. This field is required.
the email message.
Message
Text
Message
Text
Text
Notification
Alert
List
Start Date
Start
Date
On the RCA Tracking Item

Details datasheet, you can
define this field manually by
The text that you

want to appear in the
clicking the
button and
body of the email
entering text in the Message
message.
Text dialog box. This field is
required.
The names of the

users to which a
notification should
be sent when the
specified
Character
reevaluation criteria
is met (i.e., the
values stored in the
Count and Cost
fields).
Date
The date on which

the evaluation will
begin.
You can select a team member

from a list of current RCA
Analysis Team Members. When
you select a name in the list, the
email address that is stored in
the corresponding Security User
record appears, and after you
navigate away from the Alert
field, the user's name appears in
the Alert field. This field is
required.
Calendar tool. This field is
required.
RCA Verification
RCA Verification records store task-related information necessary to verify a hypothesis.
for the RCA Verification family and appear by default on the RCA Verification datasheet.
The information in the table reflects the baseline state and behavior of these fields.
Field
Datasheet
Caption
Data
Type
Description
Behavior and Usage
On the RCA Verification

datasheet, you can choose Yes
A value that
or No from the Completed? list.
specifies whether
Completed? Completed? Character
When you set this value to Yes,
or not the task is
the Date Completed field will be
completed.
populated automatically to the
current date.
Date
Completed
Date
Completed
Date

The date on
automatically with the current
which the task
date when the Completed? field
was completed.
is set to Yes.
The number of This field is enabled only when

days prior to the the Send Alert on Due Date?
due date that an field is set to True. Then this
Days Before Days Before
alert message is field is required. You must enter
Due Date to Due Date to Number
sent to the team a numeric value in this field, or
be Notified be Notified
member to whom an error message will appear.
the record is
The units for this field are
assigned.
automatically set to Days.
The deadline for
completing the
task.
Due Date
Due Date
Date
Calendar tool.
Frequency
After Due
Date to be
Frequency
After Due
Date to be

Character The frequency the Send Alert on Due Date?
after the due date field is set to True. Then this
field is required. This field
that an alert
contains a list of the following

values:
Notified
message will be
sent to the team
member to whom
the record is
assigned.
Notified
Never
Daily
Weekly
Monthly
Yearly

defines how frequently an alert
should be sent after the due date
of the RCA Preserve Item
record.
Method
Method
Text
Notification Alert Email

Text
Email Text Text
Outcome
Outcome
Send
Send Alert
Notification on Due
on Due Date? Date?
Text
How the task

was completed.

datasheet, you can define this
field manually by clicking the
button and entering text in
the Method dialog box.

The body of the
alert that will be
sent via email.
the Alert Email Text dialog box.
The result of
completing the
task.

the Outcome dialog box.
Logical A value that

This field is enabled when there
specifies whether is a value in the Due Date field.
or not an alert
When the Send Notification on
email message Due Date? field is set to True,
will be sent to
when you save the RCA
the team member Verification record, an Alert
to whom the
record will be created
record is
assigned.
automatically in the Meridium

APM database and a Scheduled
Item will be created
automatically in the Schedule
Manager. The Alert record that
was created automatically will
not be linked automatically to
URL Paths for Root Cause Analysis

The following table lists and describes the paths for accessing features in the Meridium
Root Cause Analysis module. 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
Path
Description
Root Cause
Analysis T Start
Page
RCA
Displays the Root Cause Analysis Start

Page. This URL does not accept any
parameters.
RCA
Administrative
Tools
RCA/AdminTools
Serves as the path for accessing the

Administrative Functions page. This path
accepts one parameter.
Manage Analyses RCA/AllAnalyses
Displays the Manage Analyses page in

RCA. This path does not accept any
parameters.
RCA Analysis
RCA/Analysis
Serves as the path for accessing RCA

Analyses. This path accepts parameters
that let you specify which analysis to
access.
RCA/AnalysisBuilder
Serves as the path for the New Analysis

Builder. The path accepts parameters that
let you specify how to build the analysis.
New Analysis
Builder
RCA/Communicate

Communicate records. This path accepts
parameters that let you specify which
records to access.
RCA/CSF
Launches the Critical Success Factors

page. This path accepts a parameter that
lets you specify the analysis whose CSFs
you want to view.
Event Diagram
RCA/EventDiagram
Serves as the path for accessing an Event

Diagram page. This path accepts
parameters that let you specify the desired
analysis.
Logic Tree
RCA/LogicTree
Serves as the path for accessing an Logic

Tree page. This path accepts parameters
that let you specify the desired analysis.
Manage Assets
Serves as the path for accessing the

Manage Assets page. This path accepts
RCA/MANAGEASSETS
parameters that let you specify the desired
analysis.
My PROACT
RCA/MyPROACT
Communicate
Records
Critical Success
Factors
Serves as the path for displaying the My

PROACT page. This path requires one
parameter.
Principal Analyst's
RCA/PAView
View
Launches the PA PROACT page. This path

does not accept any parameters.
Preserve Records RCA/PreserveRecords
Displays the Preserve Failure Data page.

This path accepts one parameter that lets
you access the failure data for a specific
analysis.
RCA Reports
RCA/Reports

reports. This URL accepts a parameter
that lets you specify the analysis for which
to access reports.
RCA Team
RCA/Team
Serves as the path for accessing the Team

page in RCA. This path accepts
parameters that let you specify the
analysis for which to access the team.

Tracking Items
RCA/Track
Displays the Analysis Tracking Items

page. This path accepts parameters that let
you customize the URL.
Parameter for the Administrative

Functions URL
The URL for accessing a specific RCA Analysis, meridium://RCA/AdminTools, accepts
the parameter described in the following table.
Parameter
Name
Description
Accepted
Value(s)
Notes
View
Specifies to display the

AdminTools
This parameter is
required.
Examples of the Administrative

Functions URL
meridium://RCA/AdminTools?View=AdminTools
Displays the Administrative Functions page, where you can perform administrative tasks
for RCA.
Parameters for the RCA Analysis URL

The URL for accessing a specific RCA Analysis, meridium://RCA/Analysis, accepts the
parameters described in the following table.
Parameter
Name
Description
Accepted
Value(s)
Notes
This parameter is required only when

Specifies which The Entity Key View=Template or View=PubAnalysis.
AnalysisKey analysis you
of the desired If you omit this parameter and use
want to view. analysis.
View=Analysis, the link will open a new
analysis.
Analysis
View
Specifies which Template

view to display.
PubAnalysis
Examples of the RCA Analysis URL
meridium://RCA/Analysis?View=Analysis
Opens the Analysis page, where you can create a new analysis.
meridium://RCA/Analysis?View=Analysis&AnalysisKey=2791890
Opens the Analysis page for the RCA Analysis with the Entity Key 2791890.
meridium://RCA/Analysis?View=Template&AnalysisKey=2791890
Opens the analysis with the Entity Key 2791890 in the Analysis Template form.
meridium://RCA/Analysis?View=PubAnalysis&AnalysisKey=2791890
Opens the analysis with the Entity Key 2791890 in the Published Analysis form.
Parameters for the Analysis Builder

URL
The URL for accessing the New Analysis Builder in RCA,
meridium://RCA/AnalysisBuilder, accepts the parameters described in the following table.
Parameter
Name
Description
Accepted
Value(s)
Action
Specifies whether
BuildAnalysis
to create a brand
new analysis or to
-ORuse an existing
analysis as a
CopyAnalysis
template to create
a new analysis.
AnalysisKey
Specifies which
analysis you want
to copy to create a
new analysis.
Field ID
Notes
This parameter is required. If

Action=CopyAnalysis, you must
also define the AnalysisKey
parameter.
The Entity Key

of the desired This parameter is required only
RCA Analysis when Action=CopyAnalysis.
record.
To use this parameter, the Action
Specifies fields in Values that are parameter value must be set to
the new RCA
appropriate for BuildAnalysis.
Analysis record the specified
that you want to fields.
When you construct a URL to
populate
create a new RCA Analysis, you
automatically.
can specify values that will be used
to populate fields in that RCA
Analysis record automatically. The
actual parameter names should
correspond to fields that you want
to populate. You must use the field
ID as the parameter name. The
parameter values will vary
depending on the values that you
want to use to populate the fields,
but you should make sure to
specify values that are appropriate
for the field types (e.g., specify
numbers for numeric fields).

Specifies the
Equipment or
Functional
AssetEntityKey Location record
that you want to
link to the RCA
Analysis record.
If you want to link the RCA

The Entity Key
Analysis to an Equipment or
of the desired
Functional Location record, you
Equipment or
must use the AssetEntityKey
Functional
parameter and the AssetFamilyKey
Location record.
parameter.
Specifies the
Equipment or
Functional
Location family
AssetFamilyKey containing the
record that you
want to link to the
RCA Analysis
record.
If you want to link the RCA

The Family Key
Analysis to an Equipment or
of the desired
Functional Location record, you
Equipment or
will need to use the
Functional
AssetFamilyKey parameter and the
Location family.
AssetEntityKey parameter.
Examples of the Analysis Builder URL
meridium://RCA/AnalysisBuilder?Action=BuildAnalysis
Opens the New Analysis Builder, where you can create a new RCA Analysis.
meridium://RCA/AnalysisBuilder?Action=CopyAnalysis&AnalysisKey=123456
Opens the New Analysis Builder and loads the information from the analysis with the
Entity Key 123456, which you can use as the basis for creating a new analysis.
meridium://RCA/AnalysisBuilder?
Action=BuildAnalysis&MI_AN_ANALY_ID_CHR=RCA Analysis Example
Displays the RCA Analysis Datasheet screen of the New Analysis Builder with the
Analysis Name cell populated automatically with the value RCA Analysis Example.
meridium://RCA/AnalysisBuilder?
Action=BuildAnalysis&AssetEntityKey=123546&AssetFamilyKey=987654
Displays the RCA Analysis Datasheet screen of the New Analysis Builder. If you
continue to the Select an Asset screen of the New Analysis Builder, the Asset text box
will contain the Record ID of the record with the Entity Key 123456, which belongs to
the family with the Family Key 987654.
Parameters for the Recommendation

Records URL
The URL for accessing RCA Recommendation records,
meridium://RCA/Communicate, accepts the parameter described in the following table.
Parameter
Name
Description
Accepted Value(s)
Specifies the analysis for which

AnalysisKey you want to view
desired analysis.
Recommendation records.
RecommKey
Notes
This
parameter is
required.

This
Specifies the Recommendation
desired Recommendation parameter is
record that you want to view.
record.
optional.
Examples of Recommendation Records

URLs
meridium://RCA/Communicate?AnalysisKey=2860801
Displays the Communicate Records page, which displays the Recommendation records
for the analysis with the Entity Key 2860801.
meridium://RCA/Communicate?AnalysisKey=2860801&RecommKey=2579812
Displays the Communicate Records page, which displays the Recommendation record
with the Entity Key 2579812 for the analysis with the Entity Key 2860801.
Parameters for the Critical Success

Factors URL
The URL for accessing Critical Success Factors, meridium://RCA/CSF, accepts the
Parameter
Name
Description
Accepted
Value(s)
Specifies the analysis

The Entity Key
for which you want to
AnalysisKey
of the desired
view Critical Success
analysis.
Factor records.
CsfKey
The Entity Key

Specifies which
of the desired
specific CSF you want
Critical Success
to open.
Factor record.
Accepted Value(s)
This parameter is optional.
Omitting this parameter,
however, will result in a link
that opens an empty Critical
Success Factors page.
The Critical Success Factor that
you specify must be associated
with the analysis indicated by
the AnalysisKey parameter.
Examples of the Critical Success Factors

URL
meridium://RCA/CSF?AnalysisKey=1234567
Opens the Critical Success Factors page, displaying the Critical Success Factors that have
been defined for the analysis with the Entity Key 1234567.
meridium://RCA/CSF?AnalysisKey=123445&CsfKey=2791902
Displays the CSF Details page for the Critical Success Factor record with the Entity
Key 2791902.
Parameters for the Event Diagram URL

The URL for accessing the Event Diagram for an analysis,
meridium://RCA/EventDiagram, accepts the parameters described in the following table.
Both of these parameters are required.
Parameter
Name
Description
Accepted Value(s)
Notes
AnalysisKey
Specifies the analysis whose Event The Entity Key of the This parameter
Diagram you want to view.
desired analysis.
is required.
View
Specifies that you want to display

the Event Diagram page for the
EventDiagram
specified analysis.
This parameter
is required.
Examples of the Event Diagram URL
meridium://RCA/EventDiagram?View=EventDiagram&AnalysisKey=2791890
Opens the Event Diagram page for the analysis with the Entity Key 2791890.
Parameters for the Logic Tree URL
The URL for accessing the RCA Logic Tree, meridium://RCA/LogicTree, accepts the
Parameter
Name
Description
Accepted
Value(s)
Notes
Specifies the analysis The Entity Key

AnalysisKey for which you want to of the desired This parameter is required.
view the Logic Tree. analysis.
NodeKey
The node that you specify must

Specifies which node The Entity Key
belong to the Logic Tree that exists
in the Logic Tree that of the desired
for the analysis defined by the
you want to view.
node.
AnalysisKey parameter.
Examples of the Logic Tree URL
meridium://RCA/LogicTree?AnalysisKey=2791890
Opens the Logic Tree page, displaying the Logic Tree for the analysis with the Entity Key
2791890.
meridium://RCA/LogicTree?AnalysisKey=2791890&NodeKey=1234567
Opens the Logic Tree page, displaying the Logic Tree for the analysis with the Entity Key
2791890 with the node with the Entity Key 1234567 selected.
Parameters for the Manage Assets URL

The URL for accessing Critical Success Factors, meridium://RCA/MANAGEASSETS,
accepts the parameters described in the following table.
Parameter
Name
AnalysisKey
Description
Accepted
Value(s)
Notes
Specifies the analysis for which you

want to link and unlink Equipment
and Functional Location records.
The Entity Key

of the desired
analysis.
This
parameter is
required.
Examples of the Manage Assets URL
meridium://RCA/MANAGEASSETS?AnalysisKey=1234567
Opens the Manage Assets page, displaying the Equipment and Functional Location
records that are linked to the analysis with the Entity Key 1234567.
Parameters for the My PROACT URL

The URL for accessing the My PROACT page, meridium://RCA/MyPROACT, accepts the
parameter described in the following table.
Parameter
Name
Description
Accepted
Value(s)
Notes
View

the My PROACT page.
MyPROACT
This parameter is
required.
Examples of the My PROACT URL
meridium://RCA/MyPROACT?View=MyPROACT
Opens the My PROACT page, displaying a list of analyses for which the current user is a
team member.
Parameters for the Preserve Records

URL
The URL for accessing the Preserve Failure Data page,
meridium://RCA/PreserveRecords, accepts the parameters described in the following
table.
Parameter
Name
Description

AnalysisKey
view the Preserve
Failure Data page.
RecordKey
Specifies a particular
Preserve Record that
you want to view.
Accepted
Value(s)
Notes
Omitting this parameter will

The Entity Key create a link that displays the
of the desired Preserve Failure Data page but
analysis.
does not display any Preserve
Records.
The Entity Key
of the desired This parameter is optional.
Preserve record.
Examples of the Preserve Failure

Records URL
meridium://RCA/PreserveRecords
Displays the Preserve Failure Data page but does not list any Preserve records in the grid.
meridium://RCA/PreserveRecords?AnalysisKey=1234567
Opens the Preserve Failure Data page, which displays the Preserve records for the
analysis with the Entity Key 1234567.
meridium://RCA/PreserveRecords?AnalysisKey=1234567&RecordKey=1234568
Displays the Preserve Record Details page for the Preserve record with the Entity Key
1234568.
Parameters for the RCA Reports URL

The URL for accessing the RCA reports, meridium://RCA/Reports, accepts the parameter
described in the following table.
Parameter
Name
Action
Description
Accepted Value(s)
Notes
Use this parameter if you

want to open the baseline
comprehensive RCA report.
Specifies that
ViewComprehensiveReport Note that ALL sections of the
action that you
report will be displayed when
want to
the report appears on the
perform using
Report Viewer page.
the URL.
AnalysisKey Specifies the The Entity Key of the

analysis whose desired analysis.
report you
want to view.
If you use the AnalysisKey

parameter and the Action
parameter, the comprehensive
report for the associated
analysis will be displayed.
If you use the AnalysisKey
parameter without the Action
parameter, the Report List
Screen page will be displayed,

where you can select the
report that you want to open
for the analysis specified by
the AnalysisKey parameter.
Examples of the RCA Reports URL
meridium://RCA/Reports?AnalysisKey=2791890
Opens the Reports List Screen, displaying the reports associated with the RCA analysis
with the Entity Key 2791890.
meridium://RCA/Reports?
Action=ViewComprehensiveReport&AnalysisKey=2791890
Opens the baseline comprehensive report for the analysis with the Entity Key 2791890.
Parameters for the RCA Team URL

The URL for accessing the Team page for a RCA Analysis, meridium://RCA/Team,
accepts the parameters described in the following table. Both of these parameters are
required.
Parameter
Name
Description
Accepted Value(s)
Notes
AnalysisKey
Specifies the analysis for which

The Entity Key of This parameter
you want to access the Team page. the desired analysis. is required.
View

the Team page for the specified
TeamList
analysis.
This parameter
is required.
Examples of the RCA Team URL
meridium://RCA/Team?View=TeamList&AnalysisKey=2791890
Displays the Team page, which displays a list of users who are on the team for the RCA
Parameters for the Tracking Items URL

The URL for accessing the Tracking Items functionality, meridium://RCA/Track, accepts
the parameters described in the following table.
Parameter
Name
Description

AnalysisKey
view the Analysis
Tracking Items page.
ItemKey
Specifies a particular
Tracking Item record
that you want to view.
Accepted
Value(s)
Notes
Omitting this parameter will

The Entity Key create a link that displays the
of the desired
Analysis Tracking Items page
analysis.
but does not display any
Tracking Items.
The Entity Key
of the desired
This parameter is optional.
Tracking Item
record.
Examples of the Tracking Items URL
meridium://RCA/Track
Displays the Analysis Tracking Items page but does not list any Tracking Items in the
grid.
meridium://RCA/Track?AnalysisKey=1234567
Opens the Analysis Tracking Items page, which displays the Tracking Items for the
meridium://RCA/Track?AnalysisKey=1234567&ItemKey=1234568
Displays the Tracking Item Details page for the Tracking Item with the Entity Key
1234568.

Elements of an RCA Analysis that allow the RCA Analysis Team to evaluate whether or
not the analysis effort has been successful. The RCA Analysis effort is considered to be
successful if the analysis team adheres to and meets the standards defined by the CSFs.
Event Diagram
A diagram that depicts a chain of events that led to a failure event. The Event Diagram
allows you to analyze events that led to a failure event and identify possible work process
problems.
Failure Event
The problem that the RCA Analysis Team is analyzing in a Root Cause Analysis. A
failure event could be comprised of several failures over a specified period of time (e.g., a
pump that overheats several times a month) or one failure (e.g., a fire).
Logic Tree
A diagram that depicts possible causes and hypotheses related to the failure event. The
Logic Tree allows you to record discussion points and organize information in order to
eliminate hypotheses and determine the root cause of the failure event.
RCA Analysis Team

A group of individuals who will complete the steps required for a comprehensive RCA
Analysis. Each RCA Analysis Team is made up of a Principal Analyst, who facilitates and
coordinates the RCA Analysis, and analysis team members.
Team Charter
The goal that the RCA Analysis Team wants to achieve by developing an RCA Analysis.
What Is Reliability Analytics?
The Reliability Analytics module is part of the Failure Elimination work process and
provides a collection of tools that apply reliability engineering principles to help you
make tactical (short term) and strategic (long term) decisions for maintenance and
operational equipment management activities. It provides a means for analyzing
historical failure data to identify trends and predict future failures, and it provides a
mechanism for to simulating what if scenarios regarding the reliability of a system to
determine if a new or modified strategy will be effective.
The Reliability Analytics module provides the following types of Reliability analyses:
Production Analysis
Spares Analysis
Reliability Growth Analysis
Reliability Distribution Analysis
Probability Distribution Analysis
System Reliability Analysis
Cost of Unreliability Analysis
Each analysis type provides a unique set of features and tools that allow you to analyze
data to develop strategies to improve reliability. D
Reliability Analytics System

Requirements
The Reliability Analytics license is required to take advantage of Reliability Analytics
functionality. In addition, your system must contain the basic Meridium APM system
architecture.
Hint: Details on the system requirements for the basic architecture and activating
licenses can be found in the Installation, Upgrade, and System Administration section of
the Meridium APM Help system.
perform some configuration tasks specifically for the Reliability Analytics feature.
About the Reliability Analytics Data

Model
The Reliability Analytics module is unique compared to other Meridium APM modules in
that you are not required to use all Reliability Analytics features to complete the
Reliability Analytics workflow. Rather, each analysis type has its own workflow and can
be used independently of all other analysis types. As such, this documentation does not
include a comprehensive Reliability Analytics data model and instead includes a data
model that is specific to each analysis type:
Production Analysis Data Model

Spares Analysis Data Model
Reliability Growth Analysis Data Model
Reliability Distribution Analysis Data Model
Probability Distribution Analysis Data Model
System Reliability Data Model
Cost of Unreliability Data Model
Note: The separation of analysis types and their respective data models within this
documentation is not meant to indicate that you would not want to use more than one
analysis type but that you are not required to do so. In many cases, you may need to
perform more than one type of analysis to get a complete understanding of the data (e.g.,
the results of a Growth Analysis may indicate that you should perform a Reliability
Distribution Analysis).
Production Analysis Data Model

The following diagram shows the Production Analysis entity families and the
relationships that exist between them. The shaded boxes represent entity families, and the
arrows represent relationship families. You can determine the direction of the each
relationship definition from the direction of the arrow head: the box from which the arrow
originates is the predecessor, and the box to which the arrow heard points is the
successor.
As you develop a Production Analysis, you will create records in these families and link
them together, either manually or automatically via the options in the Meridium APM
Framework. Throughout this documentation, we use the term Production Analysis to
mean the combination of the Production Analysis record and all the records that are
linked to it.
A Production Analysis is meant to be conducted at the unit level and can be linked to a
Functional Location record representing a unit or a Production Unit record representing
the same unit. The Production Unit family will be available only if the Production Loss
Accounting (PLA) module is active.
Spares Analysis Data Model

The following diagram shows the Spares Analysis entity families and the relationships
that exist between them. The shaded boxes represent entity families, and the arrows
represent relationship families. You can determine the direction of the each relationship
definition from the direction of the arrow head: the box from which the arrow originates
is the predecessor, and the box to which the arrow heard points is the successor.
As you develop a Spares Analysis, you will create records in these families and link them
together, either manually or automatically via the options in the Meridium APM
Framework. Throughout this documentation, we use the term Spares Analysis to mean the
combination of the Spares Analysis record and all the records that are linked to it.
Reliability Growth Analysis Data Model

The following diagram shows the Reliability Growth Analysis entity families and the
successor.
As you develop a Reliability Growth Analysis, you will create records in these families
and link them together, either manually or automatically via the options in the Meridium
APM Framework. Throughout this documentation, we use the term Reliability Growth
Analysis to mean the combination of the Reliability Growth record and all the records
that are linked to it.
Reliability Distribution Analysis Data

Model
The following diagram shows the Reliability Distribution Analysis entity families and the
successor.
Note: In this image, the Distribution box represents one of four Distribution subfamilies
in which records can exist: Exponential, Lognormal, Normal, or Weibull. When you
create a Distribution record using the Reliability Distribution Analysis workflow, the
specific family to which that Distribution record will belong will depend upon the
distribution type that is selected on the Time To Failure Distribution or Time To Repair
Distribution page.
As you develop a Reliability Distribution Analysis, you will create records in these
families and link them together, either manually or automatically via the options in the
Meridium APM Framework. Throughout this documentation, we use the term Reliability
Distribution Analysis to mean the combination of the Reliability Distribution record and
all the records that are linked to it.
Probability Distribution Analysis Data

Model
The following diagram shows the Probability Distribution Analysis entity families and
the relationships that exist between them. The shaded boxes represent entity families, and
the arrows represent relationship families. You can determine the direction of the each
successor.
Note: In this image, the Distribution box represents one of four Distribution subfamilies
in which records can exist: Exponential, Lognormal, Normal, or Weibull.
As you develop a Probability Distribution Analysis, you will create records in these
families and link them together, either manually or automatically via the options in the
Meridium APM Framework. Throughout this documentation, we use the term Probability
Distribution Analysis to mean the combination of the Distribution record and all the
records that are linked to it.
System Reliability Data Model

The following diagram shows the entity and relationship families that are used in a
System Reliability Analysis. Throughout this documentation, we use the term System
Reliability 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:
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.
Red arrows and boxes represent entity families, relationship families, and
associated relationship definitions that may require customization.
In this image:
The System Action box represents one of four System Action subfamilies in which
records can exist: System Condition Monitor, System Inspection, System
Preventive Maintenance, or System Special Action. The specific family that is
used will depend upon the type of Action that is created for a given Asset or
Switch element.
The Distribution box represents one of four Distribution subfamilies in which
records can exist: Exponential, Lognormal, Normal, or Weibull record. The
specific family that is used will depend upon the distribution type selected for the
associated Risk.
Cost of Unreliability Data Model

The following diagram shows the Cost of Unreliability Analysis entity families and the
successor.
As you develop a Cost of Unreliability Analysis, you will create records in these families
and link them together, either manually or automatically via the options in the Meridium
APM Framework. Throughout this documentation, we use the term Cost of Unreliability
Analysis to mean the combination of the Unreliability Cost record and all the records that
are linked to it.
What is Failure Data?

A failure is the inability of a piece of equipment to perform its intended function. A
failure may involve the complete loss of function, a partial loss of function, or the
potential loss of function.
Reliability describes how likely it is that a piece of equipment will perform its intended
function without failure for a given period of time. Reliability is expressed as a
percentage and is expressed mathematically as (1 - The Probability of Failure).
The Meridium APM Reliability Analytics module allows you to analyze failure data so
that you can draw conclusions and make predictions about the reliability of your
equipment and locations. To perform an analysis in Reliability Analytics, you must first
collect failure data and store it in Meridium APM. Examples of important data include:
Equipment type and location.

Failure modes.
Failure type, class, repair actions, and cost.
Design, process, diagnostic, and work order data.
After the data has been collected, you will need to gather the data, format it, and supply it
to the Meridium APM Reliability Analytics tools. Throughout this documentation, we
assume that you are collecting and can access the data that is necessary to perform a
Reliability analysis.
Supplying Failure Data to Meridium

APM Reliability
When you create a new analysis in Reliability Analytics, you will need to select a query
or dataset on which to base the analysis or manually enter the data that you want to
analyze. One of the easiest and most efficient ways to conduct an analysis is to create one
based upon a query. The advantage of using queries is that each time you view the
analysis, Meridium APM will run the underlying query to retrieve the most current
information from the database. Analyses based on datasets and manually entered data, on
the other hand, require more manual intervention to reflect updates.
Note: Throughout this documentation, we assume you have entered all important data and
will be creating analyses based on queries.
The specific data that you need in order to create an analysis will vary, depending on the
type of analysis that you are creating, the specific information that is available, and the
results that you want to see. The following information provides a basic example of a
query that you might use for collecting data to perform most types of Reliability analyses.
This query returns failure data for Centrifugal Pump PMP-4543. The query results are
limited to failures where the Equipment Subunit is Seals and the Failure Mode is Wear.
Running this query will return the results shown in the following image.
Note: The type of failure data you collect will influence the conclusions you can make
about your equipment. If you have one pump or several pumps with a specific failure
mode, then you can perform a very specific analysis. If you have many pumps with many
different failure modes, then your analysis will be less specific.
The following columns of information are included in the results:
Asset ID (from the Pump record)

Asset Installation Date (from the Pump record)
Equipment Subunit (from the Failure record)
Failure Mode (from the Failure record)
Failure Date/Time (from the Failure record)
Total Downtime (from the Failure record)
Lost Profit Opportunity (from the Failure record)
Total Failure Cost (from the Failure record)
For additional information on creating queries, click here.
The Importance of Failure Modes

It is important that the type of failure data you collect will influence the conclusions you
can make about your equipment. If you have one pump or several pumps with a specific
failure mode, then you can perform a very specific analysis. If you have many pumps
with many different failure modes, then your analysis will be less specific.
For example, if you want to know the chances of a certain part on the pump failing, and
in your dataset you have several pumps that have failed in that way, then your analysis
will be more accurate than using data with multiple failure modes. If you are analyzing
all of the pumps at your site, and you have many different reasons for failure, you will be
able to determine overall failure statistics. This analysis, however, will not be particularly
useful in determining the probability of failure of a specific piece of equipment.
About Failure Probability

Conditional Reliability is used in Meridium APMs Failure Probability Calculator. The
calculator is available for all distribution models and uses conditional probability to
compute the probability of failure at time, t.
The concept of Conditional Reliability involves the following questions:
What is the probability of failure given that the item has survived until today?
How many days until I reach a certain % probability of failure?
-or-
The results of a failure probability calculation in Meridium APM can be a bit confusing.
However, the results are correct. For example, the user may find the current probability
of failure for a given element to be 90% or more after 3 years of operating time. If the
user were to calculate the future probability of failure 10 days from the current date, the
estimate of future failure probability might be around 1%. This is not incorrect. This
often occurs when the future is small compared to the total life experienced by the
elements under study.
R(T,t) = R (T+t)/R(T)
The Probability of surviving (T + t) days equals the Probability of surviving (T) days and
then surviving additional (t) days.
Meridium APM Reliability allows you to specify the operating time and calculate the
probability of equipment failure. Or you can choose to specify the probability of
equipment failure and then calculate the future age when the specified probability will be
reached.
Accessing Reliability Analytics in the

Meridium APM Framework
To access Reliability Analytics in the Meridium APM Framework:
Elimination, and then click Reliability Analytics.
The Reliability Analytics Start Page appears.
Aspects of the Reliability Analytics Start

Page
The following links appear on the Reliability Analytics Start Page:
Production Analysis: Displays the Select a Production Analysis from the List
page, where you can view, create, edit, delete, and save Production Analyses. You
can also define Reliability, Demonstrated lines, Nameplate lines, and Production
lines. In addition, you can set the minimum production value, the unit of measure
for production output, the margin value, and the unit of measure for the margin.
Spares Analysis: Displays the Select a Spares Analysis from the List page, where
you can view, create, edit, delete, and save Spares Analyses. You can run a Monte
Carlo simulation to view results on the Spare Level Plot, Downtime Plot, Spare
Usage Plot, Sensitivity Plot, and Optimal Holding Plot. In addition, you can
export the simulation results to a dataset, and save it within the Meridium APM
Catalog for future reference.
Reliability Growth: Displays the Select a Growth Analysis from the List page,
where you can view, create, edit, delete, and save Reliability Growth Analyses.
You are able to track changes in Mean Time Between Failure (MTBF) over a
specified period of time to determine strategies or repairs necessary to increase
the reliability of a product (i.e., element, system, or subsystem).
Reliability Distribution: Displays the Select a Distribution Analysis from the List
page, where you can view, create, edit, delete, and save Reliability Distribution
Analyses. You can also view Probability Plots, Failure Rate Plots, Probability
Density Function Plots, Cumulative Distribution Function Plots, and Competing
Failure Modes Plots. In addition, you can view failure data, calculate the future
probability of failure, and calculate the future age when specified probability will
be reached. Meridium APM Reliability supports four Distribution types: Weibull,
Normal, Lognormal, and Exponential.
Probability Distribution: Displays the Probability Distribution List page, where

you can view, create, edit, delete, and save Probability Distribution Analyses. You
can also view Probability Plots, Probability Density Function Plots, Cumulative
Distribution Function Plots, and Composite Plots. Meridium APM Probability
supports four Distribution types: Weibull, Normal, Lognormal, and Exponential.
System Reliability Analysis: Displays the Select a System Reliability Analysis

from the List page, from which you can open or delete an existing analysis or
create a new analysis.
Unreliability Cost of Analysis: Displays the Select a Cost of Unreliability

Analysis page, where you can view, create, edit, delete, and save Cost of
Unreliability Analyses. You can also view Total Cost Plots, Mean Time Between
Failures Plots, Mean Time to Repair Plots, Availability Plots, Failure Plots,
Downtime Plots, and Trend Plots for Cost of Unreliability Analyses.
Reliability Automation Rules: Displays the Automation Rules List Screen,

where you can search for existing automation rules and create new Reliability
Automation Rules. You can also view a preview of the Analysis Failure Data,
merge analyses, execute Reliability Automation Rules, and delete Reliability
Automation Rules.
Note: You must be a member of the MI Reliability Administrator Security Group or a

Super User in order to access the Automation Rule List Screen page. If you are not a
member of one of these Security Groups, the Reliability Automation Rules link will not
appear.

Deploying and configuring Reliability Analytics 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 the
Reliability Analytics module on top of the basic Meridium APM system architecture.
are marked as Required if you must perform the steps to take advantage of Reliability
Analytics functionality.
Step Task
Optional
Review the Reliability Analytics

data models to determine which
This task is necessary only

if you store equipment and
relationship definitions you will

need to modify to include your
custom equipment and location
families. Modify any relationship
definitions as needed via
Configuration Manager.
location information in
families other than the
baseline Equipment and
Functional Location
families.
Required
Users will not be able to
access Reliability Analytics
unless they have
permissions to the
families.
Assign the desired Security Users to

one or more Reliability Analytics
Security Groups in Configuration
Manager.
Optional
3
Modify Reliability Analytics

queries.
Configure the ability for users to

create Reliability Distribution and
Reliability Growth Analyses from
Associated Pages using URL
Manager.
Optional
if you want to implement
this functionality.
Optional
Configure Reliability Automation

Rules.

if you want to change the
behavior of the baseline list
queries.

if you want to use
Reliability Automation
Rules to create analyses
automatically.
Upgrade Workflow
are upgrading:
V3.5.1
V3.5.0 SP1 LP
V3.5.0
V3.4.5
Upgrading Reliability Analytics From

V3.5.1 to V3.6.0.0.0
Reliability Analytics will be upgraded from V3.5.1 to V3.6.0.0.0 automatically when you
steps are required.

V3.5.0 SP1 LP to V3.6.0.0.0
Reliability Analytics 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.5.0 to V3.6.0.0.0
Reliability Analytics will be upgraded from V3.5.0 to V3.6.0.0.0 automatically when you
steps are required.

V3.4.5 to V3.6.0.0.0
The following table lists the step that is required to upgrade and configure Reliability
Analytics from V3.4.5 to V3.6.0.0.0. This step assumes that you have completed the steps
for upgrading the components in the basic Meridium APM system architecture.
Step Task
Configure the ability for Optional

users to Reliability
Distribution and
Reliability Growth
Analyses from Associated
Pages using URL
Manager.
This feature is new in V3.5.0, so even

if you have deployed Reliability
Analytics in V3.4.5, you will not
have completed this step. You need to
complete this task, however, only if
you want to implement this
functionality.
Reliability Analytics Security

The following Security Groups are provided for Reliability Analytics.
MI Reliability Viewer
MI Reliability User
MI Reliability Administrator
These Security Groups are provided as part of the baseline Meridium APM database. In
addition to assigning Security Users to the appropriate Security Group, you must assign
the appropriate family privileges to any Security User or Security Group who should be
able to perform Reliability Analytics tasks. Specifically, you must set family privileges
for any custom-defined families that will be used in Reliability Analytics.
The baseline privileges for the baseline Security Groups are listed in the following table.
Family
Analysis
MI Reliability
Viewer
MI Reliability User MI Reliability

Administrator
View
View
View
Distribution
View
View, Update,
Insert, Delete
View, Update, Insert,

Delete
Exponential
View
View, Update,
Insert, Delete

Delete
Growth Model
View
View, Update,
Insert, Delete

Delete
Lognormal
View
View, Update,
Insert, Delete

Delete
Normal
View
View, Update,
Insert, Delete

Delete
Production Analysis
View
View, Update,
Insert, Delete

Delete
Production Losses
View
View, Update,
Insert, Delete

Delete
Reliability Automation
Rule

Delete
Reliability Distribution
View
View, Update,
Insert, Delete

Delete
Reliability Growth
View
View, Update,
Insert, Delete

Delete
Reliability
Recommendation
View
View, Update,
Insert, Delete

Delete
Spare
View
View, Update,
Insert, Delete

Delete
Spares Analysis
View
View, Update,
Insert, Delete

Delete
Spare Analysis Chart
View
View, Update,
Insert, Delete

Delete
Spare Application
View
View, Update,
Insert, Delete

Delete
Spare Application
Population
View
View, Update,
Insert, Delete

Delete
System Action
View
View, Update,
Insert, Delete

Delete
System Action Mapping
View
View, Update,
Insert, Delete

Delete
System Action
Optimization
View
View, Update,
Insert, Delete

Delete
System Action Result
View
View, Update,
Insert, Delete

Delete
System Analysis
View
View, Update,
Insert, Delete

Delete
System Asset
View
View, Update,
Insert, Delete

Delete
System Buffer
View
View, Update,
Insert, Delete

Delete
System Condition Monitor View
View, Update,
Insert, Delete

Delete
System Element
View
View, Update,
Insert, Delete

Delete
System Element Result
View
View, Update,
Insert, Delete

Delete
System Global Event
View
View, Update,
Insert, Delete

Delete
System Inspection
View
View, Update,
Insert, Delete

Delete
System Link
View
View, Update,
Insert, Delete

Delete
System Preventative
Maintenance
View
View, Update,
Insert, Delete

Delete
System Reource
View
View, Update,
Insert, Delete

Delete
System Resource Result
View
View, Update,
Insert, Delete

Delete
System Resource Usage
View
View, Update,
Insert, Delete

Delete
System Risk
View
View, Update,
Insert, Delete

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

Delete
System Scenario
View
View, Update,
Insert, Delete

Delete
System Sensor
View
View, Update,
Insert, Delete

Delete
System Special Action
View
View, Update,
Insert, Delete

Delete
System Subsystem
View
View, Update,
Insert, Delete

Delete
System Switch
View
View, Update,
Insert, Delete

Delete
Unreliability Cost
View
View, Update,
Insert, Delete

Delete
Weibull
View
View, Update,
Insert, Delete

Delete
Analysis Link
View
View, Update,
Insert, Delete

Delete
Has Global Events
View
View, Update,
Insert, Delete

Delete
Has Mitigated TTF

Distribution
View
View, Update,
Insert, Delete

Delete
Has Planned Resource

Usages
View
View, Update,
Insert, Delete

Delete
Has Recommendations
View
View, Update,
Insert, Delete

Delete
Has Reliability
View
View, Update,
Insert, Delete

Delete
Has Resource Usage
View
View, Update,
Insert, Delete

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

Delete
Has Root System
View
View, Update,
Insert, Delete

Delete
Has Scenarios
View
View, Update,
Insert, Delete

Delete
Has System Actions
View
View, Update,
Insert, Delete

Delete
Has System Elements
View
View, Update,
Insert, Delete

Delete
Has System Optimization View
View, Update,
Insert, Delete

Delete
Has System Resources
View
View, Update,
Insert, Delete

Delete
Has System Results
View
View, Update,
Insert, Delete

Delete
Has System Risks
View
View, Update,
Insert, Delete

Delete
Has TTF Distribution
View
View, Update,
Insert, Delete

Delete
Has Unplanned Resource

Usages
View
View, Update,
Insert, Delete

Delete
Has Unreliability Cost
View
View, Update,
Insert, Delete

Delete
Modifying the Reliability List Queries

The baseline Meridium APM database contains queries that are used to display results on
the analysis list pages. If desired, you can modify these queries to customize the lists that
are displayed. For example, you may want to customize these queries to add additional
prompts or filters. Note that if you modify one of the baseline queries or create your own
query to be used for one of the list pages, the query will be used by anyone who accesses
the list of analyses.
Before you modify or create Reliability Analytics queries, note the following:
Meridium APM is hard-coded to look for the Reliability Analytics queries in the
folder \\Public\Meridium\Modules\Reliability Manager\Analyses. Any query that
you want to use must exist in this location.
Meridium APM is hard-coded to look for the query names as they are delivered. If
you want to use a customized query, you must modify a query that Meridium
APM delivers, or you can rename or delete a query we deliver and add your own
query to the same folder using the exact name of the delivered query. For
example, if you want a query to return a list of Reliability Growth Analyses
filtered according to a specific value in the Analysis Start Date field, you would
modify the delivered Reliability Growth query or rename or delete this query and
add your own Reliability Growth query to the same folder.
The analysis query source alias must be analy, and the automation rule query
source alias must be relrules.
The following fields must exist in all queries and must use the aliases as they
appear in this list:
Analysis ID
Published
ENTY_KEY
LAST_UPBY_SEUS_KEY
LAST_UPDT_DT
Note: The Automation Rules query will not contain the Published field. It should contain
all other fields in the preceding list.
About Creating a Reliability Analysis

from an Associated Page
Within the Reliability Analytics module, you can create a Reliability Growth Analysis
from the Reliability Growth Builder, and you can create a Reliability Distribution
Analysis from the Reliability Distribution Builder. In addition to these standard features,
which require no manual configuration, you also have the option of allowing users to
create a Reliability Growth Analysis or Reliability Distribution Analysis from an
Associated Page while they are viewing an Equipment or Functional Location record in
the Record Manager. If you configure this functionality, when a user creates a new
analysis in this way, certain values in the Equipment or Functional Location record will
be mapped to the analysis using the parameter values that are defined in the Associated
Page's underlying URL.
This feature is supported by two main components:
The AutoCreate parameter value, which is available for the Reliability Growth
and Reliability Distribution URLs.
A query that is required by the AutoCreate parameter value and passes in values
that will be used for creating the new analysis.
If you are following the Meridium APM Best Practice and are storing equipment and
location data in the baseline Equipment and Functional Location families, in order to take
advantage of this functionality, you will need to create an Associated Page on these
families manually. You can create this Associate Page using the baseline query that is
provided to support this functionality and passing in values to the URL that will cause
values returned by the query to be used in the new analysis.
This documentation assumes that you are following the Meridium APM Best Practice and
will therefore:
Use the baseline query.

Construct your Associated Page URLs based upon the baseline query.
If your equipment and location information is stored in non-baseline families, to take

advantage of this functionality, you will need to modify the baseline queries to work with
your custom families and then create Associated Page URLs to accommodate those
changes. The Reliability Growth and Reliability Distribution URL documentation provide
basic information about this URL parameter that should allow you to customize the URLs
to suit your needs. Note that even if you are following the Meridium APM Best Practice
for storing equipment and location information, you may want to modify the baseline
query to provide additional functionality (e.g., additional prompts).
About the Baseline Associated Page

Queries
The baseline queries Equipment - Work History and Functional Location - Work History,
which are stored in the Catalog folder \\Publich\Meridium\Modules\Reliability
Manager\Queries, can be used to create an Associated Page on the Equipment and
Functional Location families that will allow users to create Reliability Growth and
Reliability Distribution Analyses automatically from Equipment and Functional Location
records.
The Equipment - Work History query includes the Equipment and Work History families
and returns information about the Work History records that are linked to a given
Equipment record. In this query:
The following fields are included for the Equipment Family:
Equipment ID
Valid From Date
The following fields are included from the Work History family:
Event Start Date
Time to Repair
The following prompt is defined for the Equipment ID field:
((? :s :caption='Equipment ID' :id=EquipmentID :query='SELECT DISTINCT

[MI_EQUIP000_EQUIP_ID_C] FROM [MI_EQUIP000] ORDER BY
[MI_EQUIP000_EQUIP_ID_C]'))
When the query is run, the value that is passed into this prompt determines the Equipment
record for which to return Work History records. Information from those Equipment and
Work History records is used to create the analysis.
The Functional Location - Work History query includes the Functional Location and
Work History families and returns information about the Work History records that are
linked to a given Functional Location record. In this query:
The following field is included for the Functional Location Family:
Location
The following fields are included from the Work History family:
Event Start Date
Time to Repair
The following prompt is defined for the Location field:
((? :s :caption='Functional Location' :id=FunctionalLocation :query='SELECT

DISTINCT [MI_FNCLOC00_LOCAT_C] FROM [MI_FNCLOC00] ORDER BY
[MI_FNCLOC00_LOCAT_C]'))
When the query is run, the value that is passed into this prompt determines the Functional
Location record for which to return Work History records. Information from those
Functional Location and Work History records is used to create the analysis.
Modifying the Associated Page Queries

If you want to use this functionality but do not use the baseline Equipment and
Functional Location families to store your equipment and location information or the
Work History family to store your failure information, you will need to create your own
custom queries or modify the following baseline queries.
If you choose to modify the baseline queries, you will need to:
Replace the sources families with your own custom families.

Include the fields whose values you want to map to the analysis.
Add a prompt to the desired field, similar to the prompt that is provided in the
baseline queries.
If you decide to use different queries other than baseline queries or add additional fields
to either baseline query, before doing so, you should review the parameters that are
required to build a Reliability Growth Analysis or Reliability Distribution Analysis to
determine what information you want to map from the query to the analysis. The values
that you want to map to the analysis will need to be returned by the fields that you
include in the query.
Creating Associated Pages That Can Be

Used to Create Analyses
The following instructions provide details on creating an Associated Page link that will
allow users to create a Reliability Growth or Reliability Distribution Analysis while
viewing an Equipment or Functional Location record in Record Manager. You may need
to repeat these steps multiple times, depending upon how many Associated Pages you
want to create.
To create an Associated Page that will allow you to create a Reliability Growth or
Reliability Distribution Analysis from an Equipment or Functional Location record:
1. In the Meridium APM URL Manager, on the Associate Families with URLs tab,
select Equipment or Functional Location in list of available families.
2. Click the New Menu Item button.
The Menu Item Information dialog box appears.
3. In the Caption text box, type New Growth Analysis or New Distribution Analysis,
depending upon the type of analysis that you want to create.
4. In the URL text box, type one of the following URLs, depending on which type of
analysis you want to create. The syntax provided here assumes that you are using
the baseline queries provided to support this functionality.
Reliability Growth Analysis for the Equipment Family:

meridium://Reliability/growth?
Action=AutoCreate&QueryPath=Public\Meridium\Modules\Reliability
Manager\Queries\Equipment - Work History&AssetIDField=Equipment
ID&FailureDateField=Event Start Date&InstallationDateField=Valid
From Date&DowntimeField=Time To
Repair&EquipmentID=[MI_EQUIP000_EQUIP_ID_C]
Reliability Distribution Analysis for the Equipment Family:

meridium://Reliability/Distribution?
Manager\Queries\Equipment - Work History&AssetIDField=Equipment
ID&FailureDateField=Event Start Date&InstallationDateField=Valid
From Date&DowntimeField=Time To
Repair&EquipmentID=[MI_EQUIP000_EQUIP_ID_C]
Reliability Growth Analysis for the Functional Location family:

meridium://Reliability/growth?
Manager\Queries\Functional Location - Work
History&AssetIDField=Location&FailureDateField=Event Start
Date&DowntimeField=Time To
Repair&FunctionalLocation=[MI_FNCLOC00_LOCAT_C]
Reliability Distribution Analysis for the Functional Location family:

meridium://Reliability/Distribution?
Manager\Queries\Functional Location - Work
History&AssetIDField=Location&FailureDateField=Event Start
Date&DowntimeField=Time To
Repair&FunctionalLocation=[MI_FNCLOC00_LOCAT_C]

The Associated Page is saved.
What Are Reliability Automation Rules?

Reliability Distribution, Reliability Growth, and Cost of Unreliability Analyses can be
created interactively or through Reliability Automation Rules, which can generate
multiple Reliability analyses for a hierarchy of equipment and location that have related
events.
Using Reliability Automation Rules, you can analyze several families in a single step.
Based on the parameters that you predefine for the analysis, the system will automatically
execute the analysis calculations on the entire population that is valid for the parameters
and generate the appropriate reliability document. The results of the analysis calculations
are captured in the database against the identified population, providing quick reference
to the current reliability.
Note: To generate a Reliability Analysis document, equipment and location families and
failure data for the equipment and location must already be defined in the database.
To access the Reliability Automation Rules function, you must be a member of the MI
Reliability Administrator Security Group or a Super User.
Reliability Automation Rule Data Model

The following diagram shows the entity and relationship families that are used by
Reliability Automation Rules.
About Creating Queries for Use with the

Rule Builder
On the Source Data page of the Reliability Automation Rule Builder, you can select a
pre-defined query to provide the data on which auto-generated Reliability Analyses will
be built for a query-based Automation Rule. Before you can use the Reliability
Automation Rule Builder, one or more appropriate queries must be defined. Ideally, these
queries will be pre-defined by an administrative user before other users access the
system.
Note: After these queries have been created and used to build rules, they should not be
deleted. Without the queries, the Automation Rules that are based on them cannot update
the analyses that they generated.
Automation Rule queries must contain:
All of the fields required for mapping to the selected analysis type (Reliability
Distribution, Reliability Growth, Cost of Unreliability). For all analysis types, the
following fields should be selected:
Asset ID (required).
Asset Installation Date (optional).
Failure Date (required).
Downtime (optional).
Maintenance Cost (optional, for Cost of Unreliability Analysis only).
LPO (optional, for Cost of Unreliability Analysis only).
The fields that will be used for grouping populations of events (including system
fields such as Family ID and Family Key and the entity family caption)
Filtering criteria.
Note: Filtering is disabled in the Reliability Automation Rule Builder if a query is used to
build analyses.
We strongly recommended that you use a query that contains the metadata information in
the Asset ID and Failure Date fields (which are required fields) and that these two fields
are defined in two separate entity families. This precludes the use of Group By queries,
complex (non metadata-based) queries in the SQL Editor, and system fields or calculated
fields for Asset ID and Failure Date information.
The master query cannot contain parameters. The master query should be stored in a
public directory in the Catalog and must not be deleted. We recommend that you store
this query in the following Catalog folder:
\\Public\Meridium\Modules\Reliability\Manager.
If you need additional fields for mapping or population grouping in the Reliability
Automation Rule, you must change the master query. The master query should be
accessible to members of the MI Reliability Administrators Security Group who will be
working with Reliability Automation Rules. When the Reliability Automation Rule is
executed to generate the analyses, sub-queries will be created using the master query as
the source. If the master query is deleted, the sub-queries will cease to operate.
Accessing the List of Reliability

Automation Rules
To access the list of Reliability Automation rules:
In the Meridium APM Framework application, on the Reliability Analytics Start

Page, click the Reliability Automation Rules link.
Note: You must be a member of the MI Reliability Administrator Security Group or a

Super User in order to access the Automation Rule List Screen page. If you are not a
member of one of these Security Groups, the Reliability Automation Rules link will not
appear.
The Automation Rule List Screen page appears.
From the Automation Rule List Screen page, you can run the Reliability Automation Rule
list query to access a list of existing Reliability Automation Rules and then view a
summary of any rule.
Aspects of the Automation Rule List

Screen Page
The Automation Rule List Screen page lets you run the Automation Rules query to
access a list of existing Reliability Automation Rules that meet your query criteria. The
Automation Rules query is stored in the Meridium APM Catalog folder
\\Public\Meridium\Modules\Reliability Manager\Analyses. While the Automation Rules
query can be customized for your specific implementation, the baseline Automation
Rules query contains one prompt: Last Updated By. This prompt appears at the top of the
page as a drop-down list that contains the following options:
Your user name, which is selected by default.

The user name of any user who last updated any Reliability Automation Rule.
The [All Users] option, which lets you retrieve a list of Reliability Automation
Rules updated by any user.
Selecting a value from the Last Updated By list will cause the list of Reliability
Automation Rules to display only the rules that meet that criteria. For example, if you
select your name, the query will return a list of all the Reliability Automation Rules that
were last updated by you.
After you select the desired criteria, you can click the Run Query button, to run the
Automation Rules query and display the results in a grid at the bottom of the page. The
default Automation Rules query is configured to display the following columns of
information: Rule Name, Last Updated, Reliability Analysis Type, Updated By, and Last
Executed. You can click any hyperlinked Rule Name to view the summary of the selected
rule.
Hint: If desired, you can customize the column display.
In addition, the Automation Rule List Screen page contains two task menus, which you
can use to perform functions associated with Reliability Automation Rules.
Rules List Tasks Menu

The Rule List Tasks menu on the Automation Rule List Screen page contains the
following link:
Execute Rule(s): Executes the selected Reliability Automation Rule(s).
Common Tasks Menu

The Common Tasks menu on the Automation Rule List Screen page contains the
following links:
New Rule: Displays the Reliability Automation Rule Builder, which will guide
you through the process of creating a new rule.
Open Rule: Displays the Find a Reliability Automation Rule window, which you
can use to find and open an existing rule.
Delete Rule(s): Deletes the current rule(s) from the database, after asking for
confirmation.
Page.
Help: Displays the context-sensitive Help topic for the Automation Rule List
Screen page.
Guidelines: Displays the Reliability Concepts, which provide reliability

workflows and descriptions of reliability concepts.
Note: The Save Rule and Save Rule As links are always disabled on the Automation Rule
List Screen page.
About Creating a New Reliability

Automation Rule
Using the Reliability Automation Rule Builder, you can create a new Reliability
Automation Rule based either on:
A query.
Note: To create a Reliability Automation Rule based on a query, the query must exist in
the Catalog.
Equipment, location, and event data.
Note: The equipment, location, and event families and any necessary relationships must
already be defined.
Creating a Rule Based on a Query

To create a rule based on a query:
1. In the Meridium APM Framework application, on the Automation Rule List
Screen page or the Summary Screen of [Automation Rule] page, on the Common
Tasks menu, click the New Rule link.
The Reliability Automation Rule Builder appears, displaying the Welcome screen.
Hint: You can select the Don't show this page again check box if you prefer to bypass the
Welcome screen in the future.
The Choose Reliability Document Type screen appears.
3. Select the option for the type of rule you want to create:
Reliability Cost of Unreliability Analysis
The Reliability Distribution Analysis option is selected by default.

The Source Data screen appears.
5. Accept the default selection: Use a Query to provide data on which the analysis
will be built.
The Select Query screen appears.
7. Click the Browse button to open the Catalog and locate an existing query.
8. Select the query, and click the Open button.
After you open the query, the Select Query builder screen will return to focus, and the
name of the query that you selected will appear in the Query field. The Available Fields
list will display the fields in the query.
Note: If you try to create a Reliability Automation Rule based on a query in which at least
one field does not have an alias, an error message will appear, and the rule will not be
created. Automation rules can be based only on queries that have an alias on every field
that will be used in the rule. Otherwise, the fields cannot be properly mapped, and the
rule cannot be created.
The Identify the Fields that are Necessary for the Analysis screen appears.
9. On the Identify the fields that are necessary for the analysis screen, select a value
for each field. Required fields are labeled with bold text.
6.
o
Asset ID: The field from your query that contains the Asset ID.
Asset Installation Date: The field from your query that contains the date
when the piece of equipment was first installed.
Failure Date: The field from your query that contains the date when the
piece of equipment or location failed.
Downtime: The field that contains the downtime. The downtime is the
amount of time that an item is not available for any reason.
Maintenance Cost: The cost of fixing the equipment after a failure occurs.
The Maintenance Cost represents both the labor and the material costs.
This appears only if you selected Reliability Cost of Unreliability Analysis
as the document type.
Lost Profit Opportunity (LPO) Cost: The field that contains the LPO Cost.
The LPO cost is the profit that the company loses when the production
fails in an oversold market. It represents the difference between the market
price of the product and the cost of producing it. This appears only if you
selected Reliability Cost of Unreliability Analysis as the document type.

The Select Population Grouping screen appears.
11. Select the check box(es) next to the fields that will allow you to create
populations of events for analyses. Note that you are not required to select any
population grouping(s). If you select a population grouping, the data will be
filtered by that population into different groups. For example, if you select the
Asset ID field to be a population field, a potential analysis will be generated on
the Automation Rule Information page for every piece of equipment and location.
The fields listed on the Select Population Grouping screen consist of fields from
the equipment/location family, relationship family, and event family selected in
the query.

The Summary Screen of [Automation Rule] page appears, displaying a list of failure
mode definitions (i.e., the analyses) that will be generated when the rule is saved and
executed.
13. To save the rule, on the Common Tasks menu, click the Save Rule link.
Creating a Rule Based on

Equipment/Location-Event Data
Structure
To create a rule based on equipment/location-event data:
Screen page or the Summary Screen of [Automation Rule] page, click the New
Rule link on the Common Tasks menu.
The Reliability Automation Rule Builder appears, displaying the Welcome screen.
Hint: You can select the Don't show this page again check box if you prefer to bypass the
Welcome screen in the future.
The Choose Reliability Document Type screen appears.
3. Select the option for the type of rule you want to create:
Reliability Cost of Unreliability Analysis
The Reliability Distribution Analysis option is selected by default.

The Source Data screen appears.
5. Select the Select entity families that will form an Asset-Event data structure
option.
The Choose an Asset Family screen appears.
7. In the Select Asset Family list, select the desired family. Alternatively, you can
click the
button to select a family from the hierarchy or simply type a family
name in the text box.
8. Determine the level at which to perform the analysis:
1.
o
To generate an analysis only for the selected family, accept the default
selection, Generate analyses for selected family.
To include all of the subfamilies of the selected family in the analysis,

select the Generate analyses for selected family and all of its sub-families
option. Note that if you choose to include subfamilies, the check box
below this option will become enabled. Select the check box if you want
to generate analyses only for the subfamilies that are located at the bottom
of the hierarchy for the selected family.
Note: If you choose this option and then choose to add filters or grouping to the
Reliability Automation Rule later in the builder, Meridium APM may incorrectly group or
filter data, resulting in analyses based on data that did not match the desired criteria. If
this happens, you may need to create automation rules individually for families at the
bottom of a family hierarchy.
The Choose Relationship and Event Families screen appears.
10. In the Select Relationship Family list, select the relationship family that identifies
the relationship that should exist between the family that you selected on the
previous screen and the Event family that you will select on this screen.
11. In the Select Event Family list, select the desired family. You can choose to
include equipment and location in the analysis that do not include event data by
selecting the Include assets even if they do not include event data check box. Note
that the Select Event Family list is disabled until you select a relationship family
in the Select Relationship Family list.
The Identify the Fields that are Necessary for the Analysis screen appears.
13. On the Identify the fields that are necessary for the analysis screen, select a value
for each field. Required fields are labeled with bold text.
1.
o
Asset ID: The field from your query that contains the Asset ID.
Asset Installation Date: The field from your query that contains the date
when the piece of equipment was first installed.
Failure Date: The field from your query that contains the date when the
piece of equipment or location failed.
Downtime: The field that contains the downtime. The downtime is the
amount of time that an item is not available for any reason.
Maintenance Cost: The cost of fixing the equipment after a failure occurs.
The Maintenance Cost represents both the labor and the material costs.
This appears only if you selected Reliability Cost of Unreliability Analysis
as the document type.
Lost Profit Opportunity (LPO) Cost: The field that contains the LPO Cost.
The LPO cost is the profit that the company loses when the production
fails in an oversold market. It represents the difference between the market
price of the product and the cost of producing it. This appears only if you
selected Reliability Cost of Unreliability Analysis as the document type.
Note: You can click the Finish button on the Identify the Fields that are Necessary for the
Analysis screen if you prefer not to define filters.
The Apply any Desired Filters screen appears.
15. In the Field list, click the

button to select a field.
16. In the Condition list, select one of the field condition operators. The field
conditions that you can select are the same as those that are available in the
Advanced search . The list of operators will change depending on the type of field
that you select (i.e., numeric, character, date, or logical) .
17.
Type the value that should meet the condition in the Value text box. When typing
dates or a number in this field, insert single quotes around the value.
17.
Click the Add Filter button. The filter criteria will appear in the pane.
17.
To apply multiple filters, repeat the previous steps. Remember to click the Add
Filter button each time you specify new filter criteria.
17.
In the Match section, select either the All conditions (And operator) option or the
Any condition (Or operator) option to apply to the filter results.
17.
The Select Population Grouping screen appears.
22. Select the check box(es) next to the fields that will allow you to create
populations of events for analyses. You are not required to select any population
grouping(s). If you select a population grouping, the data will be filtered by that
population into different groups. For example, if you select the Asset ID field to
be a population field, a potential analysis will be generated on the Automation
Rule Information page for every piece of equipment and location. The fields listed
on the Select Population Grouping screen consist of fields from the
equipment/location family, relationship family, and event family that you selected.
The Summary Screen of [Automation Rule] page appears, displaying a list of failure
mode definitions (i.e., the analyses) that will be generated when the rule is saved and
executed.
24. To save the rule, on the Common Tasks menu, click the Save Rule link.
Accessing an Existing Reliability

Automation Rule
To open an existing Reliability Automation Rule:
Screen page, in the Last Updated By list, select the criteria that you want to use
for limiting the list of automation rules. The available criteria will vary, depending
on how the automation rules list query has been configured.
2. Click the Run Query button.
The Meridium APM system runs the Reliability Automation Rules list query and displays
the results in the grid at the bottom of the page.
3. In the Rule Name column, click the hyperlinked name of the rule that you want to
open.
The Summary Screen of [Automation Rule] page appears.
Aspects of the Reliability Automation

Rule Summary Screen
The Summary Screen of [Automation Rule] page displays information about the selected
Reliability Automation Rule. You can access the summary screen from the Automation
Rules List Screen page. This screen also appears when you create a new Reliability
Automation Rule.
The Summary Screen of [Automation Rule] page contains the following items, which
provide details about the Reliability Automation Rule:
Rule Name: The name of the rule that you selected.

Rule Description: A short description of the rule that you selected.
Automation Rule Criteria section: Displays a description of the criteria that

identify the rule, including the type of analysis that will be generated from the
rule. In addition, this section contains the name of the family to which the
analyzed events belong, along with the relationship between the family and
events. If filters or groupings have been applied to the rule, they will be noted in
this section. You can click the Update Rule Information link to display the
Reliability Automation Rule Builder, which will be populated with the
information you entered when you created the rule. You can modify the rule by
making different selections in the builder.
Automation Rule Information section: Lists the potential analyses that are based
upon the filters and groupings specified. A Reliability Analysis will be created for
each potential analysis that contains at least the minimum number of failure
events required for the analysis the next time you execute the rule. You can click
any name in the list to view a preview of the data that will be included in the
analysis.
For Reliability Automation Rules based on an Equipment/Location-Event

data structure, the name of the analysis is populated automatically by the
Meridium APM system based on the name of the equipment/location
family that you selected on the Choose an Asset Family builder screen.
If you made no selections on the Select Population Grouping

screen, the Meridium APM system will use only the
equipment/location family name as the name of the analysis.
If you make Group By selections on the Select Population

Grouping screen, the Meridium APM system will append the name
of each member of the selected population group(s) on this screen
to the name of the analysis.
For Reliability Automation Rules based on a query, the name of the

analysis is populated automatically using values that correspond to the
fields you selected on the Select Population Grouping screen. If you did
not select any groupings, the new analysis will be named New Analysis.
For example, suppose that Equipment is the name of the selected equipment/location
family. If you selected the Manufacturer field for population grouping, the name of each
manufacturer is listed next to the Equipment family name.
In addition, the Summary Screen of [Automation Rule] page also contains two task
menus: Rule Tasks and Common Tasks.
Rule Tasks Menu

The Rule Tasks menu on the Summary Screen of [Automation Rule] page contains the
following links:
View Rule List: Displays the Automation Rule List Screen page.
Execute Rule: Executes the rule that is currently displayed.
Merge Analyses: Merges the selected analyses. This link is enabled only when
more than one analysis is selected in the Automation Rule Information list.
Unmerge Analyses: Displays the Unmerge Analyses dialog box, where you can
select the merged analyses that you want to unmerge. This link is enabled only
when one or more merged analyses exist.
Note: You can merge only analyses that share similar characteristics.
Common Tasks Menu

The Common Tasks menu on the Summary Screen of [Automation Rule] page contains
the following links:
New Rule: Displays the Reliability Automation Rule Builder, which lets you
create a new Reliability Automation Rule.
Open Rule: Displays the Find a Reliability Automation Rule window, which you
can use to find and open an existing rule.
Save Rule: Saves the currently displayed Reliability Automation Rule.
Save Rule As: Saves the currently saved analysis with a different name.
Delete Rule: Deletes the current rule(s), after asking for confirmation.
Page.
Help: Displays the context-sensitive Help topic for the Summary Screen of
[Automation Rule] page.
Guidelines: Displays the Reliability Concepts, which provide reliability

workflows and descriptions of reliability concepts.
Displaying a Preview of the Analysis

Failure Data
Based on the selections that you choose in the Reliability Automation Rule Builder, a
query is generated for analysis. From the Summary Screen of [Automation Rule] page,
you can access the query containing the failure data for the analysis that will be generated
when the Reliability Automation Rule is executed.
To display a preview of the analysis failure data:
In the Meridium APM Framework application, in the Automation Rule

Information section, click the name of the desired analysis in the Analysis Name
column.
The Analysis Failure Data Details dialog box appears.
The Analysis Failure Data Details dialog box displays the query that is being used to
retrieve the failure data for the selected analysis, and a grid displays the result set of the
query based on the mapping fields you selected in the Reliability Automation Rule
Builder.
Note: You cannot edit the fields listed in the query results.
Merging Analyses
If two or more analyses share similar characteristics, you may find it useful to merge
them and produce one analysis instead of separate analyses. Also, if an analysis does not
have the minimum number of failure events required in order to create an analysis, you
can merge it with another analysis.
Note: You can merge analyses only if they contain the same equipment and population
groupings.
To merge two analyses:
1. In the Meridium APM Framework application, on the Summary Screen of
[Automation Rule] page, in the Automation Rule Information section, select the
rows containing the analyses that you want to merge.
When you select more than one analysis, the Merge Analyses link becomes enabled on
the Rule Tasks menu.
2. Click the Merge Analyses link.
The Merge Analysis Grouping Fields dialog box appears.
The groupings for the selected analyses are listed in the list at the top of the dialog box.
3. Click a grouping in the first list to select it.
The lower list is populated with the fields belonging to that grouping.
4. Click a field in the second list to select it as the reference field. The field(s) that
you do not select are the alternate field(s).
5. Click OK.
The reference field now contains the values for the alternate field, and one analysis will
be generated based on the reference field when the rule is executed. The system updates
the list of analyses in the Automation Rule Information section.
Undoing a Merge
To undo the merge of two or more analyses to create separate analyses:
1. In the Meridium APM Framework application, on the Summary Screen of

[Automation Rule] page, in the Automation Rule Information section, select the
desired analysis.
2. On the Rule Tasks menu, click the Unmerge Analyses link. Note that this link is
enabled only if the selected analysis has been merged.
The Unmerge Analyses dialog box displays a list of existing merge conditions.
3. Select the desired merge condition(s), and click OK.
A prompt appears, asking if you really want to delete the selected merge condition(s).
The merge conditions are deleted, and the system updates the list of analyses in the grid
in the Automation Rule Information section. The separate analyses appear in the list.
Executing Reliability Automation Rules

You can execute Reliability Automation Rules either from the Summary Screen of
[Automation Rule] page (to execute the currently displayed rule) or from the Automation
Rules List Screen page (to execute one or more selected rules). Either procedure produces
the same results.
When a rule is executed, only the potential analyses that contain the minimum number of
failure points for an analysis will be created or updated. The following number of failure
points is required for each analysis that can be created from a Reliability Automation
Rule.
Reliability Growth Analysis: 3 failure points

Reliability Distribution Analysis: 2 failure points
Cost of Unreliability Analysis: 1 failure point
If the potential analysis does not contain the corresponding number of failures or more,
when the rule is executed, the analysis will not be created.
Note: Before you use a rule to create an analysis, you should review the data required for
the type of analysis you are creating. If you use invalid data, the analysis will still be
created, but the results will not be valid.
To execute a Reliability Automation Rule:
On the Summary Screen of [Automation Rule] page, on the Rule Tasks menu,
click the Execute Rule link.
-orOn the Automation Rules List Screen page, in the list of rules, select one or more rules
that you want to execute. Then, on the Rule Tasks List menu, click the Execute Rule(s)
link.
The system executes the rule(s) and generates the resulting analysis.
Deleting Reliability Automation Rules

To delete one or more Reliability Automation Rules:
1. On the Summary Screen of [Automation Rule] page, on the Common Tasks menu,
click the Delete Rule link.
-orOn the Automation Rules List Screen page, in the list of rules, select one or more rules
that you want to delete. Then, on the Common Tasks menu, click the Delete Rule link.
A confirmation message appears, asking if you really want to delete the rule.
The rule is deleted from the database.
Parameters for the Reliability

Automation Rules URL
The URL for accessing Reliability Automation rules, meridium://Reliability/Automation,

accepts the parameters described in the following table. Note that to create a functional
URL, you must define at least the Page parameter. For examples of these parameters,
click here.
Note: Some parameter values for the Reliability Automation Rules URL are case
sensitive. When constructing URLs for Reliability Automation Rules, use the exact case
that appears in the following table.
Parameter
Name
EntyKey
Description
Accepted
Value(s)
Notes
Specifies which
You can use this parameter in
automation rule you
conjunction with the Summary,
The Entity Key
want to view.
ParetoPlot, or PlotData parameter.
of the desired
automation rule.
List: Displays the

Automation Rule List Screen
page.
Summary: Displays the

Summary Screen for
[Automation Rule] page for the
automation rule specified by
the EntyKey parameter.
List
Page
Specifies whether to
Summary
display the list of
existing rules or a
specific rule.
Examples of Reliability Automation

Rules URLs
meridium://Reliability/Automation?Page=List
Displays the Automation Rule List Screen page.
meridium://Reliability/Automation?Page=Summary&EntyKey=1234567
Displays the Summary Screen for [Automation Rule] page for the automation rule with
the Entity Key 1234567.
About Navigating the Reliability

Analytics Module
Within the Meridium APM Framework application, the Reliability Analytics module
provides the following navigational tools:
A start page with links that provide access to the Reliability analyses and their
various features and tools.
A Site Map that you can use to navigate within the Reliability Analytics module.
The Site Map indicates your current location and shows the typical path for
arriving there. To access a previous page, you can click its hyperlinked name in
the Site Map.
Using the Reliability Analytics Site Map

The Site Map in Reliability Analytics allows you to navigate from the current page to
other pages in Reliability Analytics. The Reliability link, which provides access to the
Reliability Analytics Start Page, will always be available. Links to other pages may also
be available depending upon your location in the application. You can click any link that
is available to access the corresponding page.
The following image shows an example of what the Site Map looks like on the
Production Analytics page. A red outline has been added to the image to highlight the Site
Map.
What is a Production Analysis?

Meridium APM Reliability Analytics offers various tools that help you analyze the
reliability of your equipment and locations so that you can make decisions about when to
repair and replace those pieces of equipment and locations. For example, a Reliability
Distribution Analysis lets you analyze historical failure data to help predict future
failures. Based upon those predictions, you can make plans for replacing equipment and
making repairs to prevent future failures. Predicting failures and replacing equipment will
ensure profitability, however, only if equipment failures are primarily responsible for
your lost profit opportunities.
Often, a large amount of profit is lost due to production problems, rather than equipment
or location problems. Therefore, analyzing losses due to operational problems is
necessary for conducting a comprehensive analysis of production losses. To quantify
losses due to operational problems, in addition to analyzing individual equipment and
locations, you must also analyze the process in which they are involved. To do this, you
can use a Production Analysis.
Production Analyses allow you to evaluate the reliability of the process in which
individual pieces of equipment and locations are involved. Instead of analyzing the
failure data, Meridium APM Production Analyses analyze production output data to help
you see patterns in the output and determine the reliability of the process as a whole.
Production Analyses provide a visual representation of production output and allow you
to quantify production losses and the cost associated with them. With regular use of
Production Analyses, your company can determine where you are losing the most money
and then take corrective actions that will help yield higher production and earn larger
profits.
Within a Production Analysis, you can plot production output data and then:
Define the observed production rate with a Demonstrated Line.
Determine the reliability of the production process by defining a Process

Reliability Line.
Define the ideal production output capacity with a Nameplate Line.
Compare the expected output to the ideal output to calculate the efficiency and
utilization costs.
Draw one or more Custom Lines to exhibit losses and gains compared to other
observed production output or based upon theoretical scenarios.
Data Used in a Production Analysis
To create a Production Analysis, you must collect production output information, which
consists of numeric values representing the output of a process over some period of time.
How you collect the output data and how often you collect it is up to you and may be
determined based upon a variety of factors, including the type of process, how often the
process produces measurable output, and how often you want to record it. While the
amount of time between output readings is up to you, note that to create a meaningful
analysis, the output data must be collected at regular intervals (e.g., hourly, daily, weekly,
or monthly) so that the output values can be compared to one another.
When you create a Production Analysis from within the Production Analysis module, you
can supply data to the analysis using a Meridium APM query or dataset, or you can enter
data manually using a grid provided for that purpose. To use a query as the basis for your
analysis, the production output data must be stored in the Meridium APM database so
that it can be queried. For example, you might store production data in custom Production
Output records that you create and associate with the systems for which you record
regular output readings.
You can also create a Production Analysis from within the Production Loss Accounting
(PLA) module. PLA allows you to create production plans and then record daily
production output against the plan. If desired, you can use these production output values
as the starting point for a Production Analysis.
Note: If you are using PLA to collect production data, Meridium provides the Production
Data family to store the output readings.
Keep in mind that production output data is collected for a process, not for individual
pieces of equipment. A single process may involve one or more pieces of equipment.
Throughout this documentation and in the Meridium APM Production Analysis tool, we
refer to this collection of equipment as the production unit. The term unit is simply a way
for us to refer to the process and all the pieces of equipment involved in it. It does not
imply a Meridium APM family or a specific record in the database.
Note: If you are using PLA to collect production data, Meridium provides the Production
Unit family for use within the PLA workflow.
If you are using a query or dataset to store production output data, the following table
lists the fields whose values you can provide to the analysis (through the Production
Analysis Builder). The source data must include at least production output values.
Data
Description
Notes
These values must

be numeric. You
can define the
units of measure
for the output
Values representing the amount of output
Production
values after you
produced by the unit during the specified period
Output
create the analysis.
of time (e.g., hourly, daily, weekly, or monthly).
Production output
values are required
for creating a
Production
Analysis.
The date on which the production output value
was recorded. If you have a date field within
Production your query or dataset and you choose not to
Production Dates
Date
map it to the Production Analysis Builder, you are optional.
can see the dates used to build the analysis in
the Edit Production Data grid.
Unit ID
A value that describes the production unit,

which consists of the individual pieces of
Units are optional.
equipment that work together to produce the
production output. You may have more than one
Unit ID value within the Production Analysis
and may group your datapoints by that specific
value.
Production Analysis Workflow

After you gather production output data and use it to create a Production Analysis, you
will need to perform a number of tasks within the analysis in order to analyze the data.
You are not required to perform these tasks in any particular order. In this topic, however,
we provide a workflow that we recommend you use for conducting a complete
Production Analysis the first time. Following this workflow will ensure that you complete
all the tasks that are necessary to conduct a complete analysis and will give you an
overview of the analysis process. After you have learned how to perform a full analysis
using this recommended workflow, you can adjust the order of the steps, omit steps, or
repeat steps to suit your specific needs.
Performing a Production Analysis consists of completing the following main steps:
1. Collect production output data. Before you can create a Production Analysis, you
first must collect production output data, which are numeric values representing
the output of a process over some period of time.
2. Use the data to create a new Production Analysis. You can create a new
Production Analysis from a Meridium APM query or dataset or from manually
entered data.
3. Define the unit of measure for your output data. Unit of measure is not taken into
account when you first create the analysis, even if a unit of measure is associated
with your production output values. After the analysis has been created, however,
you can label the production output data with the appropriate unit by setting the
unit of measure for the analysis.
4. Adjust the cost value for your unit of measure. To calculate the cost of your
production losses, you will need to define the cost associated with each unit of
output.
5. Draw the Demonstrated Line, which represents the production output when the
unit is operating at its observed rate of capability.
6. Draw the Process Reliability Line, which is the first point at which output
suddenly changes and the datapoints begin to deviate significantly from the
Demonstrated Line.
7. Draw the Nameplate Line, which represents the ideal production output of the
unit under ideal conditions.
8. Draw one or more Custom Lines, which let you make a visual comparison
between your demonstrated production rate and other observed or theoretical
production rates.
9. Evaluate the results by viewing the calculations on the Production Loss
Regions pane.
Example of a Production Process

To make this documentation easier to follow and to help explain how Production
Analyses can be used to evaluate production processes, in this topic, we provide an
example of a simple production process. We will refer to this example throughout the
Production Analysis documentation as necessary.
Consider the process of manufacturing bottled water, which might consist of the
following steps:
1. Collect water from spring.
2. Fill bottles.
3. Attach labels.
4. Attach caps.
5. Sort bottles, discard any that fail quality inspection, and package for shipping.
All of these steps must be completed in order to produce a finished product. In our
example, the production unit consists of the individual pieces of equipment that together
perform the steps in the process. The production output of this unit is a bottle of water
ready to be sold.
For our example, we will assume that we collect production output as the number of
bottles produced per day. We will also assume that we began producing bottled water on
January 1, 2000. Once a year we generate a Production Analysis to evaluate the actual
production output, to calculate losses compared to the ideal production output, and to
establish goals for improving production the following year.
Note: This example is extended in the Production Loss Accounting (PLA)
documentation. The PLA documentation assumes that a separate facility has production
units that create bottles, labels, and caps and distributes them to the facility that performs
the process described above.
Using the Production Analysis Builder

Using the Production Analysis Builder, you can create a new Production Analysis:
Based on a new or existing query or dataset.
From manually entered data.
-or-
You can access the Production Analysis Builder from the Select a Production Analysis
from the List page or the Production Analysis page.
Creating a Production Analysis from a

Query or Dataset
To create a new Production Analysis based on a new or existing query or dataset:
1. On the Reliability Analytics Start Page, click the Production Analysis link.
The Select a Production Analysis from the List page appears.
2. On the Common Tasks menu, click the New Analysis link.

Hint: If you do not want to view this screen the next time you access the builder, select
the Dont show this page again check box.
The Select Data Source Type screen appears.
4. Select one of the following options:
Production data will be loaded using an existing Query. If you select this option,
when you click the Next button, you will be asked to find and select the desired
query in the Catalog.
I will create a new Query and use it to load the production data. If you select this
option, when you click the Next button, the Query Builder will appear so that you
can design a new query. Click the Help button in the Query Builder for details on
building a new query.
Production data will be copied from an existing Dataset. If you select this option,
when you click the Next button, you will be asked to find and select the desired
dataset in the Catalog.
I will create a new Dataset and use its contents as production data. If you select
this option, when you click the Next button, the Dataset Builder will appear so
that you can design a new dataset. Click the Help button in the Dataset Builder for
details on building a new dataset.
After you have selected or created the desired query or dataset and clicked the Next
button, it appears on the Select screen of the Production Analysis Builder.

The Select Production Fields screen appears. The Production Output list and the
Production Date list are populated automatically.
6. In the Production Output list, select the field that stores values representing the
production amount that you want to use in your analysis. The list displays all the
numeric fields that exist in your query or dataset; the first numeric field is selected
by default. This field is required.
7. In the Production Date list, select the field that will be used as the date of
production for the analysis. The list displays all date fields that exist in your query
or dataset, the first date field is selected by default. This field is optional.
8. In the Unit ID field, select the field that stores values identifying the production
unit for which the production data has been recorded. The list displays all
character fields but is not populated automatically. This field is optional.
Note: If the query returns or the dataset contains any null production values, a warning
message appears, notifying you that all null production values will be converted to a
value of zero within the analysis. Click OK.
If Meridium APM finds zeros or negative numbers for the Production Output value in the
dataset or the query results, the Minimum Production Output dialog box appears.
10. In the Min Production Output text box, type the value that you want to use to
replace zero and negative production output values. The suggest value is
calculated based on the highest production output. Zero and negative values
cannot be plotted and will instead be plotted using the value specified here. You
can also change the Minimum Production value after the Production Analysis has
been created.
Note: To determine the suggested value, 0.00001 is multiplied by the highest production
output value and then rounded down. For example, if the highest production output value
is 823, that value is multiplied by .00001 to equal .00823. That value is then rounded
down to one at the first non-zero decimal place, or .001 in this example, to become the
default value in the Minimum Production Output dialog box.
11. Click OK.
The Production Analysis page appears, displaying the results of the analysis.
12. Click the Save Analysis link on the Common Tasks menu to save the analysis
results. After you have created a new analysis, our first step will be to draw the
Demonstrated Line.
Creating a Production Analysis from

Manually Entered Data
To create a new Production Analysis based on manually entered data:
1. On the Reliability Analytics Start Page, click the Production Analysis link.
2. On the Common Tasks menu, click the New Analysis link

Hint: If you do not want to view this screen the next time you access the builder, select
the Dont show this page again check box.
The Select the Data Source Type screen appears.
4. Select the I will manually enter production data option.

5. Click the Finish button
The Edit Production Data grid appears, displaying a single empty row.
6. In the Production Output cell of the first row, type the first production output
value. This field is required.
Note: If you do not have any data for a given date, you must type 0 (zero). Null values
are not allowed.
7. In the Date cell of the first row, if you want to enter a date:
o
Click the
button, and use the Calendar to select a date associated with
the first production output value.
-or
Type the first production date.
The date is optional.

8. In the Ignore cell of the first row, select the check box if you want to exclude this
output value from calculations performed by the Production Analysis. The
datapoint will be plotted but will be displayed as an X.
9. In the Product cell of the first row, type the name of the product. This field is
optional.
10. In the Production Comments cell of the first row, type any additional comments.
This field is optional.
11. Repeat steps 6-10 until all production data has been entered.
12. Click OK.
The Edit Production Data grid closes. If you entered zeros or negative numbers for the
production output values, the Minimum Production Output dialog box appears.
13. In the Min Production Output text box, type the value that you want to use to
replace zero and negative production output values. The suggest value is 0.00001,
but is calculated based on the highest production output. Zero and negative values
cannot be plotted and will instead be plotted using the value specified here. You
can also change the Minimum Production value after the Production Analysis has
been created.
Note: Note: The value .00001 is multiplied by the highest production output value and
then rounded down. For example, if the highest production output value is 823, that value
is multiplied by .00001 to equal .00823. That value is then rounded down to the nearest
tenth decimal place, or .001 in this example, to become the suggested value in the
Minimum Production Output dialog box.
14. Click OK.
The Production Analysis page appears, displaying the results of the analysis.
15. Click the Save Analysis link on the Common Tasks menu to save the analysis
results. After you have created a new analysis, our first step will be to draw the
Demonstrated Line.
Accessing the List of Production

Analyses
To display the list of existing Production Analyses:
On the Reliability Analytics Start Page, click the Production Analysis link.
When you first access the Select a Production Analysis from the List page, Meridium
APM runs the Production Weibull query to display all the Production Analyses that were
updated by the Meridium APM user who is currently logged in. From the Select a
Production Analysis from the List page, you can:
Click any hyperlinked analysis in the results list to access that analysis. Note that
you can also select more than one analysis, and click the Multiple Analyses link
on the Plots menu to view multiple Production Analyses on the Multiple
Production Analyses Plot.
Select different criteria and rerun the Production Weibull query to view a different
list of Production Analyses and then access any analysis in that list.
Click the New Analysis link on the Common Tasks menu to begin the process of
creating a new Reliability Production Analysis.
Aspects of the List of Production

Analyses
The Select a Production Analysis from the List page lets you run the Production Weibull
query to view a list of existing Production Analyses that meet your query criteria.
The Production Weibull query is stored in the Meridium APM Catalog in the folder
\\Public\Meridium\Modules\Reliability Manager\Analyses. The baseline Production
Weibull query contains one prompt: Last Updated By. This prompt appears at the top of
the page as a drop-down list that contains the list of users.
The Last Updated By list contains the following options:
Your user name, which is selected by default and will cause the query to return
only the Production Analyses that were last updated by you.
The user name of any user who last updated any Production Analysis, which will
cause the query to return only the Production Analyses that were last updated by
that user.
The [All Users] option, which will cause the query to return a list of Production
Analyses updated by any user.
Each time you access the Select a Production Analysis from the List page, 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 Production Weibull query and
display the results in a grid at the bottom of the page.
Note: Although the results are returned by the Production Weibull query, query page size
is ignored. The entire list of analyses is displayed at once.
The default Production Weibull query is configured to display the following columns of
information: Analysis ID, Last Updated, and Updated By. You can click any hyperlinked
Analysis ID to view the associated Production Analysis summary. In addition, you can
use the options on the Common Tasks menu to perform various tasks for the analyses in
the list.
Plots Menu
The Plots menu on the Select a Production Analysis from the List page contains the
following link:
Multiple Analyses: Displays the datapoints of multiple existing Production

Analyses on the Multiple Production Analyses Plot.
Common Tasks Menu
The Common Tasks menu on the Select a Production Analysis from the List page contains
the following links:
New Analysis: Displays the Production Analysis Builder, which will guide you
through the process of creating a new Production Analysis.
Open Analysis: Opens the Find Items window, which lets you search for an
existing Production Analysis.
Delete Analyses: Deletes the currently displayed analysis.
Page.
Help: Displays the context-sensitive Help topic for the Select a Production
Analysis from the List page.
Note: The Save Analysis and Save Analysis As links are always disabled on the Select a
Production Analysis from the List page.
Opening an Existing Production

Analysis
To open a Production Analysis:
1. On the Select a Production Analysis from the List page, in the Last Updated By
list, select the user for which you want to return a list of Production Analyses.
Note: Additional fields may appear if the baseline query has been modified. If additional
fields are available, use them to limit the query results as desired.
Meridium APM runs the Production Weibull query and displays the results in the grid in
the main display area.
3. In the Analysis ID column, click the analysis ID of the analysis that you want to
open.
The Production Analysis page appears.
When you open an existing analysis, the analysis will display the data and calculations
that were last saved with the analysis. If you want to reload the underlying query or
dataset and update calculations based on any changes to the underlying data, you must
reload the analysis after opening it.
Opening Multiple Existing Production

Analyses
To open multiple existing Production Analyses:
1. On the Select a Production Analysis from the List page, in the Last Updated By
list, select the user for which you want to return a list of Production Analyses.
Note: Additional fields may appear if the baseline query has been modified. If additional
fields are available, use them to limit the query results as desired.
Meridium APM runs the Production Weibull query and displays the results in the grid in
the main display area.
3. Select the rows containing the Production Analyses that you want to open.
4. On the Plots menu, click the Multiple Analyses link.
The selected analyses appear on the Multiple Production Analyses Plot page, displaying
the datapoints, Process Reliability Lines, and Production Lines for each analyses. Each
separate analysis and the lines associated with it appear in coordinating colors. The
legend appears to the right of the plot by default to display which colors represent what
for the different analyses.
Note that even though the Process Reliability Lines are represented as a dotted, horizontal
line on the Multiple Production Analyses Plot, they are not represented in the legend.
From the Multiple Production Analyses Plot page, you can:
Pause on a defined analysis or Production Line in the legend to highlight

the associating analysis or Production Line in the plot area.
View the details of a specific analysis by clicking a datapoint, reliability

line, or production line to open that analysis on the Production Analysis
page.
View the details of a datapoint, reliability line, or production line by

pausing on a datapoint, reliability line, or production line.
Customize the Multiple Production Analysis Plot using the standard graph
toolbar or the annotation toolbar.
Click the New Analysis, Open Analysis, Send To, or the Help links on the
Common Tasks menu.
Aspects of the Production Analysis Page

The Production Analysis page displays the Production Analysis Plot as datapoints on a
graph. The dates for which the datapoints represent are displayed as a subtitle above the
graph. There are two windows that appear below the analysis by default and display the
values from defining the Process Reliability line, the Demonstrated Line, the Nameplate
Line, and the Production Line:
Production Loss Regions pane
Production Lines pane
The Production Analysis page contains the following task menus: Analysis Tasks,
Analysis Settings, Common Tasks, and Associated Pages. These task menus give you
quick access to common tasks associated with Production Analyses.
The Production Analysis page provides a standard graph toolbar, where only some of
standard toolbar options are available. The standard graph toolbar for a Production
Analysis contains an additional Zoom in feature, which allows you to zoom in on any
selected area. A Zoom out feature is also available to let you revert to the original view of
the Production Analysis. The annotation toolbar for a Production Analysis allows you to
customize the plot with features such as shapes and text boxes.
Analysis Tasks Menu
The Analysis Tasks menu on the Production Analysis page contains the following links:
Define DL: Displays a submenu that lets you define the Demonstrated Line using
the following options: Regression Fit, Draw Line, Select Point and Specify Beta,
or Specify Beta and Eta.
Define Reliability: Allows you to draw the Process Reliability Line, which
defines the reliability of the process as a percentage.
Define NL: Displays a submenu that lets you define the Nameplate Line using the
following options: Regression Fit, Draw Line, Select Point and Specify Beta, or
Specify Beta and Eta.
Create CL: Displays a submenu that lets you define a Custom Line using the
following options: Regression Fit, , Draw Line, Select Point and Specify Beta, or
Specify Beta and Eta.
Edit Data: Displays the Edit Production Data window, where you can view and
edit the production data.
Reload Data: Reloads the data stored in the database after asking for confirmation
to overwrite any existing data. This link appears only if the analysis is based on a
query or a dataset.
View Data Source: Displays the data that serves as the source of the analysis. This
link appears only if the analysis is based on a query or a dataset.
If the analysis is based on a query, this link will open the query results.
If the analysis is based on a dataset, this link will open the dataset.
Group Data By: Displays a submenu that allows you to separate datapoints into
groups using the values in a selected field. Each group will be identified on the
Production Analysis with a different color.
Generate Report: Displays the Report Options dialog box, where you can select
the elements of the analysis that you want to include in a report.
Rename Analysis: Displays the Rename Analysis dialog box, where you can
change the name and description of the analysis. Note that changes to the name
and description take effect immediately, but you must save the analysis to save the
changes.
View Recommendations: Allows you to view and edit recommendations related to

the current analysis. This link is enabled only if you are viewing a saved analysis.
Analysis Settings Menu
The Analysis Settings menu on the Production Analysis page contains the following links:
Show/Hide: Displays a submenu, where you can choose to show or hide the
Production Lines pane and the Production Loss Regions pane.
Min Production: Displays the Minimum Production Output dialog box, where you
can change the minimum value used by the current analysis.
Unit of Measure: Displays the Unit of Measure dialog box, where you can change
the units of measure for the production output.
Margin Value: Displays the Margin Value dialog box, where you can define the
cost associated with each unit of output.
Margin Currency: Displays the Margin Currency dialog box, where you can
change the cost currency of the analysis.
Common Tasks Menu

The Common Tasks menu on the Production Analysis page contains the following links:
New Analysis: Displays the Production Analysis Builder, which will guide you
through the process of creating a new Production Analysis.
Open Analysis: Displays the Find Items window, which you can use to locate ad
open an existing Production Analysis.
Save Analysis: Saves the currently displayed analysis. If you are viewing a brand
new analysis that has not yet been saved, this link will display the Save Analysis
dialog box, where you can save the analysis. If you are viewing an existing
analysis, when you click this link, Meridium APM will save any changes that you
made to the analysis since it was last saved.
Save Analysis As: Displays the Save this Analysis dialog box, where you can
choose to save it with a different name.
Delete Analysis: Deletes the currently displayed analysis.
Page.
Help: Displays the context-sensitive Help topic for the Production Analysis page.
The Associated Pages menu on the Production Analysis page displays only links that
have been configured for the Production Analysis family. For details on configuring items
to appear on the Associated Pages menu, see the URL Manager Help.
About the Production Analysis Plot

When you create a Production Analysis, Meridium APM plots the production output
values. The output values themselves are plotted along the x-axis, and the Reliability
Percentage values for each datapoint are plotted along the y-axis. The Reliability
Percentage is calculated by first determining the median rank of each output value and
then using the median rank in a second equation that converts it to the Reliability
Percentage. The following simplified equation can be used to determine an approximated
median rank for each output value:
Median Rank=1-(i-.3)/(N+.4)
...where:
i = The order of each datapoint with respect to other datapoints. To determine the
i value of each datapoint, the output values are sorted from highest to lowest. The
highest output value is assigned a value of i=1. The second-highest value is
assigned i=2, and so on until all the output values have been numbered.
N = The number of output values. For example, if your Production Analysis has a
year's worth of datapoints, then N=365. If your Production Analysis has only a
month's worth of datapoints, then N=31 or N=30, depending on what month you
are using.
After the median rank has been calculated, the Reliability Percentage is calculated using
the following equation and then plotted along the y-axis:
Reliability Percentage=100-(Median Rank*100)
The general shape of the plot can provide you with basic information about your
production process:
Ideally, the datapoints will be plotted to form a vertical line at the highest possible Xvalue. This would mean that your process is producing the highest rate of output at all
times, with no variation, and that you have no reliability or process problems. While this
scenario is not realistic, visualizing the ideal plot compared to your actual plot can be
useful in understanding how far your actual data deviates from ideal data.
If the datapoints are plotted in a straight, diagonal line that slopes downward from
right to left with no sharp change in production rate, then any variation in output is due to
process problems; you have no equipment/location reliability problems.
If the datapoints show a sharp change in production, then you have both process
problems and equipment/location reliability problems. You will draw your Process
Reliability where you notice this sharp change in production output.
Within the reliability loss region, you may notice distinct areas where the production
output varies greatly from the rest of the datapoints in the region. These variations may
be due to different types of reliability problems, such as system shutdowns, intentional
cutbacks, and equipment/location failures. You can create breakpoints to divide the
reliability loss region into separate areas where you notice these changes.
About the Process Reliability Line

An ideal process will produce the maximum possible output at all times, but actual
processes demonstrate variation in output over time. The variation in output can be
caused by various factors, including process problems, equipment and location problems,
shutdowns, and cutbacks.
The Process Reliability Line marks the location at which datapoints begin to trend away
from the Demonstrated Line. This is the location at which variation in output shifts from
being attributed to production losses to being attributed to reliability losses and defines
the reliability of the process, expressed as a percentage. It is the point at which the
process shifts from being fairly reliable to being unreliable.
For example, in the following Production Analysis, notice the Process Reliability Line for
the bottled water production process.
Reading the analysis from right to left, notice that the output closely follows the
Demonstrated Line until the production output is around 3000 bottles per day. The output
then decreases and begins to trend away from the Demonstrated Line toward a lower
Reliability rate. We have drawn the Process Reliability Line where we observed this
distinct change.
Notice that the line is labeled Process Reliability: 65.15%. This means that our process
is reliable 65.15% of the time. The other 34.85% of the time, production loss is due to
equipment/location failures, downtime, or intentional cutbacks in production.
The decision of where to draw the Process Reliability Line is somewhat subjective and
will be determined by how your datapoints look after they have been plotted and how you
interpret the plot. If your datapoints do not exhibit a distinct trend away from the
Demonstrated Line, and are plotted in a fairly, straight, diagonal line, it may not be
appropriate to draw the Process Reliability Line at all.
Defining the Process Reliability Line

To create a Process Reliability line on a Production Analysis:
On the Production Analysis page, on the Analysis Tasks menu, click the Define
Reliability link.
Select the point on the analysis at which datapoints begin to trend away from the
Demonstrated Line.
A dotted line appears and is labeled Process Reliability: [Percentage], where
[Percentage] indicates the reliability of the process, represented as a percentage.
On the Common Tasks menu, click the Save Analysis link to save the changes.
Note: To delete the Process Reliability Line, right-click the line, and then click
Delete Reliability Line.
Types of Production Lines

When viewing the results of a Production Analysis, you can define the following
types of lines:
Demonstrated Line: Represents the production output when the unit is
operating at its observed rate of its capability. The region between the
Demonstrated Line and the Nameplate Line is represented as the
Efficiency/Utilization Loss region on the Production Loss Regions pane.
Nameplate Line: Represents the most ideal production output of the unit.
Custom Line: Provides a visual comparison between the Demonstrated Line

and other observed or theoretical production rates. You can have more than one
Custom Line per analysis.
All of these lines can be drawn by:
Using Regression Fit.
Selecting a point and specifying the Beta value.
Drawing the line manually.
Specifying Beta and Eta values.
Note: To delete any of the lines, right-click the line, and then click Delete Line.
About the Demonstrated Line

Somewhere on the Production Analysis you should be able to identify a group of
datapoints that represent your typical output. Consider again our example of the
bottled water production process. In the Production Analysis plot, notice the
group of datapoints between 3000 and 4000 bottles per day. Within this range, the
variation in number of bottles produced is relatively small. This is the
demonstrated production output of our production process, where the production
unit produces the same amount on a regular basis. Therefore, we have defined the
Demonstrate Line along these datapoints.
The Demonstrated Line extends beyond the plotted datapoint to show what the
production would have been if the production rate had not started to drop off due
to reliability problems, such as equipment and location failures, cutbacks, and
downtime.
Hint: Drawing the Demonstrated Line first can help you determine where to draw
the Process Reliability Line. You will want to draw the Process Reliability Line
where the datapoints begin to deviate from the Demonstrated Line.
About the Nameplate Line

Every process will have both ideal output value and actual output values. Ideally,
a process should always produce the maximum possible output. The maximum
possible output is determined by a variety of factors and is often influenced most
significantly by manufacturer specifications. Many manufacturers specify a
nameplate value for their equipment to indicate the highest capacity of a given
piece of equipment under ideal operating conditions. Together, the nameplate
values for the individual pieces of equipment can help you determine the
nameplate value for the entire unit, which is the maximum production output for
the process under ideal operating conditions.
After you have plotted your production data, you will want to draw a Nameplate
Line on the Production Analysis Plot to indicate the ideal output. Meridium APM
will calculate the difference between the ideal output and your observed output
values (represented by the Demonstrated Line) to determine your
Efficiency/Utilization Losses.
Note that it may not always be appropriate to use the manufacturers nameplate
value as the nameplate value for your process. The maximum production capacity
based upon manufacturers specifications may be unrealistic if you intentionally
operate under conditions that do not meet those specifications. For example, you
may operate at a lower temperature due to environmental constraints. If you
calculate your production losses based upon an impossible goal, your losses may
appear inflated. In this case, you may want to consider these factors into account
to determine a more realistic nameplate value: one that actually can be achieved.
Consider again our example of the bottled water production process. On the
Production Analysis Plot, notice that on October 18, 2006, the bottled water
production process produced 4100 bottles of water, the highest observed value all
year. In this example, we have drawn the Nameplate Line (green) through the
highest actual production value, which we consider our ideal value. This will help
us determine the efficiency and utilization losses by comparing the ideal
production output to the observed production output.
Alternatively, your process may be operating precisely according to the

manufacturers specifications. In this case, you may want to draw your Nameplate
Line at a location determined by the manufacturers nameplate values. In this
case, the location of the Nameplate Line may or may not correspond to any actual
output values that have been plotted. Even though the manufacturers
specifications are being followed, the process may still be operating well below
its maximum capacity, in which case the Nameplate Line may be drawn above
your first observed output value.
About the Custom Line

After you have drawn the Demonstrated Line, the Process Reliability Line, and
the Nameplate Line, you can optionally draw one or more additional Custom
Lines to compare historical or projected production rates to the observed
production rate. For example, you might draw a Custom Line:
To compare the current years production to the previous years
production.
To compare your companys production rates with the production rates
of another company that is using the same process.
To project how much more you could produce the next year if you
improved your process to achieve a projected production rate.
Again, consider our example of the bottled water production process. To
increase our profits, we want to have a higher rate of production in 2007
than we did in 2006. To set a stretch goal for 2007, we have drawn a
Custom Line using the Beta and Eta values that we want to achieve for
2007.
To draw the line, we used the Specify Beta and Eta option and chose the
Eta value of 3368.8576, which is the same as the Demonstrated Line for
2006, and a Beta value of 25 to project less production variation than
shown by the Demonstrated Line. After we have evaluated the differences
in the current 2006 production rate and the anticipated 2007 production
rate, we can begin determining what actions we need to take to achieve
that goal for the following year.
Using Regression Fit

The Regression Fit option lets you select a group of datapoints and then
calculates the best-fit method to draw a line for that set of datapoints. For
the following example, we will draw a Demonstrated Line using the
Regression Fit option.
To draw a line using the Regression Fit:
On the Production Analysis page, on the Analysis Tasks menu, click
the Define DL link.
A submenu appears.
Click Regression Fit.

The pointer changes to a cross
selecting a group of datapoints.
, indicating that you can begin
Click and drag the pointer to create a box around at

least two datapoints.
Note: If you attempt to draw a regression fit around
datapoints where the Beta value will be close to zero and
Eta will be too large, an error message appears, explaining
that Eta is out of range.
Meridium APM draws the line through the area of selected
datapoints using the best-fit method, and the pointer reverts
back to an arrow. The following image shows a magnified
example of a line drawn using the Regression Fit method.
On the Common Tasks menu, click the Save

Analysis or Save Analysis As link to save all
changes.
V3.6.0.0.0 - Copyright 1993-2014 Meridium, Inc.

All rights reserved.
Drawing a Line
Manually
The Draw Line option allows you to draw a line
manually anywhere on the current analysis. For
example, we will show you how to draw a
Nameplate Line using the Draw option.
To draw a line manually:
On the Production Analysis page, on the
Analysis Tasks menu, click the Define NL link.
A submenu appears.
Click Draw Line.
The pointer changes to a pencil

,
indicating that you can draw the line
manually anywhere on the Production
Analysis.
Click and drag the pointer where
you want the line to appear.
The line appears, and the pointer
reverts back to an arrow. In the
following image, we show an
example of a Nameplate Line drawn
using the Draw Line option.
On the Common Tasks

menu, click the Save Analysis
or Save Analysis As link to
save all changes.
V3.6.0.0.0 - Copyright
1993-2014 Meridium, Inc.
Selecting a
Point and
Specifying
Beta
The Select Point and Specify
Beta option allows you to
select a datapoint for a line to
pass through and enter the
Beta value to determine the
slope of the line. For the
following example, we will
draw a Nameplate Line using
the Select Point and Specify
Beta option.
To draw a line by selecting a
point and specifying the Beta
value:
On the Production
Analysis page, on the
Analysis Tasks menu, click
the Define NL link.
A submenu appears.
Click Select Point

and Specify Beta.
Click the
datapoint through
which you want the
line to pass.
The Define
Nameplate Line
dialog box appears.
In the Beta
text box, type
the desired
Beta value. If
a Nameplate
Line does not
currently exist,
the value for
Beta is set by
default to 10
but can be
changed to
any number
between .001
and 1000. If a
Nameplate
Line does
exist, the
value for Beta
is set to the
value of that
line but can be
changed to
any number
between .001
and 1000.
Keep in mind
that the higher
the Beta value,
the more
vertical the
line will be.
Click OK.
The line is
drawn through
the selected
datapoint with
the slope
designated by
the specified
Beta value.
The following
image shows a
magnified
view of a line
that was
drawn using a
Beta value of
50.
On
the
Comm
on
Tasks
menu,
click
the
Save
Analys
is or
Save
Analys
is As
link to
save
change
s.
V3.6.0.
0.0 Copyri
ght
19932014
Meridi
um,
Inc. All
rights
reserve
d.
S
pec
ifyi
ng
Bet
a
an
d
Eta
Val
ues
The
Specify
Beta
and
Eta
option
allows
you to
draw a
line by
enterin
g both
the
Beta
and
Eta
values.
This
tool
may be
useful
when
you
create
a
Custo
m Line
to
indicat
e the
produc
tion
rate of
output
used in
another
Produc
tion
Analys
is.
Simply
copy
the
Beta
and
Eta
values
for the
Demon
strated
Line
from
that
analysi
s and
then
provid
e them
when
using
this
option.
In the
followi
ng
exampl
e, we
will
create
a
Custo
m
Line.
To
draw a
Custo
m Line
by
specify
ing
Beta
and
Eta
values:
On
the
Produ
ction
Analys
is
page,
on the
Analys
is
Tasks
menu,
click
the
Create
CL
link.
A
subme
nu
appear
s.
C
l
i
c
k
S
p
e
c
i
f
y
B
e
t
a
a
n
d
E
t
a
.
T
h
e
C
r
e
a
t
e
C
u
s
t
o
m
L
i
n
e
d
i
a
l
o
g
b
o
x
a
p
p
e
a
r
s
.
In
the
Beta
text
box,
type
the
desired
Beta
value.
The
Beta
value is
set to
10 by
default
but can
be
change
d to
any
number
betwee
n .001
and
1000.
In
the Eta
text
box,
type
the
desired
Eta
value.
The Eta
value is
set to 1
by
default
but can
be
change
d to
any
number
less
than
100000
0000.
Click
OK.
The
line
appears
and
intersec
ts the
product
ion
output
where
the
Reliabil
ity
Percent
age is
36.8%
with a
slope
designa
ted by
the
specifie
d Beta
value.
The
Beta
and Eta
values
specifie
d
appear
on the
Produc
tion
Lines
pane.
In the
followi
ng
exampl
e, the
Beta
value is
set to
25 and
the Eta
value is
set to
3368.8
576.
These
are the
values
we
chose
to use
for the
Custom
Line in
our
bottled
water
product
ion
process
exampl
e.
On the
Common Tasks
menu, click the
Save Analysis
or Save
Analysis As
link to save all
changes.
V3.6.0.0.0 Copyright
1993-2014
Meridium, Inc.
All rights
reserved.
Grou
ping
Produc
tion
Data
When a
Production
Analysis has
been created
using fields in
addition to
Production
Output and
Date, you can
color code the
datapoints
according to
the values in
any of those
fields.
Consider again
our example of
the bottled
water
production
process. The
dataset used to
create our
Bottled Water
Production
Analysis
contains three
columns: Date,
Production,
and Category.
We used the
Category field
to record the
reasons for the
Production
Output on a
given day, such
as Equipment
Failure,
Process
Variability,
Budgeted
Maintenance,
and so on. We
can use the
Group By
feature to color
code our
datapoints for
each of these
categories.
To group the
data by a field:
On the
Analysis Tasks
menu, click the
Group By link.
A submenu
appears with
the fields
available in the
query or
dataset.
Select the field

that you want to us
for color coding.
The datapoints with

the Production
Analysis change co
to correspond to the
values in the field.
different color is
assigned automatic
to each unique valu
Note: The legend w

not appear
automatically. You
enable the legend
using the standard
graph toolbar.
By grouping our
example analysis b
the Category field,
can see which
datapoints are
associated with eac
category.
Hint: You can hove

over a datapoint on
Production Analysi
highlight all the
datapoints in the sa
group.
V3.6.0.0.0 - Copyri
1993-2014
Meridium, Inc. All
rights reserved.
What is
a
Breakpoi
t?
On a Production
Analysis Plot, you
draw the Process
Reliability Line to
identify your
Reliability Loss
Region. Datapoints
below the Process
Reliability Line hel
make up the
Reliability Loss
Region.
Typically, the
Reliability Loss
Region will show
large variations in
output that can be
attributed to proble
that impact the
production process
significantly, such a
equipment and
location failures,
system shutdowns,
and intentional
cutbacks. For
example, if you col
production output d
daily and the system
shut down complet
for five days during
your collection peri
then five datapoints
will have near-zero
values. These value
should be easily
distinguishable from
the rest of the value
in the Reliability Lo
Region.
To calculate your
Reliability Losses
accurately, you may
want to separate the
datapoints associate
with shutdowns fro
the datapoints wher
losses are attributed
actual equipment
slowdowns or
intentional cutback
You can use the
breakpoint tool to
separate the
Reliability Loss
Region into these
categories. The
breakpoints will be
taken into account i
calculations so that
your Reliability
Losses represent
losses due to actual
equipment and
location problems.
Breakpoints also ca
be used to identify
areas of distinct
change in output w
you do not know th
reason for the chan
Consider again our

example of a bottle
water production
process. In the
following example,
have circled the
datapoints associate
with unplanned
shutdowns due to
uncontrollable issue
(e.g., lack of raw
material), where the
production output i
near zero.
To separate this reg

from the rest of the
reliability losses, w
can create a
breakpoint on the
highest Reliability
value within that
distinct region. Afte
the breakpoint has
been created,
Meridium APM
automatically shade
the different region
production output.
Hint: You can chan

the color of any reg
by right-clicking th
shaded region and
clicking Set Region
Color. A color
template window w
appear where you c
select the desired
region color.
Now two shaded

Reliability Loss
regions are visible o
the Production
Analysis Plot. The
gray area represent
losses associated w
unplanned and
planned shutdowns
and the purple area

represents the losse
due to equipment a
location failures an
intentional cutback
All reliability losse
will be calculated f
each region and wil
appear as Sub
Reliability Loss
regions on the
Production Loss
Regions pane.
Note: You can crea

more than one
breakpoint when yo
production output
displays more than
two regions of
shutdowns, equipm
and location failure
intentional cutback
or other unknown
variations.
V3.6.0.0.0 - Copyri
1993-2014
Meridium, Inc. All
rights reserved.
Creatin
a
Breakpoi
t
To create a breakpo
for a Production
Analysis:
On the Product
Analysis page, righ
click the datapoint
where you want to
insert the breakpoin
A shortcut menu
appears.
Click Break.
Meridium APM sep

Reliability Loss reg
two shaded regions
Production Loss Re
includes the values
Sub Reliability Los
and the total Reliab
region.
Repeat steps 1 a
desired breakpoints
created.
Hint: If the datapoi

together, you may n
before creating a br
V3.6.0.0.0 - Copyri
Meridium, Inc. All
Removi
Breakpoi
To remove a breakp
associated region:
On the Producti
right-click the desir
A shortcut menu ap
Click Delete Re
The region is remov

associated breakpoi
Hint: You can also

right-clicking on th
clicking Break. A b
indicates that this is
V3.6.0.0.0 - Copyri
Meridium, Inc. All
About t
Productio
Window
The Edit Productio

you to view the dat
Production Analysi
the Edit Production
correspond to value
the analysis. For in
For an analysis
Production Data w
returned by the que
For an analysis
Production Data w
stored in the datase
For an analysis
data, the Edit Produ
information that yo
analysis.
Other fields show v

Meridium APM sys
in the Edit Product
the Production Data
record.
You can modify cer

order to update data
would not want to c
an error in the origi
calculated by the M
be modified.
The following imag

Production Data w
V3.6.0.0.0 - Copyri
Data M
Edit Prod
Window
When you create a

query or dataset, th
will prompt you to
query or dataset to
Analysis. The value
Select Production F
Analysis Builder w
columns in the Edit
Note: If the analysi

and contains additio
to columns in the a
will appear in the E
with the column na
The following char

mapped from fields
Builder to columns
window.
V3.6.0.0.0 - Copyri
Accessin
Productio
To view and modify
On the Product
link on the Analysis
The Edit Productio
V3.6.0.0.0 - Copyri
rights reserved.
Aspects
Productio
The Edit Productio

are specific to the f
are any additional v
Production Output
parentheses along t
Hint: You can sort t

grid.
The following colu

grid on the Edit Pro
Production Out
create the analysis.
manually entered w
Date: The date

record. This value i
entered when you c
Ignore: A value
selected row is igno
calculations and plo
row will be exclude
selected row will be
value manually.
Total Rows: Th
Data window.
Ignored Rows:
Data window in wh
Total Productio
Output column.
Note: If you change

window, after you c
Production Analysi
link on the Commo
the Edit Production
click OK, if there w
Minimum Productio
V3.6.0.0.0 - Copyri
reserved.
Changin
Productio
The Minimum Prod

zeros and negative
create a new analys
numbers, you will b
Output value. You w
Production Output
zeros and negative
previously contain
following instructio
with the analysis.
To change the Mini
On the Producti
menu, click the Min
The Minimum Prod

Production Output
selected when the a
In the Min Prod

use to replace zeros
Click OK.
The Production An
Output value.
On the Commo
to save all changes.
Note: The Min Prod

production output d
V3.6.0.0.0 - Copyri
Changin
When viewing the r

characterized along
of measure is taken
created if the data i
data, then there is n
it has to be set. Afte
production data wit
To set a unit of mea
On the Product
Unit of Measure lin
The Unit of Measur
In the Unit of M
used to collect the d
Click OK.
The Production An
and on the Product
values in the Quant
On the Common
changes.
V3.6.0.0.0 - Copyri
Changin
On the Production
expense associated
ratio of lost produc
then Meridium AP
Cost value accurat
To change the Marg
On the Producti
The Margin Value d
In the Margin V
loss to determine th
Margin Value text b
Click OK.
The Production Los
On the Commo
V3.6.0.0.0 - Copyri
Changin
On the Production
the calculated prod
currency. If you wa
Margin Currency d
Note: When you cr

Culture setting that
saved with the anal
Culture setting has
associated with you
saved with the anal
settings.
To change the marg
On the Product
The Margin Curren
In the Margin C
Click OK.
The Production Los
On the Common
V3.6.0.0.0 - Copyri
About t
The Production Los
The Production Los

Utilization Losses.
the analysis.
Total Loss: The
Reliability Loss
the Demonstrated L
the Sub Reliability
Sub Reliability
first breakpoint, bel
the previous breakp
Note: Sub Reliabili

Loss rows will corr
Because all Reliabi

change if you chang
Efficiency/Utili
For each row on the
Name: The nam
Quantity: A val
you can change the
Cost: A value re
rounded up to the n
Hint: To export the

Regions Data. Afte
V3.6.0.0.0 - Copyri
About t
The Production Lin
The Production line

corresponds to the c
specified on the ana
Demonstrated:
Custom: The C
Nameplate: The
For each row, the P
Name: The nam
Beta: The Beta

The closer the line
process (more relia
following general g
Beta = 5: L
Beta = 10: Mod
Beta = 25: Som
Beta = 50: Min
Beta = 100: On
Beta = 200: Alm
Eta: The Eta va

Reliability.
You can manually c

defining a different
Hint: To export the

the values have bee
V3.6.0.0.0 - Copyri
Hiding
The Production An
analysis details are
To hide the Product
On the Product
A submenu appears
appears next to the
Click the name
The submenu close

selected.
To display the Prod
On the Product
A submenu appears
appears next to the
Click the name
The submenu close
To move the Produ
On the Product
If you are opening
changes.
V3.6.0.0.0 - Copyri
Ignorin
Certain production
will be three near-z
data in your produc
individual producti
You can ignore any

Reliability Loss cal
intentional losses. Y
losses due to equipm
To ignore datapoint
On the Producti
The Edit Productio
Locate the row
In the Ignore ce
Repeat these ste

Note: To include a
Click OK.
Meridium APM rec

the analysis but are
Hint: You can also
V3.6.0.0.0 - Copyri
Overvie
The baseline Merid

you run the Produc
The Production An
The main repor
The subreport, S
The supporting
Manager\Reports. T
ProductionA
ProductionAnal
Data sections of the
ProductionAnal
Throughout this do
The Production An
Production Analysi
results for the curre
will need to supply
cannot be run direc
The Production An
Analysis Summa
Production Line
Production Los
Production Wei
Production Dat
V3.6.0.0.0 - Copyri
Runnin
You can run the Pro
To run the Producti
On the Producti
The Report Options
Select the desir
The Production An
V3.6.0.0.0 - Copyri
Analysi
The Analysis Summ
The following table
V3.6.0.0.0 - Copyri
Product
The Production Lin

Production Analysi
The following table
V3.6.0.0.0 - Copyri
Product
The Production Los

linked to the Produ
The following table

report.
V3.6.0.0.0 - Copyri
Product
The Production We
V3.6.0.0.0 - Copyri
Product
The Production Da
Analysis record.
The following colu

field in the Product
Production Out
Date
Ignored
V3.6.0.0.0 - Copyri
Results
After you have crea

your liking, you can
In the previous ima
Sub Reliability
represents the prod
Sub Reliability
represents the prod
Efficiency/Utili
Each area represent

table, we list our lo
Note: The shaded r

calculations, howev
highest loss.
The loss calculation
Many companies au
process problems. T
we repair the equip
If, as in our exampl

problems to be. For
example might beg
manager to monitor
first step in helping
If, on the other han

the piece of equipm
V3.6.0.0.0 - Copyri
What is
Meridium APM Re
replace those piece
predictions, you can
sure that you have a
The key to a succes
Optimizing the
Not having a su
To help you mainta

failure and repair d
You can modify the

seals for a pump, yo
After creating a Spa
Run a Monte C
View the cost d
View the results

Export a log of
V3.6.0.0.0 - Copyri
Spares A
To create a full Spa
Create a Spares
Create a Spare r
Create a Spare A
Create a Spare A
Run the Monte
View the results
After these initial s
V3.6.0.0.0 - Copyri
Exampl
To make this docum

the spare parts asso
For our example, w

impellers on the pu
stored in the wareh
In the Spares Analy

the recommended s
The following reco

Data tables.
Spares Analysis
Seals (Spare
Indoor Appl
Indoor Popu
Indoor Populati
Outdoor Applic
Outdoor Po
Outdoor Popula
Outdoor Popula
Bearings (Spare
Indoor Appl
Indoor Popu
Indoor Populati
Outdoor Applic
Outdoor Po
Outdoor Popula
Outdoor Popula
Impellers (Spar
All Applica
Pump Popu
Pump Populatio
Pump Populatio
Pump Populatio
When viewing this

Population record i
This example repre

creating a Spares A
Spares Analysis usi
V3.6.0.0.0 - Copyri
Spares A
The following topic

Spare Analysis
Spare Record D
Spare Applicati
Spare Applicati
V3.6.0.0.0 - Copyri
Spare A
The following table
V3.6.0.0.0 - Copyri
Spare R
The following table
V3.6.0.0.0 - Copyri
Spare A
The following table
V3.6.0.0.0 - Copyri
Spare A
The following table
V3.6.0.0.0 - Copyri
Accessin
To access the list of
On the Reliabil
Meridium APM run
V3.6.0.0.0 - Copyri
Aspects
The Select a Spares
The Spares query is

By. These prompts
The Published Ana
Any (%): Will c
Yes (Y): Will ca
No (N): Will ca
The Last Updated B
Your user name

The user name
The [All Users]
Each time you acce

button to run the Sp
Note: Although the

The default Spares
Hint: If desired, yo
V3.6.0.0.0 - Copyri
Commo
The Common Tasks
New Analysis: D
Open Analysis:
Publish Analyse
Delete Analyses
Send To: Displa

Help: Displays
V3.6.0.0.0 - Copyri
Opening
To open an existing
On the Select a
Any(%): Will c
Yes(Y): Will ca
No(N): Will cau
In the Last Upd

updated by any use
Click the Run Q
The Meridium APM
In the Analysis
The Spares Analysi
V3.6.0.0.0 - Copyri
Creatin
To create a new Sp
appears, explaining which record(s) are missing.
y a value for a field that contains a default value of 0 (zero), make sure to at least leave the default value in
s Analysis workspace. Note that a green arrow will appear next to the link that is currently selected on the
ation.
the page or plot that you are currently viewing.
y Level text boxes in the Analysis section). This link is enabled after you run a Monte Carlo simulation.
r you run a Monte Carlo simulation.
p of any plot that you are viewing, indicating that you need to re-run the Monte Carlo simulation to update
ave any changes that you made to the analysis since it was last saved.
s selected in the Spares Analysis tree. For details on configuring Associated Pages, see the URL Manager
pare Application record, Meridium APM will delete the Spare Application record, and also any associated
on record.
Simulation Options section, proceed to step 6.
es Analysis record.
the year 2010, the start date will be set to 1/1/2010 by default. If desired, you can type or select a different
example, if the start date is 1/1/2010 by default, then the end date will be set to 1/1/2020 by default. If
for U.S. currency, $, or you can type text for U.S. currency, US Dollars. Note that any data that you type in
Spares Analysis record, the Number of Iterations is set to 1000 by default. If desired, you can type a
run the Monte Carlo simulation.
after the Monte Carlo simulation is complete, where you can navigate to the location where you want to save
of equipment.
ll appear in the Applications section of the linked Spare record.
re record. For example, the name of the first Spare record that you create for a Spares Analysis will be Spare
d must be unique to the root Spares Analysis. If you type a name that already exists for another Spare record
ame for the record.
of the On-site Delivery Time text box lets you define the unit of measure for the specified period of time.
o the right of the Normal Order Time text box lets you define the unit of measure for the specified period of
e in the Normal Cost ($) text box that is greater than the value in the Expedited Cost ($) text box, the
matically to 1500.
of the Expedited Order Time text box lets you define the unit of measure for the specified period of time.
st ($) text box that is less than the value in the Normal Cost ($) text box, an error message will appear, and
mum inventory level. If you type a value in the Min Inventory Level text box that is greater than the value in
omatically to 4.
ventory level. If you type a value in the Max Inventory Level text box that is less than the value in the Min
less than or equal to the maximum inventory level. If you type a value in the Current Holding Level text box
ing Level text box reverts back to the original value.
. For example, a spare part might be used in a piece of equipment that is located in an indoor environment,
e parts. Therefore, you would want to create one Spare Application record for the spare part that is used in
e following image, you can see that the name of the Spare Application record is Spare Application 1.
order of the new Spare Application record. For example, the name of the first Spare Application record that
n 2, and so on. If desired, you can type a different name for the Spare Application record. The name of each
record that is linked to the same Spare record, the symbol appears to the left of the text box. You will not
Spare Application record. The following image shows an example of the Failure Distributions section.
the Reliability Distribution or Reliability Growth record from which you imported failure distribution
displayed in the Name cell box by default.
m which you have imported failure distribution information.
is set to Exponential by default, but you can select any of the following additional distribution types:
the following guidelines:

from which you have imported failure distribution information.
is set to Days by default, but you can select any of the following additional units of measure:
r a parameter that can be modified, all decimal places for the value will be displayed.
ter in an Exponential distribution
n Exponential distribution.
rameter 2 columns are the only parameters in a Normal distribution.
d from Reliability Growth and Reliability Distribution Analyses for the Spare Application record that is
es from which you want to import failure distribution information for the Spare Application record that is
n record that is currently selected in the Spares Analysis tree.
ed in the Spares Analysis tree.
ribution information in that row:
bution Analysis whose failure distribution information you want to use to replace the data for the selected
ribution Analyses and was used to create the values for the selected row.
on Analysis whose failure distribution information you want to use to replace the data in the selected row.
ation for the Spare Application record.
g up equipment that may be used for the repair or disassembling any equipment. Note that spare parts are not
on record.
alue in the Preparation Time text box. The unit of measure Days is selected by default. This value is stored
me Value field in the Spare Application record.
n the Repair Time text box. The Days unit of measure is selected by default. This value is stored in the
ulated automatically after you enter values in the Preparation Time and Repair Time text boxes. This value
plication record.
s the largest between the selections in the Preparation Time and Repair Time lists. If the units of measure
n Time list. This value is not stored in the Spare Application record; it appears only in the Failure
d in the Repair Labor Cost field in the Spare Application record.
ess of the length of downtime. For example, when the piece of equipment fails, there might be incomplete
his value is stored in the Fixed Lost Production Cost field in a Spare Application record.
For example, your organization might lose $100,000 per day that the piece of equipment is down. This
corresponds to the value in the Variable Lost Production Cost Rate ($) text box. The unit of measure Day is
Spares field in the Spare Application record.
ormation for the Spare Application Record. The following image shows the Preventive Maintenance section.
ance work that is done for the spare part(s) in the calculations of the Monte Carlo simulation. When you
s that you specify in the Preventive Maintenance section. This selection is stored in the Enable Preventive
his text box becomes enabled only if you selected the Enable Preventive Maintenance check box. This value
hat corresponds to the value in the Time-based Replacement Interval text box. The unit of measure Days is
omes enabled only if you selected the Enable Preventive Maintenance check box. This value is stored in the
work. This value is stored in the PM Downtime Value field in the Spare Application record. When you run
ost Production Cost Rate and # of Required Spares text boxes in the Failure Consequence section to
value in the Downtime text box. The unit of measure Days is selected by default. This value is stored in the
part can fail, requiring a replacement (or repaired to as good as new) spare part. You can define one or
orting the information from an existing Reliability Distribution or Reliability Growth Analysis.
-service for the spare part is reset to zero (0) for ALL the failure distributions defined for that Spare
re part is reset to zero (0) for ALL the failure distributions defined for that Spare Application record to
new) the spare part.
for which you want to define failure distribution information.
t to define failure distribution information.
New button.
hows what the new row looks like, by default.
cation record. The Distribution record is created in a subfamily of the Distribution family, where the
rmation for the piece of equipment that you are analyzing in a Spares Analysis, you can import that failure
, we enter failure distribution information manually.
plication record for which you want to import failure distribution information.
wth Analysis:
which you want to import failure distribution information.
Add From Analysis button.
h Analysis containing the failure distribution information that you want to import, and click the Find Now
you want to import into the Spares Analysis, and click the Open button.
n the Failure Distributions section in the details area of the Spare Application record.
ers, an error message appears, indicating that the unit of measure Quarters is not supported in Spares
Failure Distributions section in the details area of the Spare Application record.
e Distribution record is created in a subfamily of the Distribution record, where the subfamily is determined
Reliability Growth Analysis from which you imported the failure distribution information was created.
ormation
ability Distribution or Reliability Growth Analysis, if the source analysis is modified, you can refresh the
lication record on the Spares Analysis page, you can refresh the failure distribution information for that
section. The following instructions assume that you want to refresh the distributions for all Spare
Spares Analysis:
utions link.
utions in the current analysis.
d.
cord
pulation records to which it is linked will also be deleted.
lysis containing the Spare Application record that you want to delete.
Spare record containing the Spare Application record that you want to delete.
elect the row containing the Spare Application record that you want to delete.
on Population records to which it is linked are deleted.
eserved.
on Population Records
ulation age of a group of equipment that together use the data in the Spare Application record to which it is
ent with different ages using the same failure and repair data from the linked Spare Application record.
an a Calendar age.
t have an associated details area on the Spares Analysis page. All Spare Application Population records in a
f the linked Spare Application record.
rights reserved.
ation Population Record
ord for which you want to create a new Spare Application Population record.
he Add Population button.
he Populations section of the details area of the Spare Application record.
lations section.
Analysis link.
d. At this point, you can:
e Application Population record.
Inc. All rights reserved.
lication Population Records
tions section on a Spare Application Population record:
plication Population record. When you create a new Spare Application Population record, Population n
where n represents the sequential order of the new Spare Application Population record. For example, the
ecord that you create for a Spares Analysis will be Population 1, the name of the second Spare Application
tion 2, and so on.
Spare Application Population record. Note that the name of each Spare Application Population record must
Note that if you type a name that already exists for another Spares Application Population record that is
symbol appears to the left of the Population Name text box. Note that you will not be able to navigate
que name for the record.
uipment that share the same age.
ation of equipment that is associated with the data in the linked Spare Application record and Spare record. In
ion has been in use.
th the Age Value. The Age Unit list is set to Years by default. If desired, you can change the value by using
lication Population Record
ant to delete a Spare Application Population record.
Application record in the Spares Analysis tree.
d, locate the Populations section, which displays a list of all existing Spare Application Population records.
e Application Population record(s) that you want to delete.
n(s) button.
n record(s) are deleted.
ridium, Inc. All rights reserved.
lo Simulations
ions are too complex to use the typical analytical methods to answer certain questions. Monte Carlo
in these situations. Consider the following simple questions with seemingly unpredictable answers:
k-out line at the grocery store at 7 P.M. on Wednesday?
et at 9 P.M. on Friday?
ur in our neighborhood?
d on a number of factors, including:
ces in these situations.
vent.
calculated outputs.
lex questions:
t continue to operate before the next failure?
ed to handle unplanned failures but not result in a surplus of parts that are not needed?
onte Carlo simulation can be run to look at the random variables and probability for a complex piece of
ble results. A number of iterations can be specified to indicate the amount of times that you want the Monte
ger the number of iterations, the more accurate the Monte Carlo results will be.
mine the probability of rolling a seven using two dice with values one through six. There are 36 possible
ch will total seven, which means that mathematical probability of rolling a seven is six in 36, or 16.67
ame as the actual probability? Or are there other factors that might affect the mathematical probability, such
surface on which they are thrown, and the technique that is used to roll them?
ling a seven, you might physically roll the dice 100 times and record the outcome each time. Assume that
100 times, or 17 percent of the time. Although this result would represent an actual, physical result, it would
ou continued to roll the dice again and again, the result would become less and less approximate.
atical representation of this process. It allows you to simulate the act of physically rolling the dice and lets
. Each roll of the dice represents a single iteration in the overall simulation; as you increase the number of
more and more accurate. For each iteration, variable inputs are generated at random to simulate conditions
hrowing technique. The results of the simulation would provide a statistical representation of the physical
ridium, Inc. All rights reserved.
Carlo Simulation
calculations are performed on the delivery time, downtime, lost production costs, and failure and repair data
d be kept on hand at any given time. A Monte Carlo simulation performs these calculations for every spare
mes the calculations are performed is determined by the value in the Number of Iterations text box in the
Analysis workspace. After a Monte Carlo simulation has been run, you can view its results on any of the
om the last time the Monte Carlo simulation was run. Therefore, if you edit any data on any record that might
ulation, you should re-run the simulation before viewing the plots. Otherwise, the plots might contain results
A message will appear at the top of the plots indicating if the simulations need to be rerun.
e. While a simulation is running, however, you can continue working in other areas of the Meridium APM
APM Framework main window outside the Run Simulation dialog box. When you do so, the simulation will
e dialog box will be hidden behind the Meridium APM Framework window. When the simulation finishes,
utomatically.
ose button on the Run Simulation dialog box. When you do so, the simulation will continue to run in the
ox will appear on your Windows taskbar. When the simulation finishes, the dialog box will be maximized
ysis, on the Tools menu, click the Run Simulation link.
ears, where you can select or create a folder in which to store the Event Logs.
is cleared in the Simulation Options section of the Spares Analysis, the Browse For Folder dialog box will
e you want to save the Event Logs.
g box appears, displaying a progress bar that indicates the progress of the simulation.
Event Logs files in the folder that you select, a warning message will appear, indicating that any existing
verwritten.
ess bar reaches the end, the Go to Analysis and Discard and Close buttons become enabled. If you do not
esults, you can click the Discard and Close button to close the Run Simulation dialog box. These instructions
ant to view the results.
o Analysis button.
n window closes, and the links on the Navigation menu become enabled.
he link on the Navigation menu for the plot whose results you want to see.
pace for the selected plot appears on the Spares Analysis page, and the green arrow appears next to the
ing link on the Navigation menu.
- Copyright 1993-2014 Meridium, Inc. All rights reserved.
erpreting Spares Analysis Results in the Dataset

or
he following image of the exported results of our Spares Analysis example in a dataset. Note the values that
fied for the following fields within our Spares Analysis:
Simulation Start Date
Simulation End Date
Min Inventory Level
Max Inventory Level
e that since the analysis period of our Spares Analysis example is 10 years, the first 10 rows of the results
play data that corresponds to an inventory level of 0 (zero) for the Seals Spare record, meaning that no spare
s are in stock. The next 10 rows display data that corresponds to an inventory level of 1 for the Seals Spare
ord, and so on for each of the 11 inventory levels for each year in the analysis period. Note that since the
entory range specified was 0 to 10, there are 11 inventory levels because it counts 0 as an inventory level.
er each of the 11 inventory levels for each of the 10 years are indicated for the Seals Spare record in the
aset, you can scroll down to see this repeated for each of the 11 inventory levels for each of the 10 years for
Bearings Spare record. And, it will be repeated for each of the 11 inventory levels for each of the 10 years
the Impellers Spare record.
6.0.0.0 - Copyright 1993-2014 Meridium, Inc. All rights reserved.
Exporting the Analysis Results to a File
er a Monte Carlo simulation has been run, results are created from calculations for each Spare record for
ry year included in the analysis period of the Spares Analysis. These results can be saved as an MS Excel,
, or XML file.
save the results of the Monte Carlo simulation as a file:
After the Monte Carlo simulation is complete, on the Tools menu, click the Export Result link.
Export Analysis Results dialog box appears.
In the File Type list, select MS Excel, Text, or XML.

Click the Export button.
The Export to File dialog box appears.
Navigate to the location where you want to save the file, type a unique name in the File name
text box, and click the Save button.
The file is saved to the specified location.
Overview of the Event Log

When you run a Monte Carlo simulation, the failure predictions and hypothetical repair scenarios
can be saved as text files for later reference. These text files are referred to as the Event Logs.
Event Logs are optional for Spares Analyses. If you enable Event Logs for a Spares Analysis
with a large number of iterations, a large number of Event Logs will be created, and the
simulation will take a long time to complete. Therefore, when you enable Event Logs for a
Spares Analysis, we recommend lowering the number of iterations so that only a few Event Logs
are created at a time. If you do not enable Event Logs for a Spares Analysis, you can continue to
run the simulation with a high number of iterations.
For each holding level for every Spare in each iteration in the Spares Analysis, one Event Log
file will be created that records every event that happens in that iteration. Each file is named
<Spare Name>-<Current Holding Level>-<Iteration Number>.txt where:
<Spare Name> is the name of the Spare in the Spares Analysis.
<Current Holding Level> is the number of spare parts that you are storing.
<Iteration number> is the number of the iteration that is detailed in the file.
Each Event Log displays hypothetical scenarios that you can expect to occur based on the
information included in the analysis, including but not limited to:
The analysis period.
The spare parts inventory range.
The number of pieces of equipment in the analysis population and the age of each of those
pieces of equipment.
The failure data for each piece of equipment in the population, such as MTBF.
The correction time for each piece of equipment in the population.
The data associated with ordering and receiving spare parts.
For each piece of equipment in the analysis population, the Event Log includes a predication
about when you can expect:
The piece of equipment to operate at normal capacity.
The piece of equipment to fail.
The preparation for the repair to begin.
The actual repairs to begin.
The spare part to be ordered.
The spare part to be received.
The spare part to be used.
The maintenance work to begin.
The maintenance work to be completed.
The repairs to be completed.
To understand the Event Logs, you will need to understand how the scenarios are displayed in the
text file.
Hint: Although the Event Logs are saved as text files, you may want to open them in Microsoft
Excel so that they are easier to read and interpret.
Creating and Saving the Event Log

The following instructions provide details on enabling the creation of Event Logs and saving
them to the location of your choice when you run the simulation.
To create the Event Log:
Open the desired Spares Analysis, and navigate to the Spares Analysis record.
In the Simulation Options section in the Spares Analysis record, select the Enable Event Log
check box.
If the Number of Iterations text box has a value greater than one, when you select the
Enable Event Log check box, a message will appear stating that due to the amount of data
that will be logged, the number of iterations will be changed to one. If you click OK, the
Number of Iterations text box will be populated automatically with the value 1. If you
click Cancel, the value in the Number of Iterations text box will stay the same and the
Enable Event Log check box remains selected, but if there is too much data the
simulation may not complete.
Run the Monte Carlo simulation.
The Browse for Folder dialog box appears.
Navigate to the location where you want to save the Event Log files,
and click OK.
An Event Log is created for each holding level for every Spare for each
iteration and is saved to the location that you specified.
Specifying the Number of

Iterations
An Event Log is created for each holding level for every Spare for each
iteration in a Spares Analysis. If you enable Event Logs for a Spares
Analysis with a large number of iterations, a large number of Event Logs
will be created, and the simulation will take longer to complete. When you
enable Event Logs, you should change the number of iterations to a small
number (i.e., one) so a small number of Event Log files will be created and
the simulation will run in the shortest amount of time. The following
instructions assume that the Enable Event Log check box is already
selected.
To specify the number of iterations for a simulation with Event Logs:
In the Simulation Options section in the Spares Analysis record,

in the Number of Iterations text box, type the number of iterations
you want the simulation to run for the Spares Analysis.
If you change the value in the Number of Iterations text box to
a number greater than 1, a message will appear stating that due to
the amount of data that will be logged, the number of iterations
will be changed to one. If you click OK, the Number of Iterations
text box will be populated automatically with the value 1. If you
click Cancel, the value in the Number of Iterations text box will
stay the same and the Enable Event Log check box remains
selected, but if there is too much data the simulation may not
complete.
-orIf you change the value in the Number of Iterations text box to 1,
when you run the simulation, one Event Log will be created and
the simulation will complete in the shortest amount of time
possible.
V3.6.0.0.0 - Copyright 1993-2014 Meridium, Inc. All rights

reserved.
Aspects of the Event Log

Consider the following images from our Spares Analysis example.
Note that the following images of the Event Log have been opened
in Microsoft Excel and contain only a piece of the whole log.
The Event Log is divided into numerous groups and columns,

which will be highlighted in red in the later examples to make the
event log easier to explain. Each group contains a set of values for
each unique combination of:
A spare part included in the Spares Analysis. For example, if an
analysis contains three Spare records, then each group within the
Event Log will contain values for only one of those Spare records
(e.g., Spare record 1).
An inventory level within the analysis inventory range
(determined by the values in the Min Inventory Level and Max
Inventory Level text boxes in the Spare section) for each spare
part. For example, if the inventory range is from 0 to 3, each group
within the Event Log will contain values for only one of those
inventory levels (e.g., 0 spare parts).
An iteration number less than or equal to the value specified in
the Number of Iterations text box in the Simulation Options
section. For example, if the Number of Iterations is 5, each group
in the Event Log will contain a set of values that resulted from only
one iteration. The Event Log as a whole represents all iterations
included in the analysis.
If an analysis is based on only one spare part, one inventory level,
and one iteration number, then the Event Log will contain only one
group of values. If an analysis is based on more than one spare
part, inventory level, or iteration number, then the Event Log will
contain more than one group.
In the following example, the first row of a group indicates that the
values below the heading corresponds to the Seals spare part, an
inventory level of 0 (zero), and an iteration of 0 (zero).
After the information for this scenario appears, another group will
appear, corresponding to the Seals spare part, an inventory level of
0 (zero), and an iteration of 1, and so on until values associated
with all spare parts, inventory levels, and iteration numbers appear.
Note: There is an additional row after the last event with the value
None in the Event column, and the number of days associated with
that event is always past the Simulation End Date. The simulation
stops at the first event after the Simulation End Date, and this
additional event indicates when the simulation actually stopped but
is not included in the Monte Carlo simulation results.
Additionally, each group in the Event Log contains the following
columns of data:
Time
Application
Event
Spares in Stock
Spares in Order

reserved.
Time Column of the Event

Log
The value in the Time column indicates the number of days that
have passed since the piece of equipment began operating. You can
think of the Time value as the analysis period. For example, if the
Simulation Start Date is 1/1/2008 and the Simulation End Date is
1/1/2018, then the analysis period, or Time, would be 10 years, or
3,650 days.
As you proceed down the Time column, the value will begin to
increase. Where the value in the Time column exists in the same
row as an event, you can infer that the event will occur n number
of days after the piece of equipment began operating, where n is
the value in the Time cell.
For example, in the following image, you can see that a failure will
occur approximately 175 days after the piece of equipment begins
operating, as indicated by the value 174.770689.

reserved.
Application Column of the

Event Log
The text in the Application column indicates the Spares
Application associated with the piece of equipment that failed. For
example, in the following image, Outdoor Application - Pump
Population 4 - 1 appears in the Application column for the first
failure in the first group of scenarios.
The first part of the example value, Outdoor Application, is the

name of the Spare Application record that is associated with the
failure that occurred (specified in the Name text box in the
Application section).
The second part of the example value, Pump Population 4 - 1,
represents the piece of equipment that failed that exists within the
population that is associated with the Spare Application. Pump
Population 4 is the name of the Spare Application Population
record (specified in the Population cell in the Populations section),
and 1 is the actual piece of equipment that failed. Note that the
pieces of equipment are numbered beginning with zero (e.g.,
0,1,2,3). For example, the value for the second piece of equipment
will be 1.
For example, since our Spares Analysis example contains the Spare
Application Population record Pump Population 4 with a
Population Size of 2 (specified in the Population Size cell in the
Populations section), two pieces of equipment exist in that
population. So, when a failure occurs on the first piece of
equipment in Pump Population 4, then the value in the Application
column of the Event Log will be Outdoor Application - Population
4 - 0, where 0 represents the first piece of equipment.

reserved.
Event Column of the Event

Log
The text in the Event column indicates the type of event that will
occur. The following list explains the event names that can appear
within an Event Log:
None: Indicates that the piece of equipment is operating at
normal capacity. Note that when this value appear in the Event
column, it could indicate any of the following options:
The simulation begins.
The simulation ends.
A spare part is ordered.
An order for a spare part is received.
Fail: Indicates that the piece of equipment fails.
BeginUnplannedCorrection: Indicates that the
preparation work to repair the failed piece of equipment
begins.
ConsumeUnplannedCorrectionSpare: Indicates that the
repair work to repair the failed piece of equipment begins.
EndUnplannedCorrection: Indicates that the
preparation work and repair work is completed, and the
piece of equipment is operating normally again.
BeginPreventiveMaintainance: Indicates that the
maintenance work begins.
ConsumePreventiveMaintainanceSpare: Indicates that
the maintenance work is completed.
Consider the following image.
In this example:
The piece of equipment is operating at normal capacity
until almost the 175th day, at which it fails.
The moment that the piece of equipment fails,
preparation to repair the failure begins, as indicated in the
Event column by the text BeginUnplannedCorrection.
A little more than an hour later, the spare part that is
indicated in the Spares in Stock column is used to repair the
failure, as indicated in the Event column by the text
ConsumeUnplannedCorrectionSpare.
About three hours later, the repair is complete, as
indicated in the Event column by the text
EndUnplannedCorrection.
V3.6.0.0.0 - Copyright 1993-2014 Meridium, Inc. All

rights reserved.
Spares in Stock Column of

the Event Log
The value in the Spares in Stock column indicates the
number of spare parts that are being stored during each type
of event within the Event Log.
In the following image, you can see that one spare seal is
being stored until the piece of equipment fails. After the
piece of equipment fails, when the repair begins, the spare
part is used for the repair, meaning that no spare seals are
being stored any longer.

rights reserved.
Spares in Order Column

of the Event Log
The value in the Spares in Order column indicates the
number of spare parts that have been ordered and that you
are waiting to receive in the storage location (i.e.,
warehouse) before beginning the necessary repairs on the
piece of equipment.
In the following image, a spare seal is not ordered until the
second failure occurs. Since no spare seals are in stock at
the time of the second failure, one is ordered to repair that
failure.

rights reserved.
Overview of the Spares

Analysis Report
The baseline Meridium APM database includes the Spares
Analysis Report, which you can use to view a summary of
the results of a Spares Analysis. When you run the Spares
Analysis report, it will appear on the Report Viewer page.
The Spares Analysis Report is built from the following
Catalog items:
The main report, SparesAnalysis, which is stored in the
Catalog folder \\Public\Meridium\Modules\Reliability
Manager\Reports.
The subreport, Spares, which is stored in the Catalog
folder \\Public\Meridium\Modules\Reliability
Manager\Reports.
The subreport, SparesApplication, which is stored in the
Manager\Reports.
The subreport, SparesChart, which is stored in the
Manager\Reports.
The supporting queries that supply data in the main
report and subreports, which are stored in the Catalog
folder \\Public\Meridium\Modules\Reliability
Manager\Reports. The following supporting queries are
available:
Spares Analysis - Applications
Spares Analysis - Charts
Spares Analysis - ChartsMain
Spares Analysis - Main
Spares Analysis - Spares

Spares Analysis - SparesMain
Throughout this documentation, we refer to the
main report, the subreports, and the supporting
queries collectively as the Spares Analysis Report.
The Spares Analysis Report contains the following
sections:
Analysis Properties
Spare Properties
Application Properties
Plots

Running the Spares

Analysis Report
Note: You cannot run a Spares Analysis report
directly from the Meridium APM Catalog. To
generate a report successfully, you must use the
Generate Report link on the Tools menu on the
Spares Analysis page.
To run the Spares Analysis Report:
On the Spares Analysis page, on the
Tools menu, click the Generate Report link.
The Spares Analysis Report appears on the
Report Viewer page.
V3.6.0.0.0 - Copyright 1993-2014

Meridium, Inc. All rights reserved.
Analysis Properties
Section
The Analysis Properties section of the
Spares Analysis Report displays information
that is stored in the Spares Analysis record.
The name of the analysis, which is stored in
the Analysis ID field of the Spares Analysis
record, is displayed in blue at the top of the
Analysis Properties section.
The following table lists each item in the

Analysis Properties section and the
corresponding Spares Analysis record field
Report Item
Record field(s)
Analysis Properties
Description
Short Description
Start Date
Analysis Start Date
End Date
Analysis End Date
Currency
Currency
Simulation Options
Iteration
Iteration Number
Random Seed
Random Seed
Events Logged
Enable Event Log
V3.6.0.0.0 - Copyright 1993-2014

Spare Properties
Section
Each Spare Analysis record can be linked to
multiple Spare records. In the Spares
Analysis report, a Spare Properties section
will appear for each Spare record that is
linked to the Spare Analysis record. The
name of the spare, which is stored in the
Spare ID field of the Spare record, is
displayed in blue at the top of each Spare
Properties section.
The following table lists each item in the

Spare Properties section and the
corresponding Spares Analysis record field
Report Item
Record field(s)
Onsite Delivery Time Valu

On-site deliver time
Normal order time
Expedited order time
Onsite Delivery Time Uni

Normal Order Time Value
Normal Order Time Unit

Expedited Order Time Val
Expedited Order Time Un
Normal cost
Normal Cost
Expedited cost
Expedited Cost
Holding Cost Rate
Holding cost rate

Inventory level range
Current holding level
Holding Cost Unit

Min Inventory Level
Max Inventory Level
Current Holding Level
V3.6.0.0.0 - Copyright 1993-2014

About the
Application
Properties Section
Spare records can be linked to multiple
Spare Application records. For each Spare
record in the Spares Analysis report, there
can be multiple Application Properties
sections. The Application Properties section
contains the following grids:
Populations
Failure Distribution
Failure Consequence
Preventative Maintenance
The name of the corresponding
Application, which is stored in the
Application ID field of each Spare
Application record, is displayed at
the beginning of each Application
Properties section.
V3.6.0.0.0 - Copyright 1993-2014

Properties Grid
The Properties grid displays
information stored in Spare
Application Population records.
There can be multiple Spare
Application Population records
linked to each Spare Application
record. For each Spare Application
Population record, one row exists in
the Populations grid.
The following table lists each item in

the Properties grid and the
corresponding Spare Application
Population record field whose data is
Report Item
Record field
Population Name
Name
Population Size
Population S
Age
Population Age
Age Time U
V3.6.0.0.0 - Copyright 1993-2014

Failure
Distribution Grid
The Failure Distribution grid
displays information that is stored in
Distribution records that are linked to
the Spare Application record. There
can be multiple Distribution records
linked to each Spare Application
record. For each Distribution record,
one row exists in the Failure
Distribution grid.

the Failure Distribution grid and the
corresponding Distribution record
field whose data is displayed in the
report. The values in the Parameter
1, Parameter 2, and Parameter 3
columns will be different depending
on whether the Distribution record is
a Exponential, Lognormal, Normal,
or Weibull distribution.
Report Item Family
Record field(s)
Notes
Name
Distribution Short Description None
Distribution
Type
Distribution Distribution Type None
Time Unit
Distribution Units
None
Exponential MTBF
Lognormal Mu
Parameter 1
Normal
Fix Mean
Weibuill
Beta
Sigma
Lognormal
Parameter 2
Normal
Fix Standard
Deviation
None
If the Distr
value is di
Weibuill
Eta
Lognormal Gamma
Parameter 3
Weibull
Gamma
If the Distr
Normal, no
V3.6.0.0.0 - Copyright 1993-2014

Failure
Consequence
Grid
The Failure Consequence grid
displays information stored in the
Spare Application record.

the Failure Consequence grid and the
corresponding Spare Application
record field whose data is displayed
in the report.
Report Item
Preparation Time
Record
Preparat
Preparat
Repair T
Repair Time
Repair T
Labor Cost
Repair L
Fixed Lost Production Cost
Fixed L
Variable
Variable Lost Production Cost Rate

# of Required Spaces
Variable
Require
V3.6.0.0.0 - Copyright 1993-2014

Preventative
Maintenance
Grid
The Preventative Maintenance grid
displays information stored in the
Spare Application record.
the Preventative Maintenance grid
and the corresponding Spare
Application record field whose data
is displayed in the report.
Report Item
Time-based Replacement Interval
Labor Cost
Downtime
R
P
P
P
V3.6.0.0.0 - Copyright 1993-2014

Plots Section
If you have run a Monte Carlo
simulation, the Spares Analysis plots
will appear in the Spares Analysis
report with the results from the last
simulation that was run. The
following image displays an example
of the Spares Level Plot graph.
V3.6.0.0.0 - Copyright 1993-2014

Error Symbol
in Spares
Analyses
Rather than displaying a pop-up error
message, to the left of any text box
where an error occurred, the
symbol appears to the left of the text
box where the error occurred in the
following circumstances:
You try to type a name for
a Spare, Spare Application, or
Spare Application Population
record that is not unique to
the root record.
You delete a value from a
required text box. If you do
not want to type a value in a

text box, you must at least
leave the default value of 0
(zero) in the text box.
You type an invalid value
in any field. For example, if
you type abc in the Number
of Iterations text box, the
symbol will appear.
You can then pause on the
symbol to display a detailed
error message.
For example, if you type the
name of an existing Spares
Application record in the
Name text box of a new
Spares Application record
that is linked to the same
Spares record, then you will
see this:
If you pause on the

symbol, then the following
error message will appear:
Invalid value.
The error message displays
the error that occurred on that
particular text box, and you
will not be able to navigate
out of that text box until you
have specified a unique name
for the record.
1993-2014 Meridium, Inc.
Interpreting
the Spares
Analysis
Example
After you have created a
Spares Analysis and run a
Monte Carlo simulation, you
can interpret the results to
determine if the current
storing level of spare parts is
appropriate. Consider the
completed Spares Analysis
from our example.
Currently, one spare seal, one
spare bearing, and no spare
impellers are stored in the
warehouse. After completing
a Spares Analysis, we can
view the results of the Monte
Carlo simulation in the
following Spares Analysis
plots for each spare part to
determine if any changes
need to be made to the
current holding level of seals,
bearings, or impellers to
avoid excessive costs and
downtime:
Spare Level Plot
Downtime Plot
Spare Usage Plot
Sensitivity Plot
Optimal Holding
Plot
V3.6.0.0.0 Copyright 19932014 Meridium, Inc.

Interpre
ting the
Spare
Level
Plots
The following Spare
Level Plots display
the optimal level of
each spare part
included in the Spares
Analysis example and
the cost difference
between what we are
currently storing and
what is recommended
that we store. The
Spare Level Plot
displays the cost of
each spare level
within the inventory
range (determined by
the values in the Min
Inventory Level and
Max Inventory Level
text boxes in the
Spare section) for the
analysis period
(determined by the
values in the
Simulation Start Date
and Simulation End
Date boxes in the
Analysis section).
Seals
By comparing the
current holding level
of one seal and the
optimal level of four
spare seals, we can
determine how much
money our
organization is losing
every 10 years by not
storing more spare
seals. The benefit of
storing more spare
seals is calculated
using the following
equation:
Benefit = Current
Level Optimal
Level
Consider the
following values from
our example:
Current Level
= 2,250,944
Optimal Level =
1,233,955
Given these values:
Benefit = 2,250,944
1,233,955
Benefit = 1,106,989
Bearings
By comparing the
of one bearing and the
optimal level of three
spare bearings, we can
determine how much
money our
every ten years by not
storing more spare

bearings. The benefit
of storing more
bearings is calculated
using the following
equation:
Benefit = Current
Level Optimal
Level
Consider the
our example:
Current Level
= 1,831,910
Optimal Level =
821,440
Given these values:
Benefit = 1,831,910
821,440
Benefit = 1,010,470
Impellers
By comparing the
of no impellers and
the optimal level of
two spare impellers,
we can determine how
much money our
every ten years by not
storing more spare

impellers. The benefit
of storing more
impellers is calculated
using the following
equation:
Benefit = Current
Level Optimal
Level
Consider the
our example:
Current Level
= 5,513,206
Optimal Level =
591,089
Given these values:
Benefit = 5,513,206
591,089
Benefit = 4,922,117

Interpre
ting the
Downtime
Plots
The following
Downtime Plots
display the specific

downtime associated
with each spare part
included in the Spares
Analysis example:
Seals
In this image, we can

determine that the
downtime associated
with our current
holding level of one
spare seal has a total
of about 22 days. If
we store the optimal
spare level (specified
in the Spare Level
Plot) of four seals, we
can determine that
there will be a total of
only about 12 days of
downtime.
Bearings

determine that the
downtime associated
with our current
holding level of one
spare bearing has a
total of about 18 days.
If we store the optimal
spare level (specified
in the Spare Level

Plot) of four bearings,
we can determine that
there will be a total of
only about eight days
of downtime.
Impellers
In this image,
we can
determine that
the downtime
associated with
our current
holding level of
0 (zero) spare
impellers has a
total of 72 days.
If we store the
optimal spare
level (specified
in the Spare
Level Plot) of
three impellers,
we can
determine that
there will be a
total of only
about eight days
of downtime.
Based on the results
for the seals, bearings,
and impellers in the
Downtime Plots
shown above, we can
use the following
equation to determine
the optimal amount of
downtime:
Consider the
our example:
Total Seals
Downtime (current
holding level) = 22
days
Total Bearings
Downtime (current
holding level) = 18
days
Total Impellers
Downtime (current
holding level) - 72
days
Given these values:
Current Holding
Level Downtime = 22
+ 18 + 72
Current Holding
Level Downtime - 112
days
Consider the
our example:
Total Seals
Downtime (optimal
holding level) = 12
days
Total Bearings
Downtime (optimal
holding level) = 8
days
Total Impellers
Downtime (optimal
holding level) = 8
days
Given these values:
Optimal Holding
Level Downtime = 12
+8+8
Optimal Holding
Level Downtime = 28
days
Consider the
our example:
Current Holding
Level Downtime =
112 days
Optimal Holding
Level Downtime = 28
days
Given these values:
Overall Downtime
(optimal) = 112 - 28
Overall Downtime
(optimal) = 84 days

Interpre
ting the
Spare
Usage
Plots
The following Spare

Usage Plots display
the annual spare usage
for each year within
the analysis period,
assuming that we are
storing the optimal
level of spare parts.
Seals
The Spare Usage Plot

shows the number of
spare parts that will be
used for each year
within the analysis
period. Using the
preceding image, if
we add the spare
usage for each year,

a total of about 24
spare seals will be
used during the entire
analysis period.
Bearings

shows the number of
used for each year
within the analysis
period. Using the
preceding image, if
we add the spare
a total of about 24
spare seals will be
analysis period.
Impellers

shows the number of
used for each year
within the analysis
period. Using the
preceding image, if
we add the spare

a total of about 21
spare seals will be
analysis period.
Spare Usage Plots
shown above, we can
use the following
equation to how many
spares we will use
during the 10-year
analysis period if we
store the optimal level
of each spare part:
Total Spares Used =
Spare Seals + Spare
Bearings + Spare
Impellers
Consider the
our example:
Spare Seals = 24
Spare Bearings =
24
Spare Impellers =
21
Given these values:
Total Spares Used =
24 + 24 + 21
Total Spares Used =
69 spare parts

Interpre
ting the
Sensitivity
Plots
The following
Sensitivity Plots
display the cost
associated with
holding the optimal
number of spare parts,
the cost of holding
one less spare part
than the optimal
number, and the cost
of holding one more
spare part than the
optimal number
during each year
within the analysis
period.
Seals

determine that there is
a minimal cost
difference between
storing the optimal
level of four spare
seals (specified in the
Spare Level Plot) and
either five spare seals
or only three spare

seals within the 10year analysis period.
Bearings

a minimal cost
difference between
storing the optimal
level of four spare
bearings (specified in
the Spare Level Plot)
and five spare
bearings or three
spare bearings within
the 10-year analysis
period.
Impellers

a minimal cost
difference between
storing the optimal
level of three spare
impellers (specified in
the Spare Level Plot)
and either four spare
impellers and a
slightly greater cost
difference with
storing only two spare
impellers.
Additionally, we can
determine that in
2008, there is a
greater cost to hold
spare impellers.
Sensitivity Plots
shown above, we can
estimate that, if
desired, we can store
one less or one more
of each spare part
with only a minimal
cost effect.

Interpre
ting the
Optimal
Holding
Plots
The following
Optimal Holding Plots
display the best
possible spare level
for each year within

the analysis period.
Seals
The optimal spare

level of four seals was
shown in the Spare
Level Plot. From the
Optimal Holding Plot

although the most
conservative optimal
holding level for the
whole period is four,
we can store three
seals until 2012.
Bearings
The optimal spare

shown in the Spare
although the most
we can store three
seals until 2012.
Impellers
The optimal spare

shown in the Spare
although the most

we can store three
seals until 2011.
Optimal Holding Plots
shown above, we can
determine that the
most conservative
optimal holding level
for the whole analysis
period is four spares.
However, around
2011 it is important to
refer back to the
graphs to determine
the optimal level for
that year.

About
the Spares
Analysis
Plots
While viewing the
Spares Analysis page,
you can access any of
the following plots
from the links on the
Navigation menu:
Spare
Level Plot
Downtime
Plot
Spare
Usage Plot
Sensitivity
Plot
Optimal
Holding Plot
When you run
the Monte
Carlo
simulation for
a Spares
Analysis, each
of the plots
will be
generated for
each Spare
record in the
analysis. If
more than one
Spare record
exists in the
Spares
Analysis, each
plot will be
generated
multiple times,
according to
the number of
Spare records
in the analysis.
When you are
viewing any
one plot type
(e.g.,
Downtime
Plot), the plot
for each Spare
record will be
displayed on a
separate tab.
Consider our
Spares
Analysis
example that
contains three
Spare records
that represent
three spare
parts: Seals,
Bearings, and
Impellers.
When you
click the Spare
Level Plot
link, four tabs
will appear,
one for each
Spare record
and one for all
Spare records,
as shown in
the following
image.
Each plot
displays a
standard graph
toolbar by
default, where
some standard
options are
available. The
annotation
toolbar for a
Spares
Analysis
allows you to
customize the
plot with
features such
as shapes and
text boxes.
Note that the
annotation
toolbar does
not appear by
default. To
display the
annotation
toolbar, rightclick the plot,
point to the
Toolbars
option, and
click
Annotation
Toolbar.
The green
arrow in the
Navigation
menu appears
next to the plot
that you are
currently
viewing. To
return to the
Spares
Analysis
workspace
from a plot,
you can click
the Analysis
Definition link
on the
Navigation
menu at any
time.
1993-2014
Meridium, Inc.
All rights
reserved.
Spar
e Level
Plot
The Spare
Level Plot is a
bar graph that
displays the
cost associated
with each
possible spare
level included
in the range
between the
Min Inventory
Level and Max
Inventory
Level values,
which were
specified in
the Spares
section of the
appropriate
Spare record.
For this image,

the Min
Inventory
Level is 0
(zero) and the
Max Inventory
Level is 10.
The x-axis
displays the
number of
spare levels,
and the y-axis
displays the
cost associated
with each
spare level.
Additionally,
the current
holding level,
the optimal
spares level,
and the
potential
savings
amounts are
displayed
above the
Spares Level
Plot.
By default,
each bar in the
Spares Level
Plot is divided
into the
following cost
categories,
which are
shaded with
different
colors that are
represented in
the legend to
the right of the
plot:
Wareh
ousing
Cost:
The
cost of
storing
the
spare
parts
betwee
n
failures
.
Labor
Cost:
The
total
cost of
labor
associa
ted
with
every
spare
level.
Lost
Produc
tion
Cost
(StockOut):
The
total
lost
product
ion
cost
accrue
d as a
result
of
waiting
for the
spare
to
arrive
when
one
must
be
ordered
.
Lost
Produc
tion
Cost
(Corre
ctive):
The
total
lost
product
ion
cost
accrue
d as a
result
of the
downti
me due
to
prepara
tion
and
repair
after a
failure.
Lost
Produc
tion
Cost
(PM):
The
total
cost of
lost
product
ion
cost
accrue
d as a
result
of the
prevent
ive
mainte
nance
activiti
es.
Note
that if
the
Enable
Preven
tive
Mainte
nance
check
box is
selecte
d in the
Preven
tive
Mainte
nance
section
, values
from
the
Preven
tive
Mainte
nance
section
will be
include
d in
this
cost
categor
y.

Norma
l Order
Cost:
The
total
cost of
all
normal
orders
placed
for the
spare
parts.
Expedi
ted
Order
Cost:
The
total
cost of
all
rushed
orders
placed
for the
spare
parts.
Hint: If
you
select
the
Show
Total
Only
check
box in
the
upperright
corner
of the
plot,
you
can
view
the
total
costs
associa
ted
with
each
spare
level.
In
additio
n to
providi
ng a
Spare
Level
Plot for
each
Spare
record
in the
analysi
s,
Meridi
um
APM
also
display
s the
All
Spares
tab,
which
compar
es all
Spare
records
accordi
ng to
the
cost
associa
ted
with
each
possibl
e spare
level.
By
looking
at the
All
Spares
tab,
you
can
estimat
e how
much
money
your
compa
ny
might
lose by
not
storing
the
optimal
level of
spare
parts.
The
followi
ng
image
shows
an
exampl
e of the
Spare
Level
Plot for
All
Spares.
V3.6.0.
0.0 Copyri
ght
19932014
Meridi
um,
Inc. All
rights
reserve
d.
D
ow
nti
me
Plo
t
The
Downti
me
Plot is
a bar
graph
that
display
s the
specifi
c
downti
me
during
which
the
piece
of
equipm
ent is
not
operati
ng
during
the
analysi
s
period.
The
Downti
me
Plot
display
s the
specifi
c
downti
me
associa
ted
with
each
spare
level in
the
range
indicat
ed in
the
Spares
section
of the
approp
riate
Spare
record.
This
image
is
based
on a
Min
Invento
ry
Level
of 0
(zero)
and a
Max
Invento
ry
Level
of 10.
The xaxis
display
s the
number
of
spare
levels,
and the
y-axis
display
s the
downti
me in
days
for
each
spare
level.
By
default,
each
bar in
the
Downti
me
Plot is
divided
into the
followi
ng
downti
me
categor
ies,
which
are
shaded
with
differe
nt
colors
that are
represe
nted in
the
legend
to the
right of
the
plot:
P
M
D
o
w
n
t
i
m
e
:
T
h
e
d
o
w
n
t
i
m
e
t
h
a
t
r
e
s
u
l
t
s
f
r
o
m
p
e
r
f
o
r
m
i
n
g
p
r
e
v
e
n
t
i
v
e
m
a
i
n
t
e
n
a
n
c
e
.
P
M
D
o
w
n
t
i
m
e
i
s
c
a
l
c
u
l
a
t
e
d
o
n
l
y
i
f
t
h
e
E
n
a
b
l
e
P
r
e
v
e
n
t
i
v
e
M
a
i
n
t
e
n
a
n
c
e
c
h
e
c
k
b
o
x
i
s
s
e
l
e
c
t
e
d
i
n
t
h
e
P
r
e
v
e
n
t
i
v
e
M
a
i
n
t
e
n
a
n
c
e
s
e
c
t
i
o
n
.
I
f
t
h
e
E
n
a
b
l
e
P
r
e
v
e
n
t
i
v
e
M
a
i
n
t
e
n
a
n
c
e
c
h
e
c
k
b
o
x
i
s
n
o
t
s
e
l
e
c
t
e
d
,
P
M
D
o
w
n
t
i
m
e
w
i
l
l
a
l
w
a
y
s
b
e
z
e
r
o
.

C
o
r
r
e
c
t
i
v
e
D
o
w
n
t
i
m
e
:
T
h
e
s
u
m
o
f
t
h
e
t
i
m
e
s
p
e
n
t
p
r
e
p
a
r
i
n
g
f
o
r
t
h
e
r
e
p
a
i
r
o
f
t
h
e
p
i
e
c
e
o
f
e
q
u
i
p
m
e
n
t
a
n
d
a
c
t
u
a
l
l
y
r
e
p
a
i
r
i
n
g
t
h
e
p
i
e
c
e
o
f
e
q
u
i
p
m
e
n
t
(
s
p
e
c
i
f
i
e
d
i
n
t
h
e
P
r
e
p
a
r
a
t
i
o
n
T
i
m
e
,
R
e
p
a
i
r
T
i
m
e
,
a
n
d
T
o
t
a
l
C
o
r
r
e
c
t
i
o
n
T
i
m
e
c
e
l
l
s
i
n
t
h
e
F
a
i
l
u
r
e
C
o
n
s
e
q
u
e
n
c
e
s
e
c
t
i
o
n
)
.
S
t
o
c
k
O
u
t
D
o
w
n
t
i
m
e
:
T
h
e
t
i
m
e
p
e
r
i
o
d
d
u
r
i
n
g
w
h
i
c
h
t
h
e
r
e
w
a
s
n
o
s
p
a
r
e
p
a
r
t
a
v
a
i
l
a
b
l
e
f
o
r
t
h
e
n
e
c
e
s
s
a
r
y
r
e
p
a
i
r
.
F
o
r
e
x
a
m
p
l
e
,
i
f
y
o
u
d
o
n
o
t
h
a
v
e
a
n
y
s
p
a
r
e
p
a
r
t
s
s
t
o
r
e
d
w
h
e
n
a
p
i
e
c
e
o
f
e
q
u
i
p
m
e
n
t
f
a
i
l
s
,
y
o
u
w
i
l
l
n
e
e
d
t
o
o
r
d
e
r
a
s
p
a
r
e
p
a
r
t
.
I
f
t
h
e
s
u
m
o
f
t
h
e
N
o
r
m
a
l
O
r
d
e
r
T
i
m
e
a
n
d
t
h
e
O
n
s
i
t
e
D
e
l
i
v
e
r
y
T
i
m
e
(
b
o
t
h
s
p
e
c
i
f
i
e
d
i
n
t
h
e
S
p
a
r
e
s
e
c
t
i
o
n
)
t
a
k
e
s
l
o
n
g
e
r
t
h
a
n
t
h
e
P
r
e
p
a
r
a
t
i
o
n
T
i
m
e
(
s
p
e
c
i
f
i
e
d
i
n
t
h
e
F
a
i
l
u
r
e
C
o
n
s
e
q
u
e
n
c
e
s
e
c
t
i
o
n
)
,
t
h
e
n
t
h
e
r
e
w
i
l
l
b
e
a
p
e
r
i
o
d
o
f
s
t
o
c
k
o
u
t
d
o
w
n
t
i
m
e
w
h
i
l
e
y
o
u
w
a
i
t
f
o
r
t
h
e
s
p
a
r
e
p
a
r
t
(
s
)
t
o
a
r
r
i
v
e
a
t
t
h
e
r
e
p
a
i
r
s
i
t
e
.
H
i
n
t
:
I
f
y
o
u
s
e
l
e
c
t
t
h
e
S
h
o
w
T
o
t
a
l
O
n
l
y
c
h
e
c
k
b
o
x
i
n
t
h
e
u
p
p
e
r
r
i
g
h
t
c
o
r
n
e
r
o
f
t
h
e
p
l
o
t
,
y
o
u
c
a
n
v
i
e
w
t
h
e
t
o
t
a
l
d
o
w
n
t
i
m
e
a
s
s
o
c
i
a
t
e
d
w
i
t
h
e
a
c
h
s
p
a
r
e
l
e
v
e
l
.
I
n
a
d
d
i
t
i
o
n
t
o
p
r
o
v
i
d
i
n
g
a
D
o
w
n
t
i
m
e
P
l
o
t
f
o
r
e
a
c
h
S
p
a
r
e
r
e
c
o
r
d
i
n
t
h
e
a
n
a
l
y
s
i
s
,
M
e
r
i
d
i
u
m
A
P
M
a
l
s
o
d
i
s
p
l
a
y
s
t
h
e
A
l
l
S
p
a
r
e
s
t
a
b
,
w
h
i
c
h
c
o
m
p
a
r
e
s
a
l
l
S
p
a
r
e
r
e
c
o
r
d
s
a
c
c
o
r
d
i
n
g
t
o
t
h
e
a
m
o
u
n
t
o
f
d
o
w
n
t
i
m
e
a
s
s
o
c
i
a
t
e
d
w
i
t
h
e
a
c
h
p
o
s
s
i
b
l
e
s
p
a
r
e
l
e
v
e
l
.
B
y
l
o
o
k
i
n
g
a
t
t
h
e
A
l
l
S
p
a
r
e
s
t
a
b
,
y
o
u
c
a
n
e
s
t
i
m
a
t
e
h
o
w
m
a
n
y
d
a
y
s
o
f
d
o
w
n
t
i
m
e
y
o
u
m
i
g
h
t
h
a
v
e
p
e
r
p
o
s
s
i
b
l
e
s
p
a
r
e
l
e
v
e
l
f
o
r
e
a
c
h
p
i
e
c
e
o
f
e
q
u
i
p
m
e
n
t
.
T
h
e
f
o
l
l
o
w
i
n
g
i
m
a
g
e
s
h
o
w
s
a
n
e
x
a
m
p
l
e
o
f
t
h
e
D
o
w
n
t
i
m
e
P
l
o
t
f
o
r
A
l
l
S
p
a
r
e
s
.
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
.
S
p
a
r
e
U
s
a
g
e
P
l
o
t
T
h
e
S
p
a
r
e
U
s
a
g
e
P
l
o
t
i
s
a
b
a
r
g
r
a
p
h
t
h
a
t
d
i
s
p
l
a
y
s
t
h
e
s
p
a
r
e
u
s
a
g
e
f
o
r
e
a
c
h
y
e
a
r
i
n
t
h
e
a
n
a
l
y
s
i
s
p
e
r
i
o
d
,
a
s
s
u
m
i
n
g
t
h
a
t
y
o
u
s
t
o
r
e
t
h
e
o
p
t
i
m
a
l
l
e
v
e
l
o
f
s
p
a
r
e
p
a
r
t
s
.
I
n
t
h
i
s
i
m
a
g
e
,
t
h
e
S
i
m
u
l
a
t
i
o
n
S
t
a
r
t
D
a
t
e
i
s
1
/
1
/
2
0
0
8
,
a
n
d
t
h
e
S
i
m
u
l
a
t
i
o
n
E
n
d
D
a
t
e
i
s
1
/
1
/
2
0
1
8
.
T
h
e
x
a
x
i
s
d
i
s
p
l
a
y
s
t
h
e
y
e
a
r
s
f
o
r
t
h
e
a
n
a
l
y
s
i
s
p
e
r
i
o
d
,
a
n
d
t
h
e
y
a
x
i
s
d
i
s
p
l
a
y
s
t
h
e
n
u
m
b
e
r
o
f
s
p
a
r
e
s
u
s
e
d
i
n
t
h
a
t
y
e
a
r
w
h
e
n
y
o
u
s
t
o
r
e
t
h
e
o
p
t
i
m
a
l
s
p
a
r
e
l
e
v
e
l
.
B
y
d
e
f
a
u
l
t
,
e
a
c
h
b
a
r
i
n
t
h
e
S
p
a
r
e
U
s
a
g
e
P
l
o
t
i
s
d
i
v
i
d
e
d
i
n
t
o
t
h
e
f
o
l
l
o
w
i
n
g
s
p
a
r
e
u
s
a
g
e
c
a
t
e
g
o
r
i
e
s
,
w
h
i
c
h
a
r
e
s
h
a
d
e
d
w
i
t
h
d
i
f
f
e
r
e
n
t
c
o
l
o
r
s
t
h
a
t
a
r
e
r
e
p
r
e
s
e
n
t
e
d
i
n
t
h
e
l
e
g
e
n
d
t
o
t
h
e
r
i
g
h
t
o
f
t
h
e
p
l
o
t
:
PM
Usage:
The
total
number
of
spare
parts
used
for
Prevent
ive
Mainte
nance
(specifi
ed in
the # of
Requir
ed
Spares
cell in
the
Failure
Conseq
uence
section
). Note
that if
the
Enable
d
Prevent
ive
Mainte
nance
check
box in
the
Prevent
ive
Mainte
nance
section
is not
selecte
d, PM
Usage
will not
be
include
d in
this
graph.
Correct
ive
Usage:
The
total
number
of
spare
parts
used
for
repairin
g
equipm
ent
failures
(specifi
ed in
the
Failure
Distrib
ution
section
).
Hint: If
you
select
the
Show
Total
Only
check
box in
the
upperright
corner
of the
plot,
you
can
view
the
total
usage
associa
ted
with
each
year in
the
analysi
s
period.
In
additio
n to
providi
ng a
Spare
Usage
Plot for
each
Spare
record
in the
Analysi
s,
Meridi
um
APM
display
s the
All
Spares
tab,
which
compar
es all
Spare
records
accordi
ng to
the
spare
usage
for
each
year.
Assumi
ng that
you are
storing
the
optimal
level of
each
spare
part, by
looking
at the
Spare
Usage
Plot for
All
Spares,
you
can
estimat
e how
many
of each
spare
part
you
might
need
each
year.
V3.6.0.
0.0 Copyri
ght
19932014
Meridi
um,
Inc. All
rights
reserve
d.
S
ens
itiv
ity
Plo
t
The
Sensiti
vity
Plot is
a line
graph
that
display
s for
each
year in
the
analysi
s
period:
The
cost
associa
ted
with
holding
the
optimal
number
of
spare
parts.
The
cost of
holding
one
less
spare
part
than
the
optimal
number
.
The
cost of
holding
one
more
spare
part
than
the
optimal
number
.
For
exampl
e, if the
optimal
level
determi
ned by
the
Monte
Carlo
simulat
ion is
three,
then
the
Sensiti
vity
Plot
will
display
the cost
associa
ted
with
holding
three
spare
parts,
two
spare
parts,
and
four
spare
parts.
In this
image,
the
Simulat
ion
Start
Date is
1/1/200
8, and
the
Simulat
ion
End
Date is
1/1/201
8. The
x-axis
display
s the
years
for the
analysi
s
period,
and the
y-axis
display
s the
costs
that
you
can
expect
to incur
in each
year.
By
default,
each
line in
the
Sensiti
vity
Plot is
divided
into the
followi
ng cost
categor
ies,
which
are
shaded
with
differe
nt
colors
that are
represe
nted in
the
legend
to the
right of
the
plot:
Total
Cost
(+):
The
total
cost
when
storing
one
spare
part
more
than
the
recom
mende
d
number
of
spare
parts.
Total
Cost
(Optim
al):
The
total
cost
when
storing
the
recom
mende
d
number
of
spare
parts.
Note
that the
Optima
l Spare
Level,
or
recom
mende
d
number
of
spare
parts, is
located
at the
top of
the
Spare
Level
Plot.
Total
Cost
(-): The
total
cost
when
storing
one
spare
part
less
than
the
recom
mende
d
number
of
spare
parts.
Note:
If the
Min
Invento
ry
Level
is 0
(zero),
the
Max
Invento
ry
Level
is 1,
and the
Optima
l Spare
Level
is 1,
then
the
Total
Cost
(+) line
will not
appear
on the
Sensiti
vity
Plot.
With
this
invento
ry
range
specifie
d on
the
Spare
record,
the
Total
Cost
(+) line
would
represe
nt the
holding
level of
two
spare
parts,
and
that
value is
not
within
the
invento
ry
range.
In
additio
n to
providi
ng a
Sensiti
vity
Plot for
each
Spare
record
in the
analysi
s,
Meridi
um
APM
display
s the
All
Spares
tab,
which
compar
es all
Spare
records
accordi
ng to
the cost
of
storing
the
optimal
amount
of the
spare
part,
one
spare
part
more
than
the
optimal
amount
, and
one
spare
part
less
than
the
optimal
amount
. By
looking
at the
All
Spares
tab,
you
can
estimat
e the
cost of
storing
the
optimal
amount
, one
more
than
the
optimal
amount
, and
one
less
than
the
optimal
amount
of each
spare
part
during
analysi
s
period.
The
followi
ng
image
shows
an
exampl
e of the
Sensiti
vity
Plot for
All
Spares.
V3.6.0.
0.0 Copyri
ght
19932014
Meridi
um,
Inc. All
rights
reserve
d.
O
pti
ma
l
Hol
din
g
Plo
t
The
optimal
spare
level is
determi
ned as
the
most
conserv
ative
value
over
the
entire
analysi
s
period.
Becaus
e
failure
data
might
change
each
year,
the
optimal
invento
ry level
might
change
for
each
year
within
the
analysi
s
period.
The
Optima
l
Holdin
g Plot
display
s the
optimal
spare
level
for the
whole
period
and for
each
individ
ual
year of
the
analysi
s
period.
Consid
er the
followi
ng
Optima
l
Holdin
g Plot
from
the
data
used in
the
Spares
Analysi
s
exampl
e.
In this
image,
the
Simulat
ion
Start
Date is
set to
1/1/200
8, and
the
Simulat
ion
End
Date is
set to
1/1/201
8 in the
Analys
is
section
of the
Spares
Analysi
s
record.
The xaxis
display
s the
years
include
d in the
analysi
s
period,
and the
y-axis
display
s the
invento
ry level
associa
ted
with
the
lowest
cost of
spares
levels
for
each
year.
By
default,
each
bar in
the
Optima
l
Holdin
g Plot
is
divided
into the
followi
ng cost
categor
ies,
which
are
shaded
with
differe
nt
colors
that are
represe
nted in
the
legend
to the
right of
the
plot:
Optimal
Spare Level
(Yearly): The
lowest cost of
spare levels
associated
with each year
included in the
analysis
period.
Optimal
Spare Level
(Whole
Period): The
recommended
number of
spare parts
associated
with the entire
analysis
period.
In addition to
providing an
Optimal
Holding Plot
for each Spare
record in the
analysis,
Meridium
APM displays
the All Spares
tab, which
compares all
Spare records
according to
the optimal
holding level
for the whole
period and for
each
individual year
during the
analysis
period. The
following
image shows
an example of
the Optimal
Holding Plot
for All Spares,
which you can
use to compare
the optimal
holding levels
for each piece
of equipment.
1993-2014
Meridium, Inc.
All rights
reserved.
What
is a
Reliabi
lity
Growt
h
Analys
is?
A Reliability
Growth
Analysis can
help you make
strategic
decisions by
indicating
whether your
data
measurements
are random or
if they follow
a trend. The
graphs
produced by a
Reliability
Growth
Analysis will
show any
timedependent
trends,
allowing you
to make
decisions
based on past
behavior and
predict how
your data will
behave in the
future.
When you
view the
results of a
Reliability
Growth
Analysis, if
you see the
data is
trending in one
direction until
a certain point
in time and
then begins
trending in
another
direction, you
can examine
what changed
at the point in
time when the
trend shifted to
determine the
impact of
those changes.
In addition, if
you make a
strategy
change and
then examine
whether the
data worsens
or begins to
improve at that
point, you can
determine the
impact of the
strategy
change. For
example, a
distinct change
in a Mean
Time Between
Failures
(MTBF) plot
can identify
the point at
which
improved
maintenance
strategies were
put into place
for a piece of
equipment.
Similarly,
when you
observe data
that is trending
at the same
rate over time
without
distinct
changes, you
can use those
trends to
predict the
data's future
behavior. For
example, if
you are
tracking the
cost associated
with running a
piece of
equipment
over a certain
period of time,
and the cost is
consistently
higher during
winter months,
you can
predict how
much more it
will cost to run
the piece of
equipment in
December than
it will in July.
Trend charts
generated by
Reliability
Growth
Analyses can
also show
outlying
events that
may have had
significant
effects on the
overall trend
of strategy
effectiveness.
For example, a
thunderstorm
that results in a
two-day power
outage at a
plant should
not reflect
poorly on a
piece of
equipment's
reliability.
Reliability
Growth
Analyses
allow you to
ignore these
types of
events.
You can
perform a
Reliability
Growth
Analysis and
examine trend
charts for one
piece of
equipment or
location a
group of
similar pieces
of equipment
or locations.
For example,
you may want
to examine
trends for one
pump that is
constantly
breaking
down, or you
may want to
examine trends
for a set of
pumps to
detect any
improvement
after you
installed a new
maintenance
strategy.
1993-2014
Meridium, Inc.
All rights
reserved.
Type
s of
Reliabi
lity
Growt
h
Analys
es
Before you can

perform a
Reliability
Growth
Analysis, you
first must
collect data, or
numeric values
representing
some
variable's
performance,
over some
period of time.
All data that
you collect
will be:
Based on
an event (e.g.,
a failure).
-or not based
on an event
(e.g., repair
cost).
Both data that
is event-based
and not eventbased will also
be:
Grouped
(i.e.,
datapoints
represent
multiple
measurements
or an amount).
-or-
Nongrouped (i.e.,
datapoints
represent a
single
measurement).
By default, the
Meridium
APM system
assumes that
your data is
not grouped.
You can
specify that
your analysis
includes
grouped data
by including
the amount of
data per
datapoint on
the Select Data
Fields screen
in the
Reliability
Growth
Analysis
Builder. Data
that is not
event-based
typically
measures an
amount (e.g.,
repair cost)
and is grouped
data.
Event-based
data can be
derived from:
Failure
Dates: specific
dates on which
failures
occurred. (e.g.,
1/3/2012)
Cumulative
Operating
Time: An
amount of time
that has passed
since the piece
of equipment
was put into
service (e.g.,
10 days).
Data that is not
event-based is
usually
derived from
cumulative
operating time.
1993-2014
Meridium, Inc.
All rights
reserved.
Abou
t Data
Used
in
Reliabi
lity
Growt
h
Analys
es
The following
table lists the
data you need
to collect in
order to
conduct a
Reliability
Growth
Analysis.
Da
Ass
Cum
Tim
Dow
Dow
Fail
1993-2014
Meridium, Inc.
All rights
reserved.
Abou
t
Reliabi
lity
Growt
h
To make this
documentation
easier to
follow and to
help explain
how
Reliability
Growth
Analyses can
be used as an
evaluation tool
in different
scenarios, we
provide some
examples that
could benefit
from a
Reliability
Growth
Analysis.
Example 1:
Demonstrates a
scenario where you
would create a
Reliability Growth
Analysis with even
based data that is
measured using fail
dates.
Example 2:
Demonstrates a
scenario where you
would create a
Reliability Growth
Analysis with even
based data that is
measured using
cumulative operatin
time.
Example 3:
Demonstrates a
scenario where you
would create a
Reliability Growth
Analysis with grou
data that is not even
based that is measu
using cumulative
operating time.
V3.6.0.0.0 - Copyri
1993-2014
Meridium, Inc. All
rights reserved.
Exampl
of an
Analysis
Using
Event
Dates
If you track events

(e.g., safety events
failures) by specific
date, then you can
create a Reliability
Growth Analysis
using event-based d
that is measured us
failure dates.
Example 1: Failure
Dates
Centrifugal Pump
1051700 was instal
at the Springfield
plant on July 20,
1998. Since its
installation, the pum
has failed several
times, and each tim
the pump fails it is
repaired immediate
without any
significant downtim
You have collected
data noting which
days the pump faile
You want to use the

following data to
perform a Reliabili
Growth Analysis to
determine the mean
time between pump
failures.
In this case, you

would use event-ba
data derived from
failure dates to
determine:
The date that th

will fail next.
How many time

pump will fail by a
date.
If the number o
increased or decrea
result of a strategy
(e.g., a new preven
maintenance schedu
was implemented a
failure on Septemb
V3.6.0.0.0 - Copyri
1993-2014 Meridiu
rights reserved.
Exampl
an Analy
Using
Cumulati
Operatin
Time
Sometimes the spec

on which a piece of
equipment or locati
may not be availabl
piece of equipment
location may not op
the same amount of
every day. In these
would be more valu
determine future fa
using cumulative o
time (COT), or the
time the piece of eq
or location has been
operation.
Example 2: Cumula
Operating Time
Haul Truck 1 was p

for a shipping firm
vehicle with 11,028
The truck now runs
routes depending o
number of shipmen
which it is assigned
the truck does not a
travel the same num
miles each day, you
the data representin
mileage points at w
truck broke down. Y
to use the following
perform a Reliabili
Analysis to determi
mean operating tim
number of miles) b
failures.
In this case, you wo

event-based data de
from cumulative op
time to determine:
The mileage po
next failure will occ
How many failu

a certain point (e.g.
have occurred after
If the number o
increased or decrea
strategy change (e.g
oil changes), which
after the failure at 7
V3.6.0.0.0 - Copyri
Meridium, Inc. All
Exampl
Analysis
Grouped
Non-Even
In Examples 1 and
represents a single
failure. In some dat
datapoint may repre
one measurement, o
data. Throughout th
this type of data is r
grouped data. To p
Growth Analyses o
when you create a d
use datapoints that
measurements or an
Datasets containing
be based on either f
cumulative operatin
For example, if you

pump for which yo
every six months an
record data you rec
failures (one datapo
multiple failures), y
Reliability Growth
event-based, group
derived from cumu
time.
In Examples 1 and
was also based on a
Examples of eventinclude equipment
failures, safety inci
equipment or locati
Sometimes, you ma
a Growth Analysis
does not measure a
(e.g., an amount). F
labels to appear thr

analysis, these data
entered as non-even
containing non-eve
based on either fail
cumulative operatin
Using a Reliability
to measure cost is t
examples of evalua
and non-event data
Example 3: A Reli
Analysis Using Co
You want to measu

equipment failures
plant in order to de
should plan a budge
the future. Individu
equipment fail at di
you measure the tot
replacement parts a
labor for the entire
months. You want t
following data to pe
Reliability Growth
the cost trends at th
In this case, you wo

event, grouped data
from cumulative op
determine:
The repair costs

by some point in th
If the repair cos

decreased as a resu
(e.g., changing the
parts), which was im
months.
V3.6.0.0.0 - Copyri
Meridium, Inc. All
Reliabil
Analysis
After you gather da

Growth Analysis, y
number of tasks to
Following this wor
complete all the tas
conduct a complete
you an overview of
Collect data. Be
Growth Analysis, y
elements you wish
Create a new R
can create a new Re
query, dataset, or m
Evaluate the re
using the features
Analysis tool.
Determine whe
using the Goodness
Predict how the

using the extrapola
Determine at w
data changed in the
V3.6.0.0.0 - Copyri
Accessin
Growth A
To display a list of
that currently exist
On the Reliabil
Reliability Growth
The Select a Growt
V3.6.0.0.0 - Copyri
rights reserved.
Aspects
Analysis
You can use the Sel

to select a Reliabili
Reliability Growth
The Select a Growt

the following items
Published Anal
Yes (Y): Wil

Reliability Growth
No (N): Will ca
Reliability Growth
Any (%): Will c

Analyses, both pub
Last Updated B
The last and

account: This value
value, the query wi
that were last updat
The last and fir

any Reliability Gro
these values, the qu
records that were la
[All Users]: Wh
all Reliability Grow
Run Query butt

populates the result
Published Analyses
Query results g
Run Query button.
displays Reliability
Analysis ID
Last Updated
Updated By
Final MTBF
Task Menus: M
functionality. The f
Common Tasks.
V3.6.0.0.0 - Copyri
reserved.
Plots M
The Plots menu on

contains the follow
MTBE Plot: Di
selected analyses.
Cumulative Plo
selected analyses.
Rate Plot: Disp

analyses.
Note: The links on

records are selected
Analysis from the L
V3.6.0.0.0 - Copyri
reserved.
Commo
The Common Tasks

List page contains t
New Analysis: D
can use to create a n
Open Analysis:
which you can use
record.
Save Analysis:
Save Analysis A
Publish Analyse
record(s). If you se
link will be labeled
records.
Delete Analyses
Reliability Growth
Send To: Displa

the current page on
on a Home Page.
Help: Displays
Analysis from the L
Guidelines: Dis
Analytics module.
V3.6.0.0.0 - Copyri
Opening
Growth A
To open an existing
On the Reliabil
link.
The Select a Growt
In the Published
In the Last Upd
Click the Run Q
The Meridium APM

displayed in the que
In the Analysis
The Reliability Gro
Note that when you

calculations that we
query or dataset and
must reload the dat
V3.6.0.0.0 - Copyri
Accessin
Builder
To access the Relia
Access one of th
Select a Growth
Reliability Grow
AMSAA Reliabi
On the Common
The Reliability Gro
V3.6.0.0.0 - Copyri
Using th
You can use the Re

manually entered o
Based on an eve
-or-
not based on an
grouped data.
In addition, event o
Failure dates. In
dates.
-or-
Cumulative ope
from cumulative op
The Reliability Gro

screens and how yo
Welcome screen
Select Data Sou
Select Data Sou
Select Data For
Select Data Fie
Provide Inform
Analysis Start T
V3.6.0.0.0 - Copyri
Creatin
Failure D
If you record event

can create a Reliabi
To create a Reliabil
Access the Reli
On the Welcom
The Select Data So
On the Select D
instructions assume
enter data option, a
The Select Data So
On the Select D
button.
The Select Data Fo
On the Select D
use throughout the
Example 1, and wil
the default value Fa
The Select Data Fie
On the Select Data

Next button.
The Provide Inf
On the Provide
In the Time Un
Hours
Days
Weeks
Months
Quarters
Years
Click the Finish
The Meridium APM
On the Commo
V3.6.0.0.0 - Copyri
Creatin
If you record event

Access the Reli
On the Welcom
The Select Data So
On the Select D
Dataset Based optio
The Select Data So
On the Select D
The Select Data Fo
On the Select D
button. These instru
Measurement Nam
The Select Data Fie
nish button, and the <Measurement> Data grid appears.
On the Select D
The Analysis Start
On the Analysis
Note: If you did no

that dates will not b
The Meridium APM
On the Commo
V3.6.0.0.0 - Copyri
Creatin
If you record data t

of data, you should
Using a Reliability
Access the Reli
On the Welcom
The Select Data So
elect the Data contains cumulative operating time option and the Data is not event count option, and enter
alues dialog box displays the value in the Location field of the current record.
the next time you access the builder.
an enter your data manually.
ysis results.
g time.
int. If the number of failures is 1, the calculation will be based on an event-terminated or time-terminated
Example 3, we entered the value Cost, so this list would be named Cost.
s based on cumulative operating time, and the value is required.
e.g., miles). This field appears only for an analysis based on cumulative operating time, and the value is
perating time only, and you will be able to extrapolate based on time only, not date.
int. If the number of failures is 1, the calculation will be based on an event-terminated or time-terminated
Example 3, we entered the value Cost, so this list would be named Cost.
ou select the Data contains dates option on the Data Format screen.
er rows will be calculated by subtracting this value.
lative operating time. The units for this text box are populated automatically with the time units that you
ur analysis is using failure dates or cumulative operating time. The following images show examples of the
ilures Data. In Example 3, we entered the value Cost, so the window is named Cost Data.
py, and paste functions to transfer data to the grid from other applications. A minimum of three failure
uming that the downtime is not accurate and that the failure dates are accurate. When you close the
s the Reliability Growth Analysis page for Example 1, an analysis that is created from event-based data that
s.
10 days. If multiple pieces of equipment or locations are included in the analysis, their operating time will be
vent-based data.
he model and lists calculated analysis values.
will be Time-Based. Likewise, if you select the Event-Based option on the Analysis Period dialog box, the
ver, the last segment will be Time-Based, but the termination type for all other segments will be Event-
alue you enter in the Measurement Name dialog box. The following image shows the Reliability Growth
played only for analyses that are not using event-based data.
he analysis. In the above image, the link is labeled Failures Plot.

dialog box for the analysis. In the above image, the link is labeled MTBF Plot.
he analysis. In the above image, the link is labeled Failures Rate Plot.
mount of time.
ou can used to view the analysis data.
d until you save the analysis.
n for the analysis. If you are viewing an existing analysis, when you click this link, the Meridium APM
nalysis, but you can later change them via the Time Units dialog box.
us the analysis on a specific period of time. Note that failures that are outside the analysis period will be
ain dates, the Analysis Period dialog box will look different.
corresponding date field is disabled automatically and displays the date on which the first event occurred.
ate will appear on the plots.
se today's date as the end date for the analysis check box is selected and disabled automatically. The
s date as the end date for this analysis check box, and then type or select the desired date and time.
d since the last event, this time is not included in the reliability model. If you want to include that time in the
n the specified analysis period.
via the Select Data Format screen in the Reliability Growth Builder. By default, the Measurement Name
pe of data that is used in the analysis.
By default, this text box contains the measurement value you entered on the Select Data Format screen in the
matically (e.g., the name of the <Measurement> Data window).
s, as appropriate.
ck a hyperlinked segment number.
s. If the Reliability Growth Analysis has been split into multiple segments, a separate set of results will be
ther or not the analysis contains event-based data. If the data is event-based, certain labels will also look
s an indicator of whether the MTBF is increasing, decreasing, or staying the same.
e is used to calculate the time to next measurement (e.g., failure, cost).
ing of the segment.
nt.
d as the time units you chose for your analysis (e.g., At 303,156.00 Miles, the MTBF is 20,757.81 Miles).
f the Reliability Growth Analysis has been split into multiple segments, a separate set of results will be
da () are different than the formulas used for non-grouped data.
ped, non-event data.
as the AMSAA Reliability Growth Model page for an event-based analysis. Instead of showing the Initial
lude dates, references to dates will be displayed as the time units you chose for your analysis (e.g., At 62
is. Most of the fields on the <Measurement> Data window correspond to values that were used to create the
eturned by the query.

stored in the dataset.
e information that you entered when you create the analysis.
ues in the <Measurement> Data window are stored in the Failures field in the Reliability Growth record.
ould not want to change the data unless there was an error in the original data source. Some values are
configured. <Measurement> will be replaced with the value that you specified in the Measurement Name
abeled Failures Data.
er will prompt you to map values from columns in the query or dataset to certain values in the Reliability
n For Downtime screens in the Reliability Growth Builder will then appear in the associated columns in the
pped to columns in the analysis dataset, those columns will appear in the <Measurement> Data window with
r to columns in the <Measurement> Data window:
ata link.
the Measurement Name text box on the Data Format window for the analysis. The following image shows
asurement> tab provides information about the event data. The Assets tab provides information about the
nd contains failure dates.
ted with the event (e.g., a Work History record). This column only appears when a query is the data source
om a query or dataset or manually entered when you create the analysis.
et or manually entered when you create the analysis and is required. If you delete a value in the Date column
ppear.
e of equipment or location was put into service until the date that it failed. If the data includes an installation
If the data does not include an installation date, this value is calculated from the first failure. <Units>
box for the analysis. Values in this column are calculated by the Meridium APM system and are read-only.
ue in the Time column for each subsequent failure date is the number of days that have passed since the
he pump was placed into service, so the Time value for that failure is 147.
or location failed until it was returned to service. This information helps determine the total operating time
time Units list on the Time Units dialog box for the analysis. In Example 1, the pump was returned to service
nually entered when you create the analysis.
contain the value 1 (one) by default, which indicates that the analysis data is not grouped, and one datapoint
ouped, and each datapoint represents more than one failure or an amount of data. This value can optionally
lysis.
ored, meaning excluded from the analysis calculations and plots. When selected, the data in the associated
ed in the analysis. You can modify this value manually.
tion of equipment or locations at the moment that a failure occurs in one of them. Values in this column are
e will be the sum of the runtime for all pieces of equipment or locations. For example, if at the time of
uld be 60 days.
t into two segments to point out a change in the data trend. Values displayed in this column are read-only.
tive operating time looks mostly the same as the Failures tab for an event-based analysis derived from
lysis using data that is event-based and derived from cumulative operating time.
operating time:
to be displayed throughout the analysis, ALL failures must have a failure date. If one or more failure dates
be shown. For instance, in Example 2, the data does not include dates on which the haul truck broke down,
ly (e.g., the next failure will occur at 324,001 miles).
passed since the piece of equipment or location was placed into service. <Units> corresponds with the value
olumn is sorted in ascending order by default. This value is mapped from a query or dataset or manually
mn are not in the same order as the values in the COT (units) column (e.g., if the Failure Date 1/1/2012 has a
e will appear, stating that sorting cumulative operating time values from smallest to largest will result in
the analysis results; only cumulative operating time will be shown.
rating time.
a population of equipment and locations at the moment that a failure occurs in one of them. Values in this
analysis has started. This may be different from the COT, which is the total runtime of the piece of
028 before the analysis starts, and fails at a mileage of 27,393. The COT is the total mileage on the truck,
93-11,028=16,365). If the piece of equipment or location is brand new (i.e., the truck has a mileage of 0), the
ociated with equipment and locations in the analysis. The grid appears mostly the same as the Failures tab
he following image displays data for Example 3, an analysis using grouped data that is not event-based and
events and uses grouped data:
n represent the amount of data (e.g., cost) recorded between that datapoint and the previous datapoint. For
ys 1 (one). For grouped data, the values can be greater than or less than 1 (one) but must be greater than 0
eate the analysis.
our analysis.
ation about each piece of equipment or location that is related to a measurement. In the following example,
ly one piece of equipment appears on the Assets tab.
associated with the piece of equipment or location. This link is displayed only when a query is the data
ed. This value is mapped from a query or dataset or manually entered when you create the analysis.
led. This column appears only for analyses based on failure dates. This value is mapped from a query or
n failed. Values in this column are calculated by the Meridium APM system and are read-only. For data that
.
rowth Analysis?
nstrate an overall picture of your data. You can view the results in graphical form, use calculated values to
our data and whether they are getting better or worse.
corded for the piece of equipment or location as a function of time. Since the log (cumulative measurement)
is plot to see how your data is trending over time.
urements are being record for pieces of equipment or locations (e.g., failures, cost) as a function of time
urement is taken every time the piece of equipment or location fails, the piece of equipment or location is
ming more reliable.
easurement is taken every time the piece of equipment or location fails, the piece of equipment or location is
coming less reliable.
(e.g., failures, cost). This plot can tell you a measurement per time unit, so that you can see per day or per
dium APM system that you can use to interpret trends within your data:
pattern or occurring at random.
method. The confidence level you select for your data helps determine whether or not the data will pass the
This value is displayed on the Reliability Growth Analysis page.
u can expect to pass before the next event will occur for the piece of equipment or location. The value is
proximate date (or time) when the next event will occur is displayed on the Reliability Growth Analysis
compare how the piece of equipment or location is behaving at the beginning of the analysis versus the end
t's or location's measurement rate has improved or gotten worse over the analysis period. These values are
overview of the formulas used by the Meridium APM system to calculate the model results.
results:
o that you can see multiple trends in the data (e.g., data before and after a strategy change).
ailures, amount of cost) that will have occurred by some point in the future.
enance and reliability activities that should be executed in the future to maintain best practices in your
ement> Plot Page
lative <Measurement> Plot graph.
mulative <Measurement> Plot graph. The following image displays the Cumulative <Measurement> Plot
Failure Dates
with data overlay, which means it uses logarithmic scales on both the horizontal and vertical axes. The
time (Cumulative Failures vs. Cumulative Operating Time), which is the total amount of time the piece of
sis.
ample 1.
ve operating time, and the y-axis shows the total number of failures. For a single piece of equipment or
e total amount of time the piece of equipment or location has been in operation. For a group of equipment or
g time multiplied by the number of pieces of equipment or locations. For example, ten pieces of equipment
e operating time. The units for the x-axis can be changed.
Model page.
color of the plot line. If the plot line is blue, it passed the GOF test. If the plot line is orange, it failed the
in the future.
eserved.
ng COT
umulative operating time contains a graph is a log-log plot with data overlay, which means it uses
used in the same way as the Cumulative Failures Plot containing failure dates, except that the x-axis is
for Example 2.
ative time to failure, and the y-axis shows the total number of failures. The cumulative time to failure
location had been in operation when a failure occurred.
ailures Plot page for an analysis based on cumulative operating time as for an analysis based on failure
r time, however, the plot displays the number of failures over the time units you specified for your analysis.
displayed at the mileage point they occurred instead of the date they occurred.
eserved.
plot with data overlay, which means it uses logarithmic scales on both the horizontal and vertical axes. When
epresents the cumulative cost as a function of the cumulative time. In Example 3, the Cumulative Cost Plot
nt or location over time.
Plot graph for Example 3, which contains grouped data that is not based on events.
e time, and the y-axis shows cumulative cost. For a single piece of equipment or location, cumulative time is
been in operation.
ailures Plot page for an analysis with grouped data that is not based on events and derived from cumulative
s derived from cumulative operating time. For grouped data, however, each datapoint will represent an
int. In addition, because the data is not event-based, the datapoints represent your custom measurement
xample 3, the first datapoint represents a cost of 1,000 dollars instead of 1,000 failures.
eserved.
ement> Plot Page
Plot link.
w of the MTB<Measurement> Trend graph.
ph appears in the Reliability Growth Model section only if the analysis is based on event count data.
d graph appears.
the MTBF Trend graph. The following image displays the MTB<Measurement> Plot page for Example 1:
rights reserved.
ng Failure Dates
ween Failures (MTBF) changes over time. MTBF is calculated from the distribution of the failures over time.
in the analysis.
Example 1.
r time, and the y-axis displays the MTBF and its units. The datapoints represent observed failure dates
r time.
F. In Example 1, notice that the MTBF is decreasing until the fifth failure. At that point in time, a strategy
g in an increase in MTBF.
what the MTBF would be) at some date in the future.
rights reserved.
ng COT
ween Failures (MTBF) changes over time. MTBF is calculated from the distribution of the failures over time.
d in the analysis.
Example 2.
operating time if the analysis does not contain dates and displays calendar time if the analysis does contain
s, so cumulative operating time is displayed. The y-axis displays the MTBF and its units. The datapoints
F Trend graph for an analysis based on cumulative operating time as for an analysis based on failure dates.
ng calendar time, however, the graph displays the mean time between failures using the time units you
ustom units of miles, so the average number of miles between each failure is displayed on the MTBF Plot
rights reserved.
ween Cost (MTBC) changes over time. MTBC is calculated from the distribution of cost over time. The
analysis.
Example 3.
ive operating time, and the y-axis displays the MTBC.
C trend displays how much time lapses between spending. If cost is directly tied to failures, this plot may be
ece of equipment or location. But if the cost measurements are not necessarily tied to failures (e.g., general
hows you the amount of time in between expenditures, which is not necessarily patterned behavior. In this
st Rate Trend graph.
as changed over time. As with an MTBF plot, you can click any datapoint to view the cost data and estimate
rights reserved.
ment> Rate Plot Page
> Rate Plot link.
e preview of the <Measurement> Rate Trend graph.
end graph appears in the Reliability Growth Model section only if the analysis is based on non-event count
ement> Trend graph appears.
splaying the <Measurement> Rate Trend graph. The following image displays the <Measurement> Rate
Graph Using Failure Dates
ilure rate of a piece of equipment or location changes over time. This graph is the inverse of the MTBF
ailure dates included in the analysis.
end graph for Example 1.
plays the calendar time, and the y-axis displays the failure rate and its units. The datapoints represent
urring.
y, rather than the number of days between failures.
ed at some date in the future.
Graph Using COT
ilure rate of a piece of equipment or location changes over time. This graph is the inverse of the MTBF
ailures included in the analysis.
end graph for Example 2.
plays cumulative operating time, and the y-axis displays the Failure Rate and its units. The datapoints
e Failures Rate Trend graph for an analysis based on cumulative operating time as for an analysis based on
e using calendar time (per day), however, the plot displays the failure rate using the time units you specified
tom units of miles, so failures are displayed per mile.
ph
ate of a piece of equipment or location changes over time. This graph is the inverse of the MTBC Trend
luded in the analysis.
graph for Example 3.
s cumulative operating time, and the y-axis displays the cost rate and its units. The datapoints represent
s being spent.
hanged the amount of money being spent over time.
pent per time unit (e.g., month).
can click any datapoint to view the cost data and estimate the amount of cost incurred at some time in the
idium, Inc. All rights reserved.
ltiple Growth Analyses Page
me plot by displaying them on the Multiple Growth Analyses page.
page:
ses from the List page, select the analyses that you want to view on one plot.
of the following links, depending upon the plot that you want to view:
e than 20 analyses to be shown on the Multiple Growth Analyses page, a warning message appears, indicating
ng time to load and that interpretation will be difficult. You can click the Yes button to continue or the No
ect a Growth Analysis from the List page.
yses page appears, displaying the selected analyses on one plot.
1993-2014 Meridium, Inc. All rights reserved.
the Multiple Growth Analyses Page
yses page allows you to view the MTBE Trend, Cumulative, or Rate Trend graphs for more than one
is at once. The following image displays an example of the Multiple Growth Analyses page displaying the
analyses looks similar to a plot that displays a single analysis. Because the analyses may not be in the same
versions must be made to allow the data to be compared more easily. When you are viewing multiple
:
Trend graph the y-axis label is MTBE if the analyses use different time units or MTBE <units> if all analyses
unit.
end graph, the y-axis label is Rate if the analyses use different time units and Rate <unit> if all analyses use
tive graph, the y-axis label is Cumulative.
the x-axis label is Cumulative Time if the analyses use different time units and Cumulative Time <units>
same time unit.
use different time units, the data is converted to the smallest unit. For example, if one analysis uses weeks
ays, the units for the former analysis are converted to days.
analyses use custom units, no conversion is made, and the x-axis and y-axis have no units.
analyses use custom units and one or more analyses use non-custom units on the same graph, the x-axis and
ts, and the data for the analyses with non-custom units will be converted to the smallest unit.
atapoints and extrapolation on all graphs.
n one of the analysis plot lines, that line is highlighted while the other plot lines are dimmed. If you click one
lines, the Reliability Growth Analyses page appears for that analysis.
ight 1993-2014 Meridium, Inc. All rights reserved.
Menu
the Multiple Growth Analyses page contains the following links:
splays the MTBE Trend graph for the analyses you accessed on the Multiple Growth Analyses page.
ot: Displays the Cumulative graph for the analyses you accessed on the Multiple Growth Analyses page.
plays the Rate Trend graph for the analyses you accessed on the Multiple Growth Analyses page.
he link that corresponds with the plot that you are currently viewing on the Multiple Growth Analyses page,
n, and the plot that you are currently viewing will continue to be displayed.
nts: Hides datapoints if they are currently displayed. If datapoints are currently hidden, this link will
Datapoints, and clicking it will cause the datapoints to reappear.
ation: Hides extrapolation if it is currently displayed. If extrapolation is hidden, this link will be labeled
on, and clicking it will cause the extrapolation to reappear.
on Tasks Menu
s menu on the Multiple Growth Analyses page contains the following links:
alysis: Displays the Reliability Growth Builder, which guides you through the process of creating a new
Growth Analysis.
nalysis: Displays the Find Reliability Growth Analysis window, which you can use to search for existing
Growth Analysis records.
o: Displays a submenu with options that let you provide a link to the current page on your desktop (create
n an email message, or on a Home Page.
Displays the context-sensitive Help topic for the Multiple Growth Analyses page.
nes: Displays overview information about the Reliability Analytics module.
odness of Fit Test for a Growth Analysis
s of Fit (GOF) test determines how well your analysis data fits the calculated data model.
data passes the GOF test, your data follows the data model closely, and you can rely on the predictions made
data fails the GOF test, it may not follow the model closely enough to confidently rely on model predictions.
ability Growth Analysis page, in the Segment grid, the Passed GOF check box is selected when your data
est and cleared when your data fails the test.
ne whether the data passes the GOF test, the Meridium APM system uses the following values:
atistic: Determines how precisely the data fits the model. This value is calculated from a Cramer-von Mises
ared test and is displayed in the GOF Statistic column in the Segment grid on the Reliability Growth Analysis
Value: Determines what critical value to use for the GOF test. This value depends on the Confidence Level
or the analysis.
Value: Determines whether the data passes the GOF test. This standard value depends on the number of
included in the analysis and the alpha value. It is displayed in the Critical Value column in the Segment grid
ability Growth Analysis page.
atistic
ent methods are used for calculating GOF for Reliability Growth Analyses, depending upon whether or not
s use grouped data.
of Fit (GOF) for a Reliability Growth Analyses based on data that is not grouped is calculated using the
n Mises test.
lyses whose end date is time-based, Cramer-von Mises test uses the following formula to calculate the GOF
lyses whose end date is event-based, Cramer-von Mises test uses the following formula to calculate the GOF
of Fit for a Reliability Growth Analysis based on grouped data is calculated using a Chi-squared test. This
e following formula to calculate a test statistic:
l Value: Cramer-Von Mises Test
ouped data, the Cramer-von Mises test is used to determine whether the data passes the GOF test. This test
he GOF Statistic to a Critical Value. The Critical Value depends on two values:
= 1- Confidence Level
e number of datapoints in the population.
termined using the Confidence Level, which you can define manually for each analysis. The Confidence
ates the percentage of uncertainty of the Goodness of Fit method. This percentage is usually determined by
or an industry standard and limits how closely the data must fit the model in order for it to pass the
of Fit test. The higher the Confidence Level, the easier it will be for your data to pass the Goodness of Fit
wer the Confidence Level, the harder it will be for your data to pass the Goodness of Fit test. If the data does
ver, the data will be a very close fit to the model.
n you select a Confidence Level, you must specify 80, 90, 95, or 98 percent. If you do not modify the
level, alpha is automatically set to 0.1 (i.e., a confidence level of 90%).
nfidence Level has been determined, the Meridium APM system uses the following Critical Values for
n Mises Test chart to find the Critical Value. The chart displays critical values at four confidence levels (80%,
and 98%) which in turn calculate 4 alpha values (0.2, 0.1, 0.05, 0.02).
number of datapoints in your analysis is between two rows in the chart (e.g., 22). the smaller value (e.g.,
If the number of datapoints is greater than 100, 100 is used.
l Value: Chi-squared Test
d data, the Chi-squared test is used to determine whether the analysis passed the GOF test. This test uses
Freedom (i.e., the number of datapoints - 2) and the Confidence Level to calculate a Critical Value, which is
ared to the GOF Statistic to determine whether the analysis passed the GOF test. The Confidence Level is
same way it is in the Cramer-von Mises test (i.e., it indicates the percentage of uncertainty of the Goodness
od).
ing formula is used to calculate the Chi-squared distribution.
ula, k is degrees of freedom and F(x;k) is the Confidence Level. These values are used to find the Critical
mining the Results
e Cramer-von Mises test and the Chi-squared test, if the GOF statistic is greater than the Critical Value at the
nfidence Level, the data fails the GOF test. This means the data does not follow the analysis pattern closely
confidently predict future measurements. If the GOF Statistic is lower than the Critical Value, the population
est, which means data is more likely to occur in a pattern and therefore is more predictable.
e, if you run a Reliability Growth Analysis on a set of failure data, and the data fails the GOF test, it may
he piece of equipment or location does not fail in a predictable pattern (i.e., the piece of equipment or
ls at random). If this is the case, any predictions you make based on this data will not be as reliable as
made against data that has passed the GOF test.
sis fails a GOF test, it does not necessarily mean that you cannot use the data model. The Reliability Growth
ight fail a GOF test because there is more than one trend within the data. If you suspect this is the case, you
e analysis into segments at the points where it looks like a change occurred. Afterwards, the separate
may individually pass the GOF test because they have been split up into multiple failure patterns.
y, if the analysis fails the GOF test, you should also check for a visual goodness of fit. Models can
still be used even if the analysis does not pass the GOF test.
out the Beta Value and MTBE
ility Growth Analysis page displays the Beta and Lambda values as calculated by the application based on
The Beta value indicates whether MTBE is increasing, decreasing, or remaining constant.
MTBF
Equipment Reliability
If the Beta value is equal to or close to

Unchanging MTBE (predictable
one (1), then the reliability is constant,
failures)
and time is not a major factor.
Increasing MTBE (improving
reliability)
If the value of Beta is less than one, the

reliability of the equipment is improving
over time.
Decreasing MTBE
(deteriorating reliability)
If the value of Beta is greater than one

(1), then the reliability of the equipment
is deteriorating over time.
value indicates that the MTBE is increasing or decreasing, you can try splitting the failure data up by time,
e, operating time, or some other appropriate value to create a set of data where the Beta value is closer to
choose to split the data into time periods, you might try using the feature that lets you split a single analysis
le segments.
tting an Analysis Into Segments
ses, a Reliability Growth Analysis may indicate that your data is trending in an undesirable direction (e.g.,
occurring very often, costs are too high). In these cases, you will probably decide to make significant
s to your work process in order improve the results. You can create a Reliability Growth Analysis that is split
nts to represent periods of time before and after you made changes to improve the reliability of your
and locations.
generate a report for an analysis that has been split into segments, the report will contain information about
ent and the analysis as a whole.
analysis into segments:
Access the Reliability Growth Analysis page for an existing Reliability Growth Analysis.
On the Plots menu, click the <Measurement> Plot link.
On the Cumulative <Measurement> Plot page, locate the datapoint that represents the last measurement
orded before you made a significant change to your work process.
Right-click the datapoint, and click Split on the shortcut menu.
e: The Split option is enabled only if there are at least three datapoints to the left and to the right of the
apoint you selected.
plot line bends at the datapoint you selected, representing two segments instead of one.
hough the analysis still has an overall Initial and Final MTBF, each individual segment now also has its own
ial and Final MTBF. The AMSAA Reliability Growth Model page will also display different information for
h segment. Each segment is colored according to whether it passed the GOF test. If the segment is blue, it
sed the GOF Test. If the segment is orange, it failed the GOF test.
esired, you can merge the segments back into one by right-clicking on a segment and clicking Merge With
vious Segment on the shortcut menu.
e: When you split the analysis manually via the Cumulative <Measurement> plot, the MTBE Trend plot and
<Measurement> Rate plot will also reflect the split.
Estimating Data in the Future
u might want to estimate the number of events that will have occurred or the amount of non-event data (e.g.,
) that has been incurred at some point in the future. This estimation assumes that you do not plan to make
additional changes in your piece of equipment, location, or work process.
estimate data measurements in the future:
On the Cumulative <Measurement> Plot, the MTB<Measurement> Plot, or the <Measurement> Rate Plot
es, on the Current Analysis menu, click the Extrapolate link.
Extrapolation dialog box appears.
ou have not yet extrapolated the analysis, the No Extrapolation option is selected by default.
To estimate the number of failures that will have occurred:
By a specific date, select the Date option. In the list to the right of the Date option, select the date on
which you want to know how many failures will have occurred.
Note: You can extrapolate by date only if your analysis data contains dates. If the analysis does not
contain dates, the Date option will not appear, and you will not be able to extrapolate based on dates.
After a certain amount of time, select the Time option. In the text box to the right of the
Time option, specify the number of time units at which you want to know how many failures will
have occurred. The unit of measure to the right of the text box corresponds with the value that
you selected in the Time Units dialog box.
Note: The date or time that you specify must be greater than the default date or time, which is the
analysis end date or time.
Click OK.
The plot returns to focus, and several lines have been added based on the extrapolation
specification.
Interpreting Extrapolation Results

Using Failure Dates
After you select an extrapolation method (by date or by amount of time), for each
segment in the analysis, a dotted green line extends from the last failure date for that
segment to the specified date in the future. The future date is calculated based on the date
or time units you provided in the Extrapolation dialog box. At the end of the dotted green
line, a number appears, representing the estimated number of failures that would have
occurred at that point in time.
A solid green line also intersects the end date for each segment, and the cumulative
operating time at the end of that segment appears on the solid green line.
For Example 1, suppose you suggested to increase inspections rounds for a pump in order
to slow the growing failure rate. This strategy was implemented on September 5, 1999.
Several years later, you create a graph using the extrapolation tool to display to
management the number of failures that have been prevented and will continue to be
prevented as a result of the strategy.
In this example, the analysis is split into two segments at the fifth failure, which took
place on 9/5/1999, the day on which the strategy was implemented. The first segment
represents the data without the strategy change, and the second segment represents the
date with the strategy change. The dotted green extrapolation lines display the future data
trend of each segment until the extrapolation date 1/30/2010, which was specified using
the Extrapolation dialog box.
The solid green lines display the date and cumulative time at the end of each segment and
at the extrapolation date. In this example, these lines represent the date of the strategy
change, the current date, and the future date, respectively.
The following chart displays the number of failures at each solid green line, which are
represented in the graph by a gray number where the solid green line intersects a segment
or extrapolation line.
# of Failures on
9/5/1999
Strategy
(date of strategy
change)
# of Failures on
1/30/2006
# of Failures on
1/30/2010
(current date)
(extrapolation date)
Segment 1
(Without Strategy
Change)
Not Displayed
158
14
20
Segment 2
(With Strategy
Change)
At the extrapolation date for the first segment the number 158 is displayed, which means
that if you had not made the strategy change, you could have expected 158 failures by
January 30, 2010.
At the extrapolation date for the second segment the number 20 is displayed, which
means that if you do not make any changes from your last failure date (January 30, 2006)
until the future date (January 30, 2010), you can expect 20 failures by that date.
Assuming the failure trend continues as expected, an observation can be made that a
strategy change introduced on September 5, 1999 allowed you to prevent 138 failures
between September 5, 1999 and January 30, 2010 (i.e., 158 - 20).
Interpreting Extrapolation Results

Using COT
After you select an Extrapolation method (by date or by time period), for each segment in
the analysis, a dotted green line extends from the last failure date for that segment to the
specified date in the future (calculated based on the date or time units you provided in the
Extrapolation dialog box). At the end of the dotted green line, a number appears,
representing the estimated number of failures that would have occurred at that point in
time.
For Example 2, suppose you began changing a haul truck's oil more frequently in order to
slow its growing failure rate. This strategy was implemented after the truck had traveled
77,314 miles. After the truck has logged some miles using the new strategy, you create a
graph to display to management the number of failures you will have prevented after the
haul truck has logged 750,000 miles.
This image represents the extrapolation results for Example 2, where we extrapolated
using time. The x-axis represents the cumulative time, or the total runtime for a piece of
equipment or location after the analysis has started, using the units of miles.
The analysis is split into two segments at the sixth failure, which took place on 77,314
miles, the mileage at which the strategy was implemented. The first segment represents
the data without the strategy change, and the second segment represents the date with the
strategy change. The dotted green extrapolation lines display the future data trend of each
segment until the extrapolation time of 750,000 miles, which was specified using the
Extrapolation dialog box.
The solid green lines display the cumulative operating time (i.e., the total mileage for the
truck) and the cumulative time (i.e., the truck's mileage since the analysis has started) at
the end of each segment and the at extrapolation date. In this example, these lines
represent the mileage of the truck at the strategy change, the current mileage, and the
future mileage, respectively.
Note: In our example, the haul truck has a mileage of 11,028 before the analysis started.
Therefore, the cumulative time and the cumulative operating time will always be 11,028
miles apart. If the piece of equipment or location is brand new (i.e., the truck has a
mileage of 0 when the analysis started), the cumulative time and the cumulative operating
time will be the same.
The following chart displays the number of failures at each solid green line, which are
represented in the graph by a gray number where a solid green line intersects a segment or
extrapolation line.
# of Failures at
77,314 miles
Strategy
# of Failures at
303,156 miles
# of Failures at 750,000
miles
(time of strategy
change)
(current mileage)
(extrapolation mileage)
Not Displayed
205
Segment 1
(Without Strategy
Change)
Segment 2
(With Strategy
Change)
16
44
At the extrapolation time for the first segment the number 205 is displayed, which means
that if you had not made the strategy change, you could have expected 206 failures by the
time the truck traveled 750,000 miles.
At the extrapolation time for the second segment the number 44 is displayed, which
means that if you do not make any changes from your last failure time (303,156 miles)
until the future failure time (750,000 miles), you can expect 44 failures by that time.
Finally, an observation can be made that the change introduced at 77,314 miles allowed
you to prevent 161 failures between a mileage of 77,314 and 750,000 (i.e., 205 - 44).
Interpreting Extrapolation Results for

Cost
After you select an Extrapolation method, for each segment in the analysis, a dotted green
line extends from the last failure date for that segment to the specified date in the future
(calculated based on the date or time units you provided in the Extrapolation dialog box).
At the end of the dotted green line, a number appears, representing the estimated number
of failures that would have occurred at that point in time.
For Example 3, suppose you changed mechanics to try to curb the growing cost of
repairing equipment. This strategy was implemented after 23 months. After a few years
have passed, you want to create a graph using the extrapolation tool to display to
management the amount of money you have saved using this strategy after a period of 10
years.
This image represents the extrapolation results for Example 3, where we extrapolated
using time. The x-axis represents the cumulative time, or the amount of time cost has
been measured, using the units of months.
In this example, the analysis is split into two segments at the third failure, which occurred
at 23 months, the time at which the strategy was implemented. The first segment
represents the data without the strategy change, and the second segment represents the
date with the strategy change. The dotted green extrapolation lines display the future data
trend of each segment until the extrapolation time of 120 months, which was specified
using the Extrapolation dialog box.
The solid green lines display the cumulative operating time (i.e., the total amount of time
that cost has been measured) and the cumulative time (i.e., the amount of time that has
passed since the analysis started) at the end of each segment and the extrapolation date. In
this example, these lines represent the cost that had been incurred at the strategy change,
the current amount of cost that has been incurred, and the future cost, respectively.
The following chart displays the amount of cost at each solid green line, which is
represented in the graph by a gray number where a solid green line intersects a segment or
extrapolation line.
Cost at 23 months
Strategy
Cost at 62
months
Cost at 120 months
(time of strategy
change)
(current time)
(extrapolation
time)
$3,133
Not Displayed
$28,840
$3,133
$6,305
$11,314
Segment 1
(Without Strategy
Change)
Segment 2
(With Strategy Change)
At the extrapolation time for the first segment the number 28,840 is displayed, which
means that if you had not made any changes after 23 months, you could have expected
repairs to cost 28,840 dollars by the time 120 months had passed.
At the extrapolation time for the second segment the number 11,314 is displayed, which
means that if you do not make any changes from your last cost measurement (62 months)
until the future time (120 months), you can expect 11,314 dollars in cost to accumulate by
that date.
Finally, an observation can be made that the change introduced at 23 months saved you
17,526 dollars between the time of 23 months and 120 months (i.e., 28,840 - 11,314).
Overview of the Reliability Growth

Report
The baseline Meridium APM database includes the Reliability Growth Report, which you
can use to view a summary of the results of a Reliability Growth Analysis. When you run
the Reliability Growth Report, it will appear on the Report Viewer page.
The Reliability Growth Report is built from the following Catalog items:
The main report, GrowthAnalysisReport, which is stored in the Catalog
folder \\Public\Meridium\Modules\Reliability Manager\Reports.
The subreport, AssetsubreportGrowth, which is stored in the Catalog folder
\\Public\Meridium\Modules\Reliability Manager\Reports.
The subreport, FailuresubreportGrowth, which is stored in the Catalog
folder \\Public\Meridium\Modules\Reliability Manager\Reports.
The supporting query that supplies data in the main report and subreports,
GrowthAnalysisQuery, which is stored in the Catalog folder
\\Public\Meridium\Modules\Reliability Manager\Reports.
Throughout this documentation, we refer to the main report, the subreports, and
the supporting query collectively as the Reliability Growth Report.
The Reliability Growth Report contains a prompt on the ENTY_KEY field in the
Reliability Growth family. When you run the Reliability Growth Report while
viewing a Reliability Growth Analysis, the ENTY_KEY of the Reliability Growth
record associated with the current analysis is passed automatically to the prompt,
and the results for the current Reliability Growth Analysis are displayed. If you
run the main report (i.e., GrowthAnalysisReport) or the supporting query (i.e.,
GrowthAnalysisQuery) directly from the Catalog, however, you will need to
supply the ENTY_KEY of a Reliability Growth record manually to retrieve

results. The subreports (i.e., Catalog items AssetsubreportGrowth and
FailuresubreportGrowth) cannot be run directly from the Catalog.
The Reliability Growth Report contains the following sections:
Analysis Summary
Growth Model Segments
Assets
<Measurement> Data
Plots
Running the Reliability Growth

Report
You can run the Reliability Growth Report to view a summary of the
results of a Reliability Growth Analysis.
To run the Reliability Growth Report:
On the Reliability Growth Analysis page, on the Current Analysis
menu, click the Generate Report link.
The Report Options dialog box appears. The following image shows what
the Report Options dialog box looks like by default.
Note: The option labels displayed on this window may look different from
this image, depending on the measurement name you selected on the
Select Data Format screen of the Reliability Growth Builder.
Select the elements that you want to include in the report, and
click OK.
The Reliability Growth Report appears on the Report Viewer page.

reserved.
Analysis Summary Section

The Analysis Summary section of the Reliability Growth Report
displays information that is stored in the Reliability Growth record
and the Growth Model record that is linked to the Reliability
Growth record. The Analysis Summary section will look different
depending on whether or not your analysis data is event-based and
the value you enter in the Measurement Name dialog box. Also,
the values in the Analysis Summary section will come from
different fields in the Reliability Growth and Growth Model
records depending on whether the analysis is based on dates or
cumulative operating time.
The following image displays the Analysis Summary section for
Example 1, an analysis based on dates that contains event-based
data.
The following table lists each item in the Analysis Summary section
for an analysis based on dates that contains event-based data and
the corresponding Reliability Growth or Growth Model record field
Reliability
Growth or
Record field(s)
Growth Model
record
Notes
Analysis Name
Reliability
Growth
Analysis ID
None
Analysis
Description
Reliability
Growth
Short Description
None
Report Item
Reliability
Growth
Analysis Start
Analysis Start Date
If the analysis is based o

cumulative operating tim
the report will used the
value in the field Analys
Start Time.
Analysis End Date
If the analysis is based o

cumulative operating tim
the report will use the
value in the field Analys
End Time.
Assets
None
Reliability
Growth
Analysis End
Number of Assets
Reliability
Growth
Total
Growth Model Number of Failures
<Measurement>
Time Units
Reliability
Time Units
Growth
Growth Model
Total Observation Time
Observation Time Reliability

Growth
Time Units
None
None
None
Initial MTBF
Initial MTBF
Reliability
Growth
Final MTBF
Reliability
Growth
Next Estimated
Event Date
Reliability
Growth
Use Confidence
Reliability
Growth
Use Confidence
None
Confidence
Reliability
Growth
Confidence Level
None
Last Modified
Reliability
Growth
LAST_UPDT_DT
None
Time Units
Final MTBF
Time Units
TTNF
Time Units
None
None
None
Modified By
Reliability
Growth
The name of the Securit

User associated with thi
LAST_UPBY_SEUS_KEY
value is displayed in the
report.
The Analysis Summary section for an analysis that is not eventbased will appear mostly the same as the Analysis Summary section
for an analysis that is event-based, with the following exceptions.
The Next Estimated Event Date field will not be
displayed in the Analysis Summary section.
The Initial MTBF and Final MTBF fields will be
labeled Initial <Measurement> Rate and Final Measurement
Rate, respectively.
Note: Although the values used in the report are stored in
Reliability Growth or Growth Model records, the report
contains additional logic in order to display the values in
this format. In other words, the values in the records are not
in the exact form in which they appear in the report.

rights reserved.
Growth Model Segments

Section
The Growth Model Segments section of the Reliability
Growth Report displays information that is stored in the
Reliability Growth record or the Growth Model record that
is linked to the Reliability Growth record. The Growth
Model Segments section will look different depending on
whether the analysis is based on dates or cumulative
operating time. The following image displays the Growth
Model Segments section for Example 1, an analysis based
on dates.
The following table lists each item in the Growth Model

Segments section for an analysis based on dates and the
corresponding Reliability Growth or Growth Model record
Reliability
Growth or
Report Item
Growth Model
record
Record
field(s)
Notes
Segment
Growth Model
Start Date
Growth Model
Sequence None
Model Start
Date
None
End Date
Reliability
Growth
Analysis
End Date
Termination Reliability
Type
Growth
None
If the value in the Is Grouped Data

True, the Termination Type is Grou
If the value is False, the Terminatio
Is Grouped
depends on the value in the Time T
Data
field.
Time
If the value in the Time Terminated
Terminated
False, the Termination Type is Eve
If the value in this field is True, the
Termination Type is Time-Based.
Beta
Growth Model
Beta
None
Lambda
Growth Model
Lamda
None
Statistic
Growth Model
GOF
Statistic
None
Critical
Value
Growth Model
GOF PValue
None
Passed
Growth Model
Passed GOF None
The Growth Model Segments section for an analysis that

contains cumulative operating time will appear mostly the
same as the Growth Model Segments section for an analysis

that contains dates, with the following exceptions.
The Start Date and End Date fields will not be
displayed in the Growth Model Segments section.
The Growth Model Segments section will
display the following fields.
Report Item Reliability Growth or Growth Model record
Start Time
Reliability Growth
End Time
Reliability Growth

Assets Section
The Assets section of the Reliability Growth Report
displays values that are stored in the Failures field in
the Reliability Growth record. The Assets section
will look different depending on whether the
analysis is based on dates or cumulative operating
time. The following image displays the Assets
section for Example 1, an analysis based on dates.
The following columns in the Assets section contain

data that is stored in the Failures field in the
Reliability Growth record:
Asset ID
Installation Date
Note: The Installation Date column appears only for
analyses based on dates.
Last Replacement

<Measurement> Data
Section
The <Measurement> Data section of the Reliability
Growth Report displays information that is stored in
the Failures field of the Reliability Growth record.
The <Measurement> Data section will look
different depending on whether the analysis is based
on dates or cumulative operating time. It will also
look different depending on the value you enter in
the Measurement Name dialog box. The following
image displays the <Measurement> Data section
for Example 1, an analysis based on dates that has a
measurement name of Failures.
The following columns in the <Measurement>

Data section contain data that is stored in the
Failures field in the Reliability Growth record:
Asset ID
Date
Time
Note: The Time column appears only for analyses
based on dates.
Downtime
Note: The Downtime column appears only for
analyses based on dates.
COT
Note: The COT column appears only for analyses
based on cumulative operating time.
<Measurement>
Ignore
Remarks
Cumulative Time

Plots Section
The Plots section of the Reliability Growth Report
displays the graphs that are accessed via the Plots
menu on the Reliability Growth Analysis page. The
following image displays an example of the MTBF
Trend graph.
The Plots section contains the following graphs:
MTB<Measurement> Trend
Cumulative <Measurement> Plot
<Measurement> Rate Trend
V3.6.0.0.0 - Copyright 1993-2014

Overview of
Reliability
Distribution Analysis
A Reliability Distribution Analysis allows
you to describe the Time to Failure (TTF) as
a statistical distribution, which is usually
characterized by a specific pattern. Four

distribution types are supported: Weibull,
Normal, LogNormal, and Exponential.
The Distribution Analysis characterizes how
failures are distributed over the life of
equipment. Analyzing the distribution of
failures means examining a particular failure
mode over one or multiple pieces of
equipment. Generating a Distribution
Analysis will help you find the answers to
the following questions:
Do most of the equipment
failures occur early on?
Does the equipment fail more at
the end of its span of service?
Are the failures fairly evenly
distributed throughout the life of the
equipment or randomly occurring?
In a Distribution Analysis, you are
trying to determine the probability of
failure at a certain point in time. The
model assumes that the shape of the
distribution is not changing over
time. A Distribution Analysis can
help you determine the pattern of
failures, and the results can be
compared to industry data.
If Time to Repair (TTR) information
is available, a Distribution Analysis
also will be calculated to describe the
maintainability of the piece of
equipment. PM Optimization and
Failure Probability calculations can
be performed on any piece of
equipment that has a valid Time to
Failure (TTF) distribution.
V3.6.0.0.0 - Copyright 1993-2014

Weibull
Distribution
A Weibull Distribution describes the
type of failure mode experienced by
the population (infant mortality, early
wear out, random failures, rapid
wear-out). Estimates are given for
Beta (shape factor) and Eta (scale).
MTBF (Mean Time Between
Failures) is based on characteristic
life curve, not straight arithmetic
average.
A Weibull Distribution uses the
following parameters:
Beta: Beta, also called the
shape factor, controls the type
of failure of the element
(infant mortality, wear-out, or
random).
Eta: Eta is the scale factor,
representing the time when
63.2 % of the total population
is failed.
Gamma: Gamma is the
location parameter that allows
offsetting the Weibull
distribution in time. The
Gamma parameter should be
used if the datapoints on the
Weibull plot do not fall on a
straight line.
If the value of Beta is greater
than one (1), you can perform
Preventative Maintenance
(PM) Optimizations. A
Gamma different from a

value zero (0) means that the
distribution is shifted in order
to fit the datapoints more
closely.
Note: This is an advanced
feature and should be used in
the proper context and with a
good understanding of how to
apply a three-parameter
Weibull distribution.
1993-2014 Meridium, Inc. All
rights reserved.
Weibull
Analysis
Information
You can use the following
information to compare the
results of individual Weibull
analyses. The following
results are for good
populations of equipment.
Beta Values Weibull Shape Factor

Components
Low Typical High
Low
Typ
(days) (day
Ball bearing
0.7 1.3
3.5 583
166
Roller
bearings
0.7 1.3
3.5 375
208
Sleeve
0.7 1
208
417
bearing
Belts drive
0.5 1.2
2.8 375
125
Bellows
hydraulic
0.5 1.3
208
0.5 3
10 5208 125
Clutches
friction
0.5 1.4
Clutches
magnetic
0.8 1
1.6 4167 625
Couplings
0.8 2
1042 312
Couplings
gear
0.8 2.5
1042 312
Cylinders
hydraulic
3.8
37500
375
0
Diaphragm
metal
0.5 3
2083 270
Diaphragm
rubber
0.5 1.1
1.4 2083 250
Gaskets
hydraulics
0.5 1.1
1.4 29167 312
Filter oil
0.5 1.1
1.4 833
Gears
0.5 2
1375 312
Impellers
pumps
0.5 2.5
5208 625
Joints
mechanical
0.5 1.2
58333 625
Bolts
583
2792 416
104
Knife edges
fulcrum
0.5 1
70833 833
Liner recip.
comp. cyl.
0.5 1.8
833
208
Nuts
0.5 1.1
1.4 583
208
"O"-rings
elastomeric
0.5 1.1
1.4 208
833
Packings
recip. comp. 0.5 1.1
rod
1.4 208
833
Pins
0.5 1.4
708
208
Pivots
0.5 1.4
12500 166
Pistons
engines
0.5 1.4
833
312
Pumps
lubricators
0.5 1.1
1.4 542
208
Seals
mechanical
0.8 1.4
125
104
Shafts cent.
pumps
0.8 1.2
2083 208
Springs
0.5 1.1
583
104
Vibration
mounts
0.5 1.1
2.2 708
208
Wear rings
0.5 1.1
cent. pumps
417
208
Valves recip
comp.
0.5 1.4
125
166
Equipment
Low Typical High Low
Typ
Assemblies
Circuit
breakers
(days) (day
0.5 1.5
2792 416
Compressors
0.5 1.9
centrifugal
833
Compressor
blades
0.5 2.5
16667 333
Compressor
vanes
0.5 3
20833 416
Diaphgram
couplings
0.5 2
5208 125
250
Gas turb.
comp.
1.2 2.5
blades/vanes
6.6 417
104
Gas turb.
0.9 1.6
blades/vanes
2.7 417
520
Motors AC
0.5 1.2
42
416
Motors DC
0.5 1.2
208
Pumps
centrifugal
0.5 1.2
42
145
Steam
turbines
0.5 1.7
458
270
Steam
turbine
blades
0.5 2.5
16667 333
Steam
0.5 3
turbine vanes
20833 375
Transformers 0.5 1.1
583
833
Instrumentation
Low Typical High
Low
Typ
(days) (day
Controllers
pneumatic
0.5 1.1
42
Controllers
solid state
0.5 0.7
1.1 833
416
Control
valves
0.5 1
583
416
Motorized
valves
0.5 1.1
708
104
Solenoid
valves
0.5 1.1
2083 312
Transducers
0.5 1
458
Transmitters 0.5 1
4167 625
Temperature
0.5 1
indicators
5833 625
Pressure
indicators
4583 520
Flow
instrumentati 0.5 1
on
4167 520
Level
instrumentati 0.5 1
on
583
104
Electromechanical
parts
0.5 1
542
104
Static
Equipment
Low Typical High
0.5 1.2
104
833
Low
Typ
(days) (day
Boilers
condensers
0.5 1.2
458
Pressure
vessels
0.5 1.5
52083 833
Filters
strainers
0.5 1
20833 208
3
3
Check valves 0.5 1
4167 416
Relief valves 0.5 1
4167 416
Service Liquids
208
Low Typical High
Low
Typ
(days) (day
0.5 1.1
458
625
Lubricants
0.5 1.1
screw compr.
458
625
Lube oils
mineral
0.5 1.1
125
417
Lube oils
synthetic
0.5 1.1
1375 208
Greases
0.5 1.1
292
Coolants
rights reserved.
Weibull
Results
Interpretatio
n
417
Meridium APM Reliability

shows the failure pattern of a
single piece of equipment or
groups of like equipment
using Weibull analysis
methods. This helps the user
to determine the appropriate
repair strategy to improve
reliability.
Is the Probability
Plot a good fit?
Follow these steps to
determine whether or not the
plot is a good fit:
Identify Beta
(slope) and its
associated failure
pattern
Compare Eta
(characteristic life) to
standard values
Check goodness of
fit, compare with
Weibull database
Make a decision
about the nature of the
failure and its
prevention
The following chart
demonstrates how to
interpret the Weibull
analysis data using the
Beta parameter, Eta
parameter and typical
failure mode to
postulate a failure
cause.
Weibull Results
Beta
Eta
Greater than 4
Low compared with

standard values for
failed parts (less th
20%)
Greater than 4
Low compared with

standard values for
20%)
Between 1 and 4
Low compared with

standard values for
20%)
Between 1 and 4
Low
Less than 1
Low
Between 1 and 4
Between 1 and 4
Around 1
Much less than
1993-2014
Meridium, Inc. All
rights reserved.
Goodnes
s of Fit
(GOF)
Tests for a
Weibull
Distributi
on
A Goodness of Fit test
is a statistical test that
determines whether
the analysis data
follows the
distribution model.
If the data passes
the Goodness of Fit
test, it means that it
follows the model
pattern closely enough
that predictions can be
made based on that
model.
If the data fails the
Goodness of Fit test, it
means that the data
does not follow the
model closely enough
to confidently make
predictions and that
the data does not
appear to follow a
specific pattern.
Weibull results are
valid if Goodness of
Fit (GOF) tests are
satisfied. Goodness of
Fit tests for a Weibull
distribution include
the following types:
R Linear
regression (least
squares): An RSquared test statistic
greater than 0.9 is
considered a good fit
for linear regression.
2
KolmogorovSmirnov: The
Meridium APM
system uses
confidence level and
P-Value to determine
if the data is
considered a good fit.
If the P-Value is
greater than 1 minus
the confidence level,
the test passes.
Note: The R-Squared
test statistic is
calculated only for
reference. The
Meridium APM
system uses the
Kolmogorov-Smirnov
test as the Goodness
of Fit test.
1993-2014
Meridium, Inc. All
rights reserved.
Normal
Distributi
on
A Normal Distribution
describes the spread
of data values through
the calculation of two
parameters: mean and
standard deviation.
When using the
Normal Distribution
on time to failure data,
the mean exactly
equals MTBF and is a
straight arithmetic
average of failure
data. Standard
deviation (denoted by
sigma) gives estimate
of data spread or
variance.
A Normal Distribution
uses the following
parameters:
Mean: The
mean is the
arithmetic
average of the
datapoints.
Standard
Deviation: The
Standard
Deviation
value
represents the
scatter (how
tightly the
datapoints are
clustered
around the
mean).
1993-2014
Meridium, Inc.
All rights
reserved.
Logn
ormal
Distrib
ution
In Lognormal
Distributions
of failure data,
two
parameters are
calculated: Mu
and Sigma.
These do not
represent mean
and standard
deviation, but
are used to
calculate
MTBF. In
Lognormal
analysis, the
median
(antilog of mu)
is often used
as the MTBF.
The standard
deviation
factor (antilog
of sigma)
gives the
degree of
variance in the
data.
A Lognormal
Distribution
uses the
following
parameters:
Mu:
Mu
present
s the
logarith
mic
average
for the
Distrib
ution
functio
n.
Sigma:
Sigma
represe
nts the
scatter.
Gamm
a:
Gamm
a is a
locatio
n
parame
ter.
V3.6.0.
0.0 Copyri
ght
19932014
Meridi
um,
Inc. All
rights
reserve
d.
E
xpo
nen
tial
Dis
tri
but
ion
An
Expone
ntial
Distrib
ution is
a
mathe
matical
distribu
tion
that
describ
es a
purely
random
process
. It is a
single
parame
ter
distribu
tion
where
the
mean
value
describ
es
MTBF
(Mean
Time
Betwee
n
Failure
s). It is
simulat
ed by
the
Weibul
l
distribu
tion for
value
of Beta
= 1.
When
applied
to
failure
data,
the
Expone
ntial
distribu
tion
exhibit
sa
constan
t
failure
rate,
indepe
ndent
of time
in
service.
The
Expone
ntial
Distrib
ution is
often
used in
reliabili
ty
modeli
ng,
when
the
failure
rate is
known
but the
failure
pattern
is not.
An
Expone
ntial
Distrib
ution
uses
the
followi
ng
parame
ter:
M
T
B
F
:
T
h
e
E
x
p
o
n
e
n
t
i
a
l
D
i
s
t
r
i
b
u
t
i
o
n
i
s
a
s
i
n
g
l
e
p
a
r
a
m
e
t
e
r
d
i
s
t
r
i
b
u
t
i
o
n
w
h
e
r
e
t
h
e
m
e
a
n
v
a
l
u
e
d
e
s
c
r
i
b
e
s
M
T
B
F
.
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
.
F
a
i
l
u
r
e
D
a
t
a
T
h
e
f
o
l
l
o
w
i
n
g
t
a
b
l
e
s
h
o
w
s
t
h
e
t
y
p
i
c
a
l
d
a
t
a
r
e
q
u
i
r
e
d
f
o
r
b
u
i
l
d
i
n
g
a
R
e
l
i
a
b
i
l
i
t
y
D
i
s
t
r
i
b
u
t
i
o
n
A
n
a
l
y
s
i
s
i
n
M
e
r
i
d
i
u
m
A
P
M
.
Data
Needed
Asset ID
Descri
Select
equipm
analysi
equipm
Installation Select
Date
piece o
Failure
Date
Select
which
can ha
Servic
Failure
Mode
Somet
even a
down"
when d
particu
purpos
If this
make t
Downtime
"return
used to
Time Units Select
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
.
C
o
n
f
i
d
e
n
c
e
L
e
v
e
l
a
n
d
P
V
a
l
u
e
I
n
a
D
i
s
t
r
i
b
u
t
i
o
n
A
n
a
l
y
s
i
s
,
t
h
e
C
o
n
f
i
d
e
n
c
e
L
e
v
e
l
a
n
d
t
h
e
P
V
a
l
u
e
a
r
e
u
s
e
d
t
o
d
e
t
e
r
m
i
n
e
w
h
e
t
h
e
r
t
h
e
d
a
t
a
p
a
s
s
e
s
t
h
e
G
o
o
d
n
e
s
s
o
f
F
i
t
t
e
s
t
.
T
h
e
C
o
n
f
i
d
e
n
c
e
L
e
v
e
l
i
n
d
i
c
a
t
e
s
t
h
e
p
e
r
c
e
n
t
a
g
e
o
f
u
n
c
e
r
t
a
i
n
t
y
o
f
t
h
e
G
o
o
d
n
e
s
s
o
f
F
i
t
m
e
t
h
o
d
.
T
h
i
s
p
e
r
c
e
n
t
a
g
e
i
s
u
s
u
a
l
l
y
d
e
t
e
r
m
i
n
e
d
b
y
e
x
p
e
r
i
e
n
c
e
o
r
a
n
i
n
d
u
s
t
r
y
s
t
a
n
d
a
r
d
a
n
d
l
i
m
i
t
s
h
o
w
c
l
o
s
e
l
y
t
h
e
d
a
t
a
m
u
s
t
f
i
t
t
h
e
m
o
d
e
l
i
n
o
r
d
e
r
f
o
r
i
t
t
o
p
a
s
s
t
h
e
G
o
o
d
n
e
s
s
o
f
F
i
t
t
e
s
t
.
T
h
e
h
i
g
h
e
r
t
h
e
C
o
n
f
i
d
e
n
c
e
L
e
v
e
l
,
t
h
e
f
a
r
t
h
e
r
a
p
a
r
t
y
o
u
r
c
o
n
f
i
d
e
n
c
e
b
o
u
n
d
s
w
i
l
l
b
e
,
a
n
d
t
h
e
e
a
s
i
e
r
i
t
w
i
l
l
b
e
f
o
r
y
o
u
r
d
a
t
a
t
o
p
a
s
s
t
h
e
G
o
o
d
n
e
s
s
o
f
F
i
t
t
e
s
t
.
T
h
e
l
o
w
e
r
t
h
e
C
o
n
f
i
d
e
n
c
e
L
e
v
e
l
a
n
d
t
h
e
c
l
o
s
e
r
t
o
g
e
t
h
e
r
t
h
e
b
o
u
n
d
s
a
r
e
,
t
h
e
h
a
r
d
e
r
i
t
w
i
l
l
b
e
f
o
r
y
o
u
r
d
a
t
a
t
o
p
a
s
s
t
h
e
G
o
o
d
n
e
s
s
o
f
F
i
t
t
e
s
t
.
I
f
t
h
e
d
a
t
a
d
o
e
s
p
a
s
s
,
h
o
w
e
v
e
r
,
t
h
e
d
a
t
a
w
i
l
l
b
e
a
v
e
r
y
c
l
o
s
e
f
i
t
t
o
t
h
e
m
o
d
e
l
.
N
o
t
e
:
W
h
e
n
y
o
u
e
n
t
e
r
a
C
o
n
f
i
d
e
n
c
e
L
e
v
e
l
,
y
o
u
m
u
s
t
s
p
e
c
i
f
y
a
v
a
l
u
e
t
h
a
t
i
s
g
r
e
a
t
e
r
t
h
a
n
o
n
e
(
1
)
b
u
t
l
e
s
s
t
h
a
n
o
n
e
h
u
n
d
r
e
d
(
1
0
0
)
.
T
h
e
f
o
l
l
o
w
i
n
g
i
m
a
g
e
s
s
h
o
w
e
x
a
m
p
l
e
s
o
f
t
h
e
s
a
m
e
g
r
a
p
h
w
i
t
h
a
C
o
n
f
i
d
e
n
c
e
L
e
v
e
l
o
f
9
0
%
a
n
d
1
0
%
,
w
i
t
h
t
h
e
c
o
n
f
i
d
e
n
c
e
b
o
u
n
d
s
r
e
p
r
e
s
e
n
t
e
d
b
y
g
r
e
e
n
l
i
n
e
s
.
A
t
a
9
0
%
c
o
n
f
i
d
e
n
c
e
l
e
v
e
l
t
h
e
c
o
n
f
i
d
e
n
c
e
b
o
u
n
d
s
a
r
e
f
a
t
h
e
r
a
p
a
r
t
,
m
o
s
t
o
f
t
h
e
d
a
t
a
f
a
l
l
s
i
n
s
i
d
e
t
h
e
b
o
u
n
d
s
,
a
n
d
t
h
e
G
O
F
t
e
s
t
i
s
p
a
s
s
e
d
.
A
t
a
1
0
%
c
o
n
f
i
d
e
n
c
e
l
e
v
e
l
,
t
h
e
c
o
n
f
i
d
e
n
c
e
b
o
u
n
d
s
a
r
e
c
l
o
s
e
r
t
o
g
e
t
h
e
r
,
m
o
s
t
o
f
t
h
e
d
a
t
a
f
a
l
l
s
o
u
t
s
i
d
e
t
h
e
b
o
u
n
d
s
,
a
n
d
t
h
e
G
O
F
t
e
s
t
i
s
f
a
i
l
e
d
.
C
o
n
f
i
d
e
n
c
e
L
e
v
e
l
=
9
0
%
C
o
n
f
i
d
e
n
c
e
L
e
v
e
l
=
1
0
%
T
h
e
P
v
a
l
u
e
i
n
d
i
c
a
t
e
s
t
h
e
p
r
o
b
a
b
i
l
i
t
y
t
h
a
t
t
h
e
d
a
t
a
f
i
t
s
t
h
e
s
e
l
e
c
t
e
d
m
o
d
e
l
.
I
f
y
o
u
h
a
v
e
a
P
v
a
l
u
e
o
f
0
.
0
1
,
t
h
e
n
t
h
e
r
e
i
s
a
1
%
p
r
o
b
a
b
i
l
i
t
y
t
h
a
t
t
h
e
d
a
t
a
i
s
c
o
m
p
a
t
i
b
l
e
w
i
t
h
t
h
e
m
o
d
e
l
,
o
r
c
o
n
v
e
r
s
e
l
y
,
t
h
a
t
t
h
e
r
e
i
s
a
9
9
%
p
r
o
b
a
b
i
l
i
t
y
t
h
a
t
t
h
e
m
o
d
e
l
i
s
n
o
t
i
n
a
g
r
e
e
m
e
n
t
w
i
t
h
t
h
e
d
a
t
a
.
I
f
y
o
u
h
a
v
e
a
P
v
a
l
u
e
o
f
0
.
9
5
,
t
h
e
r
e
i
s
a
9
5
%
p
r
o
b
a
b
i
l
i
t
y
t
h
a
t
t
h
e
m
o
d
e
l
i
s
a
p
p
r
o
p
r
i
a
t
e
.
T
o
c
a
l
c
u
l
a
t
e
w
h
e
t
h
e
r
t
h
e
G
o
o
d
n
e
s
s
o
f
F
i
t
t
e
s
t
h
a
s
p
a
s
s
e
d
o
r
f
a
i
l
e
d
,
y
o
u
n
e
e
d
b
o
t
h
t
h
e
c
o
n
f
i
d
e
n
c
e
l
e
v
e
l
a
n
d
t
h
e
P
v
a
l
u
e
.
I
f
t
h
e
P
v
a
l
u
e
i
s
l
e
s
s
t
h
a
n
o
r
e
q
u
a
l
t
o
1
m
i
n
u
s
t
h
e
c
o
n
f
i
d
e
n
c
e
l
e
v
e
l
,
t
h
e
f
i
t
t
e
s
t
h
a
s
f
a
i
l
e
d
a
n
d
y
o
u
s
h
o
u
l
d
r
e
j
e
c
t
t
h
e
d
i
s
t
r
i
b
u
t
i
o
n
m
o
d
e
l
a
t
t
h
e
c
h
o
s
e
n
c
o
n
f
i
d
e
n
c
e
l
e
v
e
l
.
O
t
h
e
r
w
i
s
e
,
t
h
e
f
i
t
i
s
s
u
c
c
e
s
s
f
u
l
a
n
d
y
o
u
s
h
o
u
l
d
a
c
c
e
p
t
t
h
e
d
i
s
t
r
i
b
u
t
i
o
n
m
o
d
e
l
a
t
t
h
e
c
h
o
s
e
n
c
o
n
f
i
d
e
n
c
e
l
e
v
e
l
.
F
o
r
e
x
a
m
p
l
e
,
s
u
p
p
o
s
e
y
o
u
h
a
v
e
a
P
V
a
l
u
e
o
f
9
9
%
(
i
.
e
.
,
0
.
9
9
)
a
n
d
a
c
o
n
f
i
d
e
n
c
e
l
e
v
e
l
o
f
9
0
%
(
i
.
e
.
,
0
.
9
0
)
.
T
h
e
f
o
l
l
o
w
i
n
g
e
q
u
a
t
i
o
n
d
e
m
o
n
s
t
r
a
t
e
s
t
h
a
t
t
h
e
G
o
o
d
n
e
s
s
o
f
F
i
t
n
e
s
s
t
e
s
t
i
s
p
a
s
s
e
d
.
P
V
a
l
u
e
>
1
c
o
n
f
i
d
e
n
c
e
l
e
v
e
l
0
.
9
9
>
1
0
.
9
0
.
9
9
>
0
.
1
0
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
c
c
e
s
s
i
n
g
t
h
e
L
i
s
t
o
f
R
e
l
i
a
b
i
l
i
t
y
D
i
s
t
r
i
b
u
t
i
o
n
A
n
a
l
y
s
e
s
T
o
d
i
s
p
l
a
y
t
h
e
l
i
s
t
o
f
e
x
i
s
t
i
n
g
R
e
l
i
a
b
i
l
i
t
y
D
i
s
t
r
i
b
u
t
i
o
n
A
n
a
l
y
s
e
s
:
On
the
Reliabi
lity
Analyt
ics
Start
Page,
click
the
Reliabi
lity
Distrib
ution
link.
The
Select
a
Distrib
ution
Analys
is from
the
List
page
appears
.
From
the
Select
a
Distrib
ution
Analys
is from
the
List
page,
you
can run
the
Reliabi
lity
Distrib
ution
query
to view
a list of
existin
g
Reliabi
lity
Distrib
ution
Analys
es and
then
access
the
summa
ry for
any
analysi
s.
Alterna
tively,
you
can
click
the
New
Analys
is link
on the
Comm
on
Tasks
menu
to
begin
the
process
of
creatin
ga
new
Reliabi
lity
Distrib
ution
Analys
is.
V3.6.0.
0.0 Copyri
ght
19932014
Meridi
um,
Inc. All
rights
reserve
d.
A
spe
cts
of
the
Rel
iab
ilit
y
Dis
tri
but
ion
An
aly
sis
Lis
t
The
Select
a
Distrib
ution
Analys
is from
the
List
page
lets
you
run the
Reliabi
lity
Distrib
ution
query
to
access
a list of
existin
g
Reliabi
lity
Distrib
ution
Analys
es that
meet
your
query
criteria
.
The
Reliabi
lity
Distrib
ution
query
is
stored
in the
Meridi
um
APM
Catalo
g
folder \
\Public
\Meridi
um\Mo
dules\R
eliabilit
y
Manag
er\Anal
yses.
While
the
Reliabi
lity
Distrib
ution
query
can be
custom
ized
for
your
specifi
c
implem
entatio
n, the
baselin
e
Reliabi
lity
Distrib
ution
query
contain
s two
prompt
s:
Publis
hed
Analys
es and
Last
Update
d By.
These
prompt
s
appear
at the
top of
the
page as
dropdown
lists
that
contain
the
various
options
.
The
Publis
hed
Analys
es list
contain
s the
followi
ng
options
:

Any
(%):
Will
cause
the
query
to
return
all
Reliabi
lity
Distrib
ution
Analys
es,
either
publish
ed or
unpubli
shed.
Yes
(Y):
Will
cause
the
query
to
return
only
publish
ed
Reliabi
lity
Distrib
ution
Analys
es.
No
(N):
Will
cause
the
query
to
return
only
unpubli
shed
Reliabi
lity
Distrib
ution
Analys
es.
The
Last
Update
d By
list
contain
s the
followi
ng
options
:
Your
user
name,
which
is
selecte
d by
default
and
will
cause
the
query
to
return
only
the
Reliabi
lity
Distrib
ution
Analys
es that
were
last
update
d by
you.
The
user
name
of any
user
who
last
update
d any
Reliabi
lity
Distrib
ution
Analys
is,
which
will
cause
the
query
to
return
only
the
Reliabi
lity
Distrib
ution
Analys
es that
were
last
update
d by
that
user.
The
[All
Users]
option,
which
will
cause
the
query
to
return
a list of
Reliabi
lity
Distrib
ution
Analys
es
update
d by
any
user.
Each
time
you
access
the
Select
a
Distrib
ution
Analys
is from
the
List
page,
the
values
that
appear
by
default
in the
prompt
s will
be used
to filter
the list.
After
you
select
differe
nt
criteria
, you
can
click
the
Run
Query
button
to run
the
Reliabi
lity
Distrib
ution
query
and
display
the
results
in a
grid at
the
bottom
of the
page.
Note:
Althou
gh the
results
are
returne
d by
the
Reliabi
lity
Distrib
ution
query,
query
page
size is
ignored
. The
entire
list of
analyse
s is
display
ed at
once.
The
default
Reliabi
lity
Distrib
ution
query
is
configu
red to
display
the
followi
ng
column
s of
inform
ation:
Analys
is ID,
Last
Update
d,
Update
d By,
and
MTBF.
You
can
click
any
hyperli
nked
analysi
s ID to
view
the
associa
ted
analysi
s
summa
ry. In
additio
n, you
can use
the
option
on the
Plots
menu
and the
Comm
on
Tasks
menu
to
perfor
m
various
tasks
for the
analyse
s in the
list.
Hint: If
desired
, you
can
custom
ize the
column
display
.
V3.6.0.
0.0 Copyri
ght
19932014
Meridi
um,
Inc. All
rights
reserve
d.
Pl
ots
Me
nu
The
Plots
menu
on the
Select
a
Distrib
ution
Analys
is from
the
List
page
contain
s the
followi
ng
links:
Probability: If
you select a
single
analysis, this
link displays
the Probability
Plot of that
analysis on the
Probability
Plot page. If
you selected
multiple
analyses, this
link displays
the Probability
Plots of those
analyses on
the Multiple
Distributions
Plot page.
Failure
Rate: If you
select a single
analysis, this
link displays
the Failure
Rate Plot of
that analysis
on the
Probability
Density
Function page.
If you selected
multiple
analyses, this
link displays
the Failure
Rate Plots of
those analyses
on the
Multiple
Distributions
Plot page.
PDF: If
you select a
single
analysis, this
link displays
the Probability
Density
Function Plot
of that analysis
on the
Probability
Density
Function page.
If you selected
multiple
analyses, this
link displays
the Probability
Density
Function Plots
of those
analyses on
the Multiple
Distributions
Plot page.
CDF: If
you select a
single
analysis, this
link displays
the
Cumulative
Density
Function Plot
of that analysis
on the
Probability
Density
Function page.
If you selected
multiple
analyses, this
link displays
the
Cumulative
Density
Function Plots
of those
analyses on
the Multiple
Distributions
Plot page.
1993-2014
Meridium, Inc.
All rights
reserved.
Com
mon
Tasks
Menu
The Common
Tasks menu on
the Select a
Distribution
Analysis from
the List page
contains the
following
links:
New Analysis:
Displays the
Reliability
Distribution Builde
which guides you
through the process
creating a new
Reliability
Distribution Analys
Open Analysis:
Lets you locate an
existing Reliability
Distribution analys
using the Find a
Reliability
Distribution Analys
window.
Publish Analyse
Publishes the select
analysis or analyses
If you select one or
more analyses that
already published, t
link reads Unpublis
Analyses and will
unpublish the selec
analysis.
Delete Analyses
Deletes the currentl
displayed analysis.
Send To: Displa

a submenu with
options that let you
provide a link to th
current page on you
desktop (create
shortcut), in an ema
message, or on a
Home Page.
Help: Displays
context-sensitive H
topic for the Select
Distribution Analys
from the List page.
Guidelines:
Displays the
Reliability Concept
which provide
reliability workflow
and descriptions of
reliability concepts
Note: The Save

Analysis and Save
Analysis As links ar
always disabled.
V3.6.0.0.0 Copyright 19932014 Meridium, Inc

Opening
an
Existing
Reliabilit
Distribut
on
Analysis
To open a Reliabili
Distribution Analys
summary:
On the Reliabil
Analytics Start Pa
click the Reliability
Distribution link.
The Select a
Distribution Analys
from the List page
appears.
At the top of the

the fields provided,
criteria that you wa
for limiting the list
Distribution Analys
available criteria w
depending on how
Reliability Distribu
has been configured
Click the Run Q

button.
Meridium APM run

and displays the res
grid at the bottom o
page.
In the Analysis
the analysis ID of t
you want to open.
The Reliability Dis

Summary page app
When you open an

the analysis will dis
calculations that we
the analysis. If you
underlying query o
update calculations
changes to the unde
must reload the ana
opening it.
V3.6.0.0.0 - Copyri
Meridium, Inc. All
Opening
Multiple
Distribut
Analyses
To open multiple ex
Distribution Analys
On the Select a
Analysis from the L
top of the page, in t
By list, select the u
want to return a list
Analyses.
Note: Additional fie

the baseline query h
modified. If additio
available, use them
results as desired.
Click the Run Q
Meridium APM run

Distribution query
the grid in the main
Select the rows

Analyses that you w
On the Plots me
graph for which yo
analyses:
Probability plot
Failure Rate plo

PDF plot
CDF plot
The selected analys

Distributions Plot p
corresponding plot
From the Multiple D
View the de
the desired plot and
Point to a plot t
the plot represents,
gamma, and R2.
Customize the M
the standard graph
Click the link to

menu for which you
Distribution analys
Click the Show

the failure dates for
failure datapoint to
the piece of equipm
Click the New A

or the Guidelines li
V3.6.0.0.0 - Copyri
rights reserved.
Using th
Distribut
Using the Reliabilit

new Distribution A
Based on a new
From manually
You can access the

a Distribution Ana
Distribution Summa
V3.6.0.0.0 - Copyri
reserved.
Creatin
Analysis
Dataset
To create a new Dis

query or dataset:
On the Reliabil
Distribution Analy
menu, click the New
The Reliability Dis

Welcome screen.
Hint: If you do not

access the builder, s
box.
Click the Next b
The Select Data So
Select one of th
Failure data wil

when you click the
query in the Catalo
I will create a n
option, when you c
can design a new q
building a new que
Failure data wil

when you click the
dataset in the Catal
query that included
select either of thos
in unformatted mod
I will create a n
option, when you c
you can design a ne
details on building
After you have sele

Select screen of the
Click the Next b
The Select Data Fo
If the failure da
-or-
If the failure data c

contains time to fai
Click the Next b
The Failure Type sc
If the piece of e
as new) option.
-or-
If the piece of equip

good as old) option
(e.g., for heat excha
Click the Next b
The Select Failure F

selected on the prev
In the Asset ID
character field.
In the Installatio
equipment was inst
In the Failure D
the Out of Service d
If you selected
you have made this
Number of Sub
you selected in the
Note: If this field is

every analyzed piec
failed elements. Mo
Number of
Replacement?:
Logical. A replacem
Click the Next b
-or-
If the selected quer
The Provide Inform
In the Downtim
In the Time Un
Note: The time unit

change the units for
Click the Finish
The system validate
On the Commo
V3.6.0.0.0 - Copyri
Creatin
To create a new Dis
On the Reliabil
The Reliability Dis
Hint: If you do not
Click the Next b
The Select Data So
Select the I will
The Select Data Fo
If the failure da
-or-
If the failure data c
Click the Next b
The Failure Type sc
If a replacemen
-or-
If no replacement is
Click the Finish
A blank Failure Da
Enter the inform
A minimum of t
If you enter dow

Analysis Informatio
The units of day

Click OK.
Note: A minimum o
ation field of the current record.
The system generat
On the Commo
V3.6.0.0.0 - Copyri
Creatin
The following instr
mount of time that the pieces of equipment are in operation during the specified analysis period.
ure Data.
dialog box, which will prompt you to enter the cost data. The Optimal Value inflection point is identified on
ou click this link, Meridium APM will save any changes that you made to the analysis since it was last saved.
u can do so via the Failure Type dialog box.
or heat exchangers, boiler tubes, or piping).
ion calculations are not supported for failures without replacement and that the results are not valid.
alculate the mean for a Weibull Distribution:
appropriate and the more likely that the fit will pass the test.
minus the confidence level, the fit test has failed and you should reject the distribution at the chosen
sed to calculate the mean for a Weibull Distribution:
(MLE).
odel is appropriate and the more likely that the fit will pass the test.
al to 1 minus the confidence level, the fit test has failed and you should reject the distribution at the chosen
isted along the x-axis. The timeline is intended to illustrate the general distribution of failures over time for
e specific information about failures and dates.
mple, in the following figure, the Analysis Period ends in February 1996, but failures that occurred after
figure able. The end date of the analysis period is indicated on the timeline by a green line if it is set to a
lysis. For input fields:
ord.
s are calculated by the Meridium APM system and cannot be modified.
n the Reliability Distribution Analysis. The values that you select to map on the Select Failure Fields and
th the column name in parentheses.
are involved in the failures.
et ID belonging to the piece of equipment that you added on the Assets tab or type the ID in the cell.
red.
d, etc. TTF values are calculated by the Meridium APM system based on the failure dates and are shown in
te the analysis.
ulations. You can modify this value manually.
ment. Select the check box if you want to censor the data in the selected row. When you create a Reliability
the time value from the last event to the end of the analysis. After the calculations for the analysis have been
check boxes will no longer be selected.
apped from a query or dataset or manually entered when you create the analysis.
resetting calculation of the time to failure. This column appears only when the failure type is Failures
nd is optional.
omponents, such as tubes in a heat exchanger bundle. The Number of Subcomponents column contains the
you create the analysis.
piece of equipment. Values in this field are read-only.
f the piece of equipment and is read-only.
his field are read-only.
cedure on a piece of equipment. PM Optimization does not calculate minor maintenance schedules, but
ailure modes and will not give accurate results for a Weibull analysis where Beta is less than 1.
y that a piece of equipment will fail.
ally enter the cost or select an existing query as the source of the cost data.
of equipment based on the Optimized Preventative Maintenance Interval is also displayed.

unplanned repair costs. This ensures that repairs are conducted in a cost-effective manner, minimizing risk
ense to do a PM at the interval specified. In particular, design flaws that manifest themselves as poor
t.
log box. PM Optimization is not available when Beta is less than or equal to one (Beta <= 1).
st box.
of equipment you are analyzing.
val.
t is that a piece of equipment will fail today. Then, using future values that you supply, the Meridium APM
d between the last replacement date (i.e., the last failure date) and the End Date of the Analysis Period.
tem will determine how likely it is that a piece of equipment will fail when it has reached that age.
ment will reach that likelihood of failing.
e calculated for all Distribution models. The Meridium APM system uses the following formula to determine
ou specify a failure probability, the Meridium APM system will use this value to calculate the future age of
n the CDF plot represents this function.
at time to the current age of the piece of equipment, and the resulting value is then used to calculate the
type of the Reliability Distribution Analysis is Failure with replacement, the number of subcomponents is 1.
u create the Reliability Distribution Analysis. The number of subcomponents appears in the Number of
specify an operating time that will be used for performing calculations. The operating time that you specify
ess the Probability of Equipment Failure page, you will have the option of changing the operating time or
he first time. If you have accessed the Probability of Equipment Failure page previously, you will not be
ill appear immediately after you click the Failure Probability link and will display the results of the last
here will be added to the Present Age of the piece of equipment to determine the Future Age for calculating
ating time of 365 days, Meridium APM will determine how likely it is that the piece of equipment will fail
Page
by the system using the Future Age that you specify and the information available for the Distribution
ecified Option.
the amount of time between the date in the Last Replacement column and the end date of the Analysis
value in the Future Age column is determined by adding the Operating Time you specified to the Present
resent age of the piece of equipment.

and the value in the Future Age column. The Future Failure Probability is based on the assumption that at
to recalculate values in the grid based on changes you make to any editable field. Note that when you
nge the probability via the Failure Probability Calculation dialog box, the values in the grid are recalculated
ected when the failure type is Failures Without Replacements.
ed Age
odify the Future Age and then recalculate the future probability of failure based on those changes.
s. You can recalculate failure probability for one or more pieces of equipment individually by modifying the
that was last used to perform the calculation. The unit of time corresponds to the Time Units that you have
e that will be added to the Present Age in order to determine the Future Age for which the failure probability
e failure probability of a piece of equipment when it is two years older than its Present Age, you would set
ce of equipment in the grid on the Probability of Equipment Failure page.
ability of Failure will be Reached

probability of failure, and the system will calculate the future age at which that probability of failure will be
uipment in the analysis. You can recalculate failure probability for one or more pieces of equipment
y Probability link.
d probability of failure. For example, type 50 to calculate the age at which a piece of equipment has a 50
em for each piece of equipment in the grid on the Probability of Equipment Failure page.
ure Probability and Future Failure Probability will only be calculated for pieces of equipment that have a
assumed for the number of sub-elements for each piece of equipment when using the Failures With
ts
w any of the following plots by clicking the associating link:
lly-censored datapoints that represent the analysis End Dates for the defined piece of equipment.
more about data censoring, click here.
bution Analysis, including the type of distribution and the distribution parameters. The value of R2 is also
sely the points fall to the least squares line, providing an indication of how confident one can be of
plays the probability (expressed as a percentage) that a failure will occur over a certain time period (CDF
the value from the cumulative distribution. Time used here refers to life data, not Calendar data.
n a log-log format. It reflects the standard technique for representing Weibull Distribution. Log-log format
clues to the presence of multiple failure modes. If a single or multiple inflection points exist in the data, then
ded in the analysis calculations and the upper and lower limits appear on the plot.
ality.
ts the number of failures between certain time periods, creating a curve that estimates how many failures you
obability vs. time. The term Probability is used here to describe the percent of the population that failed at
on such as, "What is the chance of a member of the population failing at exactly the time in question?"
the curve fit, what is the probability that failure will occur below or above a certain value?" The chart is a
he data, but it is not used often for analysis.
y of a piece of equipment failing over time, as shown in the following figure. The dotted line illustrates that
ility.
nt of the total population that will fail by time (t). Time used here refers to life data, not Calendar data. The
the Probability of Failure from 1 (R = 1-P). The Probability of Failure Plot shows the probability that the unit
e Rate for a given system based on the System Reliability calculations.
ility of failure at time(t)?" The CDF curve is the area under the PDF curve. The CDF accumulates all
ber of failures increases with increasing time, the slope of the curve is always positive, always increasing.
s from the list of analyses and generate a composite plot in order to compare the competing failure modes.
e of fault, dominates the survivor population from another type of fault. If the failure patterns overlap like
re included in the analysis calculations and the upper and lower limits appear on the plot.
ribution Report
tion Report, which you can use to view a summary of the results of a Reliability Distribution Analysis. When
t Viewer page.
items:
Catalog folder \\Public\Meridium\Modules\Reliability Manager\SSRS.
e Catalog folder \\Public\Meridium\Modules\Reliability Manager\Reports.
atalog folder \\Public\Meridium\Modules\Reliability Manager\Reports.
eports, which are stored in the Catalog folder \\Public\Meridium\Modules\Reliability Manager\Reports. The
orts, and the supporting queries collectively as the Reliability Distribution Report.
ution Report
page, on the Analysis Tasks menu, click the Generate Report link.
hat the Report Options dialog box looks like by default.
click OK.
er page.
eserved.
eport displays information that is stored in the Reliability Distribution record and Distribution records that
tion and the corresponding Reliability Distribution or Distribution record field whose data is displayed in the
Notes
None
None
None
None
None
None
None
None
None
None
None
None
The name of the Security

User associated with this
alue is displayed in the
eport.
eserved.
mation Section
ility Distribution Report displays information that is stored in each Distribution record that is linked to the
mber of one of four Distribution subfamilies in which records can exist: Exponential, Lognormal, Normal,
ion information for a Weibull record.
ecord that is linked to the Reliability Distribution:
rights reserved.
the <Variable> Distribution subsection, where <Variable> is the value that is stored in the Variable field in
istribution record. Throughout the documentation, we will refer to this subsection as the Distribution
bsection and the corresponding Distribution record field whose data is displayed in the report.
Field
Type
viation
rights reserved.
ters subsection, which contains information stored in a Distribution record (i.e., Weibull, Lognormal,
l, Exponential, or Normal record is linked to the Reliability Distribution record. The items that appear in the
he type of Distribution record. The following image displays an example of the Parameters subsection for a
bsection for a Weibull record whose data is displayed in the report. For a Weibull record, one row is
Eta, and Gamma.
bsection for a Lognormal record whose data is displayed in the report. For a Lognormal record, one row is
igma, and Gamma.
bsection for an Exponential record whose data is displayed in the report. For an Exponential record, one row
bsection for a Normal record whose data is displayed in the report. For a Normal record, one row is
, Standard Deviation.
rights reserved.
on
the Goodness of Fit Test subsection, which displays information from the corresponding Distribution
easure goodness of fit, so the Name column in the report is populated automatically with the value
h remaining item in the Goodness of Fit Test subsection and the corresponding Distribution record field
Field
rights reserved.
displays information that is stored in the Failure Data field in the Reliability Distribution record.
and they are stored in the Failure Data field in the Reliability Distribution record:
bution Report displays information that is stored in the Failure Data field in the Reliability Distribution
e Data section, and they are stored in the Failure Data field in the Reliability Distribution record:
bution Report displays the graphs that are displayed on the Reliability Distribution Summary page or
bility Distribution Summary page. The following image shows an example of the Probability Plot.
graphs:
Plot
tion Plot
014 Meridium, Inc. All rights reserved.
Results of a Reliability Distribution Analysis?
ty Distribution Analysis, the following options are available:
clude confidence intervals and parameters for the selected Distribution and goodness of fit measures.
be done by Least Squares or Maximum Likelihood (MLE).
s of Reliability plots (Probability of Failure, Failure Rate, Probability Density Function, and Cumulative
be displayed. In addition, you can select between 2 and 10 Distribution analyses and choose to view and
t types for the selected analyses using the Competing Failure Plots feature.
n Analyses can support Failures without Replacement, which are needed to calculate reliability for heat
iping, and other pieces of equipment where a repair does not necessarily involve changing the whole unit.
nance Optimization calculator can utilize the results of the Distribution analysis and allow you to input the
anned repair versus a planned repair. Based on the MTBF and the ratio of unplanned cost to planned cost, the
mal time to maintain equipment.
alculator can utilize the results of a Distribution Analysis; based upon MTBF, Beta, and the last Failure Date,
robability of equipment failure at the time in the future that you specify. The system also provides the
re life based upon a failure probability that the user specifies.
results, you can generate recommendations for the maintenance and reliability activities that should be
maintain best practices in your organization.
1993-2014 Meridium, Inc. All rights reserved.
ilure
of data for distributions is Time to Failure (TTF), which is also sometimes known as Time to Event (TTE) or
BF).
following timeline, where each number represents the amount of time that passes between failures.
23
38
16
22
44
32
Out of Service
stribution to this data. A Probability Density Function (PDF) is similar to a histogram of the raw TTF data:
urring between time 0 & 10.
curring between time 11 & 20.
occurring between time 21 & 30.
curring between time 31 & 40.
urring between time 41 & 50 (Out of service).
counts the number of failures between certain periods. This creates a curve, which you can examine and ask:
ow many failures can I expect to have? The answer: Between two and three failures. You are distributing the
e of the equipment so that at any given point in that life, you can calculate the probability that the equipment
ulation is generated based on the area under the curve, as shown in the previous graphic. In practice, the PDF
a way that the area under the curve is exactly one, and the number on the y-axis represents the number of
nit.
torical data: other pieces of equipment by the same manufacturer, other pieces of equipment in the same
es of equipment of the same type, etc. For example, suppose that you want to buy a new pump. You could
tion Analysis on the other pumps of the same model to predict the reliability of the new pump.
s a Probability Distribution Analysis?
dataset, or data that you manually enter, you can pull in an independent variable to generate a Probability
is. This type of analysis allows you to describe the Time to Failure (TTF) as a statistical distribution, which
rized by a specific pattern. Meridium APM Reliability supports four Distribution types: Weibull, Normal,
xponential.
sed in a Probability Distribution Analysis
e shows the typical data required for building and analyzing Reliability Distribution documents in Meridium
Description
Notes
Select the field that contains

Select a numeric field. This
the value you want to
is a required field.
analyze.
If desired, select a field
provides censoring
information. Select the field
from the data source that
Select a logical field. This
contains a value that
field is optional.
indicates censored values,
i.e. not included in the
Probability Distribution
analysis calculations.
If the data source is a query,

the name of the random
variable and the units of
measure will be prepopulated based on the
selection you made in the
Value field on the previous
screen. If you selected a
different data source, type
the name of the random
variable in the Random
Variable field and the units of
measure for the random
variable in the Units field.
Select the units of measure
for the random variable.
ng the List of Probability Distribution Analyses
isting Probability Distribution Analyses:
Reliability Start Screen, click the Probability Distribution link.
bility Distribution List page appears.
robability Distribution List page, you can run the Probability Distribution query to retrieve a list of
Distribution Analyses that exist in the database. From the list of analyses, you can access the analysis
or any analysis. Alternatively, you can click the New Analysis link on the Common Tasks menu to begin the
creating a new Probability Distribution analysis.
ects of the Probability Distribution Analyses List
bility Distribution List page lets you run the Probability Distribution query to access a list of existing
Distribution Analyses that meet your query criteria.
ility Distribution query is stored in the Meridium APM Catalog folder

eridium\Modules\Reliability Manager\Analyses. While the Probability Distribution query can be customized
ecific implementation, the baseline Probability Distribution query contains two prompts: Published Analyses
pdated By. These prompts appear at the top of the page as drop-down lists that contain the various options.
hed Analyses list contains the following options:
): Will cause the query to return all Probability Distribution Analyses, either published or unpublished.
: Will cause the query to return only published Probability Distribution Analyses.
Will cause the query to return only unpublished Probability Distribution Analyses.
pdated By list contains the following options:
er name, which is selected by default and will cause the query to return only the Probability Distribution
at were last updated by you.
r name of any user who last updated any Probability Distribution Analysis, which will cause the query to
the Probability Distribution Analyses that were last updated by that user.
l Users] option, which will cause the query to return a list of Probability Distribution Analyses updated by
you access the Probability Distribution List page, the values that appear by default in the prompts will be
er the list. After you select different criteria, you can click the Run Query button to run the Probability
n query and display the results in a grid at the bottom of the page.
ugh the results are returned by the Probability Distribution query, query page size is ignored. The entire list
is displayed at once.
Probability Distribution query is configured to display the following columns of information: Analysis ID,
ed, and Updated By. You can click any hyperlinked analysis ID to view the associated Probability
n Analysis summary. In addition, you can use the options on the Plots and Common Tasks menus to perform
ks for the analyses in the list.
sired, you can customize the column display.
s Menu
menu on the Probability Distribution List page contains the following links:
Probability: Displays a Probability Plot for the selected analysis.
PDF: Displays a Probability Density Function Plot for the selected analysis.
CDF: Displays a Cumulative Distribution Function Plot for the selected analysis.
Common Tasks Menu

Common Tasks menu on the Probability Distribution List page contains the following links:
New Analysis: Displays the Distribution Builder, which will guide you through the process of
creating a new Probability Distribution Analysis.
Open Analysis: Lets you locate an existing Probability Distribution Analysis using the Find a
Reliability Distribution Analysis window.
Publish Analyses: Publishes the selected analysis or analyses. If you select one or more analyses that
are already published, this link reads Unpublish Analyses and will unpublish the selected analysis.
Delete Analysis: Deletes the currently displayed analysis.
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 Probability Distribution List page.
Guidelines: Displays the Reliability Concepts, which provide reliability workflows and descriptions
of reliability concepts.
Note: The Save Analysis and Save Analysis As links are always disabled.
About the Multiple Distributions Plot Page for

a Probability Distribution Analysis
You can select one or more Probability Distribution Analyses (a minimum of 2 analyses and a maximum
of 10 analyses) from the list of existing analyses, select the desired plot type on the Plots menu, and
generate a composite plot in order to compare the distribution curves. The composite plot appears on the
Multiple Distributions Plot page.
From this page, you can do the following:
To display the selected Distribution Analyses as datapoints on the plot, click the Show
Failures link on the Plots menu. A Hide Datapoints link now appears on the Plots menu.
Pause on the distribution plot line to display a tool tip that shows summary details about the
Distribution Analysis, including the type of distribution and the distribution parameters.
Click the distribution plot line to access the Probability Distribution Results page for a
distribution.
To return to the list of Distribution Analyses, click the Back button.
Using the Distribution Builder

Using the Distribution Builder, you can create a new Probability Distribution Analysis:
Based on a new or existing query or dataset.
By manually entering failure data.
You can access the Distribution Builder either from the Probability Distribution List page
or from the Probability Distribution Results page.
Creating a Probability Distribution from

a Query or Dataset
To create a new Probability Distribution Analysis based on a new or existing query or
dataset:
On the Probability Distribution List page or on the Probability Distribution Results
page, on the Common Tasks menu, click the New Analysis link.
The Distribution Builder appears, displaying the Welcome screen.
Hint: If you do not want to view this screen the next time that you access the builder,
select the Dont show this page again check box.
The Select Data Source Type screen appears, displaying the options that are
available for entering the data for analysis in the Reliability Manager application.
Select one of the following options:

Failure data will be loaded using an existing Query. If you select this
option, when you click the Next button, you will be asked to find and
select the desired query in the Catalog.
I will create a new Query and use it to load the failure data. If you
select this option, when you click the Next button, the Query Builder will
appear so that you can design a new query. Click the Help button in the
Query Builder for details on building a new query.
Failure data will be copied from an existing Dataset. If you select this
option, when you click the Next button, you will be asked to find and
select the desired dataset in the Catalog. Note that if the dataset you choose
was created from a query that included installation or failure dates you will
not be able to select either of those columns in the analysis. To avoid this
problem, run the query in unformatted mode and then export to a dataset.
I will create a new Dataset and use it to load the failure data. If you
select this option, when you click the Next button, the Dataset Builder will
appear so that you can design a new dataset. Click the Help button in the
Dataset Builder for details on building a new dataset.
After you have selected or created the desired query or dataset, it appears
on the Select screen of the Distribution Builder.

The Select Data Fields screen appears.
In the Value list, select a numeric value from the list.

This is a required field. A random variable associates a
numerical value with every event. It describes a (possibly
infinite) set of different events having a related probabilistic
structure. The probability distribution of the random
variable is a function that maps each possible value of the
random variable to a particular probability.
If desired, in the Censored list, select a field that
indicates censored values (i.e., not included in the
Probability Distribution Analysis calculations). The selected
field must be a logical field.
The Specify Random Variable and Its Units screen appears.
Note that the name of the random variable and the units of
measure are pre-populated based on the selection you made
in the Value selection box on the previous screen.
Click the Finish button.
The system validates the field mappings and
generates the analysis. The Probability Distribution
Results page displays the results of the analysis.
On the Common Tasks menu, click the
Save Analysis link to save the analysis
results.
V3.6.0.0.0 - Copyright 1993-2014

Creating a
Probability
Distribution from
Manually Entered
Data
To manually enter the data for a Probability
Distribution Analysis:
On the Probability Distribution List page
or on the Probability Distribution Results
page, on the Common Tasks menu, click the
New Analysis link.
The Distribution Builder appears, displaying
the Welcome screen.
Hint: If you do not want to view this screen

the next time that you access the builder,
select the Dont show this page again check
box.
The Select Data Source Type screen
appears, displaying the options that
are available for entering the data for

analysis in the Reliability Manager
application.
Select the I will manually

enter data option, and click
the Finish button.
The Distribution Builder
closes, and a blank
Distribution Data grid
appears.
Enter the
information about the
random variables that
you want to include in
the analysis. By
default, the following
properties are listed on
the grid:

X: The
value
of the
random
variabl
e.
Censor
ed:
Select
the
check
box to
censor
data.
Ignore:
Select
the
check
box if
you do
not
want to
include
the data
on the
selecte
d row
in the
calculat
ions.
Remark
s:
Comme
nts
about
the
event.
To
enter
data,
you can
manual
ly type
the data
in the
cells or
you can
use the
clipboa
rd
operati
ons
(cut,
copy,
paste)
to
transfer
data to
the grid
from
other
applicat
ions.
C
l
i
c
k
O
K
t
o
s
a
v
e
t
h
e
d
a
t
a
a
n
d
g
e
n
e
r
a
t
e
t
h
e
a
n
a
l
y
s
i
s
.
N
o
t
e
t
h
a
t
a
m
i
n
i
m
u
m
o
f
t
h
r
e
e
f
a
i
l
u
r
e
d
a
t
a
p
o
i
n
t
s
i
s
r
e
q
u
i
r
e
d
t
o
p
e
r
f
o
r
m
a
c
a
l
c
u
l
a
t
i
o
n
o
r
y
o
u
w
i
l
l
r
e
c
e
i
v
e
a
w
a
r
n
i
n
g
m
e
s
s
a
g
e
a
n
d
t
h
e
a
n
a
l
y
s
i
s
w
i
l
l
n
o
t
b
e
g
e
n
e
r
a
t
e
d
.
T
h
e
D
i
s
t
r
i
b
u
t
i
o
n
D
a
t
a
g
r
i
d
c
l
o
s
e
s
,
a
n
d
t
h
e
s
y
s
t
e
m
g
e
n
e
r
a
t
e
s
t
h
e
a
n
a
l
y
s
i
s
a
n
d
d
i
s
p
l
a
y
s
t
h
e
s
u
m
m
a
r
y
p
a
g
e
.
On
the
Comm
on
Tasks
menu,
click
the
Save
Analys
is link
to save
the
analysi
s
results.
V3.6.0.
0.0 Copyri
ght
1993-
2014
Meridi
um,
Inc.
All
rights
reserve
d.
O
pe
nin
g
an
Exi
sti
ng
Pr
ob
abi
lity
Dis
tri
but
ion
An
aly
sis
To
open
an
existin
g
Probab
ility
Distrib
ution
analysi
s:
On
the
Reliabi
lity
Start
Screen,
click
the
Probab
ility
Distrib
ution
link.
The
Probab
ility
Distrib
ution
List
page
appear
s.
At the top
of the page, in
the fields
provided,
select the
criteria that
you want to
use for
limiting the
list of
Probability
Distribution
Analyses. The
available
criteria will
vary,
depending on
how the
Probability
Distribution
query has
been
configured.
Click the
Run Query
button.
Meridium
APM runs the
Probability
Distribution
query and
displays the
results in the
grid at the
bottom of the
page.
In the Analysis
column, click the
analysis ID of the
analysis that you w
to open.
The Probability
Distribution Result
page appears,
displaying the
selected analysis.
Note that when you

open an existing
analysis, the analys
will display the dat
and calculations tha
were last saved wit
the analysis. If you
want to reload the
underlying query o
dataset and update
calculations based o
any changes to the
underlying data, yo
must reload the
analysis after openi
it.

Overvie
w of the
Probabili
y
Distribut
on Result
Page
Note: Depending o
the type of
Distribution Analys
that is selected,
different types of
information will be
available on the
Probability
Distribution Result
page.
The Probability
Distribution Result
page contains the
following sections
information:
Analysis Inform
Distribution
Calculated Par
Kolmogorov-Sm
Goodness of Fit Tes
Probability Den
Function (PDF) Pl
Cumulative Den
Function (CDF) plo
In addition, the Pro

Distribution Result
provides the follow
menus: Plots, Distr
Options, Analysis T
Common Tasks.
V3.6.0.0.0 - Copyri
1993-2014 Meridiu
Analysi
Informat
Section
The Analysis Inform

section contains inf
that identifies the c
analysis, including
following:
Analysis Name:
selected Probability
Analysis.
Description: Th
the analysis as defin
analysis was saved.
Random Variab
the random variable
associates a numeri
every event and des
infinite) set of diffe
having a related pro
structure. You can c
random variable an
Units: The unit

measure the random
can change the rand
specify units.
Rename: Displa
Analysis dialog box
rename the analysis
V3.6.0.0.0 - Copyri
Meridium, Inc. All
Distribu
Section
The Distribution se
details about the se
type. It includes the
information:
Type: The type
Fit Method: Th
estimation method
the parameters for t
The method of fit f
Distribution Analys
Least Squares or M
Likelihood Estimat
Confidence Lev
selected to use conf
selected confidence
is listed here. The c
used to indicate tha
model to fit with a
certainty.
Mean: The aver

distribution. This v
using parameters in
Parameters section,
depending on the d
For example, the fo
is used to calculate
Weibull Distributio
Standard Devia
variability of the ra
around the mean.
Median: The m
distribution. This v
using parameters in
Parameters section,
depending on the D
For example, the fo
is used to calculate
Weibull Distributio
R2: The R-Squa

Coefficient, which
strength of a linear
measures how close
to the least squares
indication of how c
be of predictions m
V3.6.0.0.0 - Copyri
Meridium, Inc. All
Calcula
Paramete
Section
The Calculated Pa
contains the parame
correspond to the se
distribution type.
If confidence was s
and lower bounds a
parameter.
V3.6.0.0.0 - Copyri
Meridium, Inc. All
Kolmog
Smirnov
Goodness
Test Secti
The Kolmogorov-S
of Fit Test section c
results of the Good
test.
Statistic: A valu
exact the fit is. Typ
number is, the bette
P-Value: A valu
Meridium APM sys
interpreted as the p
statistic is due to ra
the higher the P-val
model is appropriat
the fit will pass the
Passed Goodne
or No that indicates
to the Test Name) w
distribution fits the
performed). If the P
equal to 1 minus th
test has failed and y
distribution at the c
Otherwise, the fit is
should accept the d
significance level.
V3.6.0.0.0 - Copyri
Meridium, Inc. All
Probabi
Function
Section
The Probability De
Plot section contain
Probability Density
To view the actual
Click the plot, o

PDF link.
V3.6.0.0.0 - Copyri
Cumula
Function
Section
The Cumulative De
section contains a p
Density Function (C
To view the actual
Click the plot, o

link.
V3.6.0.0.0 - Copyri
rights reserved.
Plots M
The Plots menu on

page contains the fo
Probability: Di
PDF: Displays
CDF: Displays
Note: You can also

generate a composi
V3.6.0.0.0 - Copyri
reserved.
Distribu
The Distribution O
Results page contai
Distribution Typ
you can select a dis
Parameters: Di
you can select the d
Fit Method: Dis

the Fit Method.
Confidence Lev
you can select to us
V3.6.0.0.0 - Copyri
Analysi
The Analysis Tasks

contains the follow
Change Units:
can specify the nam
units used to measu
Edit Data: Dis
Generate Repor
can select the eleme
Note: You must sav
Create Task: Di
new task for the cu
View Tasks: Dis

shows a list of all th
record.
View Analysis L
Rename: Displa
enter a new name a
View Recommen
you can view and m
the analysis.
V3.6.0.0.0 - Copyri
Commo
The Common Tasks

contains the follow
New Analysis: D
you through the pro
Analysis.
Note: If you create

summary page of a
been saved, the cha
new analysis will c
problem, save the e
Open Analysis:
Analysis using the
Save Analysis:
viewing a brand ne
display the Save An
you are viewing an
APM will save any
saved.
Save Analysis A
you can choose to s
Delete Analysis
Send To: Displ

link to the current
message, or on a H
Help: Displays
Distribution Result
Guidelines: Dis
reliability workflow
V3.6.0.0.0 - Copyri
About t
Window
The Distribution D
with a Probability D
Distribution Data w
the analysis. For in
For an analysis
the information retu
For an analysis
the information sto
For an analysis
window displays th
Other fields show v

read-only. All value
in the Distribution r
You can modify cer

cases, however, you
in the original data
system and cannot
The following imag
V3.6.0.0.0 - Copyri
Data M
Data Win
When you create a

Distribution Builde
dataset to certain va
you select to map o
then appear in the a
Note: If the analysi

columns that are no
will appear in the D
parentheses.
The following char

Distribution Builde
V3.6.0.0.0 - Copyri
Accessin
Window
To access the Distri
On the Probabi
Edit Data link.
The Distribution D
V3.6.0.0.0 - Copyri
Aspects
Window
Note: You can grou
By default, the follo

on the Distribution
Datasheet: The
associated with the
privileges, after you

save any changes. T
analysis.
X: The value of
dataset using the or
Censored: A va
censored, meaning
time of the piece of
data on the selected
query or dataset as
beginning of the An
to the end of the an
each time that the q
censored.
Regardless of the d
For MLE (M
one (1) less than th
For Least Squar

total number of dat
Ignore: A value
excluded from the a
excluded from the a
can modify this val
Note: A minimum o
number of ignored
events marked as ig
Remarks: Comm
the text editor.
V3.6.0.0.0 - Copyri
Modifyi
Units
To change the rand
On the Probabil
link.
The Random Variab
Type the name
Type the corres

Click OK.
The system recalcu
V3.6.0.0.0 - Copyri
About t
On the Plots menu

clicking the associa
Failure Probabi
PDF Plot
CDF Plot
While viewing any
Click any datap
Censor a datapo
here.
Customize the a
Pause on the dis

type of distribution
strength of a linear
indication of how c
V3.6.0.0.0 - Copyri
Failure
The Probability plo

(expressed as a perc
Occurrence % used
refers to life data, n
This plot shows the

representing Weibu
(GOF). Data overla
points exist in the d
V3.6.0.0.0 - Copyri
PDF Plo
The Probability De
time periods, creati
time units. This plo
population that fail
"What is the chance
PDF shows the curv

failure will occur b
the variance or spre
V3.6.0.0.0 - Copyri
CDF Plo
The CDF plot is a l

Probability is used
refers to life data, n
Cumulative Distrib
time(t)?" The CDF
the point in time in
is always positive,
V3.6.0.0.0 - Copyri
Overvie
The baseline Merid

a summary of the re
Report, it will appe
The Probability Dis
The main repor

\\Public\Meridium\
The subreport, S
\\Public\Meridium\
The supporting
folder \\Public\Mer
ProbabilityD
Weibull Distrib
Lognormal Dist
Normal Distribu
Exponential Dis
Throughout this do
collectively as the P
The Probability Dis

Distribution family
the ENTY_KEY an
automatically to the
you run the main re
need to supply the E
subreport (i.e., Cata
The Probability Dis
Analysis Summ
Statistical Distr
Distribution Da
Plots
V3.6.0.0.0 - Copyri
Runnin
You can run the Pro

Analysis.
To run the Probabil
On the Probabil
The Report Options

like by default.
Select the desir
The Probability Dis
V3.6.0.0.0 - Copyri
Analysi
The Analysis Summ

Distribution record
Lognormal, Norma
The following table

whose data is displa
V3.6.0.0.0 - Copyri
Overvie
Section
The Statistical Dist

stored in the Distrib
displays an exampl
The following subs

Distribution
Parameters
Goodness of Fi
V3.6.0.0.0 - Copyri
Distribu

stored in the Distrib
The following imag
The following table

displayed in the rep
V3.6.0.0.0 - Copyri
Parame

record. The type of
Lognormal, Expone
record.
The following table

One row is displaye
The following table

For a Lognormal re
The following table

report. For an Expo
The following table

a Normal record, on
V3.6.0.0.0 - Copyri
Goodne

the Distribution rec
The Kolmogorov-S
automatically with
Test subsection and
V3.6.0.0.0 - Copyri
Distribu
The Distribution D
Distribution record
The following valu

Distribution record
X (i.e., the Rand

Median Rank
Censored
Ignored
Remarks
V3.6.0.0.0 - Copyri
Plots Se
The Plots section o

page or accessed vi
Probability Plot gra
The Plots section d
Probability Plot
Probability Den
Cumulative Dis
V3.6.0.0.0 - Copyri
Overvie
System Reliability
Monte Carlo simula
System Reliability
When you are c

construction of the
For existing sys

production output.
Using a System Re
Estimate the ov
Use equipment
Add maintenanc
View a graphica
Model different
V3.6.0.0.0 - Copyri
Monte C
Meridium APM Sy
common statistical
When you create a
generated at random
projected system re
Consider a simple e
one through six. Th
This means that ma
But is the mathema

probability, such as
To determine the ac
that you did this an
result, it would still
approximate.
A Monte Carlo sim

and lets you specify
the number of itera
simulate conditions
representation of th
V3.6.0.0.0 - Copyri
Compon
A System Reliabilit
System Reliability
main elements of th
System Reliabil
Reliability Analysis
records that make u
Scenario: A rep
all the identifying i
following compone
Diagram: A
between them. A D
physical system dev
contains one Diagra
A Diagram is repre
System Asset, and S
make up the Diagra
Risk: A com
and includes Time t
the identifying info
Action: A comp
condition-based ma
represented by reco
which contain all th
Global Event:
efficient by providi
represented by a Sy
Resource: A com
a System Reliabilit
Simulation Res
are stored in System
V3.6.0.0.0 - Copyri
System
To develop a System
Develop Scenar
To develop a Scena
model different des
Run simulation
You can perform a

elements included i
Evaluate results
Running the simula

of each Scenario re
Modify Scenari
By modifying Scen
step as many times
Make recomme
After you have mod

reliability. You can
V3.6.0.0.0 - Copyri
About t
To make this docum

example of a System
Our System Reliab
Collects water f
Runs the water
Note: In this examp
For our example, w

Scenario A.
Scenario B.
Scenario C.
In addition to these
Bearing: A repl
Seal: A replacem
Mechanic: A m
Vibration Techn
V3.6.0.0.0 - Copyri
Scenari
Scenario A represen
Water Source:
represented by an A
Water Pump: Pu
Water Tank: Sto
Bottling Subsys
component is repre
Link: Combines
Subsystem to run. T
V3.6.0.0.0 - Copyri
Scenari
When the Water Pu

Seal Failure.
Bearing Failure
Impeller Failure
Every time the Wat

replacement as the
Unplanned Res
Planned Resour
V3.6.0.0.0 - Copyri
Scenari
There are no Action
V3.6.0.0.0 - Copyri
Scenari
The physical mode

Risks.
V3.6.0.0.0 - Copyri
Scenari
The same Risks are
V3.6.0.0.0 - Copyri
Scenari
For Scenario B, the
Replace Seal: A
Vibration Analy
Analysis Action.
Redesign Impel
V3.6.0.0.0 - Copyri
Scenari
The physical mode

Water Pump 2:
Scenario C.
Sensor 1: Moni
has stopped running
Sensor 2: Moni
indicating that Pum
Switch 1: Is init
Tank. When deactiv
Switch 2: Is init
When deactivated b
V3.6.0.0.0 - Copyri
Scenari
The same Risks are
V3.6.0.0.0 - Copyri
Scenari
There are no Action
V3.6.0.0.0 - Copyri
What C
By comparing Scen
Scenario A represen
system:
Scenario B prop
Scenario C prop
By modeling and co
Note that this exam

continue to use this
create a more comp
V3.6.0.0.0 - Copyri
About t
In this area of the d

Analysis document
Note: In these topic
The following topic
Example System
Example System
Example System
Example System
Example System
Example System
Example System
Example Switch
Example Risk D
Example Action
Example System
Example System
V3.6.0.0.0 - Copyri
Exampl
Like all System Re

Name: System
Currency: $
Start Date: 1/1/
Period: 7 Years
Iterations: 1000
Time Analysis T
Confidence (%)
Histogram Bins
Enable Event L
Random Seed: T
V3.6.0.0.0 - Copyri
Exampl
The following table
V3.6.0.0.0 - Copyri
Exampl
Each Scenario in ou
the Bottling Lines,
V3.6.0.0.0 - Copyri
Exampl
The following table
1. All Bottling Lin
V3.6.0.0.0 - Copyri
Exampl
The following data
Name: Water Ta
Production Con
Initial Quantity
Time to Empty:
Time to Empty
Time to Refill:
Time to Refill U
V3.6.0.0.0 - Copyri
Exampl
The following data

Name: Link
Minimum Prede
V3.6.0.0.0 - Copyri
Exampl
The following table
V3.6.0.0.0 - Copyri
Exampl
The following table
V3.6.0.0.0 - Copyri
Exampl
The following table
Note: The Source c
V3.6.0.0.0 - Copyri
Exampl
The following table
Note: The Source c
1. When you asso

Correction Cost fie
V3.6.0.0.0 - Copyri
Exampl
The following table
V3.6.0.0.0 - Copyri
Exampl
The following table
V3.6.0.0.0 - Copyri
Accessin
The Select a System
To access the list of
On the Reliabil
The Select a System
V3.6.0.0.0 - Copyri
Aspects
The Select a System
The System Reliab

contains two promp
The Published Ana
Any (%): Will c
Yes (Y): Will ca
No (N): Will ca
The Last Updated B
Your user name

The user name
The (All Users)
Each time you acce

Reliability query an
Note: Although the
The default System

Analysis summary.
V3.6.0.0.0 - Copyri
Commo
The Common Tasks
New Analysis: D
Open Analysis:
Analysis ID column
Publish Analyse
Note: If you have s

the name of the link
Delete Analyses
Send To: Displa

Help: Displays
V3.6.0.0.0 - Copyri
ty Analysis Example. Throughout the documentation, we refer to the page names without the text System
About N
From the Select a S
lts are displayed.
m to different locations on the Diagram Canvas.
the System Reliability Scenarios - Global Events page.
ions:
llowing plots are displayed.
e recommend that you rerun the simulation to ensure that valid results are displayed.
am Validation Results dialog box.
m for any Scenario is invalid, detailed results will be displayed on the Diagram Validation Results dialog box
nerated.
bility Analysis, you will be prompted to save your changes before the Recommendations page will be
TTF and TTR distributions from the source distribution.
tem Reliability Analysis. For example, if you open a System Reliability Analysis from the Select a System
a System Reliability Analysis from the List page will be displayed, not the System Reliability Summary page.
h datasheet you are viewing.
longing to the analysis. Rather than saving these records individually, you will need to save the entire
ALL records that are linked to it, either directly or indirectly. In other words, when you save a System
Analysis link is enabled on the Common Tasks menu. Additionally, when you navigate away from System
es in System Reliability, you can manage the components that belong to an analysis, including adding,
element are deleted as well. If you delete a Resource, any linked System Resource Usage records will be
ut the component will not be deleted from the database until you save the analysis. In other words, when you
omponent and do not save the analysis, your deletion will be discarded.
e away from System Reliability, if the analysis contains unsaved changes, you will be prompted to save those
process.
will serve as inputs to the simulation and will affect the simulation results. You can modify the analysis
ld. You can modify the Scenario and include it in your System Reliability Analysis, or you can delete the
nts, Switch elements, and Asset elements).
s the name of the System Scenario record that you copied.
ontent of this dialog box is controlled by the default datasheet defined for the System Scenario family.
em record, which is linked to System Subsystem, System Sensor, System Buffer, System Link, System
record. Therefore, after you have created a Scenario, there is no manual step required for creating a Scenario
m on the System Reliability Scenarios - Grid page.
e Meridium APM database when you add each element to the Diagram. Click the hyperlinked element in the
e Diagram you want to access.
iagram. When the Diagram is complete, the Diagram Canvas will contain a visual representation of the
ble on the Diagram Canvas itself, including the following features.
ag the element to the desired location.
to import into the Diagram.
lysis to import into the Diagram.
the Diagram.
e System Reliability Scenarios - Diagram page.
are displayed.
grid lines on the Diagram Canvas.
ments between lines. This option appears on the menu only when the grid lines are displayed.
from the associated Reliability Distribution Analysis or Reliability Growth Analysis.
nalysis to import.
on Analysis to import.
only when you right-click an imported element.
NO options will appear on the shortcut menu.
s - Diagram page, you can use the overview feature to display a more compact view of the Diagram.
s currently shown on the Diagram Canvas.
do so, the view on the Diagram Canvas will change to reflect your location within the Diagram on the
Diagram Canvas. The header text of the Properties pane will indicate which element is selected by showing
selected element. For example, in the following image, the value in the Name field is Asset, so the
n generically as the Properties pane.
ciated with the selected element. For each row, you will see a label on the left and a text box on the right.
box is Asset.
ame field is Asset.
o view the fields alphabetically, you can click the
n click the
button. The following image shows the Properties pane
button. Each category can be collapsed by clicking the minus sign (-) or expanded by clicking
ord associated with it, the Distributions category does not appear.
box and then modify the value in the associated field. If a value already exists in a field, it will be
d for the selected field will be displayed. For example, in the following image, the help text that is
am Canvas. When you select an element, the Properties pane will display the fields that belong to the record
n the associated record in the Properties pane:
that Asset. The following table lists:

Canvas. The table is organized by the categories that are displayed when you view the Properties pane in a
be displayed in the Distributions category in the Properties pane. In some cases, depending upon which
u can use the Notes column in the table to view any exceptions.
that if the value in a row is not stored in a record, the table contains the following text: This row does not
s not stored in a field, the table contains the following text: This row does not display any values from a
cord or more than one System Risk record associated with it.
u selected the Water Source element in Scenario A.
that Buffer. The following table lists:
iagram Canvas. The table is organized by the categories that are displayed when you view the Properties
yed in that row.
ed if you selected the Water Tank element in Scenario A.
ted to that Link. The following table lists:

the Diagram Canvas. The table is organized by the categories that are displayed when you view the
hat row.
displayed if you selected the Link element in Scenario A.
mation related to that Sensor. The following table lists:
Sensor on the Diagram Canvas. The table is organized by the categories that are displayed when you view
value is displayed in that row.
ould be displayed if you selected the Sensor 1 element in Scenario C.
plays information related to that Subsystem. The following table lists:
elect a Subsystem on the Diagram Canvas. The table is organized by the categories that are displayed when
cord whose value is displayed in that row.
e that would be displayed if you selected the Diagram for Scenario A subsystem in Scenario A.
displays information related to that Switch. The following table lists:
n you select a Switch on the Diagram Canvas. The table is organized by the categories that are displayed
. Note that if the value in that row is not stored in a record, the table displays the following text: This row
t row. Note that if the value in a row is not stored in a field, the table displays the following information:
row.
Notes
None
None
None
None
None
None
None
ost None
ost
None
This row displays the

m a number of System
Action records that

are linked to the
selected Switch
record. When you
click inside the
Number of Actions
cell, the button
appears, which you
can click to display
the Action Editor
window, where you
can create, modify, or
delete System Action
records that are
linked to the selected
Switch record.
This row displays the

number of System
Risk records that are
linked to the selected
Switch record. When
you click inside the
Number of Risks cell,
the button appears,
m a which you can click
to display the Risk
Editor window,
where you can create,
modify, or delete
System Risk records
that are linked to the
selected Switch
record.
None
isplayed if you selected the Switch 1 element in Scenario A.
eserved.
os - Diagram page provides a hierarchical view of the elements in a Diagram. This view is especially useful
bsystems.
e. In this case, the Diagram Hierarchy pane would look like this:
splay that element on the Diagram Canvas. For example, if you clicked Bottling Line 1, the element that
Canvas as shown in the following image.
eserved.
m Palette pane contains icons that represent the physical elements of the Diagram. You can select an element
ts properties and include it in the Diagram. The following icons are available.
eserved.
ase the display area of the Diagram Canvas. You can do so by hiding the Diagram Hierarchy, Diagram
on.
e's original position. For example, the following image shows the Diagram Hierarchy pane after it has been
side of the screen.
want to display.
pane will disappear again. You can lock the pane back into the display position by clicking the button again.
eserved.
y adding elements and connections. You have two options for adding elements to a Diagram:
he Diagram Palette pane. When you add an element in this way, the Meridium APM system will create a
w record will be linked to the System Subsystem that represents the Diagram.
at already exist in the Meridium APM database. When you add an element in this way, the Meridium APM
populate information in a new record to represent the appropriate Diagram element. The original record will
w record will be linked to the System Subsystem record that represents the Diagram.
nnections between them to indicate their relationship to one another and their physical arrangement within
rights reserved.
the Diagram Palette Pane
Palette pane:
ne.
ent to the Diagram Canvas, and then release your mouse button to drop it in the desired location.
s selected automatically, so the Properties pane displays the properties of the new element. When you save
ecord will be created in the Meridium APM database to store information for that element.
ssets
existing Equipment and Functional Location records into a Diagram. You can import one or more records in
ated for each record that you import, and a new System Asset record will be created to store information for
tional Location record will be mapped to the System Asset record.
tribution Analysis or Reliability Growth Analysis associated with the Equipment or Functional Location
e Reliability Growth or Reliability Distribution record will be mapped to System Risk and Distribution
ng record is imported and linked to the System Asset record.
existing records:
port, and then click Asset.
or Functional Location.
ottom of the Find Items window.
t you want to import.
appears.
a list of records that you selected from the search results. The Options pane allows you to import the
alyses or Reliability Growth Analyses associated with the Equipment or Functional Location records that
tribution Analyses or Reliability Growth Analyses are associated with the selected Equipment or Functional
ons pane will be disabled.
ed import options.
nt is added to the Diagram for each selected Equipment or Functional Location record.
Mapped From Equipment or Functional Location
n existing Equipment or Functional Location record into the Diagram, a new System Asset record is created,
om the imported record is mapped to the System Asset record.
t displays the values that are imported from fields in Equipment or Functional Location records and the
cord and field to which they are mapped. All other values in System Analysis records are populated
default values.
Analysis
ield
Notes
None
orting an Equipment or Functional Location record, if you choose to import the Reliability Distribution
lity Growth Analysis associated with the Equipment or Functional Location record that you selected, values
liability Distribution Analyses or Reliability Growth Analyses will also be mapped to records in the System
s.
l be mapped are the same values that are mapped when a Reliability Distribution Analyses or Reliability
s imported without an Equipment or Functional Location record, with the following exception:
ue in the ID field of the Equipment or Functional Location record will be mapped to the Name field in the
et record. The values in the Analysis ID field in the Reliability Growth or Reliability Distribution record will
ped to the System Asset record.
porting a Reliability Distribution Analysis
ate new Asset elements by importing existing Reliability Distribution Analyses into a Diagram. You can
or more analyses in a single operation. One Asset element will be created for each record that you import,
System Asset record will be created to store information for that element. Fields from the Reliability
n record will be mapped to the System Asset record.
Reliability Distribution Analysis into a Diagram:
lick the Diagram Canvas, point to Import, and then click Reliability Distribution.
ems window appears, displaying the Reliability Distribution family in the Search In list.
Click the Find Now button.

search results appear at the bottom of the Find Items window.
Select the Reliability Distribution Analysis that you want to import. You can select multiple
Reliability Distribution Analyses, if desired.
Click the Open button.
A new Asset element is added to the Diagram for each selected Reliability Distribution Analysis.
Fields Mapped From a Reliability Distribution

Analysis
When you import an existing Reliability Distribution record into the Diagram, a new System Asset
record is created, and information from the imported record is mapped to the System Asset record.
Information is also mapped to System Risk and Distribution records, which are created when a record is
imported and linked to the System Asset record.
The following chart displays the values that are imported from fields in records from a Distribution
Analysis and the System Analysis record and field to which they are mapped. All other values in System
Analysis records are populated automatically with default values.
Note: If you import an Equipment or Functional Location record and import the Reliability Distribution
Analysis associated with that record, all of the fields in the following chart will be mapped except the
Analysis ID field will not be mapped to the Name field in the System Asset record.
R
el
ia
b
il
it
y
D
is
tr
i
b
u
ti
o
n
Reli Syst Syst Not

abili em em es
ty An An
Dist alys alys
ribu is is
tion Rec Rec
Ana ord ord
lysis
Fiel
Rec
d
ord
Fiel
d
A
n
al
y
si
s
R
e
c
o
r
d
Reli
abili
Syst
Ana
ty
em Na Non
lysis
Dist
Ass me e
ID
ribu
et
tion
Reli
abili
Ana Syst
ty
Na Non
lysis em
Dist
me e
ID Risk
ribu
tion
Fail
Fail
Reli ures
ure
abili Wit
Wit
Syst
ty hout
hout Non
em
Dist Rep
Rep e
Risk
ribu lace
lace
tion men
men
t
t
Dist Sho Dist Sho This
ribu rt ribu rt valu
tion Des tion Des e is
cript
cript map
ion
ion ped
fro
m
the
TTF
and
TT
R
Dist
ribu
tion
reco
rds
that
are
link
ed
to
the
Reli
abili
ty
Dist
ribu
tion
reco
rd to
the
corr
espo
ndin
g
TTF
and
TT
R
Dist
ribu
tion
reco
rds
that
are
link
ed
to
the
Syst
em
Risk
reco
rds.
Dist
ribu Dist Dist
tion ribu ribu
tion tion
Typ
e
Dist
ribu
tion
Typ
e
This
valu
e is
map
ped
fro
m
the
TTF
and
TT
R
Dist
ribu
tion
reco
rds
that
are
link
ed
to
the
Reli
abili
ty
Dist
ribu
tion
reco
rd to
the
corr
espo
ndin
g
TTF
and
TT
R
Dist
ribu
tion
reco
rds
that
are
link
ed
to
the
Syst
em
Risk
reco
rds.
Dist
ribu Unit Dist Unit This
tion s
ribu s
valu
tion
e is
map
ped
fro
m
the
TTF
and
TT
R
Dist
ribu
tion
reco
rds
that
are
link
ed
to
the
Reli
abili
ty
Dist
ribu
tion
reco
rd to
the
corr
espo
ndin
g
TTF
and
TT
R
Dist
ribu
tion
reco
rds
that
are
link
ed
to
the
Syst
em
Risk
reco
rds.
Exp MT Exp MT This
one BF one BF valu
ntial
ntial
e is
map
ped
fro
m
the
TTF
and
TT
R
Dist
ribu
tion
reco
rds
with
a
Dist
ribu
tion
Typ
e of
Exp
one
ntia
l
that
are
link
ed
to
the
Reli
abili
ty
Dist
ribu
tion
reco
rd to
the
TTF
and
TT
R
Dist
ribu
tion
reco
rds
with
a
Dist
ribu
tion
Typ
e of
Exp
one
ntia
l
that
are
link
ed
to
the
Syst
em
Risk
reco
rds.
Mu
Mu
Log
Log
This
nor Sig nor Sig valu
mal ma mal ma e is
map
Ga
Ga ped
mm
mm fro
m
a
a
the
TTF
and
TT
R
Dist
ribu
tion
reco
rds
with
a
Dist
ribu
tion
Typ
e of
Log
nor
mal
that
are
link
ed
to
the
Reli
abili
ty
Dist
ribu
tion
reco
rd to
the
TTF
and
TT
R
Dist
ribu
tion
reco
rds
with
a
Dist
ribu
tion
Typ
e of
Log
nor
mal
that
are
link
ed
to
the
Syst
em
Risk
reco
rds.
Mea
Nor n
Nor
mal
mal
Stan
dard
Dev
Mea
n
This
valu
Stan e is
dard map
Dev ped
iatio
n
iatio fro
n
m
the
TTF
and
TT
R
Dist
ribu
tion
reco
rds
with
a
Dist
ribu
tion
Typ
e of
Nor
mal
that
are
link
ed
to
the
Reli
abili
ty
Dist
ribu
tion
reco
rd to
the
TTF
and
TT
R
Dist
ribu
tion
reco
rds
with
a
Dist
ribu
tion
Typ
e of
Nor
mal
that
are
link
ed
to
the
Syst
em
Risk
reco
rds.
Beta
Beta
Wei
Wei
This
bull Eta bull Eta valu
e is
Ga
Ga map
mm
mm ped
fro
a
a
m
the
TTF
and
TT
R
Dist
ribu
tion
reco
rds
with
a
Dist
ribu
tion
Typ
e of
Wei
bull
that
are
link
ed
to
the
Reli
abili
ty
Dist
ribu
tion
reco
rd to
the
TTF
and
TT
R
Dist
ribu
tion
reco
rds
with
a
Dist
ribu
tion
Typ
e of
Wei
bull
that
are
link
ed
to
the
Syst
em
Risk
reco
rds.
Importing a Reliability Growth Analysis

You can create new Asset elements by importing existing Reliability Growth Analyses into a Diagram.
You can import one or multiple analyses in a single operation. One Asset element will be created for each
record that you import, and a new System Asset record will be created to store information for that
element. Fields from the Reliability Growth record will be mapped to the System Asset record.
To import a Reliability Growth Analysis into a Diagram:
Right-click the Diagram Canvas, point to Import, and then click Reliability Growth.
The Find Items window appears, displaying the Reliability Growth family in the Search In list.
Click the Find Now button.

The search results appear at the bottom of the Find Items window.
Select the Reliability Growth Analysis that you want to import. You can select
multiple Reliability Growth Analyses, if desired.
Click the Open button.
A new Asset element is added to the Diagram for each selected Reliability Growth
Analysis.
Fields Mapped From a Reliability

Growth Analysis
When you import an existing Reliability Growth record into the Diagram, a new System
Asset record is created, and information from the imported record is mapped to the
System Asset record. Information is also mapped to System Risk and Distribution records,
which are created when a record is imported and linked to the System Asset record.
The following chart displays the values that are imported from fields in a Reliability
Growth record and the System Analysis record and field to which they are mapped. All
other values in System Analysis records are populated automatically with default values.
Note: If you import an Equipment or Functional Location record and import the
Reliability Growth Analysis associated with that record, all of the fields in the following
chart will be mapped except the Analysis ID field will not be mapped to the Name field in
the System Asset record.
R
el
ia
b
il
it
y
G
r
o
w
t
h
R
e
c
o
r
d
F
ie
l
d
Syst
Syst em
em An
An alys
Not
alys is
es
is Rec
Rec ord
ord Fiel
d
Syst
Ana
em Na Non
lysis
Ass me e
ID
et
Ana Syst
Na Non
lysis em
me e
ID Risk
Sho Dist
rt ribu
Des tion
cript
ion
Sho This
rt valu
Des e is
cript map
ion ped
to
the
TTF
Dist
ribu
tion
reco
rd
that
is
link
ed
to
the
Syst
em
Risk
reco
rd
and
app
ears
in
the
TTF
colu
mn
on
the
Syst
em
Reli
abil
ity
Sce
nari
os Risk
s
pag
e.
Fina Exp MT
l
one BF
MT ntial
BF
This
valu
e is
map
ped
to
the
TTF
Dist
ribu
tion
reco
rd
that
is
link
ed
to
the
Syst
em
Risk
reco
rd
and
app
ears
in
the
TTF
colu
mn
on
the
Syst
em
Reli
abil
ity
Sce
nari
os Risk
s
pag
e.
Tim Dist Unit This
e
ribu s
valu
Unit tion
e is
s
map
ped
to
the
TTF
Dist
ribu
tion
reco
rd
that
is
link
ed
to
the
Syst
em
Risk
reco
rd
and
app
ears
in
the
TTF
colu
mn
on
the
Syst
em
Reli
abil
ity
Sce
nari
os Risk
s
pag
e.
Using the Import Subsystem Window

The Import Subsystem window contains a grid that displays a list of all records belonging
to the System Subsystem family. These records can be imported into the Diagram to create
a new Subsystem element.
The grid displays the following columns:

Subsystem Name: The value stored in the Name field of the System Subsystem
record.
Scenario Name: The value stored in the Name field of the System Scenario
record to which the System Subsystem record is linked.
Analysis ID: The value stored in the Analysis ID field of the System Analysis
record to which the System Subsystem record is linked.
Modified By: Displays the name of the Security User who last modified the
System Analysis record to which the System Subsystem record is linked, as
identified by the value in the LAST_UPBY_SEUS_KEY field in the System
Analysis record.
Modified Date: Displays the date when the analysis was last modified, as
identified by the value stored in the LAST_UPDT_DT field in the System
Analysis record to which the System Subsystem record is linked.
You can type a keyword or phrase in the Search text box to filter the list of System
Subsystem records that is displayed.
Importing a Subsystem
You can create new Subsystem elements by importing existing System Subsystem
records into the Diagram. You can import one or multiple records in a single
operation. For each System Subsystem record:
An element will be created in the diagram.
A copy of the record will be created and linked to the System Analysis
record.
All related records within the subsystem (e.g., System Asset records)
will also be imported. An element and copy of each record will be created
for each related record.
To import a Subsystem into the Diagram:
Right-click the Diagram Canvas, point to Import, and then click
Subsystem.
The Import Subsystem window appears, displaying a list of all records
belonging to the System Subsystem family.
In the Search text box, type a keyword or phrase to filter the list
of System Subsystem records displayed, if desired.
Select the row containing the System Subsystem record
that you want to import. You can select multiple records, if
desired.
Click OK.
The Import Subsystem window closes and a new Subsystem
element is added to the Diagram for each selected System
Subsystem record.

rights reserved.
About Connecting
Elements
After you add elements to a Diagram, you must connect the
elements to create the Diagram. Depending on the structure
of the system for which you are creating a Diagram, you
will want to connect elements to each other in a series or
parallel to one another.
Elements Connected in a Series

When you connect elements to each other in a series, every
element has one preceding connection and one succeeding
connection, with only one path from the Start element to the
End element. For example, in the following image of
Scenario A in the System Reliability Analysis Example, the
elements in the Diagram for Scenario A root subsystem are
connected in a series: every element between the Start and
End elements has one connection from an element and one
connection to an element, and you can reach the End
element from the Start element in only one way.
Elements Connected in Parallel

When you connect elements in parallel to one another, one
or more elements will be connected to multiple elements,
and there will be multiple paths from the Start element to
the End element. For example, in the System Reliability
Analysis Example, the Bottling Line elements in the
Bottling Subsystem root subsystem are connected in
parallel. In this case, the Start element and the Link element
are connected to three Subsystem elements: Bottling Line 1,
Bottling Line 2, and Bottling Line 3. Therefore, there are
three different paths from the Start element to the End
element, depending on which of the three Bottling Lines
that you pass through.

rights reserved.
Connecting Elements in a
Diagram
To connect two elements in a Diagram:
Using your pointer, for the desired element, point to the
black circle on the side from which you want to start the
connection.
Click the port and drag your pointer in the

direction that you want to create the connection.
An arrow will be drawn automatically in the
direction that you drag your pointer.
Continue dragging your pointer 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.
Release your mouse button to set

the connection.
V3.6.0.0.0 - Copyright 1993-2014

Deleting
Elements from a
Diagram
If desired, you can delete any element
from a Diagram. As you delete
elements from a Diagram, note that:
If you delete an Asset element
that was created by importing an
Equipment or Functional Location
record, when you delete the Asset
element, only the Asset element will
be deleted. The source record will not
be deleted. Additionally, if the source
record is linked to the System
Analysis record, the link will ALSO

be deleted.
You cannot delete the Start or the
End node.
To delete an element from a Diagram:
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.
Click the Yes button.
The element is deleted from
the Diagram.
rights reserved.
Deleting
Connections
Between
Elements
To delete a connector between
two elements in the Diagram:
Click the connector to
select it.
Note: This image shows the

Canvas Diagram with Hide
Grid option selected.
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.
Click the
Yes button.
The connection
is deleted from
the Diagram.
1993-2014
Meridium, Inc.
All rights
reserved.
Perfo
rming
Validat
ion
For the
Meridium
APM system to
run
simulations,
the elements
within
Diagrams must
be connected
correctly.
Problems
within a
Diagram, such
as 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
ALL Diagrams
associated with
any Scenario in
a given System
Reliability
Analysis.
The validation
process
evaluates each
Diagram in
two 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
reporte
d in the
validati
on
results.
An
error
that is
found
along
both
paths
will be
reporte
d twice.
To
validate
the
Diagra
ms
within
an
analysis
:
While
viewing
a
System
Reliabil
ity
Analysi
s on
any
page,
on the
Tools
menu,
click
the
Validat
e
Diagra
ms link.

If all
Diagra
ms are
valid,
the
Diagra
m
Validati
on
Results
dialog
box
will
display
a
messag
e
stating
that the
Diagra
ms are
valid.

If any
Diagra
ms are
invalid,
the
Diagra
m
Validati
on
Results
dialog
box
will be
display
ed,
where
you can
view
the
results
of the
validati
on.
V3.6.0.
0.0 Copyri
ght
1993-
2014
Meridiu
m, Inc.
All
rights
reserve
d.
A
spe
cts
of
the
Dia
gra
m
Val
ida
tio
n
Res
ults
Dia
log
Bo
x
The
Diagra
m
Validati
on
Results
dialog
box
display
s all the
errors
that
exist in
any of
the
Diagra
ms
within a
System
Reliabil
ity
Analysi
s.
The
Diagra
m
Validati
on
Results
dialog
box
display
s the
Error
grid,
which
display
s error
informa
tion,
organiz
ed first
by
Scenari
o and
then by
error
type.
Below
the
Error
grid,
the
followi
ng
buttons
appear:
O
K
:
C
l
o
s
e
s
t
h
e
D
i
a
g
r
a
m
V
a
l
i
d
a
t
i
o
n
R
e
s
u
l
t
s
d
i
a
l
o
g
b
o
x
.
C
o
p
y
D
e
t
a
i
l
s
:
C
o
p
i
e
s
t
h
e
c
o
n
t
e
n
t
o
f
t
h
e
E
r
r
o
r
g
r
i
d
s
o
t
h
a
t
y
o
u
c
a
n
p
a
s
t
e
t
h
e
e
r
r
o
r
i
n
f
o
r
m
a
t
i
o
n
i
n
t
o
a
n
o
t
h
e
r
a
p
p
l
i
c
a
t
i
o
n
o
r
f
i
l
e
,
s
u
c
h
a
s
a
M
i
c
r
o
s
o
f
t
W
o
r
d
o
r
M
i
c
r
o
s
o
f
t
E
x
c
e
l
d
o
c
u
m
e
n
t
.
Y
o
u
c
a
n
u
s
e
t
h
i
s
m
e
t
h
o
d
t
o
v
i
e
w
t
h
e
D
i
a
g
r
a
m
C
a
n
v
a
s
a
n
d
e
r
r
o
r
i
n
f
o
r
m
a
t
i
o
n
s
i
m
u
l
t
a
n
e
o
u
s
l
y
w
h
i
l
e
y
o
u
c
o
r
r
e
c
t
t
h
e
e
r
r
o
r
s
.
H
e
l
p
:
D
i
s
p
l
a
y
s
t
h
e
c
o
n
t
e
x
t
s
e
n
s
i
t
i
v
e
H
e
l
p
t
o
p
i
c
f
o
r
t
h
e
D
i
a
g
r
a
m
V
a
l
i
d
a
t
i
o
n
R
e
s
u
l
t
s
d
i
a
l
o
g
b
o
x
.
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
.
T
y
p
e
s
o
f
E
r
r
o
r
s
I
f
y
o
u
v
a
l
i
d
a
t
e
S
y
s
t
e
m
R
e
l
i
a
b
i
l
i
t
y
A
n
a
l
y
s
i
s
D
i
a
g
r
a
m
s
a
n
d
M
e
r
i
d
i
u
m
A
P
M
i
n
d
i
c
a
t
e
s
t
h
a
t
a
n
y
D
i
a
g
r
a
m
i
s
i
n
v
a
l
i
d
,
t
h
e
D
i
a
g
r
a
m
V
a
l
i
d
a
t
i
o
n
R
e
s
u
l
t
s
d
i
a
l
o
g
b
o
x
w
i
l
l
b
e
d
i
s
p
l
a
y
e
d
,
w
h
e
r
e
y
o
u
c
a
n
v
i
e
w
t
h
e
r
e
s
u
l
t
s
o
f
t
h
e
v
a
l
i
d
a
t
i
o
n
.
T
h
e
D
i
a
g
r
a
m
V
a
l
i
d
a
t
i
o
n
R
e
s
u
l
t
s
d
i
a
l
o
g
b
o
x
c
a
n
d
i
s
p
l
a
y
a
n
y
o
f
t
h
e
f
o
l
l
o
w
i
n
g
e
r
r
o
r
m
e
s
s
a
g
e
s
,
d
e
p
e
n
d
i
n
g
u
p
o
n
t
h
e
c
o
n
d
i
t
i
o
n
s
t
h
a
t
a
r
e
f
o
u
n
d
w
i
t
h
i
n
t
h
e
D
i
a
g
r
a
m
:
Not
Reach
End
Error.
Not
Reach
Start
Error.
Isolate
d
Eleme
nt(s)
Error.
Circul
ar
Error.
V3.6.0
.0.0 Copyri
ght
19932014
Meridi
um,
Inc.
All
rights
reserve
d.
N
ot
Re
ac
h
En
d
Er
ror
A Not
Reach
End
Error
in a
Syste
m
Reliabi
lity
Analys
is
Diagra
m
results
from a
Diagra
m
config
uration
where
the
End
elemen
t
cannot
be
reache
d from
the
Start
elemen
t when
followi
ng
connec
tions
in the
Diagra
m.
Each
Diagra
m
must
be
connec
ted
such
that a
path
exists
from
the
Start
elemen
t to the
End
elemen
t. If
this
path
does
not
exist,
the
simula
tion
will
not
run.
You
must
correct
this
error
before
you
can
run the
simula
tion.
The
followi
ng
images
show a
Not
Reach
End
Error
in
Scenar
io C
and the
corres
pondin
g error
messa
ge in
the
Diagr
am
Valida
tion
Result
s
dialog
box.
V3.6.0
.0.0 Copyri
ght
19932014
Meridi
um,
Inc.
All
rights
reserve
d.
N
ot
Re
ac
h
Sta
rt
Er
ror
A Not
Reach
Start
Error i
na
Syste
m
Reliabi
lity
Analys
is
results
from a
Diagra
m
config
uration
where
the
Start
elemen
t
cannot
be
reache
d from
the
End
elemen
t by
followi
ng
connec
tions
in the
Diagra
m.
Each
Diagra
m
must
be
connec
ted
such
that a
path
exists
from
the
End
elemen
t to the
Start
elemen
t. If
this
path
does
not
exist,
the
simula
tion
will
not
run.
You
must
correct
this
error
before
you
can
run the
simula
tion.
The
followi
ng
images
show a
Not
Reach
Start
Error
in
Scenar
io C
and the
corres
pondin
g error
messa
ge in
the
Diagr
am
Valida
tion
Result
s
dialog
box.
Note:
This
broken
connec
tion
produc
ed
both a
Not
Reach
End
Error
and a
Not
Reach
Start
Error
becaus
e there
is not a
compl
ete
connec
tion
anywh
ere in
the
Diagra
m.
V3.6.0
.0.0 Copyri
ght
19932014
Meridi
um,
Inc.
All
rights
reserve
d.
Is
ola
ted
Ele
me
nt(
s)
Er
ror
An
Isolate
d
Eleme
nt(s)
Error
in
Syste
m
Reliabi
lity
Analys
is
results
from a
Diagra
m
config
uration
where
an
elemen
t is not
connec
ted, on
one or
both
sides,
to the
elemen
ts that
run
from
the
Start
elemen
t to the
End
elemen
t in the
Diagra
m.
This
type of
error
will
not
preven
t the
simula
tion
from
runnin
g, but
the
elemen
t that
is
missin
g the
connec
tion(s)
will be
ignore
d by
the
simula
tion.
The
followi
ng
images
show
an
isolate
d
elemen
t error
in
Scenar
io A
and the
corres
pondin
g error
messa
ge in
the
Diagr
am
Valida
tion
Result
s
dialog
box.
V3.6.0
.0.0 Copyri
ght
19932014
Meridi
um,
Inc.
All
rights
reserve
d.
C
irc
ula
r
Er
ror
A
Circul
ar
Error
in a
Syste
m
Reliabi
lity
Analys
is
Diagra
m
results
from a
Diagra
m
config
uration
where
an
elemen
t in the
series
has a
connec
tion to
an
earlier
elemen
t in the
series
in the
Diagra
m.
This
will
preven
t the
simula
tion
from
runnin
g and
you
must
repair
the
connec
tion so
that it
starts
at the
Start
elemen
t and
ends at
the
End
elemen
t.
The
followi
ng
images
show a
circula
r error
in
Scenar
io B
and its
corres
pondin
g error
messa
ge in
the
Diagr
am
Valida
tion
Result
s
dialog
box.
V3.6.0
.0.0 Copyri
ght
19932014
Meridi
um,
Inc.
All
rights
reserve
d.
A
bo
ut
Ris
ks
In
Syste
m
Reliabi
lity, a
Risk
identifi
es one
way in
which
a piece
of
equip
ment
or
locatio
n can
fail. If
the
Risk
occurs,
then
the
piece
of
equip
ment
or
locatio
n will
fail,
and the
system
cannot
run. In
Syste
m
Reliabi
lity
Analys
es,
Risks
are
stored
in
Syste
m Risk
record
s,
which
can be
linked
to
Syste
m
Asset
and
Syste
m
Switch
record
s.
A
piece
of
equip
ment
or
locatio
n may
have
multipl
e Risks
to
represe
nt
multipl
e ways
in
which
that
piece
of
equip
ment
or
locatio
n can
fail. As
such,
Syste
m
Asset
and
Syste
m
Switch
record
s can
be
linked
to
multipl
e
Syste
m Risk
record
s.
Each
Risk
has a
charact
eristic
pattern
of
causin
ga
piece
of
equip
ment
or
locatio
n to
fail as
define
d by
its
TTF
distrib
ution
data or
maxim
um
operati
ng
time.
Risks
also
have
TTR
distrib
ution
data,
which
charact
erizes
the
time
require
d to
correct
the
failure
that
occurs
as the
result
of the
Risk
and get
the
system
runnin
g
again.
This
distrib
ution
data is
stored
in
Distrib
ution
record
s,
which
are
linked
to Risk
record
s.
V3.6.0
.0.0 Copyri
ght
19932014
Meridi
um,
Inc.
All
rights
reserve
d.
A
bo
ut
Pot
ent
ial
an
d
Fu
nct
ion
al
Fai
lur
es
A Risk
identifi
es a
way in
which
a piece
of
equip
ment o
rlocati
on can
fail but
does
not
necess
arily
indicat
e that a
failure
will
absolut
ely
occur
or will
occur
immed
iately.
For
examp
le, a
piece
of
equip
ment
might
fail if a
bearin
g
wears
out.
Throu
gh an
inspect
ion,
we
may
notice
that
the
bearin
g is
beginn
ing to
wear
thin
and
determ
ine
that it
will
last
only
about
two
more
month
s
before
it
wears
out
compl
etely
and
causes
the
piece
of
equip
ment
to shut
down.
In this
scenari
o:
The Risk is
a bearing
failure.
The
potential
failure is
identified
when an
inspection
detects a thin
bearing.
The
functional
failure occurs
when the
bearing
completely
wears out,
causing the
piece of
equipment to
shut down.
The time
between when
a potential
failure is
detected and
when a
functional
failure occurs
is the P-F
Interval. In
this example,
the P-F
Interval is two
months.
Before the P-F
Interval,
defects are
small and are
unlikely to be
detected. After
the P-F
Interval is
reached,
defects can be
found using
proper
inspection
techniques.
The following
image
demonstrates
how the P-F
Interval is
connected to
the piece of
equipment
failure.
Using this
information,
we can
determine a
repair strategy
for our
example. If
inspections
were not
properly
conducted and
we did not
find the
bearing
defect,
potential
failures would
not have been
detected, and
a functional
failure would
eventually
occur,
requiring the
immediate
replacement
of the
defective
bearing. But
in this case,
the inspection
identified a
potential
failure, so
instead of
replacing the
bearing
immediately,
we can
determine a
percentage of
the P-F
interval at
which to
replace the
bearing
sometime
before the
piece of
equipment
fails while
still
preventing the
eventual
equipment
failure.
1993-2014
Meridium,
Inc. All rights
reserved.
Diag
ram
Hierar
chy
Pane
The Diagram
Hierarchy
pane on the
System
Reliability
Scenarios Risks page
displays the
elements in
the Diagram
that you have
defined on the
System
Reliability
Scenarios -
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
the preceding
image, the
selected Water
Pump has
three
associated
Risks:
Bearing Failure
Impeller Failure
Seal Failure.

Risks
Pane
The Risks pane is

displayed on the
System Reliability
Scenarios - Risks
page and on the Ris
Editor window. The
Risks pane displays
the Risks associated
with the Asset or
Switch element
selected in the
Diagram Hierarch
In the following
image, the Risks pa
is outlined in red.
The grid in the

Risks pane contains
the following
columns of
information:
Name: Displays
the value in the Nam
field in the System
Risk record.
Description:
Displays the value
the Description fiel
in the System Risk
record.
TTF: Displays t
TTF Distribution li
which you can click
to open the TTF
Distribution windo
and view the Time
Failure (TTF)
distribution data fo
the associated Syste
Risk record.
TTR: Displays t
TTR Distribution li
which you can click
to open the TTR
Distribution windo
and view the Time
Repair (TTR)
distribution data fo
the associated Syste
Risk record.
Planned Resour
Usages: Displays th
Planned Resource
Usages link, which
you can click to op
the Planned Resour
Usages window an
view any planned
Resource usages th
have been assigned
the Risk.
Unplanned
Resource Usages:
Displays the
Unplanned Resourc
Usages link, which
you can click to op
the Unplanned
Resource Usages
window and view a
unplanned Resourc
usages that have be
assigned to the Risk
Risks to Reset:
Displays a number
representing the
number of addition
Risks that will be
reset following the

planned or unplann
correction of the Ri
in that row. This
number appears as
hyperlink, which yo
can click to access
Risks to Reset dialo
box, where you can
manage the additio
Risks that will be
reset in the simulati
following the plann
or unplanned
correction of the
source Risk.
When you right-cli

any cell in the grid
the Risks pane, a
shortcut menu
appears containing
options that you can
use to manage the
Risks that you wan
to reset following th
planned or unplann
correction for the
Risk in that row.
Below the grid in th

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.
Associate
Distribution: Displa
the Find Items
window, where you
can search for a
Reliability
Distribution or
Reliability Growth
Analysis to associa
with the selected
Risk.
Open Analysis:
Displays the
Reliability
Distribution
Summary page or t
Reliability Growth
Analysis page for
Reliability
Distribution Analys
or Reliability Grow
Analysis that is
associated with the
selected Risk. This
button is enabled on
when the selected
Risk is associated
with a Reliability
Distribution Analys
or a Reliability
Growth Analysis.
Refresh
Distribution:
Refreshes the
associated
distributions by
replacing the TTF a
TTR distribution
information with th
most current
information from th
associated Reliabili
Distribution Analys
or Reliability Grow
Analysis. This link

enabled only when
the selected Risk is
associated with a
Reliability
Distribution Analys
or a Reliability
Growth Analysis.
Delete Risk: Af
asking for
confirmation, delet
the System Risk
record that is
currently selected i
the Risks pane.

Mitigati
ng
Actions
Pane
The Mitigating
Actions pane is
displayed on the
System Reliability
Scenarios - Risks
page and on the Ris
Editor window. It
displays the
Mitigating Actions
associated with the
Risk selected in the
Risks pane. In the
following image, th
Mitigating Actions
pane is outlined in
red.
When you select a

Risk in the Risks
pane, the associated
Mitigating Actions
for that Risk are
displayed in the
Mitigating Actions
pane. For example,
the preceding imag
the Impeller Failure
Risk has one
associated Mitigatin
Action, Redesign
Impellers.
The grid in the
Mitigating Actions
pane contains the
following columns
information:
Name: Displays
the value in the Nam
field in the System
Action record.
Description:
Displays the value
the Description fiel
in the System Actio
record.
Resource Usage
Displays the
Resources Usages
link, which you can
click to open the
Resource Usages
window to view an
manage the
Resources that have

been assigned to th
Action.
Below the grid in th

Actions pane, the
following buttons
appear:
Assign New
Action: Displays th
Select Action Type
dialog box, where
you can create a ne
System Action reco
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 Risk
pane.
Assign Existing
Actions: Displays t
Assign Actions
window, where you
can assign an existi
Action to mitigate t
Risk currently
selected in the Risk
pane or remove an
existing Action from
mitigating the Risk
the Risks pane.

Accessin
g the
Propertie
Pane
The Properties pan

on the System
Reliability Scenario
- Risks page lets yo
view and modify th
properties of the
element that is
the Diagram
Hierarchy pane, Ri
pane, or Mitigating
Actions pane.
To access the
Properties pane:
Select the elem

on the System
- Risks page for
which you want to
view or modify
properties.
Pause on the
<Name>'s Propert
tab on the right side
of the page.
The <Name>'s
Properties pane
appears. When you
move your pointer

away from the
<Name>'s Propert
tab, the <Name>'s
Properties pane wil
collapse.
Note: If you want t

<Name>'s Propert
pane to remain on t
page after you mov
your pointer away
from the <Name>'s
Properties tab, clic
the
button.

About
Fields
Displayed
on the
Propertie
Pane
Different fields are

displayed in the
Properties pane
depending upon the
element that is
selected on the
System Reliability
Scenarios - Risks
page. When you
select an element, t
Properties pane wil
display the fields th
belong to the record
that is associated w
the selected elemen
You can select any
the following
elements to view th
fields in the
associated record in
the Properties pane
Actions
Assets
Risks
Switches
V3.6.0.0.0 - Copyri
1993-2014 Meridiu
Risk Fie
When you select a

the Risks pane on th
page, the Propertie
displays informatio
to that Risk. The fo
table lists:
The row labels

displayed in the Pro
pane when you sele
in the Risks pane. T
organized by the ca
that are displayed w
view the Propertie

a categorized view.
Note: In the table,

Distributions categ
displays in alphabe
ALL of the fields th
displayed in the
Distributions categ
Properties pane. In
cases, depending up
Risk you select in t
pane, not all of thes
will appear in the P
pane. The Notes co
contains informatio
any exceptions.
The family capt

family containing t
whose value is disp
that row.
The field captio

field whose value is
displayed in that ro
Notes that prov

information about t
in a row.
The following imag

the categorized view
Properties pane tha
be displayed if you
the Seal Failure Ris
Scenario B.
V3.6.0.0.0 - Copyri
1993-2014 Meridiu
About
Actions a
Risks
After you create an

a System Reliabilit
Analysis, you can a
single Risk or mult
to that Action. Whe
assign a Risk to an
link is created betw

System Risk Assess
record, which store
GUID of the mitiga
in the Risk GUID f
the Action. This all
Action to mitigate t
An Action may mit
Risk by changing c
properties, such as
consequences or th
distribution, of the
Actions mitigate Ri
different ways depe
upon the type of Ac
is assigned to the R
different types of A
mitigate Risks in th
following ways:
Preventive Mai
Can mitigate the Ti
distribution of the R
the maximum opera
Risk, as defined by
Distribution record
TTF distribution as
Risk. For example
Action in Scenario
mitigates the Seal F
creating more opera
replacing the existi
have a smaller amo
time, with new seal
larger amount of op
Condition Moni
Action: Can mitiga
consequences of fa
potential failures be
This allows proacti
planned corrections
the system instead o
fixing a failure usin
correction. Planned
consume less Resou
the costs of a Scena
the Vibration Analy
Scenario B of the S
Analysis Example m
Bearing Failure Ris
potential Bearing F
executing a planned
which requires less
less Resource usage
an unplanned corre
Special Action:
failure consequence
defined in the Fixed
Correction Cost fie
Risk record, and th
distribution, as defi
Distribution record
the TTF distribution
the Risk. For exam
occurrence of the R
Action in Scenario
mitigates the Impel
reducing the fixed u
correction cost and
TTF distribution of
Failure Risk.
Note: An Action do
mitigate a Risk, but
Action with a Risk
the Risk creates a m
system.
V3.6.0.0.0 - Copyri
Meridium, Inc. All
Creatin
on the Ri
Page
The following instr

details on creating R
simultaneously assi
Actions via the Sys
Scenarios - Risks p
complete this work
System Reliability S
Actions page.
To add a Risk to an
element in a Scenar
While viewing
Active Scenario on
the Diagram Hiera
the element to whic
add a Risk.
Below the grid

click the Add Risk b
The Add New Risk

displaying the defa
the System Risk fam
In the fields on
window, define the
Risk record as desir
Click OK.
The System Risk re

pane.
V3.6.0.0.0 - Copyri
Meridium, Inc. All
Creatin
the Actio
The following instr

on creating a Risk r
simultaneously assi
using the System Re
Actions page. You c
workflow using the
Scenarios - Risks p
To assign a new Ri
While viewing
Scenario on the Sys
Scenarios - Actions
Hierarchy pane, sel
contains the Action
assign a Risk.
In the grid in th
Action to which yo
Below the grid

pane, click the Assi
The New Risk wind

the default datashee
family.
In the fields on
properties of the Sy
Click OK.
The new Risk is cre

element, assigned t
the grid in the Mitig
V3.6.0.0.0 - Copyri
Inc. All rights reser
Assignin
Risks to A
To assign existing R
While viewing
System Reliability
Diagram Hierarchy
contains the Action
Risk.
In the grid in th
to which you want
Below the grid

click the Assign Ex
The Assign Risk w

Risks that exist in t
belongs.
In this image, the A

some of the Risks t
On the Assign R
of the grid, select th
want to assign to th
Hint: You can remo

the Action by cleari
Click OK.
The Risk(s) are ass

and appear in the g
V3.6.0.0.0 - Copyri
reserved.
Options
You can modify the

the following pages
System Reliabil
System Reliabil
V3.6.0.0.0 - Copyri
Modifyi
Page
To modify a Risk u
While viewing
Scenarios - Risks p
contains the Risk y
In the Name co
hyperlinked name o
The <Risk Name>

the System Risk rec
Modify the prop

Click OK.
Your changes to the
V3.6.0.0.0 - Copyri
Modifyi
Page
To modify a Risk u
While viewing
Actions page, in the
you want to modify
In the Name co
hyperlinked name o
The <Risk Name>

System Risk record
Modify the prop

Click OK.
Your changes to the
V3.6.0.0.0 - Copyri
About R
After Resources ex
When you do so, yo
result of that Risk.
consequences of th
When you assign a

and will store infor
and duration). Ther
Planned Resour
Unplanned Res
V3.6.0.0.0 - Copyri
Assignin
To assign a Resourc
On the System
element that contai
In the grid in th
Resource, click the
-or-
In the grid in the Ri

Resource, click the
The <Resource Usa

Resource Usage tha
In this image, the P

that are assigned to
Click the Add E

exist for the analysi
A new row appears
Hint: Alternatively,
a Risk. After you ha
In the Resource
Risk.
Type the desired

populate the corres
Note: The Total Fix

the System Resourc
enter on the Resour
values in these cells
Click the Close
The <Resource Usa
V3.6.0.0.0 - Copyri
Modifyi
When you modify a

System Resource re
To modify a Resou
While viewing
page, in the Diagra
In the grid in th
Planned Resource U
-or-

Resource Usages li
The <Resource Usa

selected and <Risk>
In the Resource
Click the Close
Your changes are sa
V3.6.0.0.0 - Copyri
Removi
When you remove

used by the selected
used if needed.
To delete a Resourc
While viewing
the Diagram Hierar
In the grid in th
Resource Usages li
-or-

Resource Usages li
The <Resource Usa

and <Risk> is the n
In the Resource
Click the Delete
A confirmation mes
Click the Yes b
The Resource Usag
V3.6.0.0.0 - Copyri
About D
You have two optio
Enter distributio
Associate distri
V3.6.0.0.0 - Copyri
Defining
To define TTF or T
While viewing
pane, select the elem
In the grid in th
In the TTF colu

-or In the TTR
The TTR Distributi
Define the prop

Click OK.
Your new distributi
V3.6.0.0.0 - Copyri
About A
As an alternative to
Distribution Analys
distribution data wi
After existing distri

Key and Family Ke
the two records tha
results.
V3.6.0.0.0 - Copyri
Associa
To associate an exis
While viewing
element that contai
In the grid in th
Below the grid
The Find Items win

associate with a Ris
In the Find Item
The search results a
In the search re
Click the Open
The distribution da
Analysis.
V3.6.0.0.0 - Copyri
Opening
You can open the R
To open an associat
While viewing
the Risk whose asso
In the grid in th
Below the grid
Note: If your Syste
The System Reliab
V3.6.0.0.0 - Copyri
Refresh
To refresh the distri
While viewing
the Risk whose dist
In the grid in th
Below the grid
A confirmation mes
Click OK.
The distribution da
V3.6.0.0.0 - Copyri
Removi
To remove the asso
While viewing
Risk for which you
In the grid in th
The <Distribution>
In the bottom o
The fields in the TT
Note: You can keep

Click OK.
Your changes are sa
V3.6.0.0.0 - Copyri
About R
When a simulation
or after actions are
be changed to zero
When a Risk will b

occurs:
An unplanned c
A planned corre
Preventive Mai
A Special Actio
A Risk whose failu
Preventive Mai
A Special Actio
For example, suppo
Bearing Failure
Impeller Failure
Seal Failure
In the simulation, a
will replace the Bea
In addition to Risks
words, you can spe
the additional Risks
Throughout the doc

to Risks that are res
You can specify tha
An unplanned c
-or-
A planned corre
It is important to no
Continuing with the
You will replace

-or-
The planned co
In this case, you wa

been in-service wil
You can manage th

specify any Risk th
V3.6.0.0.0 - Copyri
Rules fo
When you set up a
You can specify
Failure With
-or-
Failure With
You can specify
Keep in mind that i

are not reset follow
type is Failure With
can be specified
Replacement.
Cannot be spec
For example, suppo

A Tube Bundle
A Shell Head Fa
A Seals (gasket
Now suppose that w

to as good as new)
(i.e., an additional R
following the plann
V3.6.0.0.0 - Copyri
Selectin
The following instr

the time in-service
These instructions a
To select Risks to r
In the Diagram
The Risks defined f
In the grid in th
In the Risks to R
The Risks to Reset
In the Risks to R
In the following im
Hint: You can use t

Click OK.
The Risks to Reset

for the components
In the following im
In the example used

was replaced (or re
V3.6.0.0.0 - Copyri
Overvie
Using the Risks to R

The Risks to Reset
<Asset ID> is
ed correction of the Bearing Failure Risk (i.e., the source Risk).
it appears when you access it from the System Reliability Scenarios - Risks page or the Risks Editor window.
heck box to clear ALL the currently selected check boxes.
rom which you access the shortcut menu.
age record will be created.
n view the additional Risks that will be reset in the simulation if the source Risk occurs or is mitigated as a
You can select any of the following elements to view the fields in the associated record in the Properties
e Meridium APM system creates a System Action record in the family whose caption appears in the ASO
button below the grid in the Actions pane.
New Action button below the grid in the Mitigating Actions pane.
an Action.
me field in the System Special Action record.
nd TTF Distribution values that you want to be used in the simulation when a Special Action is completed to
TTF Distribution values that you want to be used in the simulation when the Special Action is completed to
ecord that is linked to the System Special Action record. For each Mitigated Risk that appears in the list to
at you specify in the Fixed Unplanned Correction Cost field.
Cost field in the selected System Risk Assessment record. This text box is enabled only if the Replace
you specify in the Distribution fields.
only if the Replace TTF Distribution check box is selected.
to be used in the simulation when the Special Action is completed to mitigate the occurrence of the given
t you want to be used in the simulation when the Special Action is completed to mitigate the occurrence of
the Close button.
select the element that contains the Action that you want to modify.
pane, select the element that contains the Action that you want to modify.
u associate the cost of that Resource with each occurrence of the Action. This allows you to assign a realistic
ormation that specifies how the Resource will be used (e.g., the quantity and duration).
- Actions page, in the Diagram Hierarchy pane, select the element that contains the Action to which you want
click the Resources Usages link.
ed, displaying any Resources that are assigned to the Action.
he Vibration Analysis Action.
exist for the analysis.
After you have created the Resource, you can skip to step 5.
nt to assign to the Action.
will be used to populate the corresponding fields in the System Resource Usage record.
be incurred when the System Resource Usage is added to the simulation results. The Total Fixed Cost is
Cost is calculated by the following calculation: Variable Cost of the Resource*Quantity*Duration. Since
age window, the cells are disabled and you cannot type values in these cells.
ed to the Action.
age record. The actual System Resource record is not changed.
Reliability Scenarios - Actions page, select the element whose Action has Resources you want to modify.
you want to modify, click the Resource Usages link.
Action that you selected.
ecord as desired.
Usage record so that the Resource is not used by the selected Action. The actual System Resource record is
ed.
System Reliability Scenarios - Actions page, in the Diagram Hierarchy pane, select the Action whose
ource assignments you want to remove, click the Resource Usages link.
e of the Action that you selected.
you want to delete.
selected item(s).
Resource Usage record is deleted from the database.
rights reserved.
ns to determine the most efficient interval at which to perform inspection or preventive maintenance Actions.
the reliability of the system.
cenarios.
ply it to your analysis by replacing the current interval value with the optimal interval value.
on at a time. While a simulation is running, however, you can continue working in other areas of the
k main window outside the Run Simulation dialog box. When you do so, the simulation will continue to run
ind the Meridium APM Framework window. When the simulation finishes, the dialog box will be returned
he Run Simulation dialog box. When you do so, the simulation will continue to run in the background, and
taskbar. When the simulation finishes, the dialog box will be maximized and returned to focus automatically.
rights reserved.
on
is and Scenario on the System Reliability Scenarios - Actions page, in the Diagram Hierarchy pane, select
you want to optimize.
ze button.
displays the data necessary to optimize the New Inspection Action.
minimum interval.
maximum interval.
crement.
Current Interval text box, which represents the current interval at which the current Action is performed.
urrent Interval field in the System Action record. Modifying the value in the Action Interval Optimization
n record to be updated with the same value.
pears, displaying a progress bar that indicates the progress of the optimization process.
e Go to Analysis and Discard and Close buttons become enabled. If you do not want to view the results, you
close the Optimization Progress dialog box. These instructions assume that you want to view the results.
n.
window appears, displaying the Cost chart in the Simulation Results section and an updated value in
ighted in the following image.
ultiple Actions
in a System Reliability Analysis:
tem Reliability Analysis on any page, on the Tools menu, click the Optimize Actions link.
mization window appears, displaying Actions in the System Reliability Analysis that can be optimized.
ns pane, select the Optimize check box for the Action that you want to optimize.
t box, type the desired minimum interval.
t box, type the desired maximum interval.
ox, type the desired increment.

5 for other Actions that you want to optimize.
hange the data in the Current Interval text box, which represents the current interval at which the current
text box is populated with the value in the Current Interval field in the System Action record. Modifying the
n Interval Optimization window will cause the value in the System Action record to be updated with the
in the Actions pane, click the Run Simulation button.
Progress dialog box appears, displaying a progress bar that indicates the progress of the optimization process.
bar reaches the end, the Go to Analysis and Discard and Close buttons become enabled. If you do not want to
u can click the Discard and Close button to close the Optimization Progress dialog box. These instructions
ant to view the results.
e Go to Analysis button.
e Action Interval Optimization window appears, displaying the Cost chart in the Simulation Results section
d values in Optimal Interval cells, as highlighted in the following image.
Copyright 1993-2014 Meridium, Inc. All rights reserved.
ut Applying Optimal Action Intervals
optimize Actions, you can determine the most efficient interval in which to perform inspection or preventive
e Actions. After you have found the optimal interval for an Action you can apply it to that Action. When you
alue in the Current Interval text box in the Actions pane and the value in the Interval field in the System
rd will be overwritten with the value that exists in the Optimal Interval text box.
pply the optimal interval, you will need to rerun the simulation for the System Reliability Analysis to update
ased upon the new action interval.
plying Optimal Intervals to Actions
the Optimal Value to a Single Action:
e optimal interval to a Single Action:
optimal Action interval value for the Action you want to optimize.
Action Interval Optimization window, in the Settings section, click the Apply Optimal Value button.
Apply Optimal Value button is enabled only after you have optimized an Action. If you close the Action
timization window, you will have to optimize the Action again for the Apply Optimal Value button to
bled.
n the Optimal Interval text box replaces the value in the Current Interval text box in the Settings section and
val field in the associated System Action record.
Optimal Intervals to Multiple Actions:
timal intervals to multiple Actions:

optimal Action intervals for the Actions you want to optimize.
rid in the Actions pane, in the Apply column, select the check box for the Actions whose current interval you
ace with the optimal interval.
he grid in the Actions pane, click the Apply Optimal Values button.
in the Optimal Interval text boxes replace the values in the respective Current Interval text boxes in the grid
ns pane and in the Interval field in the associated System Action records.
eting Actions
n Action:
System Reliability Scenarios - Actions page, in the Diagram Hierarchy pane, select the element whose Action
delete.
rid in the Actions pane, select the Action that you want to delete.
he grid in the Actions pane, click the Delete Action button.
ion message appears, asking if you really want to delete the Action.
Action is removed from the grid in the Actions pane..
About Global Events
lobal Event is an optional component of a System Reliability Analysis that groups together Actions requiring
stem shutdown so that they will be performed at the same time, thereby maximizing the availability of the
em. The information for a Global Event is stored in a System Global Event record.
en you create a Global Event, you select Actions that may be rescheduled and performed as part of the Global
nt. The execution of the selected Actions is called a Global Event. To be performed with the Global Event,
ons must occur during the time period defined by the Max Delay and Max Advance values in the System
bal Event record. Actions assigned to the Global Event that are performed outside of this time period will not
ncluded in the Global Event, and their occurrence is not be affected by the occurrence of the Global Event.
next occurrence of any recurring Actions that have been rescheduled and performed as part of a Global
nt will be performed according to the values in the Interval and Interval Units fields in the System Action
rd.
e: Actions that are represented by a System Condition Monitor record occur continuously and cannot be
gned to a Global Event. All other Actions can be performed in a Global Event.
example, consider Scenario B in our System Reliability Analysis Example, which contains two Actions that
ire a system shutdown: Redesign Impellers and Replace Seals. The Redesign Impellers Action has a duration
ne week, and the Replace Seals Action has a duration of one day. Performed independently of one another,
would result in a system shutdown lasting a total of eight days.
w, assume that you group the two Actions together using a Global Event with a Max Delay value of 3 months
a Max Advance value of 4 weeks. This Global Event specifies that the two Actions will be rescheduled and
ormed together during the same system shutdown, as long as the Actions fall into the time period from 3
ths before the Global Event and 4 weeks after the Global Event. Managing the Actions in this way would
lt in a shutdown lasting the longest of the two durations, or seven days. This approach is preferable, as it
ld save one day of costs associated with the system shutdown.
em Reliability Analyses support the use of two types of Global Events:

Action-driven Global Events.
Datedriven Global Events.
Note: While Global Events limit downtime and the history of a Global Event can be seen in the Event
Logs generated from a System Reliability Analysis which contains a Global Event, the effects of Global
Events are not presented explicitly anywhere in the simulation results. The effects of the Global Events
are expressed as less downtime for the system, which means lower lost production costs.
About Action-Driven Global Events

An Action-driven Global Event is a collection of Actions that may occur based upon the occurrence of a
driving Action. When the driving Action occurs, any Actions that fall into the time range specified by the
Max Advance and Max Delay values are triggered to be rescheduled and performed with the driving
Action. Action-driven Global Events can occur only one time in a simulation. If you select a recurring
Action as the driving Action, the Global Event will occur the first time that the driving Action occurs. If
you select more than one Action as the driving Action, then the first driving Action that occurs will
trigger the other Actions in the Global Event.
For example, in Scenario B of our System Reliability Analysis Example, you might create an Actiondriven Global Event, which is assigned both the Redesign Impellers and Replace Seal Actions, with the
Redesign Impellers Action designated as the driving Action. In this case, when the Redesign Impellers
Action occurs according to the properties specified in the System Action record that represents it, the
Global Event will trigger any Replace Seals Action that falls within the time period specified by the Max
Delay and Max Advance values to be rescheduled and completed with the occurrence of the Redesign
Impellers Action.
About Date-Driven Global Events

A date-driven Global Event is a collection of Actions that may occur on a certain date. When the
simulation reaches the date of the Global Event, any assigned Actions that fall into the time range
specified by the Max Advance and Max Advance Duration values are triggered to be performed on the
date of the Global Event. A date-driven Global Event can occur one or more times throughout the
simulation period.
For example, in Scenario B of our System Reliability Analysis Example, you might create a date-driven
Global Event and specify that it should occur on a date halfway through the simulation. To this Global
Event you would assign the Redesign Impellers and Replace Seals Actions. In this case, the Global Event
would trigger both of the Actions which fall into the time period, specified by the Max Advance Duration
and Max Delay Duration values, almost three and a half years into the simulation, regardless of what
properties existed in the System Action records that represent the Redesign Impellers and Replace Seal
Actions.
Global Events Pane

The Global Events pane appears on the System Reliability Scenarios - Global Events page and displays
the Global Events associated with the Scenario that you are currently viewing.
The grid in the Global Events pane contains the following columns:
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.
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.
Actions to Align Pane
The Actions to Align pane appears on the System Reliability Scenarios - Global Events page and displays
the Actions that are currently assigned to the Global Event that is selected in the Global Events pane.
The grid in the Actions to Align pane displays the following columns:
Name: Displays a hierarchy that lists the Actions that exist in the Scenario Diagram. The Actions
appear in the hierarchy below the element to which they belong, with elements appearing below the
Scenario Diagram to which they belong.
Note: For example, the preceding image displays the Replace Seals and Redesign Impellers Actions,
which are assigned to the Water Pump element, which exists in the Diagram for Scenario B.
Is Driver: Displays check boxes that allow you to identify driving Action(s) for Action-driven Global
Events. You cannot change the Is Driver status of the Action from this pane.
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.
About Creating Global Events

To create a Global Event, you must complete two steps:
Create a System Global Event record.
Assign Actions to the Global Event.
Creating System Global Event Records

To create a System Global Event record:
While viewing the desired System Reliability Analysis and Scenario on the System Reliability
Scenarios - 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.
Define the properties of the System Global Event record as desired.

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 an Action to a Global Event:
While viewing the desired System Reliability Analysis and Scenario on the System
Reliability Scenarios - 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.
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.
This image displays the Actions in Scenario B of our System Reliability Analysis
Example.
In the Is Selected column, select the check box for the Actions that you want to
assign to the selected Global Event.
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.
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 an Action from a Global Event:
While viewing the desired System Reliability Analysis and Scenario on
the System Reliability Scenarios - 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.
Below the grid in the Actions to Align pane, click the Assign Actions
button.
The Assign Actions window appears.
In the Is Selected column, clear the check box for any Actions
that you want to remove from the Global Event.
Click OK.
Your changes are saved, and the Actions to Align pane is updated to
reflect those changes.

reserved.
Modifying System Global

Event Records
To modify a System Global Event record:
While viewing the desired System Reliability Analysis and
Scenario on the System Reliability Scenarios - 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.
This image displays the datasheet for a possible System Reliability

Analysis Example Global Event which could be used in our System
Reliability Analysis Example.
Modify the properties of the System Global Event record
as desired.
Click OK.

rights reserved.
Deleting Global Events

When you delete a Global Event, the System Global Event
record that represents the Global Event is deleted. This
removes any properties of the Global Event, such as the
interval at which the Global Event may be repeated and
which Actions may be performed with the Global Event, but
the System Action records that represent the Actions that
exist in the Scenario are not modified or deleted in any way.
To delete a Global Event:
While viewing the desired System Reliability Analysis
and Scenario on the System Reliability Scenarios - Global
Events page, in the grid in the Global Events pane, select the
Global Event that you want to delete.
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.

Overview of the
System Reliability
Scenarios - Grid Page
In addition to working with Scenarios on the System
Reliability Scenarios - Diagram page, you can also
view Scenarios on the System Reliability Scenarios Grid page. On this page, you can view and modify
certain properties of elements that exist in a given

Scenario, but you cannot use this page to add or
delete Scenario elements. By using the Scenario and
Filter lists at the top of the System Reliability
Scenarios - Grid workspace, you can select options
to view data that is specific to a given Scenario and
element.
The main display area of the System Reliability

Scenarios - Grid page contains a grid that shows
information for the elements that exist in the selected
Scenario. By default, the grid is configured to
display certain columns in a particular order,
depending upon the type of elements that are
displayed. If desired, you can customize the
appearance of the grid.
Within the grid, under the Name column, a hierarchy
displays an organizational view of the elements in
the Diagram associated with the selected Scenario.
The root Subsystem is displayed at the top, with any
elements belonging to the root Subsystem listed
below it. Any other subsystems are listed below the
root Subsystem, with any elements belonging to
them listed below them.
For example, the preceding image shows Scenario C
in our System Reliability Analysis Example. In this
image, Diagram for Scenario C appears at the top of

the hierarchy and represents the root Subsystem for
the Diagram. Below it appear the Subsystem and the
Assets that exist at the main level of the Diagram:
Bottling Subsystem, Water Pump 1, Water Pump 2,
and Water Source. Below the Bottling Subsystem
element are the Asset elements that make up that
subsystem: Bottling Line 1, Bottling Line 2, and
Bottling Line 3. The properties for each element
appear in the columns to the right of the element
name.
An icon appears to the left of each element to help
identify it. The icons that appear in the list are the
same as the ones used on the System Reliability
Scenarios - Diagram page. Actions, Risks, and
Distributions are not represented by icons in the
Diagram, but they are represented by the following
icons on the System Reliability Scenarios - Grid
page:
Actions are represented by the
Risks are represented by the
icon.
icon.
Time to Failure Distributions are represented by

the icon.
Time to Repair Distributions are represented by
the icon.
Note: You can click the plus sign (+) to the left of
any Subsystem icon to view additional information
about a Subsystem element. Similarly, you can click
any minus sign (-) to collapse that level of the
hierarchy.
Within the grid, you can modify the properties of the
Scenario elements. To do so, click in any cell, and
modify the current value. Some properties cannot be
modified via the grid. Editable cells correspond to
modifiable fields in the records that store
information for the elements in System Reliability
Analyses. Disabled cells are used to display fields
that do not exist or are disabled in the record for the
element that is displayed in the grid. For example, in
the image shown above, the Production

Contribution cell for the Diagram for Scenario C
Subsystem is disabled because the value in the
Production Contribution field for a root System
Subsystem record of a Diagram cannot be modified
through System Reliability Analyses.
Using the Scenario and Filter lists, which appear at
the top of the System Reliability Scenarios - Grid
workspace, you can select options to view data that
is specific to a given Scenario and element. For
instance, selecting Action in the Filter list will
display a list of Actions that exist for the Asset and
Switch elements in the Scenario that you selected in
the Scenario list. The Scenario list contains the
names of the System Scenario records that are
associated with the current System Reliability
Analysis. You can select any name in the list to view
elements of that Scenario in the grid. The Filter list
contains the following options:
Action
Asset
Buffer
Distribution
Link
Risk
Subsystem
Switch
You can select any item in the Filter list to view
those elements for the Scenario that is selected in the
Scenario list.

By Action
When you select Action in the Filter list on the
System Reliability Scenarios - Grid page, the grid
will display data related to the Actions that exist in
the Scenario selected in the Scenario list. The
following image shows the grid that is displayed for
the System Reliability Analysis Example when
Scenario B is selected in the Scenario list and Action
is selected in the Filter list.
The following columns of information are displayed

in the grid when the Action option is selected in the
Filter list:
Name: Displays a hierarchy that lists the
Subsystems, Assets, Switches, and Actions that exist
in the Scenario. Actions appear in the hierarchy
below the Asset, Switch, or Subsystem element to
which they belong.
Action Cost ($): Displays the value that exists in
the Action Cost field in the System Action record.
Interval: Displays the value that exists in the

Interval field in the System Action record.
Interval Units: Displays the value that exists in
the Interval Units field in the System Action record.
Duration: Displays the value that exists in the
Duration field in the System Action record.
Duration Units: Displays the value that exists in
the Duration Units field in the System Action record.
Detection Probability: Displays the value that
exists in the Detection Probability field in the
System Action record.
Shutdown Required: Displays the value that
exists in the Shutdown Required field in the System
Action record.
One Time Action: Displays the value that exists
in the One Time Action field in the System Action
record.

By Asset
When you select Asset in the Filter list on the System
Reliability Scenarios - Grid page, the grid will
display data related to the Assets and Subsystems
that exist in the Scenario selected in the Scenario list.
The following image shows the grid that is displayed
for the System Reliability Analysis Example when
Scenario A is selected in the Scenario list and Asset
is selected in the Filter list.
The following columns of information are displayed

in the grid when the Asset option is selected in the
Filter list:
Name: Displays a hierarchy that lists the
Subsystems and Assets that exist in the
Scenario. Assets appear below the Subsystem
element to which they belong.
Production Contribution: Displays the
value that exists in the Production
Contribution field in the System Asset or
System Subsystem record.
Fixed Cost: Displays the value that exists
in the Fixed Cost field in the System Asset or
System Subsystem record.
Variable Cost ($): Displays the value that
exists in the Variable Cost field in the System
Asset or System Subsystem record.
Variable Cost Units: Displays the value
that exists in the Variable Cost Units field in
the System Asset or System Subsystem
record.
Lost Production Cost ($): Displays the

value that exists in the Los Production Cost
field in the System Asset or System
Subsystem record.
Lost Production Cost Units: Displays the
value that exists in the Lost Production Cost
Units field in the System Asset or System
Subsystem record.
V3.6.0.0.0 - Copyright 1993-2014

By Buffer
When you select Buffer in the Filter list on
the System Reliability Scenarios - Grid page,
the grid will display data related to the
Buffers that exist in the Scenario selected in
the Scenario list. The following image shows
the grid that is displayed for the System
Reliability Analysis Example when Scenario
A is selected in the Scenario list and Buffer is
selected in the Filter list.
The following columns of information are

displayed in the grid when the Buffer option
is selected in the Filter list:
Name: Displays a hierarchy that
lists the Buffers that exist in the
Scenario, including Buffers that
belong directly to the root Subsystem
and Buffers that belong to any
Subsystem elements. Buffers appear
in the hierarchy below the Subsystem
element to which they belong.
Description: Displays the value
that exists in the Description field in
the System Buffer record.
Production Contribution: Displays
the value that exists in the Production
Contribution field in the System
Buffer or System Subsystem record.
Initial Quantity in Percentage:
Displays the value that exists in the
Initial Quantity in Percentage field in
the System Buffer record.
Time to Empty: Displays the
value that exists in the Time to Empty
field in the System Buffer record.
Time to Empty Units: Displays
the value that exists in the Time to
Empty Units field in the System
Buffer record.
Time to Refill: Displays the value
that exists in the Time to Refill field
in the System Buffer record.
Time to Refill Units: Displays the
value that exists in the Time to Refill
Units field in the System Buffer
record.
V3.6.0.0.0 - Copyright 1993-2014

By Distribution
When you select Distribution in the
Filter list on the System Reliability
Scenarios - Grid page, the grid will
display data in the Distribution
records associated with the Scenario
selected in the Scenario list. On the
System Reliability Scenarios - Grid
page, Distribution records are shown
as properties of the Risk elements
with which they are associated.
The following image shows the grid
that is displayed for the System
Reliability Analysis Example when
Scenario A is selected in the Scenario
list and Distribution is selected in the
Filter list.
The following columns of

information are displayed in the grid
when the Distribution option is
selected in the Filter list:
Name: Displays a hierarchy that
lists the Subsystems, Assets,
Switches, Risks, and distributions that
exist in the Scenario. Distributions

appear in the hierarchy below the
Risk to which they belong.
Distribution Type: Displays the
name of the family to which the
Distribution record belongs.
Time Unit: Displays the value that
exists in the Unit field of the
Distribution record.
Parameter 1: Displays the value
that exists in the Beta field in a
Weibull record, the MTBF field in an
Exponential record, the Mean field in
a Normal record, or the Mu field in a
Lognormal record.
Note: When you select the value
Single Value in the Distribution Type
list on the TTF Distribution or TTR
Distribution window, you create a
Normal record with a Standard
Deviation value of 0 (zero). For these
records, the Parameter 1 column
displays the value that exists in the
Value field, rather than the Mean
field.
that exists in the Eta field in a Weibull
record, the Standard Deviation for a
Normal record, or the Sigma field for
a Lognormal record.
that exists in the Gamma field in the
Weibull record or Lognormal record.
V3.6.0.0.0 - Copyright 1993-2014

By Link
When you select Link in the Filter list
on the System Reliability Scenarios Grid page, the grid will display data
related to the Links that exist in the
Scenario selected in the Scenario list.
The following image shows the grid
that is displayed for the System
Reliability Analysis Example when
Scenario A is selected in the Scenario
list and Link is selected in the Filter
list.

information are displayed in the grid
when the Link option is selected in
the Filter list:
Name: Displays a
hierarchy that lists only the
Subsystems which contain
Links and the Links that
exist in the Scenario. Links
appear in the hierarchy
below the Subsystem

element to which they
belong.
Minimum Predecessors:
Displays the value that exists
in the Minimum Predecessors
field in the System Link
record. You cannot modify
this value from the System
Reliability Scenarios - Grid
page.
rights reserved.
By Risk
When you select Risk in the
Filter list on the System
Reliability Scenarios - Grid
page, the grid will display data
related to the Risks that exist
in the Scenario selected in the
Scenario list. The following
image shows the grid that is
displayed for the System
Reliability Analysis Example
when Scenario C is selected in
the Scenario list and Risk is
selected in the Filter list.

information are displayed in
the grid when the Risk option
is selected in the Filter list:
Name: Displays a
hierarchy that lists the
Subsystems, Assets,
Switches, and Risks
that exist in the
Scenario. Risks appear
in the hierarchy placed
below the Asset or
Switch element to
which they belong.
Fixed Unplanned
Correction Cost ($):
Displays the value that
exists in the Fixed
Unplanned Correction
Cost field in the
System Risk record.
Variable
Unplanned Correction
Cost ($): Displays the
value that exists in the
Variable Unplanned
Correction Cost field
in the System Risk
record.
Planned Correction
Cost ($): Displays the
Planned Correction
Cost field in the
System Risk record.
Planned Correction
Cost Units: Displays
the value that exists in
the Planned Correction
Cost Units field in the
System Risk record.
Planned Correction
Duration: Displays the
Planned Correction
Duration field in the
System Risk record.
Planned Correction
Duration Units:
exists in the Planned
Correction Duration
Units field in the
System Risk record.
PF
Interval: Displays the
PF Interval field in the
System Risk record.
PF Interval Units:
exists in the PF
Interval Units field in
the System Risk
record.
1993-2014
Meridium, Inc. All
rights reserved.
By
Subsystem
When you select
Subsystem in the Filter
list on the System
Reliability Scenarios Grid page, the grid
will display data
related to the
Subsystems that exist
in the Scenario
selected in the
Scenario list. The
following image shows
the grid that is
displayed for the
System Reliability
Analysis Example
when Scenario A is
selected in the
Scenario list and
Subsystem is selected
in the Filter list.
The following columns

of information are
displayed in the grid
when the Subsystem
option is selected in
the Filter list:
Name:
Displays a
hierarchy that
lists the
Subsystems
that exist in the
Scenario.
Production
Contribution:
Displays the
value that
exists in the
Production
Contribution
field in the
System
Subsystem
record.
Fixed Cost
($): Displays
the value that
exists in the
Fixed Cost
field in the
System
Subsystem
record.
Variable
Cost ($):
Displays the
value that
exists in the
Variable Cost
field in the
System
Subsystem
record.
Variable
Cost Units:
Displays the
value that
exists in the
Variable Cost
Units field in
the System
Subsystem
record.
Lost
Production
Cost ($):
Displays the
value that
exists in the
Lost
Production
Cost field in
the System
Subsystem
record.
Lost
Production
Cost Units:
Displays the
value that
exists in the
Lost
Production
Cost Units field
in the System
Subsystem
record.
1993-2014
Meridium, Inc.
All rights
reserved.
By
Switch
When you
select Switch in
the Filter list
on the System
Reliability
Scenarios Grid page, the
grid will
display data
related to the
Switches that
exist in the
Scenario
selected in the
Scenario list.
The following
image shows
the grid that is
displayed for
the System
Reliability
Analysis
Example when
Scenario C is
selected in the
Scenario list
and Switch is
selected in the
Filter list.
The following
columns of
information are
displayed in the
grid when the
Switch option
is selected in
the Filter list:
Name:
Displays a
hierarchy that
lists the
Switches that
exist in the
Scenario,
including
Switches that
belong directly
to the root
Subsystem and
Switches that
belong to any
Subsystem
elements.
Buffers appear
in the hierarchy
below the
Subsystem
element to
which they
belong.
Is Initially
On: Displays
the value that
exists in the Is
Initially On
field in the
System Switch
record.
Note: Because
this field does
not exist in
System
Subsystem
records, this
cell is disabled
in the row
representing
the root
Subsystem.
Fixed
Cost: Displays
the value that
exists in the
Fixed Cost
field in the
System Switch
or the System
Analysis
record.
Variable
Cost: Displays
the value that
exists in the
Variable Cost
field in the
System Switch
or the System
Analysis
record.
Variable
Cost Units:
Displays the
value that
exists in the
Fixed Cost
field in the
System Switch
or the System
Analysis
record.
Lost
Production
Cost: Displays
the value that
exists in the
Lost
Production
Cost field in
the System
Switch or the
System
Analysis
record.
Lost
Production
Cost Units:
Displays the
value that
exists in the
Lost
Production
Cost Units field
in the System
Switch or the
System
Analysis
record.
1993-2014
Meridium, Inc.
All rights
reserved.
Abou
t
Resour
ces
Resources are
optional
components in
a System
Reliability
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 Resource
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 a System
Reliability
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).
1993-2014
Meridium, Inc.
All rights
reserved.
Abou
t
Addin
g
Resour
ces to
Analys
es
You have two
options for
adding
Resources to a
System
Reliability
Analysis. You
can:
Create
new
Resourc
es from
scratch.
Import
Resourc
es that
already
exist in
other
System
Reliabil
ity
Analyse
s.
Note:
Resourc
es can
also be
created
within
the
context
of
Actions
and
Risks.
Doing
so will
cause
those
Resourc
es to be
availabl
e at the
analysis
level so
that
they
can be
assigne
d to
other
Actions
and
Risks.
V3.6.0.
0.0 Copyrig
ht
19932014
Meridiu
m, Inc.
All
rights
reserve
d.
C
rea
tin
g
Res
our
ces
fro
m
Scr
atc
h
To
create a
new
Resourc
e for a
System
Reliabil
ity
Analysi
s:

While
viewing
the
desired
System
Reliabil
ity
Analysi
s on any
page,
on the
Tools
menu,
click
the
Resourc
es link.
The
Resourc
es
window
appears.
C
l
i
c
k
t
h
e
A
d
d
N
e
w
b
u
t
t
o
n
.
T
h
e
A
d
d
N
e
w
R
e
s
o
u
r
c
e
w
i
n
d
o
w
a
p
p
e
a
r
s
.
T
h
e
A
d
d
N
e
w
R
e
s
o
u
r
c
e
s
w
i
n
d
o
w
d
i
s
p
l
a
y
s
t
h
e
d
e
f
a
u
l
t
d
a
t
a
s
h
e
e
t
t
h
a
t
h
a
s
b
e
e
n
d
e
f
i
n
e
d
f
o
r
t
h
e
S
y
s
t
e
m
R
e
s
o
u
r
c
e
f
a
m
i
l
y
.

Define
the
proper
ties of
the
Syste
m
Resour
ce
record
as
desire
d.
Click
OK.
The
Resour
ce is
create
d and
appear
s in
the
grid
on the
Resour
ces
windo
w.
V3.6.0
.0.0 Copyri
ght
19932014
Meridi
um,
Inc.
All
rights
reserv
ed.
I
mp
ort
ing
Ex
isti
ng
Re
so
urc
es
When
you
import
a
Resour
ce
from
one
Syste
m
Reliab
ility
Analys
is into
anothe
r, the
Meridi
um
APM
system
creates
a copy
of the
existin
g
Syste
m
Resour
ce and
links
the
new
record
to the
root
Syste
m
Analys
is
record
of the
target
analysi
s.
To
import
a
Resour
ce
from
one
analysi
s into
anothe
r:
Open
the
Syste
m
Reliab
ility
Analys
is into
which
you
want
to
import
the
Resour
ce.
While
viewin
g the
desire
d
Syste
m
Reliab
ility
Analys
is on
any
page,
on the
Tools
menu,
click
the
Resour
ces
link.
The
Resour
ce
windo
w
appear
s.
Click the
Import button.
The Resource
Finder
window
appears,
which
displays the
Resources that
are available
to be
imported.
In this image,
the Resource
Finder
window
displays what
Resources can
be imported
into an
analysis,
assuming the
System
Reliability
Analysis
Example
Resources
have already
been created.
Select the row
containing the
Resource that you
want to import.
Click OK.
A copy of the Syste

Resource record is
and the imported R
appears on the Reso
window.
V3.6.0.0.0 - Copyri
1993-2014 Meridiu
Modifyi
Resource
To modify an existi
Resource:
While viewing
desired System Rel
Analysis on any pa
Tools menu, click t
Resources link.
The Resources win

appears.
Click the hyper

the Resource that y
modify.
The <Resource Nam

appears, where <Re
the name of the Sys
record that you sele
The <Resource Nam

displays the default
has been defined fo
Resource family. T
displays the Vibrati
window, which def
properties for the V
Technician System
Modify the field

Resource record as
Click OK.
Your changes are sa
V3.6.0.0.0 - Copyri
Meridium, Inc. All
Deleting
To delete a Resourc
While viewing
Tools menu, click t
The Resource wind
Select the row c

record that you wan
Click the Delete
A confirmation mes
really want to delet
Click the Yes b
The Resource is rem

window. The Syste
the database when y
V3.6.0.0.0 - Copyri
rights reserved.
About R
Simulatio
When you run a sim

running Monte Car
System Reliability
calculated from tho
You will want to ru

creating the System
changes to a System
the simulation resu
parameters or modi
simulation, all Diag
are valid or contain
If changes have
all Scenarios will b
If no changes h
parameters, only th
since the last simul
new simulation run
If no changes h
parameters or any o
you are directed to
Note: If no changes
parameters or any o
or Event Log check
will include every S
Keep in mind that i

Various factors infl
process, including:
The number of
The complexity
Assets, Risks, Actio
The frequency a
The frequency a
To shorten the run t

the number of itera
You can run only o

simulation is runnin
in other areas of the
Clicking anywh
main window outsi
When you do so, th
background, and th
Meridium APM Fra
finishes, the dialog
automatically.
-or-
Clicking either
Run Simulation dia
simulation will con
minimized dialog b
taskbar. When the s
be maximized and r
V3.6.0.0.0 - Copyri
rights reserved.
Runnin
To run a simulation
On any page in
click the Run Simu
The Browse For Fo

select or create a fo
Note: If the Enable

System Reliability
For Folder dialog b
Navigate to the
Logs.
Click OK.
The Run Simulatio

that indicates the pr
Note: If there are al

select, a warning m
Event Log files ma
After the progress b

Discard and Close b
view the results, yo
close the Run Simu
that you want to vie
Click the Go to
The System Reliab
V3.6.0.0.0 - Copyri
About E
The Event Log is a

you run simulations
Event Log field in t
you run the simulat
every Scenario in th
that happens in the
<Iteration Number
<Scenario Nam
<Iteration num
the file.
The Event Log files

simulation. The Ev
opened in Microsof
information:
Time: The start
Name: The nam

record, that is detai
Event: The even

can be listed are:
Alert: A con
Complete: An A
Complete Unpl
repairs to an elemen
Failed: An elem
can run again.
Global Event O
assigned to that Glo
Running: The e
Schedule next <

schedule of an Acti
rescheduled and <N
Action.
Shutdown: An e
Simulation End
Standby: A Swi
Start: An Action
Start Unplanned
element that has fai
Stopped: The el
Path: The locati
V3.6.0.0.0 - Copyri
Underst
Event Lo
The following imag

Scenario A for our
As you can see in th

which point every e
In the following im
the Impeller Failure
caused an unplanne
is detailed in row 2
In the following im
correction, the Wate
stopped, in lines 24
as seen in line 27.
At the same time, in

following image.
At time 4.76786241
line 30. In line 31, h
Failure Risk is com
At time 4.76786241
Failure Risk in line
33-38, all of the Ris
run. The system is a
260.4044794.
V3.6.0.0.0 - Copyri
Refresh
Using the Refresh D

distribution data tha
Analysis.
To refresh multiple
While viewing
Tools menu, select
A confirmation mes
distributions having
Click OK.
The distribution da
V3.6.0.0.0 - Copyri
About t
The baseline Merid

can used to view a
run the System Rel
The following table

generate the System
supporting query id
in the subreport, yo
\\Public\Meridium\
Throughout this do
supporting queries
Each report query c

family. When you r
Analysis, the ENTY
analysis is passed a
Analysis will be dis
directly from the C
Analysis record ma
The System Reliab

Summary
Simulation Res
Plots
Simulation Res
Simulation Res
Simulation Res
V3.6.0.0.0 - Copyri
Runnin
To run the System R
While viewing
Generate Report lin
The System Reliab
V3.6.0.0.0 - Copyri
Summa
The Summary secti

stored in the System
The following table

Analysis record fie
V3.6.0.0.0 - Copyri
Simulat
The Simulation Res

information that is
Results for each sce
each element within
Reliability Report.
The following table

System Element Re
V3.6.0.0.0 - Copyri
Plots Se
The Plots section o

Reliability Summar
Analysis Example.
The Plots section d

Total Cost.
Total Cost Tren

Annual Action
Action Cost Tre
Resource Occur
Resource Time.
Resource Cost.
V3.6.0.0.0 - Copyri
Simulat
The Simulation Res

and any Subsystem
System Element Re
page. The following
The results for each

record. The followi
System Element Re
V3.6.0.0.0 - Copyri
Simulat
The Simulation Res

belong to each Scen
appears in the Actio
Simulation Results

record. The followi
System Action Res
V3.6.0.0.0 - Copyri
Simulat
The Simulation Res

used in the System
information that ap
image shows the Si

each record. The fo
corresponding Syst
V3.6.0.0.0 - Copyri
What C
Analysis?
When you run a Mo

performance, and re
simulation results a
Results pages.
By reviewing the re
Which Scenario
Which Scenario
Which Scenario
Which Actions
How many time

How much did
For how long w
How many time
After reviewing the

provides the best re
might decide to com
Refine the Scen

components to furth
Create Recomm
desirable Scenario.
V3.6.0.0.0 - Copyri
Underst
When you run a Mo

performance, and re
presented in the Sys
The System Reliabi

simulation using gr
Total Cost.
Cost Trend.
Annual Action
Action Cost Tre
Resource Occur
Resource Time.
Resource Cost.
The simulation resu

following grids are
Elements Grid.
Actions Grid.
Resources Grid
By clicking a cell in
Histogram.
Trend.
Impact.
V3.6.0.0.0 - Copyri
What Is
The average total i

Meridium APM sys
a simulation, such a
In our System Relia

displays the averag
analysis had one th
system for the total
In this image, the 2

were calculated for
V3.6.0.0.0 - Copyri
What is
Some results of a S
selected. The simul
pane on the System
The values in th
System Analysis re
The value in the

field in the System
month of the simula
Yearly, the g
Period, Period Unit
Monthly, the gr
the Period, Period U
For example, for ou
So the Total Cost T

year in our simulati
If the values were c

were changed to tho
In this case, the foll
V3.6.0.0.0 - Copyri
Show T
The Show Total che
Total Cost grap

Annual Action
Resource Cost g
In these graphs, eac

displayed, as descri
When the Show

individual cost type
are represented in e
When the Show

displays the total co
The following imag

is selected.
The following imag

Show Total check b
V3.6.0.0.0 - Copyri
Total Co
The Total Cost tab

for each Scenario. T
Planned Correction
The following imag
Note: If you prefer

the Show Total chec
The preceding imag

graph, Scenario B h
Scenario B which i
Actions. To see the
The categories in th
Lost Production
production for any
record that represen
Action Cost: Th
complete any Actio
to calculate Action
System Acti
System Resourc
System Resourc
Planned Correc
cost to repair an ele
Resources used. Th
System Subs
System Asset re
System Switch r
System Risk
System Resourc
System Resourc
Unplanned Cor
includes the cost to
unplanned correctio
System Subs
System Asset re
System Swit
System Risk
Correction Cost Un
System Resourc
System Resourc
V3.6.0.0.0 - Copyri
Total Co
The Total Cost Tren

average total cost fo
The following imag
This image shows t

the Total Cost Tren
The cost for Sce
The cost for Sce
The cost for Sce
You can draw the fo
Neither Scenari
Scenario B had
the one singular occ
comparing the year
reduce the cost of t
the graph, you can
Hint: While Scenar

the highest overall
having the lowest o
interval.
V3.6.0.0.0 - Copyri
Annual
The Annual Action
the average cost of
The following imag
Note: If you prefer

the Show Total che
This image shows t

Scenario B is the on
annual action costs
You can also compa

maintenance (Vibra
green bar, and rede
From this graph, yo

Technician Resourc
investigate whether
V3.6.0.0.0 - Copyri
Action C
The Action Cost Tr

average total cost fo
The following imag
This image shows t

B is the only Scena
costs over time for
You can also use th

graph to the Cost T
the large increase in
took place, and the
2013 combined. By
action is worth the
V3.6.0.0.0 - Copyri
Resourc
The Resource Occu

displays statistics a
Resource record is
Note: For System R

will be zero, and it
contains the value F
both the Resource T
The following imag
This image shows t

Bearing Resource w
and C and about ze
only in unplanned R
repair any potential
From looking at thi

to repair Bearings s
the Seal Resource w
V3.6.0.0.0 - Copyri
Resourc
The Resource Time

amount of time that
time that the Resou
The following imag
This image shows t

graph, you can see
The Mechanic R
Scenario B has Act
for maintaining equ
A and C by designi
The Vibration T
Resource is assigne
Scenario B. From t
Resource can be us
V3.6.0.0.0 - Copyri
Resourc
The Resource Cost

Resources used in t
The following imag
Note: If you prefer

Show Total check b
The preceding imag

Plot graph, you can
Scenario A and
used during unplan
Scenario B used
The Vibratio
This Resource acco
The Bearing an
Action. These two
Whereas an unplan
correction requires
the need for a plann
we can conclude th
failure itself.
Note: While the Re

that the Resource C
must also be taken
V3.6.0.0.0 - Copyri
Elemen
The Elements grid o

Analysis.
The following colu
Element: Displa
Failures: The av
Downtime (Day
Scenario to which i
Cost ($): The av

belongs to the item
Reliability: The
belongs.
Note: Reliability is
Availability: Th
Next Failure (D
V3.6.0.0.0 - Copyri
Actions
The Actions grid on

Analysis.
The following colu
Action: Display
to which they belon
Occurrences: T
Cost ($): The av
Detected Failur
monitoring Actions
V3.6.0.0.0 - Copyri
Resourc
The Resources grid
The following colu
Resource: Disp
hierarchy to which
Occurrences: T
Note: For System R
Time (Days): T
Cost ($): The av
V3.6.0.0.0 - Copyri
About t
While the grids on

calculate the averag
The distribution of
When an actual val
bin.
Note: The number o
Additional values a
Optimistic Valu
Average Value:
Scenario.
Realistic Value:
Scenario.
Note: If the median
Pessimistic Valu
This image displays

bins are defined for
Bin One: Repre

from 0.00 to 0.35 ti
Bin Three: Rep

failed from 0.70 to
Bin Six: Repres

Bin Nine: Repre

failed from 2.80 to
Bin Twelve: Rep

failed from 3.85 to
Bin Fifteen: Re
failed from 3.85 to
Bin Eighteen: R
failed from 4.90 to
Bin Twenty: Re
Note: Bins that are
failure within their
In addition, in the i
Optimistic: Rep
failure is 1.00.
Average: Repre
Realistic: Repre
Pessimistic: Re
failure is 5.00.
V3.6.0.0.0 - Copyri
Trend P
While the grids on

helpful as well. The
System Analysis re
Yearly, the Cos
Monthly, the Co
This image displays

most Water Pump f
Failure column of t
breaks out the total
2010 Bar: Repr
2011 Bar: Repr
2012 Bar: Repr
2013 Bar: Repr
2014 Bar: Repr
2015 Bar: Repr
2016 Bar: Repr
The value in the gri
V3.6.0.0.0 - Copyri
Impact
While the grids on

as well. The Impact
Note: This plot is n
This image displays

information in the F
The Impact Plot bre
Right bar: Repr
Center bar: Rep
Left bar: Repre
The value in the gri
V3.6.0.0.0 - Copyri
Interpre
The results for a sim

understand how to
should keep in min
If an unplanned
correction of the so
If a planned cor
Risk:
Planned cor
Planned resourc
Downtime
Downtime for each
If an unplanned
individual Risk:
Fixed unpla
Variable unplan
Unplanned reso
Downtime
Variable unplanned
If planned or un
record to which the
suppose that the fol
A Bearing f
A Seal failure R
In this case, when t
If planned or un
that additional Ris

two times as a res
simulation results.
V3.6.0.0.0 - Copyri
What is
Performing a Cost o
failure data to calcu
such as:
Unplanned labo
Production and
Purging the sys
Cleanup or fine
Lost Profit Opp
Meridium APM Re
effect on maintenan
comparison.
The production sys

units can be treated
production unit fail
Based on these resu

indicate specific fai
Cost of Unreliabilit
population of equip
V3.6.0.0.0 - Copyri
Data Us
The following table
V3.6.0.0.0 - Copyri
Accessin
To view a list of ex
On the Reliabil
The Select a Cost o
From this page, you

analysis summary f
V3.6.0.0.0 - Copyri
Aspects
The Select a Cost o
The Unreliability C
customized for you
top of the page as d
The Published Ana
Any (%): Will c
Yes (Y): Will ca
No (N): Will ca
The Last Updated B
Your user name
The user name

updated by that use
The [All Users]
Each time you acce

different criteria, yo
Note: Although the
The default Unrelia

Failures, and Main
can use the options
V3.6.0.0.0 - Copyri
Commo
The Common Tasks
New Analysis: D
Open Analysis:
Publish Analyse
selected analysis.
Delete Analysis
Send To: Displa

Help: Displays
Guidelines: Dis
Note: The Save Ana
V3.6.0.0.0 - Copyri
Using th
Using the Cost of U
Based on a new
By manually en
You can access the
V3.6.0.0.0 - Copyri
Creatin
To create a Cost of
On the Select a
The Cost of Unrelia
Hint: Select the Do
Click the Next b
The Select Data So
Select one of th
Failure data wil
I will create a n
in the Query Builde
Failure data wil

you choose was cre
unformatted mode
I will create a n
button in the Datase
After you have sele
Click the Next b
The Select Failure F
Select the desir
Unit ID: Th
Installation Dat
Failure Date: T
Click the Next b
The Provide Inform
In the Downtim
In the Time Un
Click the Next b
The Provide Inform
You can genera
Maintenanc
LPO: The profi

reserves over costs
offered to keep the
Currency: The t
appears in the resul
oad the analysis after opening it.
le to higher costs to produce reserves over costs to produce current production (had production not been
you are viewing an existing analysis, when you click this link, Meridium APM will save any changes that
nput fields:
culated by the Meridium APM system and cannot be modified.
Unreliability Analysis. The values that you select to map on the Select Failure Fields, Provide Information
lumn name in parentheses.
n the failures.
e for the analysis.
quired.
reate the analysis.
nually entered when you create the analysis.
mapped from a query or dataset or manually entered when you create the analysis.
be excluded from the analysis. When cleared, data in the selected row will be included in the analysis. You
lick OK on the Failure Data grid. The failure events marked ignored on the grid will not appear on the plots.
a source for the analysis.
ntime columns on the Failures tab and is read-only.
e sum of the values in the Maintenance Cost column on the Failures tab associated with each piece of
and the cost of producing it. This value is the sum of the values in the LPO column on the Failures tab
is value is calculated by the Meridium APM system using the costs in the LPO and Maintenance Cost fields
ce of equipment or location. This value is calculated by the Meridium APM system and is read-only.
or capacity. Availability is not tied to production and profits. Values in this column are calculated by the
verts them to the units that you select.
change the downtime units for the failure data independently from the analysis results.
n you click OK, the system displays the new currency on the axis label of the plots.
TBF trend analysis shows the MTBF for a selected set of equipment or locations over time. The MTBF
number. For example, if you selected Years in the MTBF Period Units field, the number you enter in the
e Cost per reporting period are shown. The Cost of Unreliability is an estimate of the total cost caused by
d production units are listed on the x-axis and the specified reporting period is shown on the y-axis.
ction unit.
it. The MTBF plot displays the units on the x-axis and the MTBF values are shown on the y-axis.
is returned to productive service. The MTTR plot displays MTTR values on the x-axis and the units on the y-
escribes the past performance of equipment but not time in service or capacity; availability is not tied to
in a given period, assuming 100% capacity is normally achieved.
s period. The units are listed on the x-axis and the number of failures are shown on the y-axis.
duction unit.
hutdowns, the Downtime Pareto plot displays the downtime for each production unit. The units are listed on
bal trend for all units or show trends for individual units. The trend frequency determines the duration
nd click the Next button.
elected unit, clear the check box located in front of the unit.
a secondary measure, skip to step 9 of these instructions.
n the Units of Measurement dialog box. Trend dates appear on the x-axis.
Plot Data link in the Plot Options menu.
ng on the chart type, the numeric data includes information such as the Unit, Cost, MTBF, MTTR,
eport
you can use to view a summary of the results of a Cost of Unreliability Analysis. When you run the Cost of
\\Public\Meridium\Modules\Reliability Manager\SSRS.
older \\Public\Meridium\Modules\Reliability Manager\Reports.
g folder \\Public\Meridium\Modules\Reliability Manager\Reports.
Unreliability Cost Query, which is stored in the Catalog folder \\Public\Meridium\Modules\Reliability

the supporting query collectively as the Cost of Unreliability Report.
the Unreliability Cost family. When you run the Cost of Unreliability Report while viewing a Cost of
ted with the current analysis is passed automatically to the prompt, and the results for the current Cost of
sisReport) or the supporting query (i.e., Unreliability Cost Query) directly from the Catalog, however, you
o retrieve results. The subreports (i.e., Catalog items AssetsubreportUnreliability and
y Report
esults of a Cost of Unreliability Analysis.
e, on the Analysis Tasks menu, click the Generate Report link.
at the Report Options dialog box looks like by default.
click OK.
page.
eserved.
rt displays information that exists in the Unreliability Cost record.
ion and the corresponding Unreliability Cost record field whose data is displayed in the report.
eserved.
alues that are stored in the Failures field in the Unreliability Cost record.
y are stored in the Failures field in the Unreliability Cost record:
rights reserved.
port displays values that are stored in the Failures field in the Unreliability Cost record.
ection, and they are stored in the Failures field in the Unreliability Cost record:
nc. All rights reserved.
ort displays the graphs that are accessed via the Plots menu on the Cost of Unreliability Analysis Summary
a Total Cost Pareto Chart graph.
ort displays the following graphs:
Chart
of Unreliability Analysis
much like a Distribution or Growth Analysis. The analysis can be based on a query or dataset, or the data can
built, it is stored in the database and displayed in a list of the existing Cost of Unreliability Analyses for
Cost of Unreliability analysis from a query, then results are automatically updated with the new data that
since the document was originally constructed.
nalysis appear on the summary page and include the following properties:
uction units included in the analysis.
ilure events that occurred in the units being analyzed.
ost due to failures.
when the production failed in an oversold market. It represents the difference between the market price of
with the failure event (includes parts, labor, LPO, etc.). It may be calculated in a query or a field in the
me that the unit is productive.
ures for the units being analyzed.
, the average amount of time that it takes to restart the production unit(s) after a failure occurs.
n item is not available for any reason.
mmary page, a Cost of Unreliability Analysis generates the following graphs, which show all the data in a
that shows the MTBF for a set of equipment or locations over time. You can view the underlying plot data by
ot Options menu while you are viewing a plot. The numeric results are presented in a grid.
o an Existing Analysis
make changes that you want to retain. The following instructions provide details on saving changes to an
ctions on any page where you see the Save Analysis link enabled on the Common Tasks menu. These
lready been saved when it was originally created.
click the Save Analysis link.
ting analysis.
nalysis
option to save an existing analysis with a different name. This will create two copies of the analysis: one with
new name.
ave it with a different name:
ry page of the analysis you are currently viewing, on the Common Tasks menu, click the Save Analysis As
g box appears.
s dialog box from the Cost of Unreliability Analysis page, it is called the Save Analysis dialog box. The
wever, are the same as shown in the preceding image.
Name text box, type the name that you want to use for the analysis copy. The name is required and must be
of analysis you are saving.
e Analysis Description text box, type a description of the analysis.
M system creates a copy of the analysis and returns you to the page from which you initiated the Save As
ght 1993-2014 Meridium, Inc. All rights reserved.
ing an Analysis
name of an analysis via the Rename Analysis dialog box. You can access this dialog box:
Rename link on the Analysis Tasks menu on the Reliability Growth Analysis page, the Probability
s page, and the Cost of Unreliability Analysis page.
Rename Analysis link on the Production Analysis page.
sis:
ate page and task menu, click the Rename or Rename Analysis link.
sis dialog box appears.
nalysis Name text box, type a new name for the analysis.
d, in the Analysis Description text box, type a new description for the analysis.
Click the Rename button.
analysis name is updated in any appropriate sections on the summary page and in the site map to reflect the
ge. In addition, the Description field in any appropriate sections will reflect any changes.
Click the Save link on the appropriate task menu to save the changes to the analysis name.
Note: While your changes appear as soon as you close the Rename dialog box, the new name is not
actually saved until you save the analysis.
Setting the Confidence Level for an Analysis

For Reliability Growth, Reliability Distribution, and Probability Distribution Analyses, the confidence
level specifies how the optimistic and realistic scenarios will be selected in a Monte Carlo Simulation.
The confidence level will be checked against the number of iterations to ensure that the confidence limits
are statistically significant. The default Confidence Level for an analysis is 90 percent.
Note: Confidence is not calculated for TTR distributions.
The following instructions provide details on setting the confidence level for these analysis types. Note
that you can also define the level of confidence for System Reliability Analyses, but these instructions do
not apply to that analysis type.
To set the confidence level for an analysis:
On the summary page of the analysis you are currently viewing, click the Confidence Level
link on the appropriate task menu.
Hint: The Confidence Level link is located on the Current Analysis, Analysis Tasks, or
Distribution Options task menu, depending upon the type of analysis you are viewing.
The Confidence Level dialog box appears.
Select the Use Confidence check box to activate the Confidence Level and enable the
Confidence Level field.
In the Confidence Level field, enter a numeric value between zero (0) and 100 to
represent the desired Confidence Level.
Click OK.
The Meridium APM system calculates the confidence intervals for the analysis based on
the percentage you entered in the Confidence Level field.
Changing the Distribution Type

When you create a Reliability Distribution Analysis or a Probability Distribution Analysis,
the distribution type is set to Weibull by default. After the analysis is created, you can
change the distribution type, if desired.
You can change the fit method via the Distribution Type dialog box. You can access this
dialog box:
For a Reliability Distribution Analysis by clicking the Distribution Type link on the
Analysis Tasks menu on the Time To Failure Distribution page or the Time to Repair
Distribution page.
-or For a Probability Distribution Analysis by clicking the Distribution Type link on the
Distribution Options menu on the Probability Distribution Results page.
To change the distribution type:
On the appropriate page and task menu, click the Distribution Type link.
The Distribution Type dialog box appears.
On the Distribution Type dialog box, select: Auto, Weibull, Normal,

LogNormal, or Exponential.
Hint: Select Auto if you want the Meridium APM system to select the
appropriate distribution type based on the results of the Goodness of Fit
test.
Click OK.
The analysis is recalculated based on the selected distribution type.

reserved.
Modifying the Fit Method

The Kolmogorov-Smirnov test is a Goodness of Fit (GOF) test
applied to Reliability Distribution and Probability Distribution
Analyses to determine how well the data fits the analytical curve.
When you create an analysis, the fit method is set to Least Squares
by default. After you have created an analysis, you can modify the
fit method using the instructions in this topic.
The method of fit for a Distribution Analysis can be:
Least Squares: A curve-fitting estimation method that
relies on linear regression techniques to estimate the
parameters for the distribution.
Maximum Likelihood Estimators: A curve-fitting

estimation method that maximizes the likelihood function
for a given population. This method includes a survivor
function that estimates changes in reliability as the piece of
equipment or location survives beyond a certain age.
To modify the fit method:
On the analysis summary page of the analysis you are
currently viewing, click the Fit Method link on the
appropriate task menu.
Hint: The Fit Method link is located on the Analysis Tasks
or Distribution Options task menu, depending upon the type
of Distribution Analysis you are viewing.
The Fit Method dialog box appears.
On the Fit Method dialog box, select the Least

Squares or Maximum Likelihood option.
Click OK.
The analysis is recalculated based on the
selected fit method.
V3.6.0.0.0 - Copyright 1993-2014

Changing the
Distribution
Parameters
In Reliability Distribution Analyses and
Probability Distribution Analyses, the
parameters of the distribution are defined on
the Distribution Parameters dialog box.
You have the option of specifying that these

values should be calculated automatically or
manually specifying values for the Beta, Eta,
and Gamma parameters. On the Distribution
Parameters dialog box, the Calculate check
box is selected for any parameter that has
been calculated by the system. By clearing
the Calculate check box, you can enable the
corresponding parameter text box and enter a
different value.
You can access the Distribution Parameters
dialog box:
For Reliability Distribution Analyses by
clicking the Change link in the Distribution
Parameters section of the Time To Failure
Distribution page or the Time to Repair
Distribution page.
-or For Probability Distribution Analyses by
clicking the Parameters link on the
Distribution Options menu on the Probability

Distribution Results page.
To modify the distribution parameters:
Click the appropriate link on the
appropriate page.
The Distribution Parameters dialog box
appears.
Clear the Calculate check box

next to the parameter(s) whose value
you want to modify.
The parameter field(s) are
enabled.
Type the desired value for
the parameter.
Click OK.
Note: If you reselect the
Calculate check box after
manually entering data and
then click OK, the manually
entered data for the parameter
will not be retained. If you
decide not to use the
parameters you entered, click
Cancel, and the previous
selection will be used in the
calculations.
The system recalculates the

analysis based on the selected
distribution parameter.
rights reserved.
Modifying
the Analysis
Period
In Reliability Growth,
Reliability Distribution, and
Unreliability Cost Analyses,
the analysis period specifies
the date range over which an
analysis occurs. The start date
specifies the first date of the
analysis and the end date
specifies the last date of the
analysis. The default analysis
period has a start date equal to
the first failure date and an
end date equal to the current
date. When the default
analysis period is used, each
time you open an analysis, the
end date is updated to the
current date. You can adjust
the analysis period to focus
the analysis on a specific
period of time.
The following instructions
provide details on modifying
the analysis period in these
analysis types. Note that you
can also modify the analysis
period for a Spares Analysis,
but these instructions do not

apply to that analysis type.
To modify the current analysis
period:
On the summary page of
the analysis you are currently
viewing, click the Analysis
Period link on the appropriate
task menu.
Hint: The Analysis Period link
is located on the Analysis
Tasks or the Current Analysis
task menu, depending upon
the type of analysis you are
viewing.
The Analysis Period dialog
box appears.
Clear the Start

Date check box, and
then type or select the
desired date.
Note: To ensure that all
failure dates appear on
the plots, make sure
the start date is before
the date associated
with the first datapoint.
Only failures that

occur after the start
date will appear on the
plots.
Clear the
End Date check
box, and then
type or select
the desired
date.
Click
OK.
The
Meridiu
m APM
system
saves
the
analysis
period
and
recalcul
ates the
analysis
using
the
selected
dates.
Note: If
you
want to
change
the
analysis
period
back to
the
default
analysis
period,
select
the Start
Date
and End
Date
check
boxes.
V3.6.0.
0.0 Copyrig
ht
19932014
Meridiu
m, Inc.
All
rights
reserved
.
C
hoo
sin
g
the
Ti
me
Uni
ts
for
an
An
alys
is
For
Reliabil
ity
Growth
and
Reliabil
ity
Distribu
tion
Analyse
s, the
time
units
are used
for
expressi
ng time
values
for
calculati
ons
perform
ed
within
the
analysis
. For
example
,a
calculati
on may
indicate
the
amount
of time
that
elapsed
between
a failure
event
and the
end date
of the
analysis
period.
This
value
would
be
express
ed in
the
Time
Units
for the
analysis
.
Your
Time
Units
selectio
n will
depend
on what
type of
data
you are
using
and
what
type of
analysis
you are
perform
ing. For
example
, in an
analysis
that
shows
the
distribut
ion of
failures
for a
number
of
equipm
ent or
location
s over
many
years,
years
might
be an
appropri
ate unit
of time.
For an
analysis
designe
d to
evaluate
failures
for a
single
piece of
equipm
ent or
location
within a
very
specific
time
period,
a
smaller
unit of
time
would
be
appropri
ate. For
this
reason,
you
have the
option
of
choosin
g the
Time
Units
that are
most
appropri
ate for a
given
analysis
.
Note:
Downti
me for
TTF
calculati
ons
should
always
be
provide
d using
days.
When
the
failure
data
contains
downti
me, the
system
selects
Days by
default.
The
followin
g
instructi
ons
provide
details
on
modifyi
ng the
time
units for
a
Reliabil
ity
Growth
or
Reliabil
ity
Distribu
tion
Analysi
s. Note
that you
can also
modify
the time
units for
a
System
Reliabil
ity
Analysi
s, but
these
instructi
ons do
not
apply to
that
analysis
type.
To
change
the time
units for
an
analysis
:
On
the
Reliabil
ity
Growth
Analysi
s page,
on the
Current
Analysi
s menu,
click
the
Time
Units
link.
-orOn the
Reliabil
ity
Distrib
ution
Summa
ry page,
on the
Analysi
s Tasks
menu,
click
the
Time
Units
link.
The
Time
Units
dialog
box
appears.

O
n
t
h
e
T
i
m
e
U
n
i
t
s
d
i
a
l
o
g
b
o
x
,
i
n
t
h
e
O
p
e
r
a
t
i
n
g
T
i
m
e
U
n
i
t
s
l
i
s
t
,
s
e
l
e
c
t
D
a
y
s
,
Y
e
a
r
s
,
Q
u
a
r
t
e
r
s
,
M
o
n
t
h
s
,
W
e
e
k
s
,
o
r
H
o
u
r
s
.
In
the
Downt
ime
Units
list,
select
Days,
Years,
Quart
ers,
Month
s,
Weeks,
or
Hours.
Click
OK.
The
Meridi
um
APM
system
autom
aticall
y
recalc
ulates
the
analys
is
based
on the
new
time
units
and
displa
ys the
new
units
on the
plot
pages
and
the
summ
ary
page.
V3.6.0
.0.0 -
Copyri
ght
19932014
Meridi
um,
Inc.
All
rights
reserv
ed.
M
odi
fyi
ng
An
aly
sis
Da
ta
via
the
Fai
lur
e
Da
ta
Wi
nd
ow
You
can
use
the
<Mea
surem
ent>
Data
windo
w to
modif
y the
data in
any
enable
d
field.
This
allows
you to
correct
errors
in the
data or
adjust
data as
neede
d.
Note
that
only
certain
fields
in the
<Mea
surem
ent>
Data
windo
w can
be
modifi
ed.
Fields
that
contai
n
calcul
ations
by the
Meridi
um
APM
system
are
disabl
ed.
When
you
modif
y data
and
click
OK,
the
analys
is will
be
update
d to
reflect
any
chang
es that
you
made.
For an
analysis that
is based upon
manually
entered data,
the changes
that you make
via the
<Measureme
nt> Data
window will
be saved for
the analysis.
For an
analysis that
is based upon
a query or a
dataset, the
query or
dataset will
not be
modified with
the updated
data.
Additionally,
any record
returned by
the query will
not be
updated with
your changes.
The changes
will be saved
to the analysis
only.
After you
modify the
data and save
the analysis,
the modified
data will
appear each
time you open
the analysis.
If you want to
revert to the
original data,
you can
reload the
original data
to the
analysis. In
addition, if a
query or
dataset has
changed in
the database,
you can
reload the
data in order
for your
analysis to
contain those
changes.
1993-2014
Meridium,
Inc. All rights
reserved.
Relo
ading
Analy
sis
Data
When you
create and
save analyses
that are based
on a query or
dataset, the
Meridium
APM system
takes a
snapshot of
the data that

exists at the
time of
creation and
saves it along
with the
analysis.
When you
open an
existing
analysis, the
Meridium
APM system
loads the data
that was last
saved with the
analysis. This
means that
any changes
to the
underlying
query or
dataset will
not be
reflected
automatically
when you
open an
existing
analysis.
Note: If the
query or
dataset has
been deleted
or renamed,
when you try
to open an
associated
analysis, an
error message
will be
displayed, and
the data will
not be
refreshed.
If you want to
refresh an
analysis based
upon changes
to the
underlying
query or
dataset or to
load new data
that has been
added since
the analysis
was last saved
(e.g., the
analysis is
based on a
query that
retrieves
failures for a
piece of
equipment or
location, and
a new failure
record has
been added to
the database),
you will need
to reload the
analysis
manually
after opening
it.
The
instructions in
this topic
provide
details on
reloading a
reliability
analysis. This
feature is
available for
the following
analyses
types:
Production
Analyses.
Reliability
Growth Analyses.
Reliability
Distribution
Analyses.
Production
Analyses.
Probability
Distribution
Analyses.
Cost of
Unreliability
Analyses.
Note: Reloading
analysis data resets
the analysis period
only if it is based o
the analysis data.
Start Dates and End
Dates that have bee
set explicitly will n
be overwritten.
To reload an analys
to display the most
recent data:
On the summar
page of the analysis
you are current
viewing, click the
Reload Data link.
Hint: The Reload

Data link is located
on the Analysis Tas
or Current Analysis
task menu, dependi
upon the type of

analysis you are
viewing.
A confirmation
message appears,
asking if you want
overwrite the curre
data with the data
stored in the
database.
Click OK.
The analysis is upd

reflect the data curr
stored in the query
dataset.
Note: If you are rel

analysis data that is
a query and an inde
range error messag
there is an error in t
You should modify
or recreate the anal
order to reload the
data.
V3.6.0.0.0 - Copyri
1993-2014 Meridiu
Generat
a Report
an Analy
By generating a rep
analysis, you are co
the analysis into a f
that can be printed.
you generate a repo

analysis, you will b
various options for
can include in the r
such as a cover pag
specific information
the analysis. The se
will vary, dependin
which analysis you
printing. Likewise,
selections you mak
depend upon your p
needs.
The following instr

provide details on g
reports for the follo
analysis types:
Production Ana
Reliability Grow
Reliability Dist
Probability Dist
Analysis.
Cost of Unrelia
The steps for creati

System Reliability
Spares Analysis dif
to create a report in
Note: Before you c

report for an analys
it to the database.
To generate a repor
On the analysis
of the analysis you
viewing, click the G
link.
Hint: The Generate

located on the Anal
Current Analysis ta
depending upon the
you are viewing.
The Report Options

appears.
The specific option

the Report Options
vary, depending on
analysis you are pri
Select the check

that you want to inc
that some options a
You can clear the c
that you do not wan
Click OK.
The report appears
page.
V3.6.0.0.0 - Copyri
Meridium, Inc. All
About P
and Unpu
Analyses
Reliability analyses
you flag each analy
unpublished. If the
selected, the analys
published. If the Pu
selected, the analys
unpublished. The P
indicate to other us
analysis. New analy
default.
The Published flag

customize the analy
published analyses,
analyses, or both. E
analysis list queries
Distribution, Reliab
Reliability Growth,
Unreliability Cost,
Published Analyses
filter the analysis li
Published flag in ea
Note: The baseline

stored in the Merid
following folder:
Public\Meridium\M
Manager\Analyses.
configured by defau
Published Analyses
customize the queri
needs of your imple
After you run the a

display the desired
list, you can publish
analysis from the fo
Select a Growth
Select a Distrib
page.
Probability Dist
Select a System
List page.
Select a Cost of
Select a Spares
Note that the Publis

analysis summary p
You can also modif
opening the analysi
modifying the valu
record.
Note: There are no

recommended work
publish and unpubl
analyses should be
default, any user ca
analysis at any time
V3.6.0.0.0 - Copyri
Inc. All rights reser
Publish
To publish an analy
unpublished:
On the appropri
of analyses, select o
analyses that you w
Note: The Common

Publish Analyses o
unpublished analys
appears as Unpubli
combination of pub
analyses, the name
for the last analysis
will perform that ac
Therefore, to publis
only unpublished a
On the Commo
Analyses link.
A confirmation mes
to publish the selec
Click the Yes b
The analysis is pub
Note: If you selecte

appears for each an
as desired, until all
V3.6.0.0.0 - Copyri
reserved.
Unpubl
To unpublish an an
On the appropri
select one or more
Note: The Common

only when you sele
appears as Publish
published and unpu
appropriate for the
perform that action
all analyses, you sh
On the Commo
A confirmation mes
the selected analysi
Click the Yes b
The analysis is unp
Note: If you selecte

analysis. Respond t
have been unpublis
V3.6.0.0.0 - Copyri
Custom
You can customize
Displaying loga
Failure Rate plot, w
values. Note that th
be changed under n
Zooming in on
Resetting the pl
settings will be sav
modified, they will
all user-defined sett
Note: Resetting the

common to standar
To reset the display
Right-click
from the shortcut m
The system applies
V3.6.0.0.0 - Copyri
Workin
Analyses
of right-censoring,
analysis end date. Y
Time To Failure (T
the piece of equipm
For example, part o

that are represented
you do not know w
not occurred, but yo

did operate for calc
When you censor d

for the updated TTF
To censor datapoin
For a Reliability
of the following plo
Probability Plot
Failure Rate Plo
Probability Den
Cumulative Den
-or-
For a Distributi
box for the desired
Additionally, when
censored datapoint
plot. Each automati
in the Analysis Peri
Note: Probability D
For example, if the

automatically censo
Analysis. If you ch
box), then the plots
and TTF values.
Note: Although aut

appear in the Failur
When you pause on

appear:
Auto-Censored
Name: Specifie
Installation Dat
TTF value: Rep

Date.
V3.6.0.0.0 - Copyri
About R
When you perform

actions should be ta
analysis suggest tha
recommend that the
These recommenda
linked to the analys
an analysis, you wi
with that analysis. F
each Recommendat
V3.6.0.0.0 - Copyri
Accessin
The Recommendati
functionality for a R
can view a summar
Reliability Recomm
Recommendation r
To access the Reco
On the analysis
Recommendations l
Hint: The View Rec

menu, depending o
-or-
On any page of a S
link on the Tools m
The Recommendati
V3.6.0.0.0 - Copyri
Aspects
The Recommendati
linked to a given R
displays the list of R
By default, the grid
Recommendatio
Recommendatio
Assigned To
Target Complet
Implemented D
If desired, you can

default display.
Each row in the list

record.
No color: Indic
following condition
Red: Indicates t
are colored red whe
Yellow: Indicat
Recommendations
current date.
Green: Indicate
V3.6.0.0.0 - Copyri
About t
Recomme
The Common Tasks

list of Reliability R
Recommendations p
For the following a

Recommendations p
Production.
Spares.
System Reliabil
For the following a

specific to that type
analysis summary p
Reliability Grow
Reliability Dist
Probability Dist
Unreliability Co
For example, if you

Analysis record, fo
Tasks. The Plots, To
analysis and contai
Summary page.
Note: When you ar

the View Summary
you are viewing the
the current analysis
V3.6.0.0.0 - Copyri
Commo
The Common Tasks
New Recomme
Recommendation r
Open Recomme
Recommendation
Save Recomme
Delete Recomm
Recommendation r
Send To: Displa

desktop (create sho
Help: Displays
V3.6.0.0.0 - Copyri
Aspects
The Recommendati
main display area c
Information and Al
associated with the
A toolbar appears a
currently displayed
Displays a blan
Reliability Recomm
system first display
Saves the curre
Saves the curre

blank datasheet on
Recommendation r
After asking fo
displayed.
Copies the info

you can create a ne
Displays the Pr
record will be print
Displays the Re
documents for the c
is related to the Ref
Displays Field
history is set to be k
V3.6.0.0.0 - Copyri
About t
Recomme
The Common Tasks

Reliability Recomm
the Recommendatio
The same task men

the Recommendatio
options are similar
For example, if you

record that is linked
Plots, Tools, Analys
specific to the Relia
on the Reliability D
Note: When you ar

View Summary link
viewing the analysi
which the current R
V3.6.0.0.0 - Copyri
Commo
The Common Tasks
New Recomme
details for the recor
View Recomme
Reliability Recomm
Save Recomme
Delete Recomm
record and then dis
Send To: Displa

(create shortcut), in
Help: Displays
V3.6.0.0.0 - Copyri
Creatin
Record
You can create a ne

Recommendation D
linked automaticall
To create a new Re
On the Recomm
Recommendation li
The Recommendati
On the General
If you want to n
as desired.
When you have

menu, click the Sav
The Reliability Rec

appropriate fields o
Progress, an Alert r
and an email messa
For example, if on
Date, and the Targe
January 5, 2005, bu
V3.6.0.0.0 - Copyri
Fields in
The following table

Recommendation r
V3.6.0.0.0 - Copyri
Opening
To open an existing
Access the Rec
In the list of Re
record that you wan
The selected Recom

information, as des
If you make any

save your changes.
V3.6.0.0.0 - Copyri
Deleting
You can use the fol
To delete an analys
In the list of ana
On the Common
If you selected one
item.
-or-
If you selected mul

simultaneously or o
To delete th
To delete one it
If there is an ite
If you do not w
The analysis is rem
V3.6.0.0.0 - Copyri
About t
The Reliability Ma
participate in the va
Analyses: Conta
Select a Pro
Select a Spates
Select a Growt
Select a Distrib
Probability Dis
Select a System
Select a Cost of
Automation Rul
Queries: Contai
the baseline produc
Reports: Contai
SSRS: Contains
the Reports folder.
V3.6.0.0.0 - Copyri
Analyse
The Catalog folder
Note: You should n

however, modify th
V3.6.0.0.0 - Copyri
Queries
The Catalog folder
Note: Before you u

the use of additiona
V3.6.0.0.0 - Copyri
Reports
The Catalog folder
assetSubreportD
AssetsubreportG
AssetsubreportU
CostAnalysisRe
to view the Cost of
DistributionAna
you are trying to vi
Exponential Dis
Failuresubrepor
Failuresubrepor
GrowthAnalysi
GrowthAnalysi
trying to view the R
Lognormal Dist
Normal Distribu
ProbabilityDist
ProbDistReport
the Probability Dist
ProductionAnal
ProductionAnal
ProductionAnal
ProductionAnal
are trying to view t
ReliabilityDistr
ReliabilityDistr
ReliabilityExpo
ReliabilityExpo
ReliabilityLogn
ReliabilityLogn
ReliabilityNorm
ReliabilityNorm
ReliabilityWeib
ReliabilityWeib
Spares
Spares Analysis
Spares Analysis
Spares Analysis
Spares Analysis
Spares Analysis
Spares Analysis
SparesAnalysis
SparesApplicat
SparesChart
SubreportDistri
SubReportProb
SubreportProdu
System Reliabil
System Reliabil
System Reliabil
System Reliabil
System Reliabil
SystemReliabil
SystemReliabil
SystemReliabil
SystemReliabil
SystemReliabil
Unreliability Co
Weibull Distrib
V3.6.0.0.0 - Copyri
SSRS F
The items in the Ca
V3.6.0.0.0 - Copyri
Product
A Production Analy
description of the fi
and behavior of the
V3.6.0.0.0 - Copyri
Product
A Production Losse
exist for the Produc
V3.6.0.0.0 - Copyri
Reliabil
A Reliability Grow
repairs necessary to
information in the t
V3.6.0.0.0 - Copyri
Growth
A Growth Model re
behavior of these fi
V3.6.0.0.0 - Copyri
Distribu
A Distribution reco
exist for the Distrib
baseline state and b
V3.6.0.0.0 - Copyri
About S
Actions in System R
System Conditio
System Inspecti
System Prevent
System Special
V3.6.0.0.0 - Copyri
System
System Condition M
exist for the System
fields. This list is n
V3.6.0.0.0 - Copyri
System
System Inspection
System Inspection
comprehensive.
V3.6.0.0.0 - Copyri
System
System Preventativ
System Preventativ
fields. This list is n
V3.6.0.0.0 - Copyri
System
System Special Act

System Special Act
comprehensive.
V3.6.0.0.0 - Copyri
System
System Analysis re
family. The informa
Note: In the follow

Definition page.
V3.6.0.0.0 - Copyri
System
System Asset recor

that exist for the Sy
comprehensive.
V3.6.0.0.0 - Copyri
System
System Buffer reco

System Buffer fami
V3.6.0.0.0 - Copyri
System
System Global Eve

maximizing the ava
table reflects the ba
V3.6.0.0.0 - Copyri
System
System Link record

that exist for the Sy
comprehensive.
V3.6.0.0.0 - Copyri
System
System Resource re
an alphabetical list
baseline state and b
V3.6.0.0.0 - Copyri
System
System Resource re
Usage family and a
V3.6.0.0.0 - Copyri
System
System Risk record

System Asset recor
the System Risk fam
V3.6.0.0.0 - Copyri
System
System Scenario re
the System Scenari
V3.6.0.0.0 - Copyri
System
System Sensor reco

alphabetical list and
V3.6.0.0.0 - Copyri
System
System Subsystem
Subsystem family.
V3.6.0.0.0 - Copyri
System
System Switch reco

of the fields that ex
This list is not com
V3.6.0.0.0 - Copyri
Unrelia
An Unreliability Co
behavior of these fi
V3.6.0.0.0 - Copyri
Parame
The URL for displa

must define at least
Note: Some parame

following table.
V3.6.0.0.0 - Copyri
Exampl
meridium://Rel
Displays the Select
meridium://Rel
Displays the Produ
meridium://Rel
Creates a new analy

the Production amo
meridium://Rel
Launches the Produ
V3.6.0.0.0 - Copyri
Parame
The URL for displa

here.
V3.6.0.0.0 - Copyri
Exampl
meridium://Rel
Displays the Select
meridium://Rel
Displays a new Spa
meridium://Rel
Displays the Spares
meridium://Rel
Opens the Recomm
meridium://Rel
Opens the Recomm
V3.6.0.0.0 - Copyri
Parame
The URL for displa

define at least the P
Note: Some parame

following table.
V3.6.0.0.0 - Copyri
Exampl
meridium://Rel
Displays the Reliab
meridium://Rel
Opens the Reliabili

update the analysis
parameter values di
values dialog box to
meridium://Rel
Launches the Relia
meridium://Rel
Displays the MTBF
meridium://Rel
Opens the Recomm
meridium://Rel
Opens a new Recom
meridium://Rel
Opens on the Recom
meridium://Rel
Opens the Multiple
V3.6.0.0.0 - Copyri
Parame
The URL for displa

Note: Some parame

following table.
V3.6.0.0.0 - Copyri
Exampl
meridium://Rel
Displays the Select
meridium://Rel
Displays the Reliab
meridium://Rel
Opens the Reliabili

dataset to update th
Enter parameter va
parameter values di
meridium://Rel
Displays the Time t
meridium://Rel
Opens the Multiple
meridium://Rel
Opens the Recomm
meridium://Rel
Opens a new Recom
meridium://Rel
Opens the Recomm
V3.6.0.0.0 - Copyri
Parame
The URL for displa

URL, you must def
Note: Some parame

following table.
V3.6.0.0.0 - Copyri
Exampl
meridium://Rel
Displays the Probab
meridium://Rel
Displays the Probab
meridium://Rel
Opens the Probabil

Enter parameter va
parameter values di
meridium://Rel
Opens the Recomm
meridium://Rel
Opens a new Recom
meridium://Rel
Opens on the Recom
V3.6.0.0.0 - Copyri
Parame
The URL for displa

V3.6.0.0.0 - Copyri
Exampl
meridium://Rel
Displays the Select
meridium://Rel
Displays a new Sys
meridium://Rel
If the System Analy

-or-
If the System Analy
meridium://Rel
Displays the Recom
meridium://Rel
Displays the Recom

the Entity Key 0123
V3.6.0.0.0 - Copyri
Parame
The URL for displa

define at least the P
Note: Some parame

table.
V3.6.0.0.0 - Copyri
Exampl
meridium://Rel
Displays the Select
meridium://Rel
Displays the Cost o
meridium://Rel
Opens the Cost of U

Enter parameter va
parameter values di
meridium://Rel
Displays the MTBF
meridium://Rel
Opens the Plot Data
meridium://Rel
Opens the Recomm
meridium://Rel
Opens a new Reliab
meridium://Rel
Opens on the Recom
V3.6.0.0.0 - Copyri
Action
An operation that c
training or procedu
Actions can be uniq
V3.6.0.0.0 - Copyri
Average
The average of all t

time in the Resourc
V3.6.0.0.0 - Copyri
Confide
A value that indicat

must fit the model i
V3.6.0.0.0 - Copyri
Cumula
The amount of time
V3.6.0.0.0 - Copyri
Event L
A text file that store
V3.6.0.0.0 - Copyri
Failure
The inability of a p
V3.6.0.0.0 - Copyri
Global E
A component of a S
the system.
V3.6.0.0.0 - Copyri
Goodne
A test that determin
V3.6.0.0.0 - Copyri
Kolmog
A Goodness of Fit (
V3.6.0.0.0 - Copyri
Least Sq
A curve-fitting estim
V3.6.0.0.0 - Copyri
Maximu
A curve-fitting estim
of equipment or loc
V3.6.0.0.0 - Copyri
Reliabil
How likely it is tha

(1 - The Probability
V3.6.0.0.0 - Copyri
Resourc
Components in a Sy
to use within the an
V3.6.0.0.0 - Copyri
Overvie
The Asset Answers
V3.6.0.0.0 - Copyri
Asset A
The Asset Answers
After you have inst
V3.6.0.0.0 - Copyri
First-Ti
Deploying and con
V3.6.0.0.0 - Copyri
Upgrad
Asset Answers Inte
V3.6.0.0.0 - Copyri
Configu
The following instr

To configure Asset
Access the Mer
On the Configu
The Asset Answers
If you have con

-or-
If you have not con
Asset Answers inte
V3.6.0.0.0 - Copyri
Accessin
To access Asset An
On the Meridiu
If you have configu
V3.6.0.0.0 - Copyri

FE

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

FE

Загружено:

Авторское право:

Доступные форматы

About the Failure Elimination Work

Allows you to recommend changes to improve overall asset

Allows you to use the APM Foundation work process to track

Allows you to measure the effectiveness of your strategy

Production Loss Accounting

Metrics and Scorecards

Root Cause Analysis

Asset Answers Integration

V3.6.0.0.0 - Copyright 1993-2014 Meridium, Inc. All rights reserved.

Failure Elimination System

Production Loss Accounting

Metrics and Scorecards

Root Cause Analysis

Asset Answers Integration

V3.6.0.0.0 - Copyright 1993-2014 Meridium, Inc. All rights reserved.

First-Time Deployment Workflow

Configure the Production Loss

Configure the Generation Management

Configure the Metrics and Scorecards

Configure the Root Cause Analysis

Configure the Reliability Analytics

Configure the Asset Answers

V3.6.0.0.0 - Copyright 1993-2014 Meridium, Inc. All rights reserved.

Production Loss Accounting

Metrics and Scorecards

Root Cause Analysis

V3.6.0.0.0 - Copyright 1993-2014 Meridium, Inc. All rights reserved.

Failure Elimination User Instructions

V3.6.0.0.0 - Copyright 1993-2014 Meridium, Inc. All rights reserved.

Accessing the Failure Elimination

The Dashboard page appears, displaying the Failure Elimination dashboard.

V3.6.0.0.0 - Copyright 1993-2014 Meridium, Inc. All rights reserved.

Aspects of the Failure Elimination

The Failure Elimination dashboard contains the following sections:

Top 10 Bad Actors

Track Results by Recommendation Implementation Year

V3.6.0.0.0 - Copyright 1993-2014 Meridium, Inc. All rights reserved.

The Content Filter section contains the following lists:

V3.6.0.0.0 - Copyright 1993-2014 Meridium, Inc. All rights reserved.

Yearly Cost Trend

The Maintenance Cost value in Work History records in your database.

V3.6.0.0.0 - Copyright 1993-2014 Meridium, Inc. All rights reserved.

Top 10 Bad Actors

Maintenance cost (sum of Maintenance Cost values in associated Work History

V3.6.0.0.0 - Copyright 1993-2014 Meridium, Inc. All rights reserved.

V3.6.0.0.0 - Copyright 1993-2014 Meridium, Inc. All rights reserved.

V3.6.0.0.0 - Copyright 1993-2014 Meridium, Inc. All rights reserved.

Track Results by Recommendation

V3.6.0.0.0 - Copyright 1993-2014 Meridium, Inc. All rights reserved.

The Completed Date field (in the Reliability Recommendation record) or

V3.6.0.0.0 - Copyright 1993-2014 Meridium, Inc. All rights reserved.

Hidden Sections on the Failure

Top 10 Bad Actors (w/o PLA)

Track Results by Recommendation Implementation Year (w/o PLA)

V3.6.0.0.0 - Copyright 1993-2014 Meridium, Inc. All rights reserved.

About the Failure Elimination Catalog

V3.6.0.0.0 - Copyright 1993-2014 Meridium, Inc. All rights reserved.

Behavior and Usage

Displays the Failure Elimination dashboard on the

V3.6.0.0.0 - Copyright 1993-2014 Meridium, Inc. All rights reserved.

Dashboard Queries Folder

Behavior and Usage

Implemented - All Years

Used by one or more source queries to the Failure