QS Rbi10

Use with: RBI10_QuickStart_Rev1.
rsgz10
Quick Start Guide
Version 10
RBI 10 Quick Start Guide

Part Identification: RPQSRB10
ReliaSoft Corporation
Worldwide Headquarters
1450 South Eastside Loop
Tucson, Arizona 85710-6703, USA
Tel: 1-520-886-0410
Fax: 1-520-886-0399
Sales and Information: 1-888-886-0410 (Toll-free in the U.S. and Canada)
ReliaSoft@ReliaSoft.com
http://www.ReliaSoft.com
1992-2015 ReliaSoft Corporation, ALL RIGHTS RESERVED.
Notice of Rights and Limited Rights to Print this Document
If you are a licensed user of the software you are hereby granted the right to print this
document in whole or in part, as needed for your exclusive use in conjunction with the use of
the software. Except for the limited print rights outlined above, no part of this document may
be reproduced or transmitted, in any form or by any means, for any purpose, without the
express written permission of ReliaSoft Corporation, Tucson, AZ, USA.
Disclaimer
Information in this document is subject to change without notice and does not represent a
commitment on the part of ReliaSoft Corporation.
Companies, names and data used herein are fictitious unless otherwise noted.
Use of the software and this document are subject to the terms and conditions set forth in
the accompanying license agreement.
This software and documentation were developed at private expense; no portion was
developed with government funds.
Trademarks
ReliaSoft, Synthesis Platform, Weibull++, ALTA, DOE++, RGA, BlockSim, RENO, Lambda
Predict, Xfmea, RCM++ and XFRACAS are trademarks of ReliaSoft Corporation.
Other product names and services identified in this document are trademarks of their
respective trademark holders, and are used for illustration purposes. Their use in no way
conveys endorsement or other affiliation with ReliaSoft Corporation.
10
RBI10QuickStartGuide
Thank you for your interest in ReliaSoft's RBI software tool. This quick start guide has been designed to
help you explore many of the software's key features by working through step-by-step instructions for
some practical application examples.
In order to demonstrate a variety of different applications for the tools available in RBI, this guide asks
you to imagine that you are a specialist in Risk Based Inspection (RBI) analysis working for a large
chemical company. Please note that the sample analyses provided are fictional and intended for
demonstration purposes. They are not intended to be realistic. Furthermore, note that although this guide
attempts to introduce you to some of the most frequently used tools, RBI supports many other methods
and applications. Within the software, you can choose File > Help to access a wide array of resources that
will help you explore other capabilities.
In addition to this introduction, the following chapters are presented in this guide.
Chapter 2: Preparing for the Analysis...........................................................................................................3
Chapter 3: Quick Qualitative Assessments ...................................................................................................9
Chapter 4: Simple Analysis for a Non-Pressurized Storage Tank ..............................................................19
Chapter 5: Full Analysis for a Pressurized Tank.........................................................................................29
Chapter 6: Competing Damage Factors in a Hydrogen Reactor.................................................................37
Chapter 7: Hydrogen Reactor with a Crack ................................................................................................45
Chapter 8: HEXTUBES ..............................................................................................................................49
Chapter 9: Pressure Relief Devices (PRDs)................................................................................................53
Chapter 10: Reports ....................................................................................................................................57
1RBI10QuickStartGuide
The quick start repository that is included with the software (called RBI10_QuickStart_Rev1.rsgz10)
contains sample projects that show the examples in this guide at various stages of completion. To access
this file, choose File > Help, click Open Examples Folder, then browse for the file in the RBI sub-folder.
Tip:Topreservetheintegrityoftheshippedexamplefiles,thesoftwarecreatesacopyofthefileeachtimeyou
access arepositoryintheExamplesfolder.Thecopyhasthesamenameastheoriginalfileandissavedinthe
defaultdocumentsfolderforyourcomputer(e.g.,MyDocuments\ReliaSoft\Files).Usethecopytoworkonthe
exampleprojectsandsaveyourchanges.Anychangesyoumakeinthecopywillnotaffecttheoriginalfile.
When applicable, the instructions in this guide will refer to a completed project in the quick start
repository. While reading any example in this guide, you have the choice to:
Examine how it was completed in the sample project.
Copy data from the sample project to help you perform the steps on your own in a different project.
IMPORTANT:Notethatitmaysometimesbenecessarytomodifythedatainthequickstartrepositorytofit
updatedinstructionsornewexamplesinthelatestprintingofthisquickstartguide.Thisprintingoftheguide
wasdesignedforusewithRBI10_QuickStart_Rev1.rsgz10(where_RevXindicatesthedatabaserevision).Ifyou
trytouseadifferentdatabaserevision,thesampleprojectsmaynotexactlymatchtheinstructionsprintedhere.
1) Ifthisguideisolderthanthelatestdatabaserevisioninstalledonyourcomputer,youcanchooseFile>Help>
Quick Start Guide to download the latest printing. 2) If this guide is newer than the latest database revision
installed on your computer, you can choose File > Help > Check for Update to download the latest software
servicerelease.
PreparingfortheAnalysis
Risk Based Inspection (RBI) analysis is a method used to collect data
relating to damage to specific equipment and components, and then forecast
the future physical and economic consequences of failure, as well as the
probabilities of failure for individual components, equipment and entire
plants. This allows you to better plan when to inspect, maintain and replace
weak components before failure occurs.
Displayedmath
precision
Projectcreation
Riskcategory
values
The inspection program is primarily based on two publications provided by

the American Petroleum Institute (API): API RP 580 and API RP 581. Both
publications provide guidance on developing a risk based inspection

program for fixed equipment in refining, petrochemical and chemical
process plants. The documents provide RBI methods for pressurized fixed
equipment, including pressure vessels, piping, tanks, pressure relief devices and
bundles, among others.
Management
score
heat exchanger tube
To begin exploring how the RBI software facilitates risk based inspection analysis, this chapter
demonstrates how to configure the workspace to reflect the risk tolerance for your organization and the
management score for the plant.
2.1PreparingfortheAnalysis
You are an RBI specialist working with a large chemical company and you have been asked to perform an
RBI analysis on their old process plant. Before starting the analysis, you must configure the RBI
application and analysis project to meet your needs.
Objectives
Set the math precision used in the display of calculated results.
Create a new analysis project in a Synthesis database.
2PreparingfortheAnalysis
Establish the risk category values for all RBI analyses in the database.
Set the management score for this particular analysis project.
Solution
To make it easier to use the results that RBI returns, the first step is to set the displayed precision of the
calculated results.
On the Settings page of the Application Setup window (File > Application Setup), you set the displayed
math precision to 2 digits and you set the point at which the software will switch to scientific notation for
the calculated results at 3 digits.
With these settings, a financial cost of $112650.25, for example, will be displayed as 1.13E+05.
Your next step is to create a new analysis project that uses the configurable settings the company has
standardized upon for risk based inspections. With a Synthesis database open, you choose Project >
Management > Create Project and set the project properties as shown in the following picture.
When you choose Standard RBI from the Select Profile from Library drop-down list, this copies the
predefined settings from the active library so they can be used in the current project.
Tip: ThisexampleshowsthedefaultoptionsthatareshippedwiththesoftwarefortheSelectProfilefromLibrary
dropdown list. For your own implementation, it is likely that you (or someone else in your organization) will
configurethislisttomeetthespecificneedsofyourorganization.
You click OK to create the new project.
RiskCategories
You start by reviewing the scoring systems that will be used to assign risk priority levels in the
quantitative RBI analysis results (i.e., Low, Medium, Medium High and High). These are determined
based on two matrices that can be customized to reflect the specific risk tolerance of your organization.
Both scoring systems use the same 5-point scale to assign a rating based on the failure probability. In one,
this is combined with a second 5-point scale that focuses on the financial consequences of failure (in terms
of US$). In the other, the second 5-point scale focuses on the size of the surrounding area that might be
affected if a containment failure occurs (in terms of square meters).
The scoring matrix that will be used later to assign risk priorities in the analysis results is shown next.
To view the risk category rating scales that will be used for all RBI analysis projects in the current
database, you choose System Hierarchy > Risk Based Inspection > Risk Categories.
For each 5-point rating scale, you can set the range of values that determine which rating will be applied in
the RBI analysis results. For example, with the default settings shown in the following picture, the
application assigns the lowest (best case) rating of 1 if the calculated failure probability is between 0 and
0.1; whereas, the application assigns the highest (worst case) rating of 5 if the probability is between 0.5
and 1. For a consequence scale, the best case is labeled A and the worst case is labeled E.
ManagementScore
The next step is to set the management score for the plant, which reflects the knowledge and expertise of
the employees that oversee and perform the day-to-day operations. A poor score indicates that the
employees are not familiar with the operations of the plant, which is reflected in an increase in the
probability of failure for the assets. The management score is project-specific, which means that each
project in a database can have a different score.
To view the management score, you choose System Hierarchy > Risk Based Inspection > Management
Score.
Because you do not yet have any information about the current management style at this plant, you decide
to accept the default average score of 500 for the initial analysis. You can change the score at any time as
you get more information about the plant.
You then click OK to close the window.

You are now ready to perform the first analysis, as described in the next chapter.
QuickQualitative
Assessments
A qualitative RBI analysis is a quick assessment of an asset to gain a rough
estimate of its importance in terms of risk. If the asset is found to be of low
risk, then less time (possibly none) should be spent on it in the future as
compared to an asset that is found to be of high risk. By doing this quick
assessment, an organization can focus its limited resources (both time and
money) on those assets that pose the greatest risk, both physically and
financially.
Systemhierarchy
Riskdiscovery
This chapter demonstrates how to build a system configuration that contains equipment and components
that you may wish to analyze with RBI analysis techniques. It also shows how to perform quick
qualitative assessments for the assets.
3.1PerformingaQualitativeAssessment
Your supervisor knows that management expects to have the entire assessment done within two months.
You know that the only way to accomplish this is to pre-screen the assets using a quick qualitative
approach to determine which components will be further analyzed using risk based inspection techniques.
Objectives
Build a system hierarchy that includes the equipment and components you wish to evaluate with an
RBI analysis.
Review the qualitative ratings that have been defined in the current project.
Perform qualitative RBI assessments to determine which components warrant more in-depth
quantitative RBI analysis.
Note: Insteadofcreatingyourownproject,youcanopenthe1QualitativeAssessmentprojectinthequick
startrepositorytoseetheanalysisthathasalreadybeencreated.
3QuickQualitativeAssessments
Solution
The first step is to configure the RBI workspace to fit your needs for the current analysis. With the
analysis project open, you right-click one of the system hierarchy column headers and choose Customize
Columns. For this analysis, you choose to enable only the columns shown next.
Next, to see the qualitative assessment rating system that has been defined for this project, you choose
Project > Management > Configurable Settings > RD Ratings.
10
The following picture shows the first few categories and the possible ratings that will be available for any
qualitative RBI risk assessment performed in this project.
You click OK to close the window.

The next step is to build a system hierarchy that includes the equipment and components you wish to
evaluate with RBI analysis. When you are finished adding and renaming the items, the full hierarchy will
look like this:
11
You start by renaming the System 1 item that was added automatically when you created the project.
You select the item and type Hydrogen Generation Unit inside the Name field of the Properties tab.
Next, to add the first component that will be analyzed, you choose System Hierarchy > Risk Based
Inspection > Add RBI Equipment.
In the Add RBI Equipment window, you select Pipe.
When the item has been added, you click inside the Name field in the Properties tab and rename it to
Water Transport Pipe.
Then, you choose System Hierarchy > Risk Based Inspection > Add Component.
12
In the Add RBI Component window, you select PIPE-8 and click OK.
Tip: NotethattheAddRBIComponentwindowisconfiguredasawizardthatallowsyoutobegindefiningsome
ofthecomponentproperties,ifdesired,whileyouarecreatingtheitem.Youwillthenhavetheopportunityto
view/edit these properties in the Analysis panel after the item has been added to the system hierarchy. The
wizardisnotapplicableforthisexamplebecauseyouarenotyetreadytoperformthefullRBIanalysis.Forother
situationsinwhichyoudowanttobeginperformingtheRBIanalysisimmediately,youcanusetheNextbuttonto
proceedthroughthewizardbeforeclickingOKtocreatetheitem.
On the Properties tab, you change the items name to Main Water Tube and then choose Analyses >
Planning > Add Risk Discovery.
The software adds a new Risk Discovery tab to the Analysis panel and puts the
Discovery column of the system hierarchy.
icon into the Risk
You assign ratings to all 12 factors, as shown next. The overall rating (bottom right) is only 13.6 so you do
not mark the water tube for more detailed analysis. (Note that some of the items in the quick start project
also include comments to indicate why the analyst selected each rating. It is not necessary to type these
13
comments if you are performing the analysis from scratch, and the comments are not shown in the
following pictures.)
Next, you use the same process to add the rest of the components shown on page 11 and then perform the
qualitative assessments.
For the Reactor Casing component of the Hydrogen Generation Reactor, the equipment type is VesselFinFan and the component type is REACTOR. You assign the factor ratings shown next. Then, because
the overall rating is much higher (58.1), you mark the item for more detailed analysis by selecting the
checkbox at the bottom of the tab.
14
For the Fuel Tank Bottom component of the Boiler Fuel Tank, the equipment type is Tank650 and the
component type is TANKBOTTOM. You perform the qualitative assessment as shown next.
For the High Pressure Tank Bottom component of the Hydrogen Storage Tank, the equipment type is
Tank650 and the component type is TANKBOTTOM. You perform the qualitative assessment as shown
next.
15
For the Tube Bundle component of the Heat Exchanger for Primary Cooling, the equipment type is Heat
Exchanger and the component type is HEXTUBE. You perform the qualitative assessment as shown
next.
For the Pressure Relief Device Protecting Reactor, the equipment type is Pressure Relief Device. (Note
that this type of device is always analyzed at the equipment level, rather than the component level. This
will be discussed in more detail in Chapter 9.) You perform the qualitative assessment as shown next.
16
After you have completed the qualitative assessments for all six items, the system hierarchy looks like the
figure shown next. In the Risk Discovery column, the green icon for the main water tube indicates that
this item has not been flagged for more detailed analysis. A red icon is displayed for the other five items
that do require full RBI analysis. The Risk Discovery Details column also displays the overall rating
assigned to each item.
Conclusion
The quick qualitative assessments indicate that five items should be analyzed with the full quantitative
RBI analysis approach. Chapters 4 and 5 will discuss the analysis for the non-pressurized fuel tank bottom
and the high pressure tank bottom. Chapters 6 and 7 will discuss two analyses performed for the reactor
casing. Chapter 8 will discuss the analysis for the tube bundle, and Chapter 9 will discuss the pressure
relief device.
17
SimpleAnalysisfora
NonPressurizedStorage
Tank
In the RBI software, storage tanks are handled somewhat differently
depending on whether or not they are pressurized. For non-pressurized tanks
(i.e., tanks that only use atmospheric pressure), the analysis is simplified
because it is not necessary to consider the consequences of containment
failure on the surrounding area. Certain inputs for the financial
consequences are also not required.
4
Nonpressurized
tankanalysis
This chapter demonstrates the simplified analysis for a non-pressurized tank, while the next chapter will
focus on the more detailed analysis for pressurized tanks.
4.1NonPressurizedStorageTanks
After the qualitative analysis of the plant (see Chapter 3), you found that several assets warrant further
quantitative analysis. One of these assets is the storage tank that holds the fuel oil. This oil is used by the
boilers to turn the water into steam before being pumped into the reactor.
The storage tank is made of welded carbon steel and is situated in concrete. It is 35 meters in diameter
with a total height of 28 meters and a maximum fluid height of 25 meters. It was installed on November
24, 1965 and is scheduled for replacement on November 24, 2025 (i.e., 60 years after it was installed).
For this tank, the company considers any risk greater than $100,000 to be excessive. You must determine
if it is possible to wait until the decommissioning of the tank without further inspection, or if the tank
needs to be inspected at an earlier date to ensure that the financial risk never exceeds the $100,000 limit.
19
4SimpleAnalysisforaNonPressurizedStorageTank
Objective
Use the RBI analysis method for non-pressurized storage tanks to determine if inspection is needed
before the planned replacement date in 2025.
Note: Instead of creating your own project, you can open the 2 Boiler Fuel Tank project in the quick start
repositorytoseetheanalysisthathasalreadybeenperformed.
Solution
Starting with the system hierarchy that you created in Chapter 3, you select the Fuel Tank Bottom
component and use the Properties tab to rename it to Fuel Tank Bottom with $100K Max Risk. You then
click the RBI Properties tab in the Analysis panel.
On the General Properties tab, you enter the properties shown next. Note that the Date of Component
Installation and Plan Date fields define the planned 60 year life span for this tank.
20
You then click the Damage Factors Selection tab and consider the possible damage factors. In this case,
you confirm that, aside from the mandatory Thinning Damage Factor, no other damage factors need to be
considered for this tank.
On the Damage Factors Properties tab you set the properties for the thinning damage factor.
21
On the Consequence Properties tab, you enter the properties shown next. Note that it is important to make
sure that the Representative Process Fluid adequately represents the process fluid used within the
component. If you cannot find the correct process fluid within the possible choices, you should choose a
representative fluid chosen based on the likeness of several properties, such as normal boiling point,
molecular weight and density. For this analysis, you choose Fuel Oil - C17-25, which is applicable for any
type of gas oil or typical crude oil.
Tip: Formoreinformationabouttheoptionsinthisdropdownlist,searchforFluidListintheRBIhelpfile.
The Risk Target for Financial Consequences ($) field reflects the maximum financial risk ($100,000)
that management specified for this analysis.
After all of the properties have been defined, you choose System Hierarchy > Risk Based Inspection >
Calculate Risk to calculate the results.
22
In the Calculation Options window, you choose to calculate only the component that is currently selected.
Note: AlthoughtheSetReliabilityPolicytoBasedonRBIAnalysischeckboxisnotapplicablefortheexamplesin
thisguide,itwillbeselectedbydefault.Whenthischeckboxisselected,theapplicationwillautomaticallycreate
areliabilitymodelbasedontheRBIresults(usingfourreliabilityvaluesthatarecalculatedforthecomponentat
differentagestofita2parameterWeibulldistribution).ThismodelwillbeusedtosettheReliabilityPolicyonthe
Propertiestabfortheitem,whichcanthenbeusedinotheranalyses(suchascalculationsintheFMRAinterface,
RCMcost/availabilitysimulations,integrationwithBlockSim,etc.).
You click OK to perform the RBI calculations based on the inputs provided. When the process completes,
you review the full report on the Results tab.
You examine all of the results and pay particular attention to the following nodes. (Note that most of the
dates in the following pictures are based on the date when the analysis was performed in the sample
project. If you repeat the analysis from scratch or if you recalculate, the specific dates in your results will
be different.)
The Plan Date Results node shows the expected probability of failure and risk if nothing is done
until the planned replacement date in November, 2025. For this analysis, you see that the
probability of failure (0.02) falls into the lowest risk category (1), but the financial risk (~$6.4 M)
23
falls into the second highest risk category (D). Therefore, the scoring matrix (which was shown on
page 6) assigns an overall Risk Priority label of Medium.
As indicated in the heading of the Target Date Results node, an inspection is recommended to be
performed several months before the planned replacement in order to keep the financial risk from
exceeding $100,000.
The Recommended Inspection(s) node shows the number of inspections needed and how
effective the inspection(s) must be.
While the exact meaning of effectiveness varies depending on the component and what its
properties are, the following table shows a generic version of the inspection levels.
24
Level
GeneralMeaning
A
B
C
D
E
HighlyEffective
UsuallyEffective
FairlyEffective
PoorlyEffective
Ineffective
For this tank bottom, the results indicate that the inspection needs to be usually effective
(class B) if it is to meet the planned goal.
Finally, the Plan Date with Inspection Results node shows the probability of failure and risk at
the planned replacement date if an inspection is performed on the target date and nothing out of the
ordinary is found. (If the inspection revealed something out of the ordinary, you should reanalyze
the component.).
Overall, the analysis results indicate that the tank bottom exceeds the maximum allowable risk of
$100,000 by ~$4,500 and therefore requires an inspection several months before the scheduled
replacement.
25
On the RBI Plot tab you choose Financial Risk in the Plot Type field. When you point to an arrowhead in
the chart, the software displays information about the year and risk at the specific date. (Plot settings have
been adjusted for optimum printing, but content remains unchanged.)
Since the inspection of the tank bottom costs more than the $4,500 excess risk, management asks you to
redo the calculations with a maximum risk allowance of $105,000 (i.e., the sum of the allowed risk and the
cost of the inspection). In other words, they decide that the gain in inspecting the tank earlier is not
justified by the cost of the inspection.
You copy the component (Home > Clipboard > Copy) and paste another instance right below the
original analysis (Home > Clipboard > Paste). You then rename the component to Fuel Tank Bottom
with $105K Max Risk.
26
On the Consequence Properties tab for the new item, you change the Risk Target for Financial
Consequences ($) value to $105,000, and leave all other properties unchanged.
You then choose System Hierarchy > Risk Based Inspection > Calculate Risk to recalculate the results
to reflect this change in the inputs.
In the Results tab, the Probability Of Failure and Risk Analysis (Financial) values remain the same, but
the report now indicates that no inspections are needed until the planned replacement date in November,
2025.
27
FullAnalysisfora
PressurizedTank
The full RBI analysis for pressurized storage tanks and other regular types
of equipment consider some additional factors that are not applicable for the
non-pressurized storage tank analysis discussed in Chapter 4. Specifically,
these components must take into consideration the area consequences,
which include the damage to the surrounding locations and personnel
caused by fire, toxicity and miscellaneous causes, such as acid burns.
FullRBIanalysis
This chapter demonstrates the full analysis for a pressurized storage tank.
5.1PressurizedStorageTanks
The next asset to be analyzed is the cryogenic pressurized tank that holds the hydrogen gas (as a liquid)
that is produced in the reactor. The first component of the tank to be analyzed will be the tank bottom,
because it is not inspected as often as the other parts of the tank. The importance of this task is vital,
because a loss of containment not only shuts down the plant, but it also causes the loss of all stored gas.
The tank was installed on July 19, 1985 and is planned to be replaced 40 years later on July 19, 2025.
Objectives
Use the RBI analysis method for pressurized storage tanks to determine if inspection is needed
before the planned replacement date in 2025.
If an inspection is needed, determine when it must take place and how thorough it must be so that
the financial risk does not exceed the $100,000 maximum.
Note: Insteadofcreatingyourownproject,youcanopenthe3HydrogenStorageTankprojectinthequick
29
5FullAnalysisforaPressurizedTank
Solution
Continuing with the same system hierarchy that you worked on in the previous chapters, you select the
High Pressure Tank Bottom component and then click the RBI Properties tab in the Analysis panel.
On the General Properties tab, you enter the properties shown next. Note that the Date of Component
Installation and Plan Date fields define the planned 40 year life span for this tank.
You then click the Damage Factors Selection tab and consider the possible damage factors. Due to the
extreme low temperatures that the tank operates under (-250C), brittleness must be taken into
30
consideration along with thinning. To select the Brittle Fracture Damage Factor, you click inside the
Applies? column to change the answer to Yes.
You then click the Damage Factors Properties tab, which displays the inputs required for the two damage
factors that are applicable for this analysis: Thinning and Brittle Fracture. The tab includes three nodes,
31
one for each damage factor and one node called Apply to Multiple Damage Factors that contains the
property that applies to both nodes. You set the properties as shown next.
On the Consequence Properties tab, you start by making the inputs related to Flow Rates/Flammability.
32
Since the hydrogen is purified before it is stored, there is no reason to consider toxicity effects. You set all
inputs to 0.
Finally, you make the inputs shown next for the financial consequences. Note that since low nickel alloy
steel is not an option in the Component Material field, you choose Carbon Steel, which is a close
representative in terms of cost. Also note that you use the Risk Target for Consequence Areas field to
record the maximum area risk of 100 m2 and use the Risk Target for Financial Consequences field to
record the maximum financial risk of $100,000.
Calculate Risk to calculate the results. In the Calculation Options window you again choose to calculate
only the component that is currently selected and click OK.
When the process completes, you review the full report on the Results tab.
33
be different.)
34
Because the tank is pressurized, the analysis results have to account for the pressure-driven
spraying of the process fluid during loss of containment. In this case, the Area Consequence
Results node shows that the possible damage to the surrounding area is found to be very low. This
is due to the extremely low temperatures, with a corresponding low probability of a fire, as well as
the lack of any toxic components within the process fluid.
The financial consequences are also adjusted to account for the damage that can occur on other
equipment surrounding the component being analyzed, as shown in the Financial Consequence
Results node. They also consider the financial cost of injuries to personnel, including hospital
bills, pain and suffering payments or even possible loss of life that could occur.
The Plan Date Results node shows that while the area risk of 0.84 m2 is well under the allowable
area risk, the estimate of financial risk is approximately $232,000, which is more than twice the
allowed risk.
As indicated in the heading of the Target Date Results node, the calculated target date to perform
an inspection is the same as the date when the RBI calculation was performed. This means that the
maximum risk has already been exceeded and an immediate inspection is required to reduce the
risk.
35
The Recommended Inspection(s) node shows the number of inspections needed and how
effective the inspection(s) must be.
The Plan Date with Inspection Results node shows the probability of failure and risk at the
planned replacement date if you perform the inspection(s) starting from the target date until the
plan date. (In other words, these results indicate what the risk is expected to be assuming that
everything is going according to plan and that no new issues are found.1)
These two nodes show that if an inspection is performed immediately, even if it is just a poorly
effective D class one, then the risk by the planned replacement date is significantly reduced to
around $82,000, which is well below the maximum financial risk of $100,000.
Conclusions
This analysis indicates that the cryogenic storage tank must be immediately inspected because the current
risk already exceeds the maximum financial risk allowed. Assuming that no new problems are found
during the inspection, then no further inspections will need to be performed until the planned replacement
date in 2025. Of course, more can always be done.
1. If a new problem is found during an inspection, then a service for fit test needs to be performed on the item and the
analysis redone with the new issues entered into the RBI software (assuming that the item passes the service for fit
test).
36
CompetingDamage
FactorsinaHydrogen
Reactor
In many cases, it is necessary to consider several competing damage factors
that contribute to the deterioration of the equipment (e.g., there may be
several sulfide stress corrosion damage factors present). In such cases, the
factor that causes the most damage is considered to be the dominant factor
for damage calculation purposes and thus, the calculated total damage factor
is less than the sum of the individual damage factors.
Competing
damagefactors
This chapter demonstrates how to analyze a component where several competing damage factors are
present.
6.1ReactorCasings
The next asset to analyze is one of the most crucial pieces of equipment within the plant, the hydrogen
generation reactor. Not only is it the equipment where the final product is generated, it is also very
complex because there are multiple gases within the process stream. Both the operating temperature
(850C) and pressure (800,000 Pa) are very high, and the final product is extremely dangerous
(i.e., flammable). In particular, the casing of the reactor must be well maintained because a loss of
containment can be potentially catastrophic.
The tank was installed on February 1, 2001 and is planned to be replaced 20 years later on February 1,
2021.
37
6CompetingDamageFactorsinaHydrogenReactor
Objectives
Use the RBI analysis method for reactor casings to determine if inspection is needed before the
planned replacement date in 2021.
If an inspection is needed, determine when it must take place and how thorough it must be so that
the financial risk does not exceed the $100,000 maximum.
Note: Insteadofcreatingyourownproject,youcanopenthe4HydrogenReactorprojectinthequickstart
repositorytoseetheanalysisthathasalreadybeencreated.
Solution
Continuing with the same system hierarchy that you worked with in the previous chapters, you select the
Reactor Casing component and then click the RBI Properties tab in the Analysis panel.
On the General Properties tab, you enter the following properties.
Next, you click the Damage Factor Selection tab. The selection of the damage factors is the most
important step for this component. Due to sulfur-based impurities within the natural gas, along with the
high temperatures and pressures within the reactor, several damage factors are applicable to the reactor
casing in addition to the required thinning factor. With both sulfide and water being present, sulfide stress
cracking (SCC) and cracking induced by hydrogen sulfide (HIC/SOHIC-H2S) are both possible. In
38
6.1ReactorCasings
addition, the high operating temperature and high operating pressure of the gas being formed with the
reactor means that the HTHA (High Temperature Hydrogen Attack) damage factor is also applicable.
Therefore, you click inside the Applies? column to change the answers to Yes for the factors shown
next.
Next, you click the Damage Factors Properties tab to make the inputs required for the four damage factors
that you specified are applicable for this analysis. The tab includes five nodes, four for the properties that
are unique to each damage factor and one node that contains the properties that apply to multiple factors.
In the Apply to Multiple Damage Factors node, you enter the following properties.
39
Then you enter the properties that apply specifically to the thinning damage factor. There have already
been two prior inspections of the reactor casing for wall thickness. You use the average value of the
performed inspections as the inspection effectiveness.
Note: Incaseswhereadamagefactorhasbeeninspectedformultipletimes,youmustuseyourjudgementto
determinehoweffectiveoveralltheinspectionshavebeen.Forexample,youcouldhaveanineffective(ClassE)
inspectionperformedbeforeausuallyeffective(ClassB)inspection.Basedonthoseresults,youmaydecidethat
theoverallvalueofthetwoinspectionsisonlyfairlyeffective(ClassC).
During the last inspection in 2011, the casing was also inspected for SCC, HIC/SOHIC-H2S and HTHA
damage. You make the required inputs for those damage factors.
40
6.1ReactorCasings
Next, you click the Consequence Properties tab and enter the properties shown next. For this portion of the
analysis, it is vital that you not only consider the output from the component, but also the inputs and
possibly the intermediaries. In this case, since the natural gas has some sulfides in the form of hydrogen
sulfide, while a by-product is carbon monoxide, you enter the specific mass fractions of those
components.
41
Calculate Risk to calculate the results. In the Calculation Options window, you choose to calculate only
the component that is currently selected, then click OK.
be different.)
In the Plan Date Results node, which estimates the probability of failure and risk if no inspections
are performed before the planned replacement date:
The Individual Damage Factor Results sub-node shows the values calculated independently
for each of the four damage factors, while the Overall Damage Factor and Probability of
Failure sub-node shows the total calculated damage factor.
Because different damage factors can affect the same parts of the reactor, the value is less than
the sum of the individual factors. Specifically, the total damage factor considers only the higher
of the two stress corrosion cracking factors and the calculated value for Thinning is so low as to
be considered negligible. So instead of 1 + 12.59 + 100.73 + 800 = 914.32, the total value is
calculated as 100.73 + 800 = 900.73.
42
The Risk Analysis (Financial) sub-node shows that the estimate of financial risk is
approximately $1,390,000 if no inspections are performed before 2021. This well exceeds the
allowed risk.
6.1ReactorCasings
maximum risk has already been exceeded and an immediate inspection is required to reduce the
risk.
The Recommended Inspection(s) node shows which damage factors require inspection and how
effective the inspections must be. For this analysis, while no inspections are needed for Thinning,
the inspection for the Sulfide Stress Cracking factor needs an inspection that is at least poorly
effective (class D), while the inspections for the SOHIC-H2S and HTHA factors must be at least
usually effective (class B).
Based on these values, the Plan Date with Inspection Results node shows that the lowest
financial risk that can be had for the reactor casing even after having performed the recommended
inspections is ~$630,000, which is still six times greater than the maximum allowed financial risk
of $100,000.
43
Conclusions
You report to management that the reactor is indeed a very high risk item within the plant, and that an
immediate inspection is recommended for several damage factors to try to minimize the risk. With the
current recommended inspections and the current recommended date, the risk will still exceed the
maximum allowed financial risk by the planned replacement date, which means that further analysis and
possibly further inspections will be needed once the current ones are completed and the RBI analysis
properties are adjusted accordingly.
44
HydrogenReactorwitha
Crack
As discussed in Chapter 6, a hydrogen generation reactor is one of the most
crucial pieces of equipment within the plant. In this chapter, you will see
how the information provided to you from prior inspections can have a big
impact on the risk estimate in a case where the most recent inspection
reveals evidence of internal cracking in the reactor.
7
Changingacritical
factor
7.1HydrogenReactorwithaCrack
To explore the impact of different factors in the analysis of the hydrogen generation reactor, you decide to
see what the analysis results would be if signs of internal cracking had been found during the most recent
inspection.
Objectives
Alter the Internal Cracking Present input in the hydrogen reactor casing analysis to see how this
change in the damage factor properties would affect the RBI results.
Note: Insteadofcreatingyourownproject,youcanopenthe5CrackedHydrogenReactorprojectinthequick
Solution
To perform the what if analysis, you first copy the Reactor Casing component (Home > Clipboard >
Copy) and paste another instance right below the original (Home > Clipboard > Paste). You then rename
the component to Reactor Casing IF Internal Cracks Present.
45
7HydrogenReactorwithaCrack
On the Damage Factors Properties tab you change the Internal Cracking Present value to Yes and
leave all other inputs unchanged.
You choose System Hierarchy > Risk Based Inspection > Calculate Risk to calculate the results. In the
Calculation Options window, you choose to calculate only the component that is currently selected, then
click OK.
As expected, the results of the reactor casing in the presence of internal cracks are much worse in terms of
risk. On the Results tab, you pay particular attention to the following nodes. (Note that most of the dates in
the following pictures are based on the date when the analysis was performed in the sample project. If you
repeat the analysis from scratch or if you recalculate, the specific dates in your results will be different.)
46
7.1HydrogenReactorwithaCrack
In the Plan Date Results node:
In the Individual Damage Factor Results sub-node, when you compare the new results to the
ones from the original analysis (see page 42), you see that the calculated values for the two
stress corrosion cracking damage factors (SCC-SSC and SCC-HIC/SOHIC-H2S) both
substantially increased. Thus, the total damage factor doubled (from approximately 900 to
1810) while the probability of failure nearly doubled (from 0.03 to 0.05).
The Risk Analysis (Financial) sub-node shows that the financial based risk almost doubled
(from approximately $1,390K to $2,741K).
The Target Date Results node continues to show that the maximum risk has already been
exceeded and that an inspection should be performed immediately.
47
7HydrogenReactorwithaCrack
The Recommended Inspection(s) node shows that the recommended inspections have increased
in both number and effectiveness for two of the damage factors. The Sulfide Stress Cracking and
SOHIC-H2S damage factors now both require two highly effective inspections (class A),. You
should immediately perform the first inspection and reanalyze the results. You would then perform
a second inspection at some future point before the plan date (e.g., after performing the first
recommended inspection, you would re-analyze the data and the RBI software may recommend
the date for a future inspection).
The following table shows the change in the number and types of inspections recommended:
Factor
WithoutCracking
WithCracking
SCCSSC
HIC/SOHIC
HTHA
Thinning
1D(PoorlyEffective)
1B(UsuallyEffective)
NoneNeeded
2A(HighlyEffective)
2A(HighlyEffective)
NoneNeeded
Conclusions
The change of just one property, if it is a crucial one, can lead to drastically different results for the
analyzed component. By changing the internal cracking property from No to Yes, the expected risk
roughly doubled and the analysis indicates that more inspections with higher effectiveness levels will be
needed.
48
HEXTUBES
In an RBI analysis, not all components can be analyzed using damage
factors. In the case of heat exchangers, while the shell inside and the tube
side of the heat exchanger can be analyzed using damage factors, the tube
bundle is analyzed differently. Heat exchanger tube bundles, or HEXTUBEs
for short, are analyzed with a user-defined failure model and a unique set of
properties.
HEXTUBEanalysis
Userdefined
failuremodels
This chapter demonstrates the analysis for a HEXTUBE.
8.1HEXTUBES
The next step is to analyze the heat exchanger tube bundle for the primary cooling system.
The HEXTUBE was installed on March 18, 2006 with scheduled maintenance 15 years later on March 18,
2021. After that, the next scheduled maintenance is on March 20, 2026. Based on your research, you have
determined that the probability of failure for the HEXTUBE can be described with a Weibull distribution
where beta = 1.5 and eta = 20 years.
Objectives
Determine the expected risk, risk priority and the next inspection/refurbish date (target date) for the
HEXTUBE in the cooling system.
Note: Insteadofcreatingyourownproject,youcanopenthe6HeatExchangerTubeBundleprojectinthe
quickstartrepositorytoseetheanalysisthathasalreadybeencreated.
49
8HEXTUBES
Solution
Tube Bundle component and then click the RBI Properties tab in the Analysis panel.
You begin by specifying the failure model on the General Properties tab. You double-click inside the
Initial HexTube Model field shown next.
In the Model Wizard, you click the New Distribution option and enter the following model parameters.
You accept the default name that will be assigned automatically and click OK to define a new model
resource and use it in the current analysis.
Tip: Inthiscase,youcreatedafailuremodelwithoutlinkingtoananalyzeddataset.However,ifyouhadaccess
to the data for the HEXTUBE, you could have used Weibull++ to analyze the data and publish the results as a
model. With this approach, if the underlying data analysis ever changes, you have the option to republish the
modelwithupdatedinformationandanySynthesisanalysisthatusesthismodelwouldbeupdatedautomatically
aswell.
50
8.1HEXTUBES
You then enter the remaining properties shown next.
Finally, you make the inputs shown next for the financial consequences.
Since these are the only inputs required for a HEXTUBE analysis, you choose System Hierarchy > Risk
Based Inspection > Calculate Risk to calculate the results. In the Calculation Options window, you
choose to calculate only the component that is currently selected and click OK.
be different.)
maximum risk has already been exceeded and an immediate highly effective (class A) inspection
is needed to reduce the risk to an acceptable level.
51
8HEXTUBES
The Plan Date with Inspection Results node shows the expected probability of failure and risk at
the planned replacement date if an inspection is performed on the target date.
A major difference between regular components and HEXTUBEs is that the later contain an
additional analysis in the Inspection Planning without Repair node that displays the
recommended actions if you do not repair the HEXTUBE, but only inspect and replace it. For this
component, the analysis indicates that if you do not repair the HEXTUBE as part of the inspection,
then you should replace it at the planned replacement date in 2021 and not wait to replace it in
2026. In addition, the optimal replacement frequency field shows that, if you want to minimize the
total expected cost of loss due to early replacement and potential risk, you should replace the
HEXTUBE every 22.47 years.
Conclusion
The analysis indicates that the HEXTUBE should be inspected/refurbished immediately because the
current potential risk is already higher than the allowed maximum.
52
PressureReliefDevices
(PRDs)
Like the HEXTUBEs discussed in Chapter 8, a pressure relief device (PRD)
is also a special case for RBI analysis. It is used to protect components from
sudden pressure buildups by venting process fluid to decrease the pressure,
and therefore preventing loss of containment due to rupture. Because they
are used to protect components from over pressurization, PRDs have to be
assigned at least one existing component that they are already protecting.
Pressurerelief
deviceanalysis
This chapter demonstrates the analysis for a pressure relief device.
9.1PressureReliefDevices
The last item to analyze in the plant is the pressure relief device protecting the main hydrogen generation
reactor/casing. The PRD is a vital piece of safety equipment for the reactor casing, preventing the
possibility of over pressurization and therefore loss of containment (rupture).
The PRD was installed on April 12, 2014 and is planned to be replaced nearly 5 years later on February 1,
2019.
Objectives
Analyze the PRD to determine the next time it has to be inspected/replaced to ensure that the risk
associated with the PRD does not exceed either the maximum financial risk of $100,000 or the
maximum area risk of of 100 m2.
Note: Insteadofcreatingyourownproject,youcanopenthe7PressureReliefDeviceprojectinthequick
53
9PressureReliefDevices(PRDs)
Solution
Pressure Relief Device Protecting Reactor component and then click the RBI Properties tab in the
Analysis panel.
On the General Properties tab, you start by making the general inputs shown next. In this case, you do not
have statistical models that reflect the failure on demand or the probability of leakage, so you select No
for both these properties.
Next, you make the inputs shown next for the financial consequences.
54
9.1PressureReliefDevices
Finally, you make the following inputs for the Demand properties. These properties determine the
overpressure demands which the device can be subjected to and the maximum risk allowed for. Note that
the Overpressure Multiplier is a value that reflects the maximum expected increase in the pressure due
to the possible overpressure demand cases. It is based on a scale of 1 to 4, where 1 indicates the best case
scenario and 4 indicates the worst case scenario. For this analysis, you enter a value of 1.5, which
indicates that the overpressure is not too extreme.
To specify that the PRD is protecting the reactor casing, you right-click inside the Assigned Components
section of the Analysis panel and choose Assign Components. You choose the Reactor Casing
component and click OK. As shown next, the Assigned Components section of the Analysis panel now
includes it.
Because the reactor casing has already been analyzed, it uses the model generated by the software when it
was analyzed. If the component has not already been analyzed and a model is not provided, then the
software treats the component as it cannot fail and thus results will not be accurate.
After adding the reactor casing, you choose System Hierarchy > Risk Based Inspection > Calculate
Risk to calculate the results. In the Calculation Options window you choose to calculate only the currently
selected PRD and click OK.
55
9PressureReliefDevices(PRDs)
The results for PRDs are very compact. Because PRDs are always replaced or refurbished to as-good-asnew condition during an inspection, and because the inspection interval for PRDs is regulated by industry,
there is no need to show results at dates other than the target date. As shown below, the target date for the
next inspection of the PRD is several months away. (Note that the date in the following picture is based on
the date when the analysis was performed in the sample project. If you repeat the analysis from scratch or
if you recalculate, the specific date in your results may be different.)
Conclusion
The analysis indicates that the PRD must be replaced or refurbished approximately 3.5 years after
installation. Although this slightly more than half as long as the required regulatory inspection interval, it
is recommended because that is the date that the maximum allowed financial risk of $100,000 will be
reached.
56
10
Reports
Once all of the analyses have been performed, it is important to be able to
display the results in compact, easy-to-read reports. Each report should
contain specific information that is vital for that particular set of results. The
RBI software has 20 built-in reports, including summary and detailed risk
matrices, damage summaries, consequence summaries and specific reports
for each of the two special cases, HEXTUBEs and PRDs.
Report
generation
This chapter demonstrates how to generate a complete set of reports for your analysis.
10.1Reports
Management would like to see the RBI analysis results in reports that they can use to quickly glance over
all the information/results generated during your analysis.
Objectives
Generate reports that display the results calculated during the analysis of the vital components of
the plant.
Note: Insteadofcreatingyourownproject,youcanopenthe7PressureReliefDeviceprojectinthequick
startrepositorytogeneratethereportfromtheanalysesthathavealreadybeencreated.
Solution
You select the top-level Hydrogen Generation Unit item in the system hierarchy, then choose Home >
Reporting > Reports. The Reports window provides a choice of predefined and custom report forms that
can be included in a report document that is generated in either Microsoft Word or Excel.
You first remove any existing reports in the Selected Reports area by clicking the Exclude All button
(<<).
57
10Reports
To build the desired report, you double-click, (or drag and drop) the following report forms to move them
into the Selected Reports area.
Component Types (All Project Items)
Area Risk Matrix at Plan Date (Selected Items)
Financial Risk Matrix at Plan Date (Selected Items)
Consequences Summary
Risk Summary at Plan Date
Recommended Inspections at Due Date
HexTubes Summary
PRDs Summary
To create a report in Excel, choose Output Types > Excel Spreadsheet, then click Generate Report and
specify the name and location where the report file will be saved. The report will then open automatically
in Excel. When you are finished reviewing the reports, you close Excel and the Reports window.
58
RELIASOFT CORPORATION END-USER LICENSE

AGREEMENT
This ReliaSoft Corporation End-User License Agreement is a legal agreement between You and ReliaSoft
Corporation for ReliaSoft Corporation's software products, which includes computer software and associated
media and printed materials as well as online or electronic documentation and any software updates or
upgrades, henceforth collectively called the Application.
By installing, copying or otherwise using the Application, You agree to be bound by the terms of this End-User
License Agreement and represent and warrant that You are authorized to do so. If You do not agree to the
terms of this End-User License Agreement, do not install or use the Application and promptly return the
Application to the vendor from which you obtained it within fourteen (14) calendar days from the date of
purchase for a full refund.
This Agreement is effective from the earlier of the date that You open the sealed software package, if
applicable, or install the Application, or fourteen (14) calendar days from the date the Application was
purchased or otherwise obtained from ReliaSoft Corporation, and continues until expressly terminated by
ReliaSoft Corporation.
This Application is protected by copyright laws and international copyright treaties, as well as other intellectual
property laws and treaties. This Application is licensed, not sold.
DEFINITIONS
1.1
1.2
1.3
1.4
1.5
1.6
Access. Means connected to or using the Application in any manner, either directly or
indirectly through any middle tier application or system.
Activate. Means the act of enabling the Application to operate on a specific computer by
registering the Application license with the ReliaSoft License Server and activating the
Application for operation.
Location. Means the postal address of the site where the Application shall be installed.
Location shall mean a single physical location.
Named User(s). Means the individual(s) permitted to Access the Application, and it refers
to specific individuals.
ReliaSoft License Server. Means the ReliaSoft server(s) that provides license activation,
registered end-user management, license management and license compliance
enforcement services for the Application.
You. Means the licensee or the individual acquiring the license of this Application and, in
either case, the affiliates, employees, contractors and agents of said licensee or individual.
LICENSE GRANT
2.1
Grant. Subject to the license types defined in Section 3 hereof, You are granted a personal,
non-exclusive and limited license to install, Activate and Access the Application under the
license type and in the quantities for which You have obtained a license. You may install
and Activate the Application onto designated equipment at the specified Location(s), solely
2.2
2.3
as necessary to use the Application in accordance with this Agreement. You may not
distribute, sublicense, copy (except as expressly permitted in this Agreement), transfer
(except as expressly permitted in this Agreement), nor give the Application to any third
party.
Ownership. The Application and the information it contains, including any updates,
upgrades, modifications and derivative works, and all copies of them, are the property of
ReliaSoft Corporation (or its licensors), and title remains with ReliaSoft Corporation (or
ReliaSoft Corporation's licensors). All applicable rights in patents, copyrights and trade
secrets in the Application are and will remain with ReliaSoft Corporation (or ReliaSoft
Corporations licensors). No title to, or ownership of, the Application or the information
contained therein is transferred to You. ReliaSoft Corporation reserves all rights not
explicitly granted in this Agreement.
Rights to Developments. This Agreement also governs your use of any enhancements,
data, or information provided by ReliaSoft Corporation while performing any technical,
training or consulting services. Any ideas, know-how, techniques and software developed
by ReliaSoft Corporation, including any enhancements or modifications made to the
Application by any person, are the property of ReliaSoft Corporation.
INSTALLATION AND USE

ReliaSoft Corporation licenses any Application under this Agreement on a per user basis. In other
words, ReliaSoft Corporation licenses an Application to each user and not to a particular computer.
This Agreement grants You the following rights, depending on the license You have obtained from
ReliaSoft Corporation:
3.1
Named User License. The Named User License is licensed to one individual Named User.
This is a perpetual license. Each software package includes the installation media and one
copy of the Application documentation per license, either in physical/hard copy format
and/or electronic format. Each Named User licensed may install, Activate and Access the
Application on a single computer at any time, provided that the Named User is the only
person who uses this Application. In the event that the Application is required on a new
computer for the Named User, the Named User will be required to deactivate the active
installation before being allowed to install and Activate the Application on the new
computer. There is a limit of 2 activations allowed per year.
Use of the Application on any computers by any user other than the Named User who has
licensed the Application is strictly prohibited. Such other users must obtain a separate
license of the Application from ReliaSoft before any use.
3.2
Floating License. The Floating License is licensed to an organization with multiple regular
and occasional Named Users on a single network of computers at one or more specified
Locations, depending on the type of Floating License obtained (LAN, Country, Regional,
Global). This is a perpetual license. The software package includes the installation media
and one copy of the Application documentation per license, either in physical/hard copy
format and/or electronic format. There is no restriction on how many Named Users can
install and Activate the Application; however, the number of Floating Licenses under license
3.3
3.4
indicates the maximum number of computers that can concurrently Access the Application
at any given time.
As an example, for a Floating License with ten (10) seats, the Application can be installed
and activated by as many Named Users and on as many computers as You deem
necessary, with only ten (10) of those computers being able to Access the Application at the
same time. If a user attempts to Access the Application from an eleventh (11th) computer,
the user must wait until one of the other ten users ends their session and releases a seat.
The Floating License allows for installation on multi-user capable environments such as
Windows, Terminal or Citrix servers.
A Floating License with a LAN option only allows installation and Activation by Named
Users on the same Local Area Network (i.e., same Location). A Floating License with a
Country option only allows installation and Activation by Named Users in the same country.
A Floating License with a Regional option only allows installation and Activation by Named
Users in the same geographical region (e.g., Americas, EMEA, APAC). A Floating License
with a Global option allows installation and Activation by Named Users worldwide.
Under this license, Named Users are allowed to check out a Floating License from the
ReliaSoft License Server for a specified period of time, effectively being guaranteed Access
to the Application while simultaneously reducing the number of available Floating Licenses
for the rest of the user pool until the Floating License is checked back into the ReliaSoft
License Server or otherwise released.
This type of license requires that you provide/allow internet access from the Application to
the ReliaSoft License Server at https://Validate.ReliaSoft.org. Concurrency authorization
and control is managed and provided by this server. You may need to modify and adjust
your internet and/or firewall settings and/or set the aforementioned server as a trusted
location in order to use the Application.
Asset-based License (only applies to Orion eAPI software). The Asset-based License is
licensed to all direct employees of a corporate entity within one or more specified Sites,
depending on the license obtained. This license excludes subcontractors, suppliers or
temporary employees, unless they are using the Application inside an eligible Site on a
computer owned by that Site. This is a perpetual license.
Under this license, an unlimited number of Named Users from the licensing Site or Sites is
allowed to Access the Application; however, the license restricts the number of physical
assets (commonly referred to as Asset TAGs) that can be configured and managed within
the Application. For this license, a Site is defined as a distinct physical address/site of a
corporate entity, where the physical assets being managed reside (e.g., a refinery or a mine
or a power station). The license specifically excludes broader geographical areas, such as
cities or states/provinces (where multiple Sites might exist).
Subscription License. Subscription licenses are available for the Named User and
Floating Licenses. The license terms are the same as the corresponding license type being
subscribed to except that the license expires according to the term purchased. The
subscription fee will not be prorated or refunded if license subscription is cancelled or not
used in full. A standard non-expiring license may be obtained at any time at the current
Application list price.
3.5
Evaluation, Demo, No Save Demo, Beta, or Otherwise Expiring or Non-Expiring
Licenses of any Type Provided for Evaluation Purposes or Free of Charge. These are
Evaluation/Not for Sale licenses and, notwithstanding any other section of this Agreement,
You may not use the Application for commercial purposes, nor sell or otherwise transfer it
for value. Commercial purposes include the use of the Application in creation of publicly
distributed computer software. You are acquiring only the limited right to use a single copy
of the Application solely for evaluation purposes and for a limited time. ReliaSoft
Corporation can terminate this Agreement at any time. You have no rights under any
sections of this Agreement other than those specifically allowed for within this section
(Section 3.5). THE APPLICATION IS LICENSED AS IS with no representations or
warranties of any kind. Note: As the section title implies, users of any license provided by
ReliaSoft Corporation for evaluation purposes or free of charge (even if it is, for example, a
Named User or Floating License), shall abide by the rules set forth in this section.
Regardless of the license type You have obtained from ReliaSoft Corporation, You may access
shared data storage files or databases relating to the Application across a wide area network (WAN)
or a virtual private network (VPN), instead of a local area network (LAN), as long as such access is
permitted by your policies and authorized by You via appropriate Application and network
configuration settings. Although such access is not prohibited by ReliaSoft Corporation, you
acknowledge that WAN and VPN data transfer rates vary widely and could lead to decreased and
unpredictable performance (as compared to a LAN) and therefore disclaim any expectation of
Application performance should you choose to: a) configure any part of the Application; b) use the
Application; or c) access shared data storage files in a distributed environment over a WAN or VPN.
Such disclaimer does not apply to any Application designated and licensed as a native Web-based
Application by ReliaSoft Corporation.
SOFTWARE TRANSFERS
4.1
4.2
Named User License. You may permanently transfer all of your rights related to a Named
User License under this Agreement, provided that You retain no copies, You transfer all of
the Application (including all component parts, media, printed or electronic materials, any
upgrades and this Agreement) and the transferee agrees to the terms of this Agreement. If
the Application is an upgrade, any transfer must include all prior versions of the Application.
Named User License transfers are only allowed between Named Users of the same
organization (i.e., transfers are not allowed across different organizations). The Named
User transferring the Application must deactivate any and all active installations of the
Application before the transferee can Activate the Application. A Named User License may
not be transferred more than two times in a year.
This section also applies to Named User License Subscriptions.
Floating Licenses or Asset-based Licenses. Floating or Asset-based Licenses are NOT
transferable across organizations, and licensing rights CANNOT be split or transferred
between multiple organizations in cases of corporate acquisitions or divestitures, except as
allowed in items (a) and (b) of this section (Section 4.2), and with ReliaSoft Corporations
written consent.
In cases of corporate acquisitions or divestitures: (a) Floating Licenses remain with the
organization that originally obtained the licenses, (e.g., if the organization that holds the
license is acquired by another entity, the licensing rights will be transferred to the acquiring
entity); (b) Asset-based Licenses remain with the original licensing site and therefore pass
on to the owner of the specific licensing site as long as the site continues to exist;
This section also applies to Floating License Subscriptions.
5
DESCRIPTION OF OTHER RIGHTS, LIMITATIONS AND MISCELLANEOUS
ITEMS
5.1
5.2
5.3
5.4
Limitations on Reverse Engineering, Decompilation and Disassembly. You may not

reverse engineer, decompile or disassemble the Application. You shall not provide, disclose
or otherwise make available the Application, in any form, to any person other than your
employees and under your direction and control for purposes specifically related to your
permitted use of the Application. You will not: (a) alter, modify or prepare derivative works
of the Application; (b) transmit the Application electronically by any means; or (c) cause or
permit the translation, reverse engineering, disassembly, or decompilation of the Application
to determine any design structure, source code, concepts and methodology behind the
Application, whether to incorporate it within any product of your own creation, create a
derivative work, create any product that is competitive with the Application or other
ReliaSoft Corporation products, or for any other purpose.
Copyright. All title and copyrights to the Application are owned by ReliaSoft Corporation (or
its suppliers or licensors). The Application is protected by copyright laws and international
treaty provisions. Therefore, You must treat the Application like any other copyrighted
material except that You may make one copy of the media solely for backup or archival
purposes.
Proprietary Notices. All title, trademarks, copyrights and intellectual property rights in and
pertaining to the Application (including but not limited to any copies thereof, software
structure and organization, source code, images and new releases) are valuable property of
ReliaSoft Corporation and are owned or licensed by ReliaSoft Corporation. You may not
intentionally remove, alter or destroy any form of copyright and trademark notices,
proprietary markings or confidential legends placed upon or contained within the
Application, including but not limited to any such notices contained in physical and/or
electronic media or documentation, in the Application interface boxes, or in any of the
runtime resources, code or other embodiments originally contained in or dynamically or
otherwise created by the Application.
Use of ReliaSoft Corporations Marks. You may not use the name, logos, trade names or
trademarks of ReliaSoft Corporation or any of its affiliates in any manner including, without
limitation, in your advertising, promotional literature or any other material, whether in
written, electronic, or other form distributed to any third party, except in the form provided by
5.5
5.6
5.7
5.8
5.9
5.10
5.11
5.12
ReliaSoft Corporation and then solely for the purposes of identifying your use of the
ReliaSoft Corporation Application.
Verification. You will provide, on ReliaSoft Corporations reasonable written request,
written verification that the Application is being used according to the terms of this
Agreement. Upon thirty days prior written notice, if ReliaSoft Corporation has reasonable
grounds to believe that this Agreement has been breached, ReliaSoft may audit your use of
the Application provided such audit is: (a) limited to records relating solely to the Application
necessary to verify compliance with the terms of this Agreement; (b) performed by a
reputable independent third party auditor acceptable to You (acting reasonably); (c) the
third party auditor shall comply with your standard security policies; (d) the third party
auditor shall execute your standard protective non-disclosure agreement; and (d) the cost of
any requested audit will be solely borne by ReliaSoft Corporation if no breach is found as a
result of the audit or will be solely borne by You if a breach is found. Such audit shall occur
no more than once every twelve months and shall not unreasonably interfere with your
normal business operations.
Modification. ReliaSoft Corporation reserves the right to modify or enhance the Application
without obligation to notify You of such changes or to furnish them to You, unless otherwise
agreed upon with a separate agreement (such as an annual maintenance agreement).
Copying. You may not, under any circumstances, copy the Application, in whole or in part,
except as expressly provided under the Copyright section above.
Separation of Components. The Application is licensed as a single product. Its
component parts may not be separated for use on more than one computer.
Rental or Other Exploitation. You may not publish, sub-license, re-license, assign, sell,
distribute, license, transfer, rent, lease or lend the Application to any party, except transfer
the Application as expressly provided under the Transfer section above. If you received any
revenues from the unlawful distribution of the Application, such revenues will be forfeited to
Fees. You will pay ReliaSoft Corporation all fees or other amounts due under this
Agreement, plus any and all applicable taxes, within the payment term due date specified
on the respective invoice. In the event that the respective invoice is not paid on time, or at
all, ReliaSoft Corporation reserves the right to terminate this Agreement and revoke the
corresponding licenses issued to You within the scope of this Agreement.
Termination. Without prejudice to any other rights, ReliaSoft Corporation may terminate
this Agreement if You fail to comply with the terms and conditions of this Agreement and
such breach is not cured within thirty days of notice of such breach. In such event, You
must destroy all copies of the Application and all of its component parts. Additionally, You
may be held liable for any damage or loss of profit caused to ReliaSoft Corporation arising
from unauthorized use or duplication of this Application.
Supplemental Licenses. If, after the effective date of this Agreement, You subsequently
purchase additional licenses of the Application, these supplemental licenses will be
included under this Agreement.
5.13
5.14
5.15
5.16
5.17
Press Releases. As part of this Agreement, You acknowledge that ReliaSoft Corporation
may make reference to You as a customer of ReliaSoft Corporation in press releases,
advertising and promotional materials, and You consent to any such reference. ReliaSoft
Corporation will NOT disclose any further details beyond referring to You as a customer
without prior written consent, not to be unreasonably withheld.
Relationship. You and ReliaSoft Corporation are independent contractors and neither is an
agent, joint venture partner, partner or employee of the other, and ReliaSoft Corporation will
not be obligated by any agreements or representations made by You to any person, nor
with respect to any other action by You, nor will ReliaSoft Corporation be obligated for any
damages to any person, whether caused by your actions, failure to act, negligence or willful
conduct.
Upgrades. If the Application is an upgrade from another product, whether from ReliaSoft
Corporation or another supplier, You may use or transfer the Application only in conjunction
with that upgraded product, unless You destroy the upgraded product. If the Application is
an upgrade of a ReliaSoft Corporation product, You may use the upgraded product only in
accordance with this Agreement. If the Application is an upgrade of a component of a
package of software programs that You licensed as a single product, the Application may
be used and transferred only as part of that single product package and may not be
separated for use on more than one computer.
U.S. Government Restricted Rights. The Application was developed at private expense.
No portion of the Application was developed with government funds and the Application is a
trade secret of ReliaSoft Corporation for all purposes of the Freedom of Information Act.
The Application and documentation are provided with RESTRICTED RIGHTS. Use,
duplication or disclosure by the Government is subject to restrictions as set forth in
subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at
DFARS 252.227-7013 (or its successor) or subparagraphs (c)(1) and (2) of the Commercial
Computer Software Restricted Rights at 48 CFR 52.227-19 (or its successor), as
applicable. Manufacturer is ReliaSoft Corporation, 1450 S. Eastside Loop, Tucson, Arizona
85710, USA.
Limited Warranty. ReliaSoft Corporation warrants that: (a) the Application will perform
substantially in accordance with the accompanying written materials, and on machines
meeting the published minimum requirements, for a period of sixty (60) days from the date
of receipt; and (b) any media on which the Application is furnished will be free from defects
for a period of sixty (60) days from the date of receipt. Some states and jurisdictions do not
allow limitations on duration of an implied warranty, so the above limitation may not apply to
You; in such states and jurisdictions the liability of ReliaSoft Corporation shall be limited to
the minimum extent permitted by law. To the extent allowed by applicable law, implied
warranties on the Application and media, if any, are limited to sixty (60) days; and (c) at the
time of installation, the Application will be free from any mechanism, feature or any other
codes or instructions that: (i) cause the Application to remotely transmit information to
ReliaSoft or any third party, except to communicate with one of ReliaSofts servers to
facilitate specific functions of the Application (such as to communicate with the ReliaSoft
5.18
5.19
5.20
5.21
5.22
License Server, access the online help files, etc.); or (ii) may be used to permit Access to,
or use of, the Application or computer system on which the Application is loaded, or to
which the Application is linked, by ReliaSoft or any third party.
Customer Remedies. ReliaSoft Corporation's and its suppliers' or licensors entire liability
and Your exclusive remedy shall be, at ReliaSoft Corporation's option, either (a) return of
the fee paid for the Application, or (b) repair or replacement of the Application or media that
does not meet ReliaSoft Corporation's Limited Warranty and which is returned to ReliaSoft
Corporation with a copy of your receipt or invoice. Any replacement Application or media
will be warranted for the remainder of the original warranty period or thirty (30) days,
whichever is longer. None of these remedies nor any product support services offered by
ReliaSoft Corporation are available without a valid License Certificate issued by ReliaSoft
Corporation.
Warranty Exclusions. The Limited Warranty is void if the damage or defect has resulted
from accident, abuse or misapplication. Any modification of the Application by any person
other than ReliaSoft Corporation shall void this warranty. Any manipulation of the
Applications data storage infrastructure or direct storage of data into the Applications data
storage from outside the Application by any person other than ReliaSoft Corporation or
ReliaSoft Corporations authorized representative shall void this warranty. The warranties in
this section extend only to You and are contingent upon proper use of the Application. The
warranties will not apply to any failure caused by (a) accident, (b) unusual physical,
electrical or electro-magnetic stress, (c) negligence, (d) misuse, (e) failure of electrical
power, air conditioning or humidity control, (f) use of the Application with any equipment or
software not reflected in ReliaSoft Corporations specifications, (g) installation, alteration or
repair of the Application by anyone other than ReliaSoft Corporation or ReliaSoft
Corporations authorized representative, or (h) or installation on equipment on which the
original identification marks have been removed or altered.
No Other Warranties. No oral or written information or advice given by ReliaSoft
Corporation, its suppliers, dealers, distributors or agents shall create a warranty or in any
way increase the scope of the Limited Warranty, and You may not rely on any such
information or advice as a warranty.
Use of Results Provided By the Application Disclaimer. You understand that the results
provided by the Application cannot replace judgment required for important decisions. Use
of the results provided is done completely at your own risk. ReliaSoft Corporation does not
warrant that the functions of this Application will meet your requirements or be error free.
You assume all risk of the use, quality and performance of the Application, and You are
advised to use your own discretion and judgment regarding the use of the Application.
RELIASOFT CORPORATION, ON BEHALF OF ITSELF AND ITS LICENSORS,
DISCLAIMS ALL OTHER WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING,
BUT NOT LIMITED TO, IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS
FOR A PARTICULAR PURPOSE, WITH REGARD TO THE APPLICATION. IN NO EVENT
SHALL RELIASOFT CORPORATION OR ITS SUPPLIERS OR LICENSORS BE LIABLE
FOR ANY SPECIAL, INCIDENTAL, INDIRECT, OR CONSEQUENTIAL DAMAGES
5.23
5.24
5.25
5.26
5.27
WHATSOEVER (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF

BUSINESS PROFITS, BUSINESS INTERRUPTION, LOSS OF BUSINESS INFORMATION
OR ANY OTHER PECUNIARY LOSS) ARISING OUT OF THE USE OF OR INABILITY TO
USE THE APPLICATION, EVEN IF RELIASOFT CORPORATION HAS BEEN ADVISED
OF THE POSSIBILITY OF SUCH DAMAGES. USE OF THIS APPLICATION IS DONE
COMPLETELY AT YOUR OWN RISK, INCLUDING THE USE OF RESULTS PROVIDED
BY THIS APPLICATION. RELIASOFT CORPORATIONS LIABILITY HEREUNDER
SHALL BE LIMITED TO PHYSICAL DAMAGE DIRECTLY CAUSED BY THE SOLE
NEGLIGENCE OF RELIASOFT CORPORATION AND SHALL NOT EXCEED THE PRICE
PAID FOR THE SOFTWARE PRODUCT. NOTWITHSTANDING ANYTHING HEREIN TO
THE CONTRARY, THE FOREGOING DISCLAIMER AND LIMITATION OF LIABLITY
SHALL NOT APPLY TO RELIASOFT CORPORATIONS OBLIGATIONS UNDER ANY
CLAIM OF INFRINGEMENT AS DESCRIBED IN SECTION 5.28 OF THIS AGREEMENT.
Venue. Venue for any proceedings arising out of or relating to this Agreement shall be in
Tucson, Pima County, Arizona. The parties disclaim the application of the United Nations
Convention on Contracts for the International Sale of Goods. This Agreement is governed
by the laws of the State of Arizona, USA, without reference to conflict to law principles.
Each party to this Agreement submits to the exclusive jurisdiction of the state and federal
courts in the State of Arizona for the purpose of resolving any disputes arising under or
relating to this Agreement. Each party waives any jurisdictional, venue or inconvenient
forum objections to such courts.
Legal Expenses. If legal action is taken by either party to enforce this Agreement, all costs
and expenses (including reasonable attorney fees) incurred by the prevailing party in
exercising any of its rights or remedies or in enforcing any of the terms, conditions, or
provisions of this Agreement will be paid by the other party.
Force Majeure. ReliaSoft Corporation will not be responsible for delays or failures in its
performance due, in whole or in part, to any cause beyond its reasonable control.
Export Control. Regardless of any disclosure made by You to ReliaSoft Corporation of an
ultimate destination of the Application, You will not export, either directly or indirectly any
Application without first obtaining all licenses required, from the U.S. Department of
Commerce or any other agency or department of the United States Government, and
complying with the applicable laws. Neither the Application nor any direct product thereof
may be exported, directly or indirectly, in violation of applicable export laws, or may be used
for any purpose prohibited by these laws including, without limitation, nuclear, chemical or
biological weapons proliferation. ReliaSoft Corporation will provide You with all reasonable
information requested by You in connection to exporting the Application, including providing
You with the U.S. Export Controls Classification Number (ECCN) for the Application.
Waiver. The waiver by either party of any breach of this Agreement shall be in writing and
shall not constitute a waiver of any other or subsequent breach. No waiver of any of the
provisions of this Agreement will be deemed, or will constitute, a waiver of any other
provision, whether or not similar, nor will any waiver constitute a continuing waiver. The
5.28
5.29
5.30
failure by a party to enforce any provision of this Agreement will not be deemed a waiver of
future enforcement of that or any other provision.
Indemnification. You will indemnify and hold ReliaSoft Corporation harmless against any
and all claims, damages, losses, costs or other expenses (including reasonable attorney
fees) that arise directly or indirectly from your breach of this Agreement. ReliaSoft
Corporation shall defend, indemnify and hold harmless, at its own expense, You and your
assigns, successors, directors, officers and employees (each an Indemnified Party)
against any and all claims incurred by or made against an Indemnified Party by a third party
in connection with a claim, suit or action which is based on an allegation that the Application
when used by You as authorized under this Agreement, misappropriates or infringes any
third party patent, copyright, trade secret or other intellectual property right (each, a Claim)
provided that ReliaSoft Corporation shall have received from the Indemnified Party: (i)
notice of such Claim as soon as possible after You receive notice of the Claim; given that a
failure to provide notice shall only relieve ReliaSoft Corporation of its indemnity obligation to
the extent ReliaSoft Corporation was prejudiced by such failure; (ii) the exclusive right to
control and direct the investigation, defense or settlement of such claim; and (iii) all
reasonable necessary cooperation by You. If your use of any of the Application is, or in
ReliaSoft Corporations opinion is likely to be, enjoined due to a Claim, ReliaSoft
Corporation may, at its sole discretion: (a) modify the Application so that it becomes noninfringing, provided such modifications result in software with substantially similar
functionality and performance; (b) procure for You the right to continue using the Application
under substantially the same terms and conditions as provided for hereunder; or (c) if (a)
and (b) are commercially impracticable, terminate the Agreement and refund to You the
license fee paid by You for the Application which is the subject of the Claim as reduced to
reflect a three-year straight-line depreciation from the applicable license purchase date. The
foregoing indemnification obligation of ReliaSoft Corporation shall not apply: (1) if the
Application is modified by any party other than ReliaSoft Corporation and such modification
was not authorized in writing by ReliaSoft Corporation, but solely to the extent the alleged
infringement is caused by such modification; or (2) to any release of the Application other
than the most current release, provided that: (I) the most current release was either made
available at no cost to You and (II) You had a commercially reasonable period of time (not
to exceed 60 days) after availability of the current release to implement the current release
so as to avoid the infringement claim. This section (Section 5.28) sets forth ReliaSoft
Corporations sole liability and your sole and exclusive remedy with respect to any claim of
infringement.
Equitable Relief. You acknowledge and agree that, due to the unique nature of the
Application, there can be no adequate remedy at law for any breach of your obligations
under this Agreement, that any such breach may allow You or third parties to unfairly
compete with ReliaSoft Corporation resulting in irreparable harm and therefore that, upon
any such breach or threat thereof, ReliaSoft Corporation shall be entitled to injunctive and
other appropriate equitable relief in addition to whatever remedies it may have at law.
Entire Agreement; Amendments. This Agreement is the complete and exclusive
statement of the agreement between the parties and supersedes all prior agreements and
5.31
5.32
communications with respect to the subject matter, and there are no oral representations,
understandings or agreements that are not fully expressed herein. Any terms appearing on
any order or other form used by You which modify or conflict with the terms and conditions
set forth herein are expressly rejected. Except for the purpose of negating implied
warranties, no course of prior dealings between the parties and no usage of the trade shall
be relevant to supplement or explain any term used in this Agreement. No ReliaSoft
Corporation employee other than an officer of ReliaSoft Corporation (Vice President and
above) shall have any actual or apparent authority to modify the terms of this Agreement in
any way. All amendments shall be in writing and signed by the authorized representative of
Severability. If any one or more of the provisions of this Agreement shall for any reason be
held to be invalid, illegal or unenforceable in any respect, any such provision shall be
severable from this Agreement, in which event this Agreement shall be construed as if such
provision had never been contained herein.
Electronic Signatures. ReliaSoft Corporation and You agree that this Agreement may be
executed electronically and that electronic copies of this Agreement shall be binding upon
the parties to the same extent as manually-executed copies.

QS Rbi10

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

QS Rbi10

Загружено:

Авторское право:

Доступные форматы

Use with: RBI10_QuickStart_Rev1.

Quick Start Guide

RBI 10 Quick Start Guide

Examine how it was completed in the sample project.

The inspection program is primarily based on two publications provided by

publications provide guidance on developing a risk based inspection

Set the math precision used in the display of calculated results.

Create a new analysis project in a Synthesis database.

Set the management score for this particular analysis project.

You then click OK to close the window.

You click OK to close the window.

In the Add RBI Equipment window, you select Pipe.

icon into the Risk

In the Plan Date Results node:

This chapter demonstrates the analysis for a HEXTUBE.

You then enter the remaining properties shown next.

This chapter demonstrates the analysis for a pressure relief device.

Component Types (All Project Items)

Area Risk Matrix at Plan Date (Selected Items)

Financial Risk Matrix at Plan Date (Selected Items)

Risk Summary at Plan Date

Recommended Inspections at Due Date

RELIASOFT CORPORATION END-USER LICENSE

INSTALLATION AND USE

Limitations on Reverse Engineering, Decompilation and Disassembly. You may not

WHATSOEVER (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF

Вам также может понравиться