CFI - GE APM - Meridium System Run Book

Meridium System Run Book
CF Industries – Donaldsonville and Port Neal

Revision History
Revisio Date Description Author
n
01 2015-10-01 Initial creation; submitted for internal review B Maslar
02 2015-12-08 Updated per discussions with CFI B Maslar
03 2016-05-25 Updated per GSS review B Maslar
04 2018-10-08 Updated with V4 Upgrade information Steve Stiles
Document Reviews
Revision Date Reviewer Role Comments
01 10-02-2015 F Hernandez Tech Consultant Minor corrections regarding DMT
versions
01 10-02-2015 J Wilson SME / Consultant OK
01 10-08-2015 M Edwards Project Manager OK
1|Page Meridium System Run Book

CFI Donaldsonville
Table of Contents
Customer & Document Overview..........................................................................................4
Implementation Details & History.....................................................................................................4
Document Audience..........................................................................................................................4
System Use & Administration............................................................................................................5
Meridium APM System Architecture.....................................................................................6
APM Foundation Setup & Configuration................................................................................8
Database & Package Solutions.........................................................................................................8
Email & SMTP...................................................................................................................................8
Site References..................................................................................................................................8
Asset Classification Taxonomy..........................................................................................................8
Work History Event Type...................................................................................................................9
Avantis EAM Interface......................................................................................................................9
Enterprise Data Filtering.................................................................................................................11
Data Management Tools (DMT)......................................................................................................12
Recommendation State Management............................................................................................12
Equipment Data Management (Criticality, P&ID, SPC Reg. & Install Date)......................................12
FrontPage Archive & Reference Document Data Loader.................................................................13
Mechanical Integrity Setup & Configuration........................................................................16
Inspection Approval Process............................................................................................................16
Inspection Checklist Reviewer Comments........................................................................................16
Inspection Recommendation Rejection Alerts.................................................................................16
RBI Approval Process......................................................................................................................17
Inspection Leak Tracking.................................................................................................................17
Inspection Fit-for-Service Authorization..........................................................................................17
Inspection Report Updates..............................................................................................................18
TM Executive Summary Report.......................................................................................................18
Inspections on Piping (TML Groups)................................................................................................18
Inspection Work Process Dashboard...............................................................................................18
TM Data Loader..............................................................................................................................19
RBI Data Loader..............................................................................................................................20
CFI Donaldsonville
Inspection Task Data Loader...........................................................................................................20
Inspection Data Loader...................................................................................................................21
Meridium APM Security Configuration & Management.......................................................22
Managing Meridium Security..........................................................................................................22
Functional Roles..............................................................................................................................22
V4 Upgrade – Donaldsonville & Port Neal............................................................................24
Meridium APM Application Support....................................................................................25
User Level Support..........................................................................................................................25
Documentation...............................................................................................................................25
Meridium Global Support Services (GSS).........................................................................................25
Implementation Project Team & Documentation................................................................27
Project Contacts..............................................................................................................................27
Customer System Access.................................................................................................................27
Customer Database.........................................................................................................................27
Project Documentation...................................................................................................................27

CFI Donaldsonville
Customer & Document Overview
CF Industries decided to implement Meridium in order, primarily, to manage and document their
mechanical integrity work processes. They have several sites, but due to IT requirements, have
decided to implement each site as a separate Meridium instance. This run book is thus specific to the
CFI Donaldsonville site. The intent is to utilize the same configuration at all sites to limit
implementation and support costs to the company.
Implementation Details & History

The following sections outline the history of the CFI Donaldsonville Meridium system and the various
implementation projects that have been executed on it.
(2015) Meridium APM Foundation w/ Avantis Interface & Mechanical Integrity

This project is to perform the initial implementation of Meridium APM at CF Industries (CFI). This
included a single site, Donaldsonville. For the initial rollout, CFI implemented the following modules:
 APM Framework V3.6.0.6.0

 Custom CMMS Integration to Avantis via APM Connect
o Equipment Extraction
o Functional Locations Extraction
o Work History Extraction
o Work Request Creation
 Manually from Recommendations
 Manually from Tasks
 Scheduled from Tasks
 Inspection Management (IM)
 Thickness Monitoring (TM)
 Risk Based Inspection (RBI)
All modules will be initially deployed based on the standard Meridium package solutions content
which supports Meridium’s recommended Mechanical Integrity work process. Based on a solution
design and various other discussions between Meridium and CFI, additional configurations were
initially implemented to support CFI’s work process requirements. Configurations that were required
to tailor the standard package content as well as all additional configuration items are outlined in the
this document.
Document Audience
The document is intended for two particular audiences:
 CFI Support Team – for the purposes of easily locating common administrative information as
well as background of what was done in the project and how to get additional, post go-live
support if required

CFI Donaldsonville
 Meridium Global Support Services (GSS) – for the purpose of providing background information
regarding the customer environment and Meridium configuration
System Use & Administration

For easy access, the following linked sections pertain to common administrative tasks:
 Meridium APM Application Support

 Managing Meridium Security
 Avantis Interface Management
 Asset Data Management
o Executing the Equipment Information Loader
o Executing the FrontPage Reference Document Extractor
o Executing the Reference Document Loader
 Mechanical Integrity Data Management
o Executing the Inspection Task Data Loader
o Executing the Inspection Data Loader
o Executing the TM Data Loader
o Executing the RBI Data Loader
 Email & SMTP Setup
 Modifying the Taxonomy Configuration

CFI Donaldsonville
Meridium APM System Architecture
The following diagram represent the Meridium APM system architecture for CFI’s Meridium environment.

CFI Donaldsonville
Additional Meridium APM System Architecture Details
 Meridium Application Servers
o Meridium Application Server V3.6.0.6.0
o Asset Health Manager (AHM) Service
o Meridium Scheduling Service
o Meridium Web (Integration) Services
 Meridium Database & Reporting Servers
o SQL Server 2008 R2
o SQL Server Reporting Service
o Meridium Adapter for SSRS V3.6.0.6.0
 APM Connect Server
o PostgreSQL IR Database
o pgAdmin PostgreSQL Tools
o APM Connect Run-time V1.0.1

CFI Donaldsonville
APM Foundation Setup & Configuration
Database & Package Solutions
The CFI implementation was implemented based on a V3.6.0.4.0 package solutions database that was
upgraded to V3.6.0.6.0 to gain support for APM Connect.
Email & SMTP

CFI has elected to forward emails through their corporate SMTP server,
DVEXCHANGE.CFIDV.CFIORG.NET. This was setup by utilizing the SMPT Preference Manager macro
which may be executed from the MIADMIN homepage.
Reference Documentation
 Integrated Technical Design
o (2) Configure SMTP Preference
Site References
CFI was configured to use a single site reference, Donaldsonville, for all assets. The lookup queries
were modified to always return that one site reference record. The standard practice risk matrix was
linked to this site reference.
o (9) Site Reference Configuration
Asset Classification Taxonomy

CFI has elected to utilize the standard package solution taxonomy configuration. Mapping records
were loaded to the system to map all existing Asset Class values from Avantis to the standard package
solution taxonomy category/class/types.
o (25) Asset Taxonomy Configuration
Modifying the Taxonomy Configuration

The Meridium Taxonomy is configured through several reference table families. Records in these
families may be added to enhance the Meridium taxonomy configuration.
 Taxonomy Category – top level of Meridium taxonomy; new records may be added using the
New button on the toolbar
 Taxonomy Class – second level of Meridium taxonomy; new records may be added by
searching for and opening the parent taxonomy category records and then clicking the add
link on the associated pages menu

CFI Donaldsonville
 Taxonomy Type – third and final level of Meridium taxonomy; new records may be added by
searching for and opening the parent taxonomy class records and then clicking the add link on
the associated pages menu
 Taxonomy Mapping – defines the relationship between SAP classifications and Meridium
taxonomy; mapping values should contain a bar delimited list of SAP Category, Class and Type;
new records may be added by searching for and opening the taxonomy type record and then
clicking the add link on the associated pages menu
Work History Event Type

CFI has elected not to utilize the Event Type field on the Work History family therefore the field was
hidden. The default business logic was left removed so the Event Type field should always remain
blank.
Avantis EAM Interface

A custom, bi-directional, EAM integration interface was developed for CFI to extract Functional
Locations, Equipment and Work History from Avantis and load it into Meridium as well as create Work
Requests in Avantis from Meridium. The APM Connect integration framework was utilized for both
the extraction and Work Request creation configurations. The following outlines functionality of each
interface; refer to the reference documentation for detailed design information.
 Functional Location Extraction – executes a stored procedure within the Avantis database to
extract entity data that was created or updated from the last successful run date of the
interface forward; the data is then loaded into the Meridium system via Web (Integration)
Services; the location hierarchy (Site/Unit/Asset) is determined by the stored procedures and
does not align with the entity hierarchy in Avantis; location records are related to their parent
location by the interface
 Equipment Extraction – executes a stored procedure within the Avantis database to extract
entity data that was created or updated from the last successful run date of the interface
forward; the data is then loaded into the Meridium system via Web (Integration) Services; an
equipment is created for each Asset level location; equipment records are related to their
parent location record by the interface
 Work History Extraction – executes a stored procedure within the Avantis database to extract
work request, work order and task data that was created or updated from the last successful
run date of the interface forward; the data is then loaded into the Meridium system via Web
(Integration) Services; each work history represents a work request and, potentially, an order
and, potentially, a task so multiple work history records are created if an order is assigned
more than one task; work history records are related to the associated equipment and
functional location in Meridium; the stored procedure filters data to only include data that
was created based on a work request that was created from Meridium
 Work History Detail Extraction – executes a stored procedure within the Avantis database to
extract activity data that was created or updated from the last successful run date of the
interface forward; the data is then loaded into the Meridium system via Web (Integration)
Services; only activites related to the two Meridium tasks, Inspection Ready and Inspection,
CFI Donaldsonville
are downloaded; Work History Details are created for each activity and related to their parent
Work History records by the interface
 Work Request Creation – work requests are created in Avantis by a stored procedure in the
Avantis database that is triggered by a web service running on the APM Connect server; the
web service is triggered by Meridium in three ways:
o Manually via Inspection and Meridium General Recommendations
 Triggered by checking the Create Work Request flag
o Manually via Inspection Tasks
 Triggered by checking the Create Work Request flag
o Automatically via Inspection Tasks
 Triggered by the Meridium.Integration.SAP.WorkOrderGeneration scheduled
item based on the results of query Public\Meridium\Modules\SAP Integration
Interfaces\Queries\Get Tasks for Work Order Generation
All stored procedures were designed by CFI resources and they are thus responsible for the
maintenance of them.
 Avantis to APM Integration High Level Design
 Avantis to APM Integration Detail Level Design
o (4) Avantis Extraction Interface – Family Fields
o (5) Avantis Extraction Interface – Family Datasheets
o (6) Avantis Extraction Interface – Field Disable Rules
o (7) Avantis Extraction Interface – Work History Business Logic
o (12) Avantis WMI Interface – Work Request Creation
Avantis Interface Management

The Avantis interface is administered from the Meridium APM Connect Administration Center web
application.
 Logging into the Meridium APM Connect Administration Center

1) Open a compatible web browser; APM Connect is most compatible with Google
Chrome or Mozilla Firefox web browsers
2) Navigate to http://<APM Connect Server>:8080/apmconnect
3) Login with user [email protected] with password admin
 Viewing Execution Logs
1) Log into Meridium APM Connect Administration Center
2) From the Menu pane, in the Conductor section, select Job Conductor
3) In the Job Conductor workspace, select the button next to the Job whose
execution details you want to view; the Task execution details window appears,
displaying the details of the latest execution
10 | P a g e Meridium System Run Book

CFI Donaldsonville
4) If the log is truncated in the window, click the Download entire log button to
download the log and then you may view it in a text editor
 Scheduling Interface Jobs
1) Log into Meridium APM Connect Administration Center
2) From the Menu pane, in the Conductor section, select Job Conductor
3) Select the Job you want to schedule; the master job is generally the only one that
must be scheduled as it will execute all other jobs
4) At the bottom of the Job Conductor workspace, select Triggers
5) In the Triggers section, select Add trigger then Add CRON trigger
6) Enter the trigger details using the following guidelines:
 Label: Enter a name for the trigger
 Description: Enter a description for the trigger
 Time zone strategy: Select JobServer time
 Minutes: Enter the time interval (in minutes) after which the execution needs
to be repeated
 Hours: Enter the time (in hours) when the execution should begin
 Days of month: Enter the days of the month on which the Job should be
executed
 Months: Enter the months during which the Job should be executed
 Days of week: Enter the days of the week on which the Job should be
executed
 Years: Enter the year during which the Job should be executed
7) At the bottom of the Job Conductor workspace, select Triggers Context parameters
8) Find the CONTEXT_FILE parameter are set the value to the path of the context file you
would like to use (after typing the new value press the Enter key to ensure the value is
saved; note that using multiples scheduled jobs with different context files allows the
same interface to be executed for different environments such as test and production
9) Select Save
Enterprise Data Filtering

The original intent was for all CFI sites to utilize the same Meridium instance so the standard data
filtering package was applied. In the end, the decision was made to use separate instances for the
different sites so the Donaldsonville site has standard data filtering enabled but with all users assigned
to the same site.
o (28) Enterprise Data Filtering
** Note – all data filter criteria were removed since this is a single site implementation

CFI Donaldsonville
Data Management Tools (DMT)
The Data Management Tools (DMT) V2.9b package was installed in order to support Mechanical
Integrity module data loading as well as some system configuration tasks.
The following standard DMT interfaces were installed:
 Inspection Management (IM)

 Inspection Tasks
 Thickness Monitoring (TM) V2
 Risk Based Inspection (RBI) V2
 Taxonomy Configuration
o (3) Install Data Management Tools Package & Interfaces
Recommendation State Management

Applied state management configuration such that all recommendations have the same state
management approval process, Proposed  Pending Review  Pending Approval  Approved
except RBI Recommendation which have the state management approval process, Proposed 
Pending Approval  Approved.
o (13) Recommendation State Management Configuration
Equipment Data Management (Criticality, P&ID, SPC Reg. & Install Date)
CFI determined that they would like various equipment properties to be initially loaded from an access
database and then maintained within Meridium in the future. In order to facilitate this, the following
functionality was configured:
 Criticality Indicator field on equipment was changed to CFI Criticality Rating

 Valid values list was added to the CFI Criticality Rating field including all valid values from
Avantis
 ‘SPC Regulated?’ flag field was added to equipment
 CFI Criticality Rating field, ‘SPC Regulated?’ field, P&ID field and Date of Installation field on
equipment were enabled for modification by members of the (new) Asset Data Manager
security group
Data Conversion Template (DCT)

The following DCT must be utilized in order for the interface to execute as expected.

CFI Donaldsonville
o (8) Equipment Criticality Configuration
o (26) Critical equipment Registry Data Load
 Equipment Data Load
Executing the Equipment Information Loader

The following steps are required to load Inspection data from the DCT into Meridium:
1) Log into Meridium APM Framework as a super user

2) Navigate to the Data Management Executer group homepage
3) Click the Equipment Information Data Loader link in the Asset Management section
4) Select the populated DCT file; note that the format must match the EQUIP DCT example file
above
5) Select a location to save the log file when the interface is complete
6) Wait for data load to complete; it is recommended that you do not use Meridium on the same
computer while the interface is running
7) Review the log file for warnings or errors; if needed, resolve the issues in the DCT and re-
execute the interface
FrontPage Archive & Reference Document Data Loader

** Note – this was never run in the production environment; if/when executed, this configuration
should be supported through professional services
CFI is currently using an intranet web site managed with FrontPage to allow users access to Equipment
history including P&IDs, inspection history and other information. Moving forward, they would like to
utilize Meridium Reference Documents, related to Equipment records, instead. To perform the initial
transfer from the FrontPage directory structure and HTML files into Meridium Reference Documents,
a macro and interface were designed.
* Note – this process assumes that the location of files currently referenced by FrontPage will remain
in the same location; if files are moved then the paths of documents in the table MI_REF_DOCUMENTS
will need to be adjusted accordingly (this can be done in the database directly or via another data load

The following DCT is produced by the FrontPage Extraction Macro but may also be populated
manually to load reference documents related to equipment. This DCT format must be utilized in
order for the Reference Document interface to execute as expected.

CFI Donaldsonville
o (27) Load Reference Documents from FrontPage Archive
Executing the FrontPage Reference Document Extractor

The following steps are required to extract the reference documents from the FrontPage directory
structure and HTML files into the EQ REF DOC DCT to be loaded into Meridium. Note that changes
and/or corrections, particularly to equipment IDs, may need to be made in the produced DCT before it
may be loaded into Meridium.
** Note – the following HtmlAgilityPack.dll file must be manually copied to the <SystemRoot>\
Program Files\Meridium\Client\100.0.0.0.0 directory on the machine where the macro is to be
executed **

3) Click the FrontPage Reference Document Extractor link in the Asset Management section
4) Select the root folder of the FrontPage directory structure
5) Wait for processing to complete
6) Select a location to save the produced DCT (xlsx) file when the interface is complete
7) Review the produced EQ REF DOC DCT file; note that a unique reference document will be
created for the combination of the ID and Description fields thus those two fields together
should be unique.
Executing the Reference Document Loader


3) Click the Reference Document Data Loader link in the Asset Management section
4) Select the populated DCT file; note that the format must match the EQ REF DOC DCT example
file above; this is the same format produced by the FrontPage Extractor macro

CFI Donaldsonville


CFI Donaldsonville
Mechanical Integrity Setup & Configuration
Inspection Approval Process
In order to maintain consistency throughout the Meridium system, state management was
implemented for all Inspection Events/Documents and Recommendations to replace the out-of-the-
box status field approval process. The following outlines the changes that were made:
 Status fields were removed from datasheets and associated behaviors disabled on all
Inspection Events and Inspection Recommendations
 Assigned To, Reviewer and Final Approver fields were removed from datasheets and
associated behaviors disabled on Inspection Recommendations
 Since the Inspector resource role is required on Inspection events but all members of the MI
Inspection group should be able to manage these records, business logic was added to
automatically add/remove that resource role to users that are added/removed from the MI
Inspection security group
 Implemented state management for Inspection Events with a Proposed  Pending Review 
Pending Approval  Approved process requiring state role privileges to change out of the
Pending Review and Pending Approval states
 Implemented state management for Inspection Recommendations with a Proposed 
Pending Review  Pending Approval  Approved process requiring state role privileges to
change out of the Pending Review and Pending Approval states
Related Sections
 Recommendation State Management
o (14) Inspection State Management Configuration
Inspection Checklist Reviewer Comments

Because an approval process was added to inspection checklists and they do not contain a Reviewer
Comments field for reviewers to pass information back to inspectors, an associated page link was
added to the Checklist Inspection Events to allow users to open reviewer comments in a text dialog.
o (16) IM Checklist Reviewer Comments
Inspection Recommendation Rejection Alerts

Applied functionality such that the assigned inspector receives and email notification if an inspection
that was submitted for approval is rejected.

CFI Donaldsonville
o (17) Rejected Recommendation Alerts
RBI Approval Process

CFI determined that the same users would be responsible for all operations within the RBI module
except for approving recommendations so all state role requirements were removed except on the
Pending Approval state on RBI Recommendations. Additionally, they did not require an implemented
or Re-Evaluating state on RBI Recommendations so those states were hidden from users.
 RBI Recommendation State Configuration
 RBI Criticality Analysis State Configuration
Inspection Leak Tracking

CFI needed a way to track leaks in Meridium. To support this requirement, the following was
implemented:
 Added ‘Leak’ and ‘Excessive Thinning’ to the Reason for Inspection pick list on Inspection
Events
 Added ‘Temporary Repair’ to the pick list for Action Taken Code on Findings
 (15) Inspection Leak Tracking Configuration
Inspection Fit-for-Service Authorization

CFI has a requirement within their business process that requires a fit-for-service form to be
completed and approved by the inspection approver for some inspections, particularly during
turnarounds where assets may need to be released before the inspection document is
complete/approved. To fulfill this need, a new family was created along with the following
functionality:
 Added family with state management approval process linked to inspection events
 Added associated page links to inspection events to access the fit-for-service datasheet
 Created a report displaying the fit-for-service authorization information as a cover page to the
associated inspection event’s report; setup to “print” the report from the fit-for-service
datasheet via the print button
o (18) IM Fit-for-Service Family

CFI Donaldsonville
o (19) Has Fit-for-Service Authorization Relationship Family
o (20) IM Fit-for-Service Macro & Associated Page Link
o (21) IM Fit-for-Service Report Updates
Inspection Report Updates

All inspection event reports were updated to include the CFI logo image in the header as well as to
display reference documents that are images as images in the report instead of hyperlinks.
o (22) Update Baseline Reports with CFI Logo
o (30) Add Support for Showing Images on Inspection Reports
TM Executive Summary Report

Created a report showing high level Thickness Monitoring data for a unit. Report may be access
through the catalog at Public\Client\Thickness Monitoring\Reports\Thickness Monitoring Executive
Summary.
o (23) TM Executive Summary Report
Inspections on Piping (TML Groups)

CFI needed to way to specify that an inspection is for a specific piping circuit which is a TML Group for
them in Meridium. In order to fulfill this need, configuration was applied to create this connection in a
similar manner to RBI.
 Added Associated TML Group(s) field to inspection tasks and events with valid value lists
based on the TML Groups related to the associated asset
 Implemented business logic to automatically populate the Associated TML Group(s) field
when possible on tasks from RBI Recommendations and on events from tasks
 Added associated page link to checklist inspection events to allow access to the Associated
TML Group(s) field
o (24) Piping Inspection Configuration
Inspection Work Process Dashboard

In order to streamline and simplify the inspection work process for users, the out-of-the-box
dashboard was enhanced to be more effective in driving the workflow.
 Added query results widget, Your Inspection Reports, showing only inspections that are
currently relevant to the current user based on the approval process

CFI Donaldsonville
 Added query results widget, Your Inspection Recommendation, showing only
recommendation that are currently relevant to the current user based on the approval
process
 Added Task Management hyperlink sections including links to:
o Bulk data form to manage task scheduling
o Query results displaying task information and schedules
o Query results displaying tasks that have active work requests
 Added the Associated TML Group(s) field to the existing Inspection Tasks Due by Date and
inspection Tasks Overdue queries
o (29) Inspection Workflow Queries
TM Data Loader
The standard TM DMT V2 Data Loader interface was installed in the system in order to allow for the
initialization of the system.

Executing the TM Data Loader

The following steps are required to load TM data from the DCT into Meridium:

3) Click the Thickness Monitoring Data Loader link in the Mechanical Integrity section
4) Select the populated DCT file; note that the format must match the TM DCT V2 example file
above

CFI Donaldsonville
RBI Data Loader
The standard RBI DMT V2 Data Loader interface was installed in the system in order to allow for the
initialization of the system.

Executing the RBI Data Loader

The following steps are required to load RBI data from the DCT into Meridium:

3) Click the Risk Based Inspection Data Loader link in the Mechanical Integrity section
4) Select the populated DCT file; note that the format must match the RBI DCT V2 example file
above
Inspection Task Data Loader

The standard Inspection Task DMT Data Loader interface was modified slightly for CFI to include extra
fields. The updated DCT was then populated from the provided Critical Equipment Register data.

o (26) Critical Equipment Registry Data Load

CFI Donaldsonville
 Inspection Task Data Load
Executing the Inspection Task Data Loader

The following steps are required to load Inspection Task data from the DCT into Meridium:

3) Click the Inspection Task Data Loader link in the Mechanical Integrity section
4) Select the populated DCT file; note that the format must match the INSP TASK DCT example
file above
Inspection Data Loader

The standard Inspection DMT Data Loader interface was modified slightly for CFI to include extra
fields. The updated DCT was then populated from the provided Critical Equipment Register data.

o (26) Critical Equipment Registry Data Load
 Inspection Data Load
Executing the Inspection Data Loader


10) Click the Inspection Data Loader link in the Mechanical Integrity section
11) Select the populated DCT file; note that the format must match the INSP DCT example file
above

CFI Donaldsonville
Meridium APM Security Configuration & Management

Managing Meridium Security
Meridium security was deployed with a configuration in which users are created and assigned
additional security manually based on the user’s functional role requirements.
 Assigning Security Groups – this is done through the Configuration Manager by using the
Security menu on the toolbar
 Assigning State Management Roles – this is done though the APM Framework application by
navigating to ‘State Role Assignment’ in the Tools menu
 Assigning Resource Roles – not required for CFI (see Inspection Approval Process); this is done
in the APM Framework application navigating to Go To > Mechanical Integrity > Inspection
Administration > Manage Inspection Resources, Roles and Certifications then selecting the All
Human Resources link and clicking Manage Resource Roles for the correct user; roles may
then be assigned in the bottom section of the screen
Functional Roles
In Meridium security configurations such as security group assignments and state roles assignments
must be made in order for users to be able to execute the various functional roles that exist within the
associated work processes. These configurations will be applied manually by CFI.
Inspection Management Functional Roles

 Inspector – Schedules inspections, performs inspections, records results, and initiates
recommendations based on asset condition. The Inspector is responsible for executing and
documenting the inspection activities to maintain both asset integrity and compliance to the
overall inspection program. The Inspector submits the inspection documentation to the
Inspection Supervisor for review and, in some cases, submits a Fit-for-Service form to the
Reliability Supervisor for approval.
o Required Security Groups
 MI Inspection
 Inspection Supervisor – In addition to the capabilities of the Inspector role, reviews the
inspection documents and recommendations prior to requesting approval from a Reliability
Supervisor.
 MI Inspection
o Required State Roles
 Inspection Reviewer

CFI Donaldsonville
 Reliability Supervisor – In addition to the capabilities of the Inspection Supervisor role,
approves the inspection documents and recommendations after they are reviewed. The
Reliability Supervisor also has the ability to approve Fit-for-Service forms as needed. The
Reliability Supervisor is ultimately responsible for the approval of the final inspection
document to maintain asset integrity and program compliance.
 MI Inspection
 Inspection Reviewer
** Optional – required to perform reviews on inspection documents and recommendations **
 Inspection Approver
Thickness Monitoring Functional Roles

 TM Corrosion Analyst – Manages Asset TM tasks, corrosion groups and measurement
locations to ensure that appropriate TM inspection plans are executed in an efficient and
optimum manner. The Corrosion Analyst also evaluates the resultant condition data for any
follow-up action that may be required to ensure asset integrity.
 MI Thickness Monitoring User
 MI Thickness Monitoring Inspector
 TM Technician – Performs TM inspections, records results, and initiates recommendations
based on asset condition. The Technician is responsible for executing and documenting the
TM inspection activities to maintain both asset integrity and compliance to the overall
inspection program. The Technician often uses a data logger device to ensure accurate field
data collection.
 MI Thickness Monitoring User
Risk Based Inspection Functional Roles

 RBI Analyst – Determines the most effective inspection strategy to maintain compliance and
asset integrity for assets that are subject to loss of containment risks. This includes
understanding the asset design and service conditions to determine the potential unmitigated
risk of loss of containment. The analyst will then determine the best approach for inspection
required to properly mitigate risk to an acceptable level. Typically the Analyst works with a
team comprised of a Process Engineer, Inspector, Inspection Engineer, Corrosion Engineer and
Operations Specialist. However the Analyst is ultimately responsible for the RBI analysis and
resulting strategy.
 MI RBI Analyst
 RBI Approver – Typically either the Asset Owner or designated to the Inspection Supervisor by
the Asset Owner. This role is responsible for the operating budget for the asset. It is at their
discretion to ultimately approve the inspection strategy for implementation. Generally this
role trusts the Analyst to determine the best inspection strategy and will approve most all
CFI Donaldsonville
recommendations for inspection. It is only by exception that recommendations will be
considered for revision or cancellation.
 MI RBI Analyst
 RBI Approver
V4 Upgrade – Donaldsonville & Port Neal
GE APM (Meridium) was upgraded to V4.3.0.4. This include deploying the solution at the Port Neal
location.
See the attached technical specification for items that were adjusted during the upgrade

CFI Donaldsonville
Meridium APM Application Support
CFI users utilize a two tier application support structure; first working internally by contacting a CFI
functional expert for help to rule out “lack of system understanding” issues and the CFI Meridium IT
staff to rule out system administration issues (such as security settings) then, if they are still unable to
resolve the issue, the functional expert or IT staff member will open a ticket with Meridium Global
Support Services. In cases of very urgent support needs, Meridium Global Support Services may also
be contacted by phone.
User Level Support

Users of Meridium at CFI are instructed to take the following steps when an issues occurs:
1) Document the work flow leading up to the issue, taking screen shots if possible
2) If an error dialog is displayed and there are a link to copy error information then that link
should be clicked and the additional error information should be pasted into the
documentation of the issue; this information is often critical to being able to quickly resolve
issues
3) Contact the assigned CFI Meridium functional expert with the collected information
Documentation
Meridium provides detailed documentation for all of its delivered product functionality both for end
users and administrative tasks. It is strongly recommended that users and/or CFI support staff
thoroughly review the documentation for the module, tool or work process before contacting
Meridium support.
General documentation including installation, configuration and user instructions as well as general
reference information may be accessed from either the Help menu in any APM application or on the
support web portal. The documentation in both locations is exactly the same.
Meridium Global Support Services (GSS)

If CFI is unable to resolve an issue internally then they will need to contact Meridium GSS. This service
is provided at no additional cost via CFI’s maintenance and support contract. The GSS team is staffed
with experienced personnel to help quickly resolve any issues that are experienced in the Meridium
software. Note that GSS may be unable to support customized components in some cases.
The preferred method of contacting GSS is to open a support case ticket through the support web
portal however GSS may also be contacted by phone if there is an urgent need. The help desk is
staffed from Sunday at 8pm US Eastern Time through Friday at 7pm US Eastern Time.
Meridium GSS Contact Information

 Support Web Portal – https://www.meridium.com/support
o Available 24/7
o Requires one-time registration

CFI Donaldsonville
oCase ticket system prompts users for all required information when the ticket is
created to avoid extra communication cycles
 Email – [email protected]
o Sending emails to this address will simply open a support case ticket exactly like if you
were to utilize the Support Web Portal however management of these tickets often
takes longer so use of the web portal is preferred
 By Phone
o 1-540-344-9205; press 2 for support
Meridium Product Releases

Meridium provides CFI with all Meridium releases, which are issued from time to time, at no
additional cost promptly upon their becoming generally available to other Meridium Licensees. All
releases received by Licensee shall be subject to the terms, conditions, restrictions and covenants of
the License Agreement.
Meridium makes major (V3.x) and service (V3.x.x) releases on a semi-fixed schedule. This means that
it can be expected that a major release can be expected each year and a minor release can be
expected approximately once a quarter. Generally, reported product issues will be addressed within
the next couple releases depending on the point in the cycle when the issues are discovered. In rare
cases Meridium may release smaller releases or patches if critical issues are raised.
Release notes for all releases are accessible through the support web portal in the documentation
section.
Upgrading the Meridium software may be performed by the customer with support from the GSS
team at no additional cost or professional services will provide more in-depth support for a rate
determined based on the size and complexity of the upgrade. In either case, it is recommended that
customers upgrade at least once per year in order to avoid the complexity that is introduced over time
by skipping many releases.

CFI Donaldsonville
Implementation Project Team & Documentation
Project Contacts
The following people were involved in the implementation effort:
Name Role Phone Email

CFI Plant Manager / Meridium Project
Thomas Guillot 225-323-1485 [email protected]
Manager
Jake Daigle CFI Plant Engineer 225-473-5583 [email protected]
CFI Senior Architect of Application
Dave Wiedenfeld 225-473-5546 [email protected]
Development / Meridium Avantis Support
Matthew Sebastian CFI Network Administrator 225-473-0384 [email protected]
Randy Sampson Meridium Project Director 540-344-9205 x2208 [email protected]
Michel Edwards
Meridium Project Manager 540-344-9205 x2243 [email protected]
Pete Ankner
Bryan Maslar Meridium Lead Technical Consultant 540-344-9205 x1109 [email protected]
Franklin Hernandez Meridium Technical Consultant 540-344-9205 x1272 [email protected]
Don Walker Project Manager 1 248 514 2838 [email protected]
Steve Stiles Services Director 540 344 9205 x 1246 [email protected]
Josie Gnanaolivu Technical Consultant 281 638 6633 [email protected]
Biff Collum Technical Consultant [email protected]
Customer System Access

Access to CFI’s system must be granted via WebEx on an as needed basis.
Customer Database
A copy of the production database that was deployed at CFI is located in the following GED box library
folder:
https://ge.ent.box.com/folder/50001153774
Project Documentation
The following supporting project documents were produced as part of the implementation.
Documents are available to Meridium personnel on the CF Industries\CFI Donaldsonville library client
site under Planning & Design and were delivered to Irving Oil during the project.
V3 Documentation - https://ge.ent.box.com/folder/50001153774
 CFI Functional Specification Addendum v1.7

 CFI - APM MI Implementation - Integrated Technical Design V1.5
 CFI Avantis to APM Integration High Level Design Document
 CFI Avantis to APM Integration Detail Level Design Document
V4 Documentation - https://ge.ent.box.com/folder/50001207376

CFI Donaldsonville

CFI - GE APM - Meridium System Run Book

Uploaded by

Copyright:

Available Formats

CFI - GE APM - Meridium System Run Book

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

CFI - GE APM - Meridium System Run Book

Uploaded by

Copyright:

Available Formats

Meridium System Run Book

CF Industries – Donaldsonville and Port Neal

1|Page Meridium System Run Book

3|Page Meridium System Run Book

Implementation Details & History

(2015) Meridium APM Foundation w/ Avantis Interface & Mechanical Integrity

 APM Framework V3.6.0.6.0

4|Page Meridium System Run Book

System Use & Administration

 Meridium APM Application Support

5|Page Meridium System Run Book

6|Page Meridium System Run Book

7|Page Meridium System Run Book

Email & SMTP

Asset Classification Taxonomy

Modifying the Taxonomy Configuration

8|Page Meridium System Run Book

Work History Event Type

Avantis EAM Interface

Avantis Interface Management

 Logging into the Meridium APM Connect Administration Center

10 | P a g e Meridium System Run Book

Enterprise Data Filtering

11 | P a g e Meridium System Run Book

The following standard DMT interfaces were installed:

 Inspection Management (IM)

Recommendation State Management

 Criticality Indicator field on equipment was changed to CFI Criticality Rating

Data Conversion Template (DCT)

12 | P a g e Meridium System Run Book

Executing the Equipment Information Loader

1) Log into Meridium APM Framework as a super user

FrontPage Archive & Reference Document Data Loader

Data Conversion Template (DCT)

13 | P a g e Meridium System Run Book

Executing the FrontPage Reference Document Extractor

1) Log into Meridium APM Framework as a super user

Executing the Reference Document Loader

1) Log into Meridium APM Framework as a super user

14 | P a g e Meridium System Run Book

15 | P a g e Meridium System Run Book

Inspection Checklist Reviewer Comments

Inspection Recommendation Rejection Alerts

16 | P a g e Meridium System Run Book

RBI Approval Process

Inspection Leak Tracking

Inspection Fit-for-Service Authorization

17 | P a g e Meridium System Run Book

Inspection Report Updates

TM Executive Summary Report

Inspections on Piping (TML Groups)

Inspection Work Process Dashboard

18 | P a g e Meridium System Run Book

Data Conversion Template (DCT)

Executing the TM Data Loader

1) Log into Meridium APM Framework as a super user

19 | P a g e Meridium System Run Book

Data Conversion Template (DCT)

Executing the RBI Data Loader