Analytical RBD:

1. Maintenance Scenario like: Corrective & Schedule maintenance & Spare Policy cannot be defined.
2. Throughput Scenario cannot be defined
3. State change trigger cannot be defined
4. Maintenance group cannot be defined.
Result of Analytical RBD: in QCP- Reliability, Probability of failure, failure rate, Mean Life etc. can be computed.

Life Cycle Cost Analysis

A life cycle cost analysis examines the costs incurred by a system or a component over its entire life span. Typical costs for a system may
include:
 Acquisition costs (or design and development costs).
 Operating costs:
 Cost of failures (e.g., contractually-specified penalties, risk of damage to equipment or people, etc.).
 Cost of repairs.
 Cost for spares.
 Downtime costs (e.g., contractually-specified restitution).
 Loss of production.
 Disposal costs.

Relationship between RBDs and Fault Trees

The most fundamental difference between fault tree diagrams and RBDs is that you work in the "success space" in an RBD while you
work in the "failure space" in a fault tree (“how likely is it that this machine will break down,” Fault Tree Analysis will help you answer that
question, it is a graphical representation of FMEA)). In other words, the RBD looks at success combinations while the fault tree looks at
failure combinations. Fault trees have traditionally been used to analyze fixed probabilities (i.e., each event that composes the tree has a
fixed probability of occurring), and are useful for risk analysis and for analyzing failures and/or pinpointing the root cause of failures. RBDs
may include time-varying distributions for the blocks' success or failure, as well as for other properties such as repair/restoration
distributions; this makes them well suited for maintainability and throughput analysis, as well as for identifying design weaknesses and
performing reliability allocation.

Although the symbols and structures of the two diagram types differ, most of the logical constructions in a fault tree diagram can also be
modeled with an RBD. In general, a fault tree can be easily converted to an RBD. It is generally more difficult to convert an RBD into a
fault tree, especially if one allows for highly complex configurations.
More Analysis & Tools:

Phase diagram:
Reliability phase diagrams represent scenarios in which a system may undergo changes over time. For example, a manufacturing
company's production may be lower during the night shift than during the day shift, Like Power Plant Grid Load variations, mining which
stops producing low or zero during night shift, or during shift changeover production stops.
Result: availability, cost, expected failure, downtime, throughput etc.

Markov Diagram:
Markov diagrams allow you to model the behavior of systems based on transitions between states, where the next state that the system
enters is dependent only upon the current state (and not affected by any previous states). This gives you the ability to look at partial or
degraded working states, and to start analysis in varying states.
For example: To demonstrate the use of continuous Markov diagrams with a very simple example, let's assume that you have a system
with two pumps, A and B. At any given time, the system may be in one of 5 states:
1. B is active, A is in standby. Both are in working condition. This is the state in which you want analysis to start.
2. A is active, B is in standby. Both are in working condition.
3. B fails. A is active and B is undergoing repair.
4. A fails. B is active while A is undergoing repair.
5. Both pumps are undergoing repair.
Results: Point Availability, Point Reliability, Point Unavailability, Point Probability of Failure

BlockSim:
BlockSim provides a comprehensive platform for reliability analysis, maintainability analysis, availability analysis, reliability optimization,
throughput calculation, process flow diagrams, resource allocation, life cycle cost estimation and other system analyses.

Block Properties:

Operations: Current age, Duty cycle

Consequential Cost: Cost per failure, Downtime rate
Maintenance group:
State Change Triggers
State change triggers (SCT) allow you to specify the starting state of a block (i.e., off or on) and its state upon repair, then specify events
that will activate and/or deactivate the block during simulation. This allows you to model a cold standby configuration (i.e., one where the
component cannot fail when in standby) without using a standby container, which may be useful if you are using a parallel or complex
configuration, as blocks can be connected only in series in standby containers. State change triggers are available for standard blocks in
simulation RBDs and for events in simulation fault trees.
State Change Trigger Assumptions
Initial State: On or Off
State upon repair: Always On or always Off or Default On or Off unless SCT overridden

Block Throughput Properties

The Throughput field allows you to enter the quantity of output and the units used for time. In addition, the Allocation field allows you to
specify how that output is routed if multiple outgoing paths from the block exist:
 If Weighted allocation across paths is selected, the allocation will be weighted according to the capacity of each block if there is more
than one block that can receive the units. The software calculates the total capacity of all possible paths and then determines the
percentage of the total capacity represented by each block. It then sends that percentage of the "stream" to each block. For example,
if 3 blocks can receive 9 units and Block A can process 5 units, Block B can process 5 units and Block C can process 10 units, then
 Block A receives 25% (5 + 5 + 10 = 20 and 5/20 = 0.25) of the stream (or 9 * 0.25 = 2.25), Block B receives 25% (5/20 = 0.25) of the
stream (2.25) and Block C receives 50% (10/20 = 0.5) of the stream (4.5).
 If Allocate equal share to all paths is selected, an equal share of units will be allocated to each of the blocks if there is more than one
block that can receive the units. In the example described above, each of the 3 blocks would receive 1/3 of the stream, or 3 units.
This option may result in a backlog if any blocks cannot process their entire allocation.

If there is more than one block that can receive units and one of those blocks has failed, the units will form a backlog for the failed block if
the Send units to failed blocks option is selected. If it is not selected, the failed block will not receive any of the units and the entire stream
will be distributed among the unfailed blocks.

URD- Universal reliability Definition:

In simulation diagrams, the URD assigned to blocks define reliability and maintenance characteristics.
1- Model: define failure behavior or distribution.
2- Corrective task: Describes the maintenance action taken to restore a failed component to operational status
 Task Duration
 Spare Part Pool:
o Unlimited spares
o Limited Spares: Schedule restock, restock as need, Emergency spares
Does task bring the system down?
Does task bring the item down?
Restoration factor

3- Scheduled Task: same properties as corrective task, only the difference in Task condition as below:
Preventive: Maintenance interval to be defined.
Inspection: & On Condition: Options- P-F interval and Failure Detection threshold (FDT)

Result of Block sim:

System level: Availability, Reliability, Expected nos. of failures, CM/PM & Inspection actions (Nos. of events & its downtime), Total Cost
(each maintenance cost like resources & spares), throughput.
Block Summary: same as above and FCI

Block Metrics
 RS Criticality Indices
 RS FCI: The ReliaSoft Failure Criticality Index for the block. This is a relative index showing the percentage of times
that a failure of the block caused a system failure
 RS DECI: The ReliaSoft Downing Event Criticality Index for the block.
Shows the number of system downing events caused by the block divided by the total number of system downing
events).
 RS DTCI: The ReliaSoft Downtime Criticality Index for the block. This is a relative index showing the contribution of
the block to the system's downtime.
 RS BCCI: The ReliaSoft Block Cost Criticality Index for the block. This is a relative index showing the contribution of
the block to the total costs (i.e., the total block costs divided by the total costs)