GRIF 2021

Fault Tree

User Manual
Version 18 February 2021

Copyright © 2021 TotalEnergies

 Abstract
This document is the user manual of Fault Tree module of GRIF 2021

User Manual 2 / 133

Table of Contents
1. Presentation ............................................................................................................................. 6
1.1. Introduction ........................................................................................................................ 6
1.2. Main window of the Fault Tree module ................................................................................... 6
1.3. Menus presentation .............................................................................................................. 6
1.3.1. File ............................................................................................................................. 7
1.3.2. Edit ............................................................................................................................ 9
1.3.3. Tools ......................................................................................................................... 10
1.3.4. Document .................................................................................................................. 13
1.3.5. Data and Computations ................................................................................................ 13
1.3.6. Group ........................................................................................................................ 15
1.3.7. ? ............................................................................................................................... 16
1.4. Vertical toolbar ................................................................................................................. 18
1.5. Data Editing Tables ........................................................................................................... 20
1.6. Tree view ......................................................................................................................... 23
1.7. Template panel .................................................................................................................. 23
2. Creating a fault tree ............................................................................................................... 24
2.1. Entering the tree ................................................................................................................ 24
2.1.1. Entering gates ............................................................................................................. 24
2.1.2. Entering events ........................................................................................................... 24
2.1.3. Initiator event for frequency computation (UFI) ................................................................ 25
2.1.4. Entering links ............................................................................................................. 25
2.1.5. NOT gate ................................................................................................................... 26
2.2. Entering Comments ............................................................................................................ 26
2.3. Dynamic fields .................................................................................................................. 27
2.4. Configuring the elements .................................................................................................... 28
2.4.1. Configuring the gates ................................................................................................... 28
2.4.2. Configuring the events ................................................................................................. 29
2.5. Using shortcuts .................................................................................................................. 32
2.5.1. Identical Transfer Gates (or Shortcuts on gates) ................................................................ 32
2.5.2. Repeated events (or Shortcuts on events) ......................................................................... 34
2.5.3. Search shorcuts ........................................................................................................... 34
2.6. Cloning ............................................................................................................................ 35
2.7. Components/Systems .......................................................................................................... 35
2.7.1. Create a component/system ........................................................................................... 36
2.7.2. Uses of the components/systems .................................................................................... 36
2.8. Page and group management ............................................................................................... 37
2.9. Shaping ............................................................................................................................ 39
2.9.1. Global shaping ............................................................................................................ 39
2.9.2. Shaping element by element .......................................................................................... 40
2.9.3. Element size ............................................................................................................... 40
3. Data Entry Aids ..................................................................................................................... 42
3.1. Copy / Paste / Renumber (without shortcut) ............................................................................ 42
3.2. Ordinary Copy/Paste .......................................................................................................... 43
3.3. Overall change .................................................................................................................. 43
3.4. Selection change ................................................................................................................ 44
3.4.1. Gates graphical editing ................................................................................................. 44
3.5. Alignment ........................................................................................................................ 45
3.6. Multiple selection .............................................................................................................. 46
3.7. Selecting connex (adjacent) parts .......................................................................................... 46
3.8. Zoom and page size ........................................................................................................... 46
3.9. Cross hair ......................................................................................................................... 47
3.10. Gluing/Associating graphics ............................................................................................... 47
3.11. Line ............................................................................................................................... 47
3.12. Table Cleaning ................................................................................................................ 48
3.13. Edit laws ........................................................................................................................ 48

User Manual 3 / 133

 3.14. Events import .................................................................................................................. 49
3.15. Event insertion from the event tab ...................................................................................... 49
3.16. Document properties / Track change / Images management ...................................................... 50
3.17. Compare 2 documents ....................................................................................................... 53
3.18. Files of the documents ...................................................................................................... 54
3.19. Hypothesis ...................................................................................................................... 55
4. The parameters ...................................................................................................................... 56
4.1. Creation ........................................................................................................................... 56
5. Attributes ............................................................................................................................... 58
5.1. Creation ........................................................................................................................... 58
5.2. Use of the attributes ........................................................................................................... 58
6. Help with common cause failures ............................................................................................. 61
6.1. Creating a CCF ................................................................................................................. 61
6.2. Editing a CCF ................................................................................................................... 61
7. Laws and uncertainties ............................................................................................................ 65
7.1. Setting ............................................................................................................................. 65
7.2. Description of the laws ....................................................................................................... 66
7.2.1. UNDEF / Undefined .................................................................................................... 66
7.2.2. CST/ Constant law ...................................................................................................... 66
7.2.3. EXP / Exponential law ................................................................................................. 66
7.2.4. EXPD / Dormant exponantial ........................................................................................ 67
7.2.5. IND / Unavailability law ............................................................................................... 67
7.2.6. WBL / Weibull ........................................................................................................... 68
7.2.7. WBP / Weibull periodic ............................................................................................... 68
7.2.8. WBD / Weibull with detected failures ............................................................................. 69
7.2.9. TPS / Simple Periodic Test law ..................................................................................... 69
7.2.10. TPE / Extended Periodic Test law ................................................................................ 70
7.2.11. TPC / Full Periodic Test law ....................................................................................... 70
7.2.12. TPC / Full Periodic Test with defined times ................................................................... 71
7.2.13. NRD / No Recovery Before Delay law .......................................................................... 71
7.2.14. GLM / GLM Asymptotic law ...................................................................................... 71
7.2.15. DOR / Dormant ......................................................................................................... 72
7.2.16. CMT / Constant mission time ...................................................................................... 72
7.2.17. EMP / Empiric .......................................................................................................... 72
7.2.18. MKR / Markov graph ................................................................................................. 72
7.2.19. OCC / Occurrences of failures ..................................................................................... 72
7.2.20. SIL / SIL level .......................................................................................................... 73
7.2.21. RRF / Risk Reduction Factor ....................................................................................... 73
7.2.22. EXP / Expression ....................................................................................................... 73
7.2.23. STO / Stored Electrical Component .............................................................................. 73
7.3. Uncertainties on the parameters ............................................................................................ 74
7.3.1. UNI / Uniform law ...................................................................................................... 74
7.3.2. NLOG / Log normal law .............................................................................................. 74
7.3.3. NORM / Normale ........................................................................................................ 75
7.3.4. OBS / Observation ....................................................................................................... 75
7.3.5. OBS (#) / Periodique Observation .................................................................................. 75
7.3.6. GAM / Gamma ........................................................................................................... 76
7.3.7. BET / Beta ................................................................................................................. 76
7.3.8. TRI / Triangulaire ........................................................................................................ 76
7.3.9. Consideration of the uncertainties ................................................................................... 77
8. Example of a Fault Tree ......................................................................................................... 78
9. Computations ......................................................................................................................... 81
9.1. Albizia computations .......................................................................................................... 81
9.1.1. Configuring the computations ........................................................................................ 81
9.1.2. Albizia Results ........................................................................................................... 91
9.2. MOCA computations .......................................................................................................... 92
9.2.1. Configuring the computations ........................................................................................ 93

User Manual 4 / 133

 9.2.2. Reading the results ...................................................................................................... 95
9.3. Tables and Panels to display results ...................................................................................... 96
9.3.1. Result-tables ............................................................................................................... 96
9.3.2. Export data ................................................................................................................ 97
9.3.3. Result-Panels .............................................................................................................. 98
9.4. Batch computation ............................................................................................................ 102
9.5. Result Bank .................................................................................................................... 103
9.6. Compute manager ............................................................................................................ 103
10. Curves ................................................................................................................................ 105
10.1. Edit curves window ........................................................................................................ 105
10.2. Selection of results window .............................................................................................. 107
10.2.1. Curves from data in result-bank .................................................................................. 107
10.2.2. Comparative curves from data in results bank ............................................................... 107
10.3. Quick curves creation ...................................................................................................... 108
11. Database of parameters ........................................................................................................ 109
11.1. Format of the databases ................................................................................................... 109
11.2. Connect to a database ..................................................................................................... 109
11.2.1. Connection to a CSV file .......................................................................................... 110
11.2.2. Connection to a XLS file .......................................................................................... 111
11.2.3. Connection to a database (with a JDBC connection) ....................................................... 112
11.3. Import parameters from a connected database ...................................................................... 113
11.4. Update of the parameters from the database ........................................................................ 114
11.5. Rebuild of the links to the database ................................................................................... 115
12. Save ................................................................................................................................... 116
12.1. Document template ......................................................................................................... 116
12.2. Save as (Confidential) ..................................................................................................... 118
12.2.1. Confidentiality of the gates ........................................................................................ 118
12.2.2. Save as confidentially ............................................................................................... 119
12.3. RTF File ....................................................................................................................... 121
12.4. Input data ...................................................................................................................... 121
12.5. Results .......................................................................................................................... 121
12.6. Curves .......................................................................................................................... 123
13. Printing .............................................................................................................................. 124
13.1. Page setup ..................................................................................................................... 124
13.2. Print ............................................................................................................................. 124
13.3. Save in RTF file ............................................................................................................ 129
14. Options of GRIF - Fault Tree ............................................................................................... 130
14.1. Executables ................................................................................................................... 130
14.2. Options ......................................................................................................................... 130
14.3. Graphics ....................................................................................................................... 130
14.4. Digital format ................................................................................................................ 131
14.5. Laws ............................................................................................................................ 131
14.6. Computations / Results .................................................................................................... 131
14.7. Events .......................................................................................................................... 131
14.8. Gates/Shortcuts .............................................................................................................. 132
14.9. Curves .......................................................................................................................... 132
14.10. Import ......................................................................................................................... 132

User Manual 5 / 133

1. Presentation

1.1. Introduction
Tree is used to model a system as a fault tree based on Boolean logic, which produces simple models suited to
all domains (aeronautics, automobile, rail, oil and gas, etc.). The Tree module uses ALBIZIA, the BDD (Binary
Decision Diagram) computation engine developed by TotalEnergies. ALBIZIA offers the advantage of running
accurate analytical computations and rapidly providing extensive information on the system under study.

1.2. Main window of the Fault Tree module

The main window is divided into several parts:

• Title bar: The title bar shows the names of the module and file being edited.
• Menu bar: The menu bar gives access to all the application's functions.
• Icon bar (shortcuts): The shortcut bar is an icon bar (horizontal) which gives faster access to the most common
functions.
• Tool bar: The tool bar (vertical) allows you to select the elements for modeling.
• Input zone: A maximum amount of space has been left for the graphical input zone for creating the model.
• Tree: A tree is between input zone and tool bar. It enables to walk through pages and groups of the document.
• Template: Templates are hidden behind the tree. They are grouped in two files following the save directory
(User or built-in directory).
• Set of tables: Tables are gathered in "hidden" tabs on the right.

1.3. Menus presentation

User Manual 6 / 133

1.3.1. File
The menu File contains the basics commands : open, close, save, print, etc.

The functionality New (default) opens a new document, which will be initialized from the default module's model.
You can change the default's model, see Section 12.1, “Document template”

The functionality New blank document creates a new blank document.

The functionality Open opens an existing document.

The functionality Save saves the current document into a file. The default proposed location for the backup is
{répertoire home de l'utilisateur}/GRIF/2021/Tree

The functionality Save as ... lets you save a copy of the file you are working on, with a different name or a different
location.

The Enregistrer sous ... (Confidentiel) action creates a new document which confidential gates (and their sub-
tree) are replaced by a basic event with the same probability (at end of mission).

The functionality Send by e-mail allows you to attach the current document to an e-mail and then to send it. The
configuration of the messaging tool is to be done in the application options Section 14.1, “Executables”

The functionality Close lets you close the current document. A window offers to save the file if changes have
been made.

The menu Document templates includes features related to document reuse and pre-configuration, see
Section 12.1, “Document template”.

User Manual 7 / 133

The menu Import a document contains all the import formats supported by the module.

The Export ... action lets your export the current document into an external format.

The print functions Page layout, Print and Save in RTF file are described in the section Section 13, “Printing”

The functionality Anonymize deletes all the comments and names filled in by the user. The document does not
contain any information helping to understand it.

The functionality Statistics of document allows to have some information about the document (number of pages,
number of groups, etc.).

The functionality Document properties allows you to edit the properties of the current document. The fields
include: name, creation date, creator, description, version, ... This function is described more specifically in the
section Section 3.16, “Document properties / Track change / Images management”

The functionality Files of the document includes files within the current document. These files can then be
exported in your reports. This feature is described more specifically in the section Section 3.18, “Files of the
documents”.

The functionality Compare 2 documents highlights the changes made between 2 versions of the same document.
This feature is described more specifically in the section Section 3.17, “Compare 2 documents”.

The menu section Recent files list recently opened files to access them faster.

The functionality Quit exits the application. Open documents will be closed.

User Manual 8 / 133

1.3.2. Edit

The menu Edition contains all the commands needed to edit the current model.

The functionalities Undo and Redo allow you to cancel or redo the last actions performed. The size of the history
of undoable actions are configurable in the application options see (Section 14.2, “Options”).

The functionalities Copy, Cut, Paste and Paste and renumber are described more specifically in this section
Section 3.1, “Copy / Paste / Renumber (without shortcut)”

The functionality Remove deletes selected graphic elements.

The functionality Hierarchical renumbering changes IDs / node numbers according to their position in the tree.

The functionalities Overall change ... and Selection change ... search and then replace names and identifiers of
the current document or selection. This feature is described more specifically in the section Section 3.3, “Overall
change” and Section 3.4, “Selection change”.

Actions Glue and UnGlue link or unlink graphical objects between them. This allows to fix the position of objects.
This feature is described more specifically in the section Section 3.10, “Gluing/Associating graphics”

The functionality Select all selects all the graphical elements of the page.

The functionality Clear selection deselects items in the current selection. The selection is then blank.

The functionality Select connected part selects all graphical elements connected to each other by a link. This
feature is described more specifically in the section Section 3.7, “Selecting connex (adjacent) parts”

The functionality Select sub-tree from a gate, selects the entire descending parts of the tree.

The functionality Select from node to root from a gate or event, selects the entire ascending parts of the tree.

User Manual 9 / 133

The menu Size of the commentary rectangle lets you configure the display of the selected comments or on the
whole document. This feature is described more specifically in the section Section 2.9.3, “Element size”

The menu Automatic layout gives access to different modes of graphical layouts. This layout can be configured
in the document options. See Section 14.3, “Graphics”

The functionality Properties edits the logical properties of the current selection.

1.3.3. Tools
The menu Tools contains all the commands needed to manage the current model (management of pages,
alignments, options ...).

The functionality New page : Create a new graphical page on the current document.

The functionality Page manager ... : Open a page manager on which you can rearrange the pages of the document.

The functionality Move to page ... : Move the current selection to another page or group in the document.

The functionality Increase page size : Increase the graphical input area of the current page.

User Manual 10 / 133

The functionality Decrease page size : Decrease the graphical input area of the current page.

The functionality Page size : Open a window to manually configure the size and zoom of the current page. This
feature is described more specifically in the section Section 3.8, “Zoom and page size”

The functionality Reset size of pages : All pages will be reset to factory format.

The functionality Refresh : Refresh the graphical objects in the current page.

The functionality Search for shortcuts : Opens a window listing the element's references and lead toward these
references. This feature is described more specifically in the section Section 2.5.3, “Search shorcuts”

The functionality Display logical tree : Displays the tree view without considering the pages and groups in which
the items are located.

The menu Align provides alignment functions for graphical objects. These features are described more specifically
in the section Section 3.5, “Alignment”.

The menu Align and distribute contains the same functions as in the menu Align. In addition, it is possible to
distribute, in the enclosing space, the elements of the selection.These features are described more specifically in
the section Section 3.5, “Alignment”.

The functionality Bring forward : Move the selected elements one layer forward.

The functionality Send backward : Move the selected elements one layer backward

The menu View toolbars lets you show or hide certain shortcut groups from the toolbar.

The functionality Display bar of opened documents : Displays in the lower part of the application, a shortcut
bar to access documents already opened in GRIF.

The functionality Document options : Opens a window to configure the document options. You have the
possibility to configure a very large number of GRIF-Workshop's features (cf. Section 14, “Options of GRIF -
Fault Tree” ). Some options only apply to the application and are accessible via the menu Application options,
and others are relative to the document being edited and are defined in the menu Document options. However,
to avoid having to redefine your options between each document, document options are also available in the
application options.
These options will then be applied to all newly created documents.
You can also save the current document settings as the default settings for the application. To do this, open the
window Application options, then the tabulation Options and finally check Save the options of the current
document as default options in the application.
You will find in this same panel the possibility to override the document options by the application options. To
do this, check The application manages the default options of the documents. Apply the default options to
the current document.

User Manual 11 / 133

The functionality Application options : Opens a window to configure the application options. This window is
described more specifically in the section Section 14, “Options of GRIF - Fault Tree”

The functionality Year length configuration (in hours) allows you to change the number of hours in a year. The
scope of this option is global to all GRIF modules.

The functionality Search page/group : Find and locate a group or document page.

The functionality Information about selection : Display a window based on the selected graphical elements. This
window gives additional information about the current selection.

1.3.3.1. View toolbars

The menu View toolbars lets you show or hide certain shortcut groups from the toolbar.

The check box Pages (select from pull down list) allows to show / hide the page shortcut bar

The check box Edit groups allows to show / hide the group shortcut bar

The check box Zoom allows to show / hide the shortcut bar for page zooms

The check box Input/Output allows to show / hide the file shortcut bar

The check box Undo/Redo allows to show / hide the command history shortcut bar

The check box Edit allows to show / hide the shortcut bar of the edit menu

The check box Computation allows to show / hide the configuration shortcut bar and start calculations

The check box Font allows to show / hide the text configuration shortcut bar

User Manual 12 / 133

The check box Align allows to show / hide the shortcut bar of alignment tools

1.3.4. Document
The menu Document gives access to all documents being modified or produced.

The functionality Next : Selects the next document

The functionality Previous : Selects the previous document

1.3.5. Data and Computations

The menu Data and computations is divided into two parts : data management (creation and management
of the different parameters) and the parameterization / launch of the calculations (calculation duration, sought
calculations ...).

Editing tables (new window) : Opens a new non-blocking window containing all the editing tables of the datas.

Edit Parameters : Opens a new non-blocking window containing the editing table of parameters.

Edit Events : Opens a new non-blocking window containing event's data. The event's settings are detailed here
Section 2.4.2, “Configuring the events”.

User Manual 13 / 133

Edit Gates : Opens a new non-blocking window containing gate's data. The gate's settings are detailed here
Section 2.4.1, “Configuring the gates”.

Edit CCF : Opens a new non-blocking window containing Common Cause Failure's data. The CCF's settings are
detailed here Section 6, “Help with common cause failures”.

Edit laws : Opens a new non-blocking window containing the editing table of laws used in the document. The
laws' settings are detailed here Section 7.2, “Description of the laws”.

Edit Degraded operations : Opens a new non-blocking window containing the editing table of degraded
operations.

Edit Attributes : Opens a new non-blocking window containing the editing table of attributes. The attributes'
settings are detailed here Attributes.

Edition of assumptions : Opens a new non-blocking window containing the editing table of assumptions. The
assumptions' settings are detailed here Section 3.19, “Hypothesis”.

The functionality Delete unused data : Cleans the document by deleting unused data. A window opens and
proposes to manually select the elements to delete.

The menu Parameters database groups all the functionalities concerning the connection of the application to
a specific parameters' database. For more details on the parameters databases, refer to Section 11, “Database of
parameters”.

The functionality Compute manager : Opens a non-blocking window to manage the calculations launched by the
application. For more details on the compute manager, refer to Section 9.6, “Compute manager”.

The functionality Invalidate the calculation cache : To optimize calculations, some calculations data are cached.
Invalidate calculation cache allows you to completely empty these data and ensure authentic results. In normal
use of the software, it is not necessary to use this function.

The functionality Let names and IDs be unique : Identifies and modifies duplicate data in the model. In normal
use of the software, it is not necessary to use this function.

The functionality Verify : Checks model data and displays errors.

The functionality Preprocessing of Markov graphs (not computed only) : Perform a pre-calculation on Markov
graphs that have never been computed or whose .jma have been modified since the last calculation. Pour plus
d'information sur les lois de Markov, se référer à Section 7.2.18, “MKR / Markov graph”.

The functionality Preprocessing of Markov graphs : Effectue un pré-calcul sur tous les graphes de Markov
utilisés dans les lois de type Modèle Markov. For more details on Markov laws, refer to Section 7.2.18, “MKR /
Markov graph”.

The functionality Set-up and start computation : Opens the calculation configuration window. This window is
detailed in Section 9.1.1, “Configuring the computations”.

The functionality Re-start computation : Restarts the calculations with the last configuration.

The functionality Display last results : Displays the result window of the last calculation performed. For more
details on the result window, refer to Section 9.3, “Tables and Panels to display results”.

The menu Batch computations includes the functionalities of multiple computations by variation of parameters.
For more details on batch computation, refer to Section 9.4, “Batch computation”.

The functionality Start Moca ... : Opens the configuration window for Moca computations. For more details on
Moca computations, refer to Section 9.2.1, “Configuring the computations”.

The functionality Re-start Moca with current settings : Restarts the computation with the last parameterization
of Moca computations.

User Manual 14 / 133

The functionality Compute target probability value for sub-tree : Calculates the probability objectives of events
based on the goal of the selected gate.

1.3.5.1. Parameters database

The menu Parameters database groups all the functionalities concerning the connection of the application to
a specific parameters' database. For more details on the parameters databases, refer to Section 11, “Database of
parameters”.

The functionality Connections ... : Opens the parameter connection's manager.

The functionality Update from database ... : Updates the settings of the current document parameters that are
connected to a database by updating their values. Opens a window to select the data to update.

The functionality Copy parameters from database ... : Imports from a parameter database a set of data in the
current document. Displays a database parameter table, the user can select the data to import into his document.

The functionality Rebuild links to the database : Attempts to reconnect parameter's settings of a document to
data from the database Opens a window that highlights parameters that can be reconnected.

1.3.5.2. Batch computations

The menu Batch computations includes the functionalities of multiple computations by variation of parameters.
For more details on batch computation, refer to Section 9.4, “Batch computation”.

The functionality Manual creation batch : Opens a window to create calculation batches. Each batch must be
configured by the user.

The functionality Automatic creation of batch (with parameter variation) : The user fills in the parameters to
be varied, the application generates the calculation batches by making all the combinations of the parameters.

1.3.6. Group
The menu Group concerns the capture and management of sub-models grouped into independent subsets.

The functionality Group : Puts the selected elements into a new group. A new group graphic object is created.
Selected elements are moved within the group.

User Manual 15 / 133

The functionality New group : Create a new empty group on the current page.

The functionality Name change : Edits the name of the selected group.

The functionality Picture change : Assigns or modifies the graphical rendering of the group, by adding an image.
The name of the group will be displayed below the image.

The functionality Ungroup : Removes the group and creates all the elements that the group used to contain.

The functionality Group sub-tree : Creates a reference gate and a group instead of the selected gate. The subtree
is moved within the group.

The functionality Edit group : Open the group page.

The functionality Quit group edition groupe : Go back to the parent page of the group.

1.3.7. ?
The menu ? combines several GRIF global configuration functions and provides access to the module's online help.

The functionality About ... : Opens an information window about the software version used.

The functionality Help ... : Provides access to the module's online help.

The menu Configuration groups together several configuration elements of GRIF.

The functionality Send errors logs : Sends an email to your reseller with the module's log files.

The functionality GRIF-Workshop update : Updates GRIF. This function detects the existence of a more recent
version of GRIF. If such a version exists, you will be offered to install it.

The functionality Français : Change the application language to French.

The functionality English : Change the application language to English.

1.3.7.1. Configuration

The menu Configuration groups together several configuration elements of GRIF.

The menu Licence groups the configuration functions of the license server.

The menu Associate GRIF files forces your operating system to associate the GRIF files and the different modules
that open them.

The menu Network configuration : Configures network access to update the system.

User Manual 16 / 133

1.3.7.1.1. License

The menu Licence groups the configuration functions of the license server.

The menu Hardware Licence (HL) configures USB license dongles.

The menu Software Licence (SL) configures license servers that do not require an USB dongle.

The functionality Configuration: Configures the access to the license server.

1.3.7.1.1.1. Hardware License (HL)

The menu Hardware Licence (HL) configures USB license dongles.

The functionality Generate c2v...: Generates a c2v (Client To Vendor) file. This file will be requested by your
reseller to create an update of your license.

The functionality Apply v2c...: Applies a v2c (Vendor To Client) file. This file will be returned by your reseller
to apply the update of your license.

1.3.7.1.1.2. Software License (SL)

The menu Software Licence (SL) configures license servers that do not require an USB dongle.

The functionality Generate fingerprint...: Generates a c2v (Client To Vendor) file. This file will be requested
by your reseller to create your license.

The functionality Generate c2v...: Generates a c2v (Client To Vendor) file. This file will be requested by your
reseller to create an update of your license.

The functionality Apply v2c...: Applies a v2c (Vendor To Client) file. This file will be returned by your reseller
to apply the update of your license.

1.3.7.1.2. Associate GRIF files

The menu Associate GRIF files forces your operating system to associate the GRIF files and the different modules
that open them.

The functionality For current user : Associates GRIF files to the current user

The functionality For all users : Associates GRIF files to every users. This operation requires administrator rights.

User Manual 17 / 133

1.4. Vertical toolbar
Each operating safety model has its own icons. All the graphical symbols for the fault trees are shown on the
vertical icon bar on the left of the data input screen.

The vertical toolbar contains the following items:

Selection tool Select the graphical objects in the input zone.

Group Add a group (sub-page) to the model.

Gate "AND" The output occurs only if all inputs occur.

Gate "OR" The output occurs if at least one of the input occurs.

Gate "K Out Of N" The output occurs if at least k of the N input occur (k < n).

Gate "NOR" The output occurs if none of the input occurs.

User Manual 18 / 133

 Gate "NAND" The output occurs if at least one of the input has not occurred.

Gate "XOR" The output occurs if one of the input occurs.

Gate "If/Then/Else" The output is worth the value of the event 'then' if the event 'if' occurs and is
worth the value of the event 'then' otherwise.

Gate "Negation" The output occurs if the input has not occurred. The exit logic state is the contrary
of the entry logic state.

Gate "Comment" Allow to inser a comment inside the model.

Basic event Event of the lowest level for which the probability of appearance or information of
reliability is available.

Elementary event Development of this event is achieved. It corresponds of the failure or error in a
system, component or element which could be detailed but for which an equivalent law is used.

To be developed event An event about which insufficient information is available, or which is of no

consequence. This event must be later developed.

"House" event Event which has to occur with certainty during the production or during the
maintenance. We can also define it as an event not - possibility, which we have to choose to put in 1
or in 0 before any processing of the tree. This type of event allows to have several variants of a tree
on a single drawing, by modifying the logic of the tree according to the value chosen by the user.
Link (one only) to create one connection (and only one) between an input (gate) and an output (gate
or event).

Links (many) to create connections between an input (gate) and an output (gate or event).

Identical transfer gate Used to create shortcut to another gate.

Repeated event Used to create shortcut to another event.

Dynamic field tool creates dynamic comments displaying the data in the model.

Comment tool creates static comments.

Line tool creates lines or arrows of different styles.

Rectangle tool creates rectangular zones of different colours. These zones can be anchored to the
page.

User Manual 19 / 133

 Polygon tool creates a zones with an polygon shape. These zones can be anchored to the page.

Circle tool creates circular zones of different colours. These zones can be anchored to the page.

Ellipse tool creates a zones with an ellipse shape. These zones can be anchored to the page.

Curve tool draws curves by selecting the computation results in the results base.

1.5. Data Editing Tables

1. Description of the Tables

To create or modify data (parameters, variables, etc.), tables are available in the Data and Computations menu
and in tabs at the right of the view. All the GRIF 2021 data tables operate in the same manner.

It is possible to edit all tables in another screen using Data and Computations - Editing tables (new
windows) menu.

The data editing table/panel is divided into 3 parts:

• The upper part consists of a toolbar;

• The main part containing the data table.
• The bottom part indicating what the selected data is used for. This table is available only if the given data can be
used by another data. The first column of this table indicates the name of these elements, the second indicates
their location in the document (page, group). A click on a line from this lower table will open the page where
the item is located and select it.

Here is an example illustrating the parameter table

Different actions are available depending on the type of data displayed. Below is a non-exhaustive list of actions
that can be found on the data tables.

Saves the table in a text file.

Import data from another Tree model or from CSV file.

Opens the column manager (cf. Section 1.2, “Column manager”).

Displays a panel for searching or filtering data (cf. Section 1.1, “Filter and sorting data”).

User Manual 20 / 133

 When the display selection button is pressed, a click in the table leads to the selection in the input
area.
Find and/or replace expression in the table .

Edit the selection.

Multiple modifications made to all the selected data.

Permit to merge data in a unique data.

Creates new data.

Create the number of data indicated by user.

Duplicate the selected data (ask a new name)

Deletes the selected data (one or many).

1.1. Filter and sorting data

The filter panel allows you to display only what is necessary in the data table.

It consists of a search part: the text entered is searched in all the cells of the table, only the lines whose text is
present are preserved; and an advanced filtering part allowing to consider finer criteria according to the different
fields of the data. It is possible to combine several filtering criteria, as below:

Select AND or OR to choose the type of association between each line (filter criterion). A line is a Boolean
expression divided into 3 parts:

1. the first is the column on which the filter is used;

2. the second is the comparator;
3. the third is the value to which the data will be compared.

If the Boolean expression is true, the data will be kept (displayed); otherwise the data will be masked. When the
filter is enabled its value is displayed between < and >.

The data in a column can be sorted by double clicking the header of this column. The first double click will sort
the data in ascending order (small triangle pointing upwards). The second double click on the same header will
sort the column in descending order (small triangle pointing downwards).

The choices that are made are kept on the current document. They will be reapplied when reopening your
document and do not affect other documents in the application.

1.2. Column manager

A table can contain many columns and to improve its readability it is possible to choose the columns that will be
displayed as well as their order. To do this, click on the Columns Manager button, the following window opens:

User Manual 21 / 133

You can choose the columns to be displayed by selecting (or deselecting) the corresponding check boxes. The
arrows on the right are used to move the columns up or down in the list to choose the order of the columns. The
Disable data sorting check box disables the data sorting. This improves the application's performance with very
complex models.

The choices that are made are kept on the current document. They will be reapplied when reopening your
document and do not affect other documents in the application.

1.3. Multiple edition

To modify data, simply double-click on the cell to modify. When several lines are selected (using the CTRL or
SHIFT keys) changes can be made to all the selected data by using Multiple changes. A window then opens to
allow you to make these changes.

Items which cannot be modified are greyed. The white lines indicate that the selected data does not have the same
value for the field in question. A new value can be entered which will be taken into account for all the selected
data. The lines with no background colour indicate that all the selected data has the same value for this field (in
this example the selected data is all "Float"); they can be changed to give a new value to all the selected data.

2. Table accessibility

As mentioned above, the tables can be accessed via the Data and Computations menu; in this case, each table
is displayed in a separate window.

To avoid having too many windows open, all the tables are grouped together in tabs on the right-hand side of the
application. This area can be hidden/displayed using the small arrows above the input zone.

User Manual 22 / 133

It is possible to choose the tables in this zone by right clicking on the tabs. A contextual menu appears, in which
the user can select the tables s/he wishes to display.

1.6. Tree view

To help users to walk through the document (pages, groups and sub-groups), a tree is available on the left of the
application. By default, every element is displayed, you can use Filter button in order to select elements you want
to display or not.

You can expand or collapse a node in a recursive way with a right click on the node.

As explained for tables on the right, you can "hide" the tree.

1.7. Template panel

Template panel located under the arborescence allows to visualize the various template saved.

A drag'n'drop allows to inser quickly the template in the model.

User Manual 23 / 133

2. Creating a fault tree

2.1. Entering the tree

2.1.1. Entering gates

To enter the different Gates, select the corresponding symbol on the vertical toolbar. A new element is then created
whenever you click right on the graphical entry area. Each of the model's gates has five parameters:

1. A number: These numbers are, with the type, the gates' true identifiers (those which will be used by the
computation engine). That is why, when you wish to change the numbers of certain gates, you must remember
that two gates cannot have an identical number. They are automatically incremented as new elements are
created.
2. A name: It is a parameter which is defined automatically and which cannot be modified by the user. The name
of each gate consists of its "type" followed by its "number" (e.g.: "And1" or "KofN3").
3. A "K out of N" integer: This field is only accessible in the case of K out of N gates. It allows you to choose
the value of K (K equals 1 by default).
4. A description: This field adds text inside the gate. This function makes the model more legible (by giving the
specific features of these elements).
5. A type: When a gate has been created, its type can be modified to one of the five types available in the drop-
down list.

2.1.2. Entering events

To enter the model's Events, select the corresponding symbol on the vertical toolbar. A new element is then created
whenever you click left on the graphical entry area. Each of the model's events has several parameters grouped
in 3 tabs:

1. General with the following information :

• A number: These numbers are, with the type, the events' true identifiers (those used by the computation
engine). That is why, when you wish to modify the numbers of certain events, you must remember that two
events cannot have an identical number. They are automatically incremented as new elements are created.
• A name: The default name assigned to the events is Evti for the "i" the element created. You are
recommended to replace this name by something more mnemonic to increase the model's legibility.

User Manual 24 / 133

 • A description: This field adds text inside the event. This function increases the model's legibility (by giving
the specific features of these elements).
• A law: This element is used to model the event's random aspect. You can choose from many laws which
must then be configured (cf. detailed description of the laws later on in this document).
• A type: When an event has been created, its type can be modified from the four types available in the drop-
down list.
2. Attributes tab to attach an attribute to the event.
3. Advanced to specified the event behavior.

2.1.3. Initiator event for frequency computation (UFI)

For each gate or event, you can set it initiator (with a right clik). This attribut must be seen from an "Event-Tree"
point of view. In an event-tree an initiator is an event that must happen befo barriers set the system in a safe mode.
In order to have a Top-event, iniator event must happen after barriers failure. Setting initiator attribut on and event
means that it must appear after the "non-initiator" events. This setting has an impact on UFI computation only.
There is no impact on Probability of Equivalent lambda.

2.1.4. Entering links

When the gates and events have been created, they must be interconnected to establish the tree's logic. There are
two possible types of connections: "gate -> gate" and "gate -> event" connections. To make a connection, proceed
as follows:

1. Click the corresponding icon on the vertical toolbar.

2. Select the start gate by a click left on the specific zone (a dot for "AND" gates, a cross for "OR" gates, etc.)
and keep the button pressed.
3. Move the mouse to the element to be connected.

User Manual 25 / 133

4. Release the mouse button.

The above icon only allows a single link to be created at a time. If you wish to create several links in
succession without having to reselect the link creation icon each time, use the icon shown below: Links
(several).

2.1.5. NOT gate

It is a very specific gate which inverts the logic of the subtree which is downstream of it.

To insert a "Negation" in a tree, proceed as follows:

• change the type of an existing gate by using the drop down list;
• OR create a new a new gate with the type "Negation":
1. Click left on the corresponding icon on the vertical toolbar.
2. A new element will then be created whenever you click left on the graphical entry area.
3. You then just have to configure and connect the "Negation" like a conventional gate: link the top part (above
the circle) to the bottom part of a gate and link the bottom part (below the circle) to the top part of an event
or gate.

2.2. Entering Comments

To add a comment anywhere on the model, simply click on the pencil icon and position the cursor in a graphical
entry zone. The Comment dialog box opens and you can then enter your comment.

User Manual 26 / 133

 The "%" sign is a special character and you have to type it twice for a single "%" to be displayed.

2.3. Dynamic fields

It may be useful to observe the change in the different parameters of the model. It is also useful to see a result next
to its corresponding system. To do this, use dynamic fields by selecting the corresponding icon on the vertical
tool bar:

The dynamic fields are a type of "improved comments". They can be used not only to enter words or phrases but
also to insert model values or results.

If you want to display information about a data of the model, you must use the following syntax:

$data.'type of data'.'field used o search data'('value that the field must match).'information you want to display
for the selected data'

We can analyze the above windows as follows: I am looking for a "parameter" which "name" is 'Capa_Max", and
I want to display its "value". When you type the first letters, a completion system helps to type script without error.

Button in right permits to enter complete expression but select what you want to appear.

If you want to display a result of the result-bank, the syntax is the following:

User Manual 27 / 133

$result.bank('path in the bank').target('target result').'what you want to display'.'at what time'

We can analyze the next picture as follows: I am looking for a result which path in the bank is "default-Moca", I
want results for "TS3 for 'available' valriable" and I want its value for the "last" time. If last is replaced by time(10)
we obtain value at t=10.

You can also display a summary of result. Replace 'what you want to display' by summary. In this case, summary
is the last word of this script.

2.4. Configuring the elements

All the graphical elements can normally be edited with a double-click on them or using the Edit - Properties
menu, or using the shortcut Alt + Enter .

2.4.1. Configuring the gates

When you click right on a gate, you can modify any parameter:

• change the number ;

• change the name , the automatic checkbox generates an automatic name made of the base name and the ID/
Number ;

• specify the value of K if the gate is a "K out of N" type;

• read and/or modify the description part;

• modify the type of gate to one of the five types available in the drop-down list:
– "OR" gate: an "OR" type logic gate is applied to the elements connected downstream.
– "AND" gate: an "AND" type logic is applied to the elements connected downstream.
– "K of N": a "K of N" type logic is applied to the elements connected upstream.

User Manual 28 / 133

 – "Comment" gate: this gate has no effect from the logic viewpoint and is only used to comment on the branch
where it is located.
– "NOT" gate: cf. above.

2.4.2. Configuring the events

When you click right on a gate, you can modify any parameter (except the name):

Configuration is made with 3 different tabs:

• General: User chooses the law, reliability data and type of event.

– to change the number ;

– change the name , the automatic checkbox generates an automatic name made of the base name and the
ID/Number ;

– to read and/or modify the description part ;

– to read and/or modify the law governing the event.

Apply a factor to apply a modifier factor to the law.In this case, unavailability is equal to factor x U(t).

User Manual 29 / 133

 – to modify the type to one of the four available types in the drop-down list:
Elementary event;
Basic event;
To be developed event;
"Home" event.

The names of these events simply have a "graphical" impact on the tree structure. There is no impact on the
logic function which will be generated to perform the computations. The aim is simply to simplify re(reading)
the fault tree

• Attributes: to attach an attribute to the event.

User Manual 30 / 133

• Advanced

– Allocation Probability allocated by user for the event.

– Behavior to affect a behavior To force possibly its value of exit (0 or 1)

Parameters for the law part are set in two stages:

1. Chose the law from all the available laws in the drop-down list located in the upper section. Many laws are
available and you can find the meaning for each law under Section 7.2, “Description of the laws”.

2. Set the parameters for the law in the lower part of the window. For each parameter, a numerical value,
a parameter name or an expression comprising operators '+','-','*' and '/' can be entered. All the available
parameters can be accessed by pressing the "down arrow"" key on the keyboard. . All the parameters that you
can type are displayed when you press the "down arrow" key. When letters are entered, a drop-down menu
gives suggestions to complete the name from among the parameters that correspond to the characters entered.

If the user needs to factor in uncertainties, these can be introduced on each of the parameters using the law
choice and the corresponding parameters (see detailed description of uncertainty calculations on parameters
further down). Uncertainties can be accessed via the ... button located to the right of each parameter.

User Manual 31 / 133

 It is advisable to enter the uncertainty in the parameters as described in Section 7.3.9, “Consideration
of the uncertainties”

2.5. Using shortcuts

2.5.1. Identical Transfer Gates (or Shortcuts on gates)

The concept of a shortcut (or repeated element) was introduced in the Fault Tree module for four main reasons:

• To link together portions of the model;

• To avoid graphically complex model, and keep readability;
• To simplify the use of the Group function (cf. below);
• To highlight what is essential and what is not.

Let a fault tree contain three base events, one "OR" gate (critical event) and one "AND" gate.

The aim here is to create a shortcut to the gate (identical trasfert gate) called "And2" to be able to dissociate the
"And2" subtree from the main tree. Proceed as follows:

1. Delete the existing link between gate "Or1" and gate "And2".

User Manual 32 / 133

2. Click left on the Transfert Gate of tool-bar then click on "And2" Gate.

3. Connect the shortcut created in this manner to gate "Or1".

The name of the original gate and the page number where the original gate is located are shown beside the shortcut
to gate "And2".

Although linked from the "computational logic" viewpoint, the two trees are now totally graphically independent.
They can now be placed on different pages or in different groups (cf. later on in this document).

User Manual 33 / 133

2.5.2. Repeated events (or Shortcuts on events)
From the logic viewpoint an event can have an "impact" on several "branches" of the same tree. To correctly
model this case, this event must be duplicated. To do this, select the corresponding icon on the vertical toolbar,
then click the event to be duplicated:

The event which has just been duplicated is now marked in dark grey whereas the duplicated event is shown in
light grey. The name and number of the original event's page are shown beside the shortcut.

The repeated event must now be inserted in the model, given that at each instant its state will be equal to that
of the original event.

Obviously, if the original event is deleted then the duplicated event is also deleted.

2.5.3. Search shorcuts

User can navigate between an element's different shortcuts, using Search shorcuts. This function is available in
the contextual menu (with a right click on the element) or in the application menu Search shorcuts.

A window opens and displays the list of shortcuts.

Clicking on a shortcut automatically positions the view on this shortcut. You can return to the original element
by clicking on its name at the top of the window.

In the shortcut contextual menu obtained with a right click, it is possible to swich the shortcut and its
source.

User Manual 34 / 133

 In the shortcut contextual menu obtained with a right click on a gate, it is possible to ungroup, in a simple
or recursive way. The recursive unbundling will ungroup the subtree and all of its shortcut which have
their sources in other localisations, which can be useful for the export of the tree for example.

2.6. Cloning
The action "Clone" will clone the selected gate, with its tree. There is two actions of cloning available:

• The first action allows you to do a complete cloning of the tree, which means all the gates and all the events
will be duplicated.

• The second action allows you to do a partial cloning of the tree, which means all the gates will be duplicated,
but the events will remain the same. The new created tree will have report of events instead of new events.

Only the tree's structure will be cloned: the attributes, parameters, and anything which can be attached to an event
will remain the same.

2.7. Components/Systems
The components are a set of events, while the systems are composed of multiples components.

User Manual 35 / 133

2.7.1. Create a component/system

The components/systems can be created in the table Components/Systems, but from a set of events selected in
the graphical view, it is possible to directly:

• Create a new component from these events.

• Add the selected events to a component.

• Remove the set of event from any component.

Or from the event's table :

2.7.2. Uses of the components/systems

Their main uses are to observe the impact of a component/system in the result of a cuts computation, and to identify
which components can be at risk. When clicking on the button Set-up and start computation, in the tab Minimal

User Manual 36 / 133

cut sets, it is possible to select Do a cut sets computation with components/systems to have in the result which
components/systems are at risk.

2.8. Page and group management

The use of shortcuts allowed us to obtain two Fault Tree which have no graphical link between them. They
communicate only by shortcuts. This can be used, for example, to place each subpart on a different page:

User Manual 37 / 133

1. Create a new page by clicking the corresponding icon in the icon bar (or use menu Tools - New Page). A page
number 2 is thus created.
2. Return to page 1 by selecting the page using the page selector in the ideographic command bar (or use menu
Tools - Page manager).
3. Select the part to be moved.
4. Open menu Tools - Change page.
5. Select page 2 and click OK. The part selected is transferred to page 2 but it continues to communicate with
page 1 via the shortcuts.

For large models the division method described above is very useful.

Another possibility for entering large Fault Tree is to use the Group concept. This is made possible by the
shortcuts and the fact that the data is global for a document. This allows quite separate subparts to be created:

1. Select a subpart.
2. Use menu Group - Group. A dialogue box then opens asking for the name to be given to the group being
created.
3. Enter the desired name and click OK (e.g.: "System 1"). The group is created: the subnet is replaced by a
rectangle assigned with the chosen name.

You can also create an empty group with Group - New Group menu or group tool in the left toolbar.

With a right click on the group, it is possible to view inside the group if Overview of the contents is
checked.

Each group can then be edited, renamed or ungrouped using the commands in the Group menu. The group can
also be edited with a click right or using the "cursor down arrow" on the left of the page manager. In Edit mode,
the submodel can then be modified as you wish. When the modification is terminated you return to the previous
figure by exiting group editing by menu Group - Quit Group Edition, or using the "cursor up arrow" on the left
of the page manager. It's also possible to choose a picture for a group by using Group - Change Picture menu.

Groups can be grouped recursively.

User Manual 38 / 133

 La combinaison CTRL + F permet d'effectuer une recherche dans les groupes. Une fois la liste des
différents groupes affichée, il est possible de les filtrer ou d'effectuer une recherche dessus.

2.9. Shaping

2.9.1. Global shaping

In the document (or application) option it is possible to modify the shaping of the fault tree elements. These options
allow to modify the police, the color, the background and the type of border for commentaries and for information.

Events shaped Gates shaped

All events will have this shaping: All gates will have this shaping:

User Manual 39 / 133

 At the bottom of the window remark height and remark width allows to define the rectangle size for
the gates and the events.

2.9.2. Shaping element by element

It is also possible to differentiate the shaping of elements one by one. In this case, it is possible to use the tool
bar Police to shape the comment:

To apply this shaping it is necessary to select 1 or several elements and to change the style.

These functions (with the information shaping) are also accessible using the contextual menu.

2.9.3. Element size

The size of the rectangles can be also adjusted thanks to the contextual menu

This menu allows set up automatically the fault tree according to the size of comments:

• Reset to default size : accessible by F9, allow to back to the default size it means the one define in the document
options.
• Adjust to text size : accessible by F11, each rectangle will have a size adapted to its text.
• Adjust to the size of the wider and higher text : accessible by F12. In this case all the rectangles will have
the same size it means the size given by the element with the wider and higher text.
• Hide commentaries : this option allows to hide the rectangle of comments.

User Manual 40 / 133

• Show commentaries : this option allows to show the rectangle of comments.

User Manual 41 / 133

3. Data Entry Aids
To simplify model creation the Fault Tree module has different data entry aids to automate time-consuming
operations.

3.1. Copy / Paste / Renumber (without shortcut)

To assist with the entry of the repeated parts of the Fault Tree "Copy / Paste and Renumber" mechanisms have
been provided. This operation is carried out in 6 steps:

1. Select the part to be copied.

2. Click the Copy icon, or use menu Edit - Copy or the shortcut Ctrl + C.
3. Click the Paste and Renumber icon, or use menu Edit - Paste and Renumber or the shortcut Ctrl + R.
4. A window appears where you choose the way to rename the elements.

Automatic names choose allows to add a number of the name of the place.

5. The previously selected part is copied and the copy is selected.

6. Move the copy to the desired location.

We then obtain the tree shown in the figure below:

• Or1 and And2 gates from original tree are become Or3 and And4 for the copy;
• Evt1, Evt2 and Evt3 events from original tree are become Evt4, Evt5 and Evt6 for the copy.

When copying to a new document, any data conflicts are handled in the following window:

User Manual 42 / 133

This window shows all the data which has the same name in the source document and the destination document.
There are three choices:

1. Use data of destination document, this will replace the occurrences of the data in the source document by the
data with the same name in the destination document.
2. Create a copy for each data in conflict, this will replace the occurrences of the data in the source document by
a copy with a name with the suffix "copy".
3. Manually manage conflict, this allows you to choose whether you use the existing data or not, depending on the
data. You can also specify the name of the copy by double clicking on the box in the "destination document"
column. The names in this column are normally masked when the Use existing check box is selected, since it
is the data which is already in the destination document which will be used.

If the selected part is made up with a shortcut, the shortcut refers always at the same source.

3.2. Ordinary Copy/Paste

In addition to the "Copy / Paste and Renumber" command there is an ordinary "Copy / Paste" function. It is used
to make a single copy without renumbering. We thus obtain double elements which, from a formal viewpoint, is
incorrect but which must be temporarily tolerated to simplify data entry.

Where possible, the "Copy / Paste and Renumber" function must be used in preference to the simple "Copy / Paste"
function to minimise the risk of errors. But when it is used you must take the necessary precautions to re-establish
the correct numbering to eliminate the duplicates.

3.3. Overall change

When creating the Fault Tree it may be necessary to change a large part of the elements in the models: changing
the names, numbers, etc. The "Replace all" function in the Edit menu allows you to perform overall changes:

• Use the Edit / Overall changes function.

• Choose the type of elements to be modified among available tabs.

User Manual 43 / 133

• The "Find / Replace" part changes a character string present in one or more variable labels, place labels or
transition labels. It is replaced by the string entered in the "Replace" part.

• The "Renumber" part only concerns the places. It is used to change place numbers. You indicate a Start number
then specify a constant Step, or Add a constant value to the current numbers.

• Click OK to return to the chart. The changes are validated.

The name changes and renumbering can be done manually if the necessary precautions are taken (avoiding
duplicates, etc.). You click the Future number or Future name column and enter the change. Do not
forget to validate it with the "ENTER" key.

3.4. Selection change

The "Replace selection" function is equivalent to a "Replace all" but only applied to the selected elements.

Only the selected gates and events can be replaced.

The "Replace selection" function does not allow the model's parameters to be replaced.

3.4.1. Gates graphical editing

By default, gates have a white background, a black border and text is written in black.

Using the shortcut bar or by a right click on an gate, you may edit the text apperance, the background color and
borders color of the selected gate:

• Select the gate you want to edit.

• You are now able to use the text configuration shortcut bar:
– From the tool bar.

User Manual 44 / 133

 – Right click on the gate and then display settings.

Bellow an edited gate:

3.5. Alignment
To improve the legibility of the model the selected elements can be aligned vertically or horizontally. To do this,
use the Align command in the Tools menu.

The following figure shows how the command works. For example, to align selected places and transitions
vertically, proceed as follows:

1. Select the elements (places, transitions, comments, etc.) to be aligned;

2. Go into the Tools menu and select the Align function;

3. Choose the type of alignment: Align center;

4. Click left on the mouse.

User Manual 45 / 133

Similarly, to align elements horizontally select the type Align middle which aligns the ordinates while keeping
the abscissa constant. The principle is the same as that described above.

3.6. Multiple selection

It may sometimes be useful to select several elements located in the four corners of the input zone. To simplify
this type of selection click on each of the desired elements one by one while holding down the Shift key on the
keyboard.

3.7. Selecting connex (adjacent) parts

It is sometimes difficult to select an additional part of a model. To simplify the selection process, select a graphical
element then use menu Select connex part in the Edit menu. The additional part can be selected directly by
clicking on the element while keeping the Control button pressed.

3.8. Zoom and page size

When creating a model, if the page size is not big enough, it can be changed using the menus: Increase page
size (Control+Keypad +), Reduce page size (Control+Keypad -), Page size (Control+Keypad /) under the
Tools menu.

The Page size menu allows the user to edit the page dimensions directly.

Page zooms can be modified either by using the toolbar menu:

User Manual 46 / 133

Or by selecting the display and using Control+mouse wheel scroll up to zoom or Control+mouse wheel scroll
down to zoom out.

The padlock on the toolbar is used to apply the zoom to the current page or to all pages in the document.

The zoom applies to all pages in the document.

The zoom is applied only to the current page.

Note that if an element is selected on the page, the zoom will centre the page on that element.

3.9. Cross hair

To be able to create an ordered and legible model quickly, the cross hair can be used to align the different elements
with each other (but less accurately than the Align function in the Tools menu). The cross hair is enabled (or
disabled) in the Graphics tab of the Option menu.

The following picture show how to quickly align two elements of the model.

In order to align horizontally, select Align au middle which align keeping constant abscissa.

3.10. Gluing/Associating graphics

When objects are where you want, you can glue a set of objects by right-clicking and selecting Glue. This command
creates a group (a graphical one, not a hierarchical one) with selected objects, so that moving one moves the others.

A double click on an element in the glue group opens the properties window of the element.

3.11. Line
To be able to draw a line, polyline or arrow, the Line can be used. Draw the line and edit properties of line to
make an arrow.

User Manual 47 / 133

3.12. Table Cleaning
Data may not be used anymore, it can be used useful to delete every unused data. To facilitate removal, use Data
and Computations / Unused data deletion menu.

This window displays unused data. Select data you really want to delete and click OK.

3.13. Edit laws

Data and computations / Edit laws allows you to work on all the laws used by the events.

User Manual 48 / 133

All the events are listed with a detail of the law and its parameters, this table increases the readability on the
realized model. For more details of the use of the laws and the parameters of law, you can refer to the section (cf.
Section 7.2, “Description of the laws”).

The modification of the laws or a parameters used by several laws can be made easier using multiple changes.

allow to hide columns that are not editable for the laws and to display columns that are editable.

3.14. Events import

It is possible to import directly events from:

• Another Tree module file;

• A dag file;
• A CSV file;

• or from clipboard.

These functionalities are accessible since the events tab using the icon Import events :

3.15. Event insertion from the event tab

Icon allows to insert an event into the current page.

User Manual 49 / 133

• If the event is not linked to a tree, the event is moved in the current page.
• If the event is yet linked to a tree, a shortcut is created in the current page.

To use this fonction, it is recommended to deselect .

3.16. Document properties / Track change / Images management

File - Document properties menu enable to save information about document: name, version, comment, ... These
information are available in General tab.

Modification tab allows to save A history of the modifications.

There are two different ways to save modifications:

• At each saving by checking: Modification track when saving dans Tools - Document (or Application)
options .

User Manual 50 / 133

•
When the user wants directly in Modification tab of the properties using the button

Images may be very useful to represent sub-system. GRIF 2021 enables to save images that can be used in different
parts of software (groups, prototypes, ...). Images management is made in Images tab.

User Manual 51 / 133

To add a new picture into document, use icon. A double click in File column enables to select a picture (jpg,
gif or png). A double click in Description column enables to give a name or a description to selected image.

Once in document, picture can be linked to a groupe with Group - Picture change menu.

Images are saved inside document, pay attention to picture size. Because images are inside document, you have
to re-add picture if picture is modified erternaly.

User Manual 52 / 133

3.17. Compare 2 documents
This function is accessible using File / Compare 2 documents. The following window appears:

Icon enables loading of the files to be compared.

Click on to launch the comparison.

Difference can be sorted using 2 keys: internal or external

• Internal key enumerates the differences according to internal elements of the model for example identifier,
creation index, etc...

User Manual 53 / 133

• External key differentiates elements according to the names of the elements of the model.

Colour signification is:

• : element is added;
• : element is modified;
• : element is deleted.

3.18. Files of the documents

It is possible to associate external file using File - Files of the document menu.

The following icons allow to:

• reload files;
• open files;
• open directory where file is saved.

User Manual 54 / 133

3.19. Hypothesis
In the data table, in Hypothesis tab, it is possible to follow-up and track the studies hypothesis.

This table allows to take into account the study hypothesis and add file or date to indicate that this hypothesis
is taken into account.

User Manual 55 / 133

4. The parameters
It is possible to create constants which can be booleans, integers or reals. These parameters can then be used for
the configuration of different elements of the model (laws, events, transitions, ...)

4.1. Creation
The tab Parameters allows the user to define his parameters.

The toolbar enables to do basic operations of the data tables(Section 1, “Description of the Tables”). The button
"New" opens the window to create a parameter :

A parameter has a name, a definition domain (Real, Boolean, Integer), a value and a dimension (Failure rate,
probability, time, factor, ...) which allow to specify the parameter. This typing is at this moment informative.

User Manual 56 / 133

Others additional fields are available in the parameters' table.

Unit allows to define an unit of the parameter

Uncertainties Activate allows to define the parameter as an uncertainty law
uncertainty
Law allows to define the uncertainty law. The law is editable and taken into account
only if Activate uncertainty is selected in the parameter.
The uncertainties laws are detailed here Section 7.3, “Uncertainties on the
parameters”
Macro if the parameter is defined by an uncertainty law, and if two events use this same
parameter, then the user can choose to use the same uncertainty value for the two
events, (Macro unselected) or values distinctly computed (Macro selected).
Add-On allows to define the parameter by a GRIF add-on

Tree is delivered by default with 2 add-ons for the parameters :

Parameters database : is an add-on which allows the user to get the data of his
parameter in a database or in a CSV or Excel file. This database is more detailed
in this section Section 11, “Database of parameters”.

Beta (61508) : is an add-on which allows the user to calculate the value of his
parameter (β) from a set of questions defined by the IEC 61508-6 Table D.1
standard - for the captors and finals elements.
Add-on details gives a synthesis of the data defined by the add-on. A double-click on the cell
allows the user to modify its definition.
Parameters Database Displays the database name containing the parameter.
database Identifier Displays the identifier of the data in the database.
Update Displays the date of the last update of the parameter from the database.
Beta (61508) MooN Define the configuration of the system (in functional logic) to use to calculate
the beta.
Beta Displays a button allowing to modify the choices made in the Table D.1 of the
standard IEC 61508-6

User Manual 57 / 133

5. Attributes

5.1. Creation
The attribute tab allows the user to create attributes that are used to qualify elements defined on system.

The attribute properties are the following ones:

• name;
• domain ;
• default value;
• type of data: to choose where apply the attribute;
• constraint.

The domain type can be of the following values:

• boolean: This kind of attribute is a boolean;

• integer: This kind of attribute is used to affect an integer value;
• float: This kind of attribute is used to affect a float value;
• string: This kind of attribute is used to affect a free text.

In Constraint field, user can enter a constraint on the attribute to ensure the proper use of the attribute in the model.

In addition, the attributes of float or integer type have a Constraint type Enumerate or Interval.

5.2. Use of the attributes

In a Fault tree, it is possible to associate attributes on events:

User Manual 58 / 133

• in Events tab:

• in Attributes tab in the event:

User Manual 59 / 133

If attributes are defined, they are specified also in the products details:

User Manual 60 / 133

6. Help with common cause failures
To facilitate the creation of model, the Fault Tree module allows the creation of CCF(Common Cause Failure), and
to link a logical entity(Event, Block) to one or more common cause failures. CCF are available in the data table.
There is no graphical entity associated with CCF. The logical entity associated with an active CCF are graphically
marked by a yellow flash:

6.1. Creating a CCF

The creation of a new CCF is possible in different ways:

1. click Add button on table data,

2. Use the contextual menu on logical entities: CCF - Add new CCF

6.2. Editing a CCF

You can edit the properties of a CCF in different ways:

1. Double-Click on a cell of the CCF table, and edit.

2.
Use the contextual menu on a table raw and click on

User Manual 61 / 133

 A configuration window opens:

Several types of laws are now possible for a CCF:

1. The beta-total law: Beta parameter is applied to the laws of concerned components.

Singularities:
a. A component can be concerned by several CCF using beta-total law.
b. The sum of the beta set on the CCF must be strictly less than 1 for a component.
c. The supported laws for a component are exponential, constant and test-periodic.
2. The beta (Standard) law: The laws of the components are replaced by the law defined by the CCF.

Singularities:
a. A component must be linked to only one CCF using beta law.
b. Laws of components are no longer used.
c. All laws are supported.
3. The Multiple Greek letter model: apply for a group of n events.

For a group of n events the aim is to have n - 1 factors ρ2, ... ρn-1. ρk denotes the conditional probability that k
components of the group fail given that k-1 failed with 2 ≤ k ≤ n.

User Manual 62 / 133

4. The Alpha factor model (NUREG/CR-5485): αk is the probability that when a common cause basic event occurs
in a common cause group of size m, it involves the failure of k components.

2 different testing mode are implemented:

• Staggered testing (components tested sequentially)

• Non-staggered testing (all components tested simultaneously)

5. The Phi factor: with a manual definition of the coefficients.

The sum of the Φk's should equal 1.

6. BFR(Binomial Failure Rate): This method splits the faire rate (Atwood - 1986) in 3 different parts:
• intrinsic failure rate;
• lethale failure rate (w);
• no-lethale failure rate (only some components are impacted with a p probability).

According to Nureg/CR-5485:

3 different implementations are included each given similar probability but different minimal cut sets. User
chooses the implementation in the calculation options:

• Atwood 1986 Definition:Events are generated according to Atwood definition (Intrinsic| Lethale | (Non-
lethale & constant p)).
• NUREG/CR-5485 with concat function: Events are generated in order to have results that are comparable
with NUREG/CR-5485. Extrem case are concatenate with concat function:
– individual failure with nonlethal failure of one component;
– lethal failure with nonlethal failure of all components.
• NUREG/CR-5485 without concat fonction: Events are generated in order to have results that are comparable
with NUREG/CR-5485. Extrem case are concatenate with OR gate:
– individual failure with nonlethal failure of one component;
– lethal failure with nonlethal failure of all components.
7. BFR ISOTR12489 is a variant of the BFR CCF, from the standard ISO/TR 12489:2013.

In this CCF, the user has to enter its failure rate, common to the lethale part and non-lethale part, as well as
the Beta (lethale and non-lethale).
User Manual 63 / 133
 The probability that the failure, within the non-lethale Beta, is independante (corresponding to the p in the BFR
ccf) is given by this estimation figuring on the norme :

This CCF can not have less than four impacted elements.
8. BFR ISOTR12489 TOTAL is a variant of the BFR ISOTR12489.

Its functionning is the same as the BFR ISOTR12489 CCF. The only difference is there is no law to enter : it
will directly create its own failure rate, from the laws of its impacted events, like the Beta TOTAL CCF. Its
impacted numbers must be higher than 4 here too.

All parameters can be edited directly using the CFF table and a color can be associated of each CCF.

User Manual 64 / 133

7. Laws and uncertainties
7.1. Setting
Several laws are available in the Fault Tree module. Each of these laws has one or more corresponding parameters.
Here is a list of the different "types" possible:

• Probability: value between 0 and 1 inclusive.

• Rate: value greater than or equal to corresponding to a failure rate.
• Duration: value greater than or equal to 0 corresponding to a duration or to a time.
• Factor: value strictly greater than 0.
• NatInt: integer value greater than or equal to 0.
• Boolean: can take a value of 0 or 1 corresponding to an option parameter.
• Other: any value.

In the remainder of this chapter, the parameter "types" will be specified for each law.

By default, unit used in this module is the hour. it is possible to change the unit in Document options

In this case, the unit can be specified in the laws parameters:

This option can be used with nammed parameters. In this case, unit is linked with the prameter when it creates
and depends of the dimension choosen by the user.

User Manual 65 / 133

7.2. Description of the laws
A modifier factor can be applied in all the lawx by checking Apply modification factor on laws in
document options.

Once the option selected, a field appears in the events to inform the factor:

In this case, the law is defined by:

7.2.1. UNDEF / Undefined

This law used as default law indicates as user, with a an error message in the computation launching, that default
law was not changed.

7.2.2. CST/ Constant law

This law has two parameters: the probability q and the inconditional failure rate w of the event. Whatever the time,
the probability of the component failing is constant.

Parameter:

• q (Probability)
• w (Inconditional failure rate)

The law is defined as follows:

This law generally corresponds to the case where the only failure considered for the components is that of a refusal
to change state (e.g.: Fails to start/stop, etc.).

7.2.3. EXP / Exponential law

This law only has a one parameter: the component's failure rate (supposed to be constant over time). It describes
the time interval before the first failure for a non-repairable component.

Parameters:

User Manual 66 / 133

• Lambda (Rate) = failure rate

The law is defined as follows:

This law is widely used since it is almost the only one to make it possible to obtain analytical results. In addition,
it describes the lifetime of a non-repairable component very well (at least when there are a large number of
components) when the component is no longer young.

7.2.4. EXPD / Dormant exponantial

This law is used to model the dormant events in a more precise way than with a simple dormant law. It has three
parameters: the failure rate of thecomponent (supposed constant during the time), the test periodicity and the
mission time. This last parameter is not seizes by the user. It corresponds to the last wanted calculation.

Parameters:

• Lambda (Rate) = failure rate

• Tau (Duration) = test period (time interval between two consecutive tests)
• Tmax (Time) = mission time (i.e. t maximum for all t to calculate) This parameter is automaticcally generated
according to the last computation time.

The law is defined as follows:

Results can be different when step by step calculation is made due to the fact that mission time is the
maximum time calculation).

7.2.5. IND / Unavailability law

This law describes the behaviour of a component (repairable or not), with (or without) failure to start, using
exponential expressions. It generalises the exponential law with the Lambda parameter (failure rate).

Parameters:

• Gamma (Probability) = probability of initial start failure (at t = 0)

• Lambda (Rate) = failure rate
• Mu (Rate) = repair rate

The law is defined as follows:

The Gamma and Mu parameters are optional. Depending on the case, they can be zero.

• If the component is not repairable, set Mu to zero.

• If the component cannot fail to start, set Gamma to zero.

The failure to start is only taken into account at t = 0.

User Manual 67 / 133

7.2.6. WBL / Weibull
This law has three parameters: alpha, beta and t0. It describes the behaviour of a component which is not repairable
and which does not fail to start. Its specific feature is that it takes account of the component's young and old periods.

Parameters:

• Alpha (Time) = scale parameter

• Beta Factor) = shape parameter
• T0 (Time) = location parameter

The law is defined as follows:

The significance of this law is that new distributions can be tested by varying the beta factor:

• If Beta is less than 1, the failure rate decreases and the law then allows the period when the component is young
to be taken into account.
• If Beta is greater than 1, the failure rate increases and the law then allows the component's ageing period to
be taken into account.
• If Beta is equal to 1, the Weibull law is equivalent to the exponential law.

7.2.7. WBP / Weibull periodic

This law follows the same logic as the classic Weibull law. It also makes it possible to take into account exclusively
periodic preventive maintenance.

Parameters:

• Age at t=0 (Time) = Virtual age of the component at the initial time.
• Scale parameter (η) (Time) = Failure rate scale parameter
• Shape parameter (β) (Factor) = Failure rate shape parameter
• T0 (Time) = First date of preventive maintenance
• Maintenance period (T1) (Duration) = Duration between two preventive maintenance
• Efficiency (α) (Factor) = Preventive maintenance efficiency (age reduction factor)
• ARA model (0 or 1) = Age reduction model:
– 0 : To use an ARA∞ model Following preventive maintenance (with or without induced corrective
maintenance), the age of the component is reduced by a factor α.
– 1 : To use an ARA1 model Following preventive maintenance (with or without induced corrective
maintenance), the age of the component taken since the last preventive maintenance is reduced by a factor α.

The definition of the law is as follows:

Either (δ) = "age reduction" parameter of the failure rate (in time units) calculated according to the specified ARA
model.

General assumptions of the age reduction model:

• No failure is present at the initial time.

• Faults are only detected during preventive maintenance

User Manual 68 / 133

• All failures are detected at each preventive maintenance
• The first preventive maintenance is carried out at T0
• From T0, preventive maintenance is carried out periodically, depending on the period T1
• The duration of preventive maintenance is negligible.
• If a fault is detected during preventive maintenance, it is repaired immediately (the duration of corrective
maintenance induced is negligible).

7.2.8. WBD / Weibull with detected failures

Model whose failure follows a classical Weibull law and whose repair begins as soon as the failure appears and
follows an exponential law with parameter Mu.

Parameters:

• Age at t=0 (Time) = Virtual age of the component at the initial time.
• Scale parameter (η) (Time) = Failure rate scale parameter
• Shape parameter (β) (Factor) = Failure rate shape parameter
• Mu = Repair rate
• Coefficient applicable to the failure rate (Factor) = Given a coefficient x, multiply the scale parameter by
x ^ (- 1 / beta))

General assumptions :

• No failure is present at the initial time.

• All faults are detected online (i.e. immediately).
• Repairs begin as soon as faults appear.
• Repairs cause downtime.
• There are no other causes of downtime than repairs.
• The repairs have no effect on the age of the element.

The definition of the law is as follows:

7.2.9. TPS / Simple Periodic Test law

This law allows a component which fails to be represented according to an exponential distribution law and whose
failure is found during a periodic test. The repair is then carried out instantaneously.

Parameters:

• Lambda (Rate) = failure rate

• Tau (Duration) = test period (time interval between two consecutive tests)
• T0 (Time) = date of first test

The law is defined as follows:

User Manual 69 / 133

Here is a small graph representing the different phases of the component's "life":

This law is a simplified version of the "TPC / Full Periodic Test" law.

7.2.10. TPE / Extended Periodic Test law

This law allows a component which fails to be represented according to an exponential distribution law and whose
failure is found during a periodic test. The repair phase is then modelled by an exponential of the Mu parameter.

Parameters:

• Lambda (Rate) = failure rate

• Mu (Rate) = repair rate (when the failure has been found during a test)
• Tau (Duration) = test period (time interval between two consecutive tests)
• T0 (Time) = date of first test

Here is a small graph representing the different phases of the component's "life":

This law is a simplified version of the "TPC / Full Periodic Test" law.

7.2.11. TPC / Full Periodic Test law

This law allows a periodically tested component to be represented as completely as possible. There are many
parameters in play.

Parameters:

• Lambda (Rate) = failure rate during operation or on standby

• Lambda* (Rate) = failure rate during the test
• Mu (Rate) = repair rate (once the test has shown up the failure)
• Tau (Duration) = test period (time interval between two consecutive tests)
• Theta (Time) = date of first test (ignore parameter value: Tau)
• Gamma (Probability) = probability of failure due to starting the test (ignore parameter value: 0 = starting the
test does not cause a failure)
• Pi (Duration) = duration of test (ignore parameter value: 0 (instantaneous test))
• X = (Boolean) indicator of component availability during the test (0 = component unavailable during the test;
1 = component available) (ignore parameter value: 1 = available during the test)
• Sigma (Probability) = test cover rate (probability that the component failure is detected during the test) (ignore
parameter value: 1 = the test covers all the possible failures)
• Omega 1 ((Probability) = probability of forgetting to reconfigure after the test (ignore parameter value: 0 =
no reconfiguration problem)

User Manual 70 / 133

• Omega 2 ((Probability) = probability of forgetting to reconfigure after the repairing (ignore parameter value:
0 = no reconfiguration problem)

the "ignore parameter value" is the value to type if you want parameter to do not affect component
availability.

Here is a small graph representing the different phases of the component's "life":

7.2.12. TPC / Full Periodic Test with defined times

This law is the same as the Full Periodic Test law with 11 parameters (see above). The difference is in times of
tests. This law does not have Tau or Teta, but there is a Times of tests parameter where you can specify the
times the tests will be made.

7.2.13. NRD / No Recovery Before Delay law

This law takes two parameters: a repair rate Mu and a delay Delay. For non repairable components, it gives the
probability of not succeeding to recover the component before a delay Delay.

This law does not depend on the time, it is a short version of a constant law.

Parameters:

• Mu (Rate) = repair rate

• d (Duration) = recovery time

The law is defined as follows:

7.2.14. GLM / GLM Asymptotic law

This law is a variation of the "IND / Unavailability" law. It corresponds to the probability of a "IND /
Unavailability" law computed at t = infinity.

This law does not depend on the time, it is a short version of a constant law.

Parameters:

• Lambda (Rate) = failure rate

• Mu (Rate) = repair rate

The law is defined as follows:

User Manual 71 / 133

7.2.15. DOR / Dormant
This law has three parameters: a failure rate, a mean repair time and a delay. In addition, it does not depend on
the time.

Parameters:

• Lambda (Rate) = failure rate

• MTTR (Duration) = average repair time
• d (Duration) = delay

The law is defined as follows:

7.2.16. CMT / Constant mission time

This law is a simplified case of the "IND / Unavailability" law. It corresponds to an exponential law with a fixed
time given as parameter.

This law does not depend on the time, it is a short version of a constant law.

The parameter Q is optional.

Parameters:

• Lambda (Rate) = failure rate

• T (Duration) = mission time
• Q (Probability) = optional law

The law is defined as follows:

7.2.17. EMP / Empiric

This not actually en law, you must enter probability and failure rate in a tableau according to the time.

If you ask for computation a times which are not in the table, the value will be interpolated according
to other points.

7.2.18. MKR / Markov graph

This law uses a Markov graph as definition. Select the path of the .jma file. In order to do Boolean computation, you
need to do a preprocessing of the law. The preprocessing automatically start Markov module and retrieve necessary
values. It can be done with a right-click on the object having the law, or in Data and computations menu.

7.2.19. OCC / Occurrences of failures

The Failure rate is calculated divided the numbers of observed failures by the observation period. The result is
a constant law.

Parameters:

• Number of failures

User Manual 72 / 133

• Period (Duration) = observation duration

The law is defined as follows:

7.2.20. SIL / SIL level

This law corresponds to a constant law with parameter Q = 1x10-(SIL-Epsilon)

7.2.21. RRF / Risk Reduction Factor

This law corresponds to a constant law with a parameter Risk reduction Factor (RRF)

7.2.22. EXP / Expression

Law is defined buy user with an Albizia expression that contains time(). An Albizia expression can contain several
operators and functions (*, +, -, /, gamma(), exp(), sqrt(), min(), pow(), sin(), ...).
Parameters:

• Q(t): expression to evaluate Probability (must contained time());

• w(t): expression to evaluate unconditional failure rate (must contained time()).

7.2.23. STO / Stored Electrical Component

This law corresponds to a constant law for stored electrical components according to the functioning time and the
storage time on the mission time.

The result of the computation will be a constant probability calculated at the end of the mission.

Parameters :

• Lambda (rate) = failure rate

• Tf (Duration) = yearly functioning time
• Ts (Duration) = yearly storage time
• K (Rate) = reduction coefficient (functioning failure rate is equal to storage failure divided by this coefficient)
• %FMD (Ratio) = failure mode ratio
• mission time (Duration) = duration of the mission

The law is defined as follows :

User Manual 73 / 133

 Mission time is taken into account in the computation of total functioning time (TTf) and total storage
time (TTs) for the electrical component

TTf is defined as follows :

and TTs is defined as follows :

Assuming the number of hours in a year is set to 8760.

7.3. Uncertainties on the parameters

For each probability law used in the model, it is possible to introduce an uncertainty on each of the parameters.
There are several laws available to model them:

• "UNIF / Uniform";
• "NORM / Normal";
• "NLOG / Lognormal";
• "OBS / Observation";
• "OBS (#) / Periodic Observation" ;
• "GAM / Gamma";
• "BET / Beta";
• "TRI / Triangular".

Using this method, it is thus possible to introduce the impact of the uncertainties on the data into the final result.

7.3.1. UNI / Uniform law

This law has two parameters: and upper limit and a lower limit.

Parameters:

• a = upper limit
• b = lower limit

The law is defined as follows:

7.3.2. NLOG / Log normal law

This law has 3 parameters: the mean and the error factor and the percentage of confidence interval.

Parameters:

• Average(Mu) = The average

• Error factor = The error factor EF (= exponential(1.645*Sigma) for a 90% confidence interval)
• Confidence interval at = Percent of confidence interval (between 0 and 1)
User Manual 74 / 133
A random variable is distributed according to a lognormal distribution if its logarithm is distributed according to
a normal distribution. The law is defined as follows:

Where Sigma is equal to ln(EF)/coef, where coef is the quantile of the normal law conresponding to the chosen
percentage (1.645 for 90%), and where Mu = ln(E(x)) - Sigma²/2

7.3.3. NORM / Normale

This law has two parameters: the mean and the standard deviation.

Parameters:

• Mu = mean
• Sigma = standard deviation

The law is defined as follows:

7.3.4. OBS / Observation

This law has two parameters.

Parameters:

• Number of events (N) = Number of events observed

• Observation duration (T) = Observation duration

The probability density function of this distribution is:

k represents the degrees of freedom.

In options, it is possible to choose the degrees of freedom

7.3.5. OBS (#) / Periodique Observation

This law has three parameters, it is based on F.Brissaud work published in Rel. Eng. Sys. Safety 2017 DOI:10.1016/
j.ress.2016.11.003

Parameters:

• Number failure revealed (N) = Total number of failure observed

• Duration between 2 tests (#) = Inspection period
• Number of proof tests (W) = Total number od proof tests.

This function is partly based on a random number generator that uses a beta distribution (W-N + 1, N).

User Manual 75 / 133

7.3.6. GAM / Gamma
The gamma distribution is a two-parameter probability distributions: the shape parameter and the scale parameter.

Parameters:

• K = Shape parameter
• Theta (θ) = Scale parameter

The probability density of the gamma distribution is:

7.3.7. BET / Beta

The beta distribution is parametrized by two positive shape parameters: Alpha et Beta.

Parameters:

• Alpha (α) = Shape parameter

• Beta (β) = Shape parameter

The probability density function for 0 ≤ x ≤ 1, and shape parameters α, β > 0 is :

7.3.8. TRI / Triangulaire

Cette loi a trois paramètres : un minimum, un maximum et un optimum.

Paramètres :

• a = minimum
• b = maximum
• c =optimum

The law definition is:

:used during Z testing

:gradient between a and c

: gradient between c and b

In propagation uncertainties:

User Manual 76 / 133

Z randomly fired and equidistributed distributed between 0 and 1;

7.3.9. Consideration of the uncertainties

Uncertainties on parameters can be evaluated with 2 different ways:

• in the configuration of the laws as described in the chapter Configuring the laws [31]
• in the tab of parameters. In this case, ff a same parameter is used in 2 events, the same uncertainty is considered

To do that, first it is necessary to select the column Activate uncertainty and Law using the columns manager.

After, in the tab of parameters, It is enough to choose or not to activate the uncertainties and the law will be
applied in Law column.

User Manual 77 / 133

8. Example of a Fault Tree
Here is a fault tree modeling the behaviour of any safety system with two possible states: "work" / "failed" (or
"available" / "unavailable"). The aim is thus to construct a tree allowing us to evaluate the system's mean
unavailability.

The above tree has nine events:

• LS
– Number: 1
– Comment: "Logic"
– Law: exponential law with "Lambda" = Lambda1.

User Manual 78 / 133

• SV1
– Number: 2
– Comment: "Valve 1"
– Law: simple periodic test law with "Lambda" = Lambda2, "Tau" = Test and "T0" = 0.

• SV2
– Number: 3
– Comment: "Valve 2"
– Law: simple periodic test law with "Lambda" = Lambda2, "Tau" = Test and "T0" = 10.

• S1
– Number: 4
– Comment: "Sensor 1"
– Law: unavailability with "Gamma" = Gamma, "Lambda" = Lambda1 and "Mu" = Mu2.

• S2
– Number: 5
– Comment: "Sensor 2"
– Law: unavailability with "Gamma" = Gamma, "Lambda" = Lambda1 and "Mu" = Mu2.

• S3
– Number: 6
– Comment: "Sensor 3"
– Law: unavailability with "Gamma" = Gamma, "Lambda" = Lambda1 and "Mu" = Mu2.

• R
– Number: 7
– Comment: "Relay"
– Law: unavailability with "Gamma" = 0, "Lambda" = 10e-4 and "Mu" = Mu1.

• SS_1
– Number: 8
– Comment: "Sub-system 1"
– Law: full periodic test law with "Lambda" = Lambda1, "Lambda*" = Lambda1, "Mu" = Mu1, "Tau" =
4380, "Theta" = 4380, "Gamma" = 0, "Pi" = 10, "X" = 0, "Sigma" = 1 and "Omega" = 0.

• SS_2
– Number: 9
– Comment: "Sub-system 2"
– Law: full periodic test law with "Lambda" = Lambda1, "Lambda*" = Lambda1, "Mu" = Mu1, "Tau" =
4380, "Theta" = 10, "Gamma" = 0, "Pi" = 10, "X" = 0, "Sigma" = 1 and "Omega" = 0.

The tree's logic is governed by four gates:

• Div1
– Number: 1
– Name: Or1
– Comment: "ER"
– Type: "OR"
• Div1
– Number: 2
– Name: And2
– Comment: "VALVES"
– Type: "AND"
• Div1
– Number: 3
– Name: KofN3
– Comment: "SENSORS"
– Type: "K out of N"
• Div1
– Number: 4
User Manual 79 / 133
 – Name: Or4
– Comment: "Sub-systems"
– Type: "OR"

In this example, different types of more or less simple laws have been used. It was produced in a short time and
allowed several more or less complex components to be modelled: non repairable, repairable, periodically-tested,
with probability of failure on demand, etc.

Using this tree, we can now run various computations on the different gates or events: unavailability computations,
unreliability computations, etc.

User Manual 80 / 133

9. Computations
The following two computation engines can be used in the Fault Tree module:

• Albizia;
• MOCA.

These two computation options are accessible in the Data and Computations menu on the task bar.

9.1. Albizia computations

The computations by Albizia are performed in two main steps:

• general configuration of compuation;

• reading the results in the bank of results.

9.1.1. Configuring the computations

The computation configuration window can be accessed in two different ways: either via Data and Computations
- Computation settings menu or via Data and Computations - Launch Computation menu. The difference
between both is that, in the second case, the configuration step is directly followed by the computation launch step.

The configuration window which opens is called Launching Albizia computation .

The configuration window is divided into 3 tabs (1 for each type ofcomputation).

User Manual 81 / 133

9.1.1.1. Configuration of probabilities computation

• Target: specifies the target of the computations. Four choices are possible: All nodes , Top Events for the
top(s) of the tree, Watched node(s) for node in the watched element list, Time Spent node(s) for nodes in the
Time Spent element list and Selected node for the node currently selected in the tree.

User Manual 82 / 133

 For watched elements, with a right click it is possible to add one node or directly a sub-tree:

Notice that watched elements can be directly added by a right click on the wanted element in the table
of events/gates.

• Computation times : specifies the computation options.

– Iterate From A to B step C: the computations will be performed for values of t ranging from A to B with
a step of C.
– List of times : the computations will be performed for the values of t given in this list.

It is possible to make the calculation just before a test period by indicating a - after the chosen time
for calculations
– Display discontinuity points : the computation engine takes into account the discontinuity points if the
option is selected.
– Times in : The values entered are supposed to be hours. The unit can be specify among hours, days, months,
years
– Compute mean value through [0, t] : the computation engine computes the mean value of each variable
to compute for each computation times.
– Compute integral value through [0, t] : the computation engine computes the integral of each variable to
compute for each computation times.

• Activate propagation of uncertainty : activate the propagtion of uncertainties, and specifies parameters of
computation and wanted results.

– Number of histories : Number of histories (Monte-Carlo simulation) that have to be made.

– Confidence range at : specifies the percentage of resultats that will be included in the confidence range.
– Quantiles chosen : With all results of histoires, the software do a "quantile computation". But there are
always many ways to chose bounds of an interval containing X % of the results. Here you can chose "on
the left" (lower bound is minimum, upper bound is the quantile at X%), "onthe right" (lower bound is the
quantile at 100-X%, upper bound is the maximum) and in the middle.

User Manual 83 / 133

• Probabilities : specifies probabilities to compute.

– Unavailability : Q(t), U(t) or PFD(t) according to different standards and countries.

– Availability : A(t) = 1 - U(t)
– Unconditional Failure Intensity : W(t), UFI(t) or PFH(t) according to different standards and countries. It is
the probability that the system fails between t and t+dt, assuming system was OK at time t=0. It is possible to
manually configure the computations of the CFI, with the "Configuration" button. (cf. Section 9.1.1.6, “UFI
computation configuration”)

– Conditional Failure Intensity : CFI(t), λ eq(t) or λ Vesely(t) according to different standards and countries.
It is equal to W(t)/A(t) It is the probability that the system fails between t and t+dt, assuming system was
OK at t and at time t=0.
– Unreliability : F(t) = 1 - R(t)
– Reliability : R(t) = R(t)=exp[-(Integral from 0 to t) of λ eq(u)du]. We can see here that this reliability
is based on an equivalent lambda, and not on the real lambda. This is a good approximation that is
conservative. Anyway, you can not compute the reliability with a fault-tree. For systems made with
unrepairable components, the result is exact (because it is equal to Availability).
– Calculation of time spent in zones : For above values, this option allows to know percentage of time spent
in each interval. These intervals are configurable using Configuration button. By default, SIL zones are used.

– Configuration of mean times allows you to configurate the computations to obtain the mean times. (cf.
Section 9.1.1.5, “Configuration of mean times”)

User Manual 84 / 133

9.1.1.2. Configuration of cut sets calculations

• Target: specifies the target of the computations. Four choices are possible: All nodes , Top Events for the
top(s) of the tree, Watched node(s) for node in the watched element list, Time Spent node(s) for nodes in the
Time Spent element list and Selected node for the node currently selected in the tree.

• Minimal cut sets algorithm: allows to choose between the two available algorithms. The MCS algorithm
(Minimal Cut Set) gathers the cuts from the construction of the ZBDD, while the PI algorithm will create the
cuts from the Prime Implicant. This last one allows the incoherent formulas, but not the first one. The Auto
mode let GRIF choose the best algorithm (depending on the formula and the options).

• Maximum number of cuts: allows to inquire a maximal number of cuts. If the number of cuts exceeds this
number, the cuts having the greater number of elements will not be saved.

• Number of cuts : number of minimal cuts of the system (no maximum order limitation).

• Number of cuts per order : summary of the number of cuts for each order (no maximum order limitation).

• List of cuts : list of minimal cuts of the system.

• Compute probability of cut sets: allows to add the probability to each cut of the list.

• Compute frequency of cut sets: allows to add the frequency to each cut of the list.

• Compute at time t= allows to inform the time when the probabilities and the frequencies of the cuts are
calculated.

User Manual 85 / 133

• Make an approximation of the frequency of cut sets: allows to compute the frequencies from the standard
ARP4761A. The computations of frequencies are quicker but more approximative.

• Order of the shortest minimal cutset containing each event allows to know for each event what is the order
of the smallest cut containing this event.

• Filter cuts allows to not take into account some cuts which do not have a probability or an order superior to
the given limit.

• Computations to be done allows to inform what computations will be done. It is possible to do the computation
on the failure mode of the formula, but depending to the module, it is possible to do the computations on the
components of the formula, or the systems of the formula.

• A cuts save in the result file is possible by selecting the option Save result as XML, but the cuts being
voluminous, the result file will be bigger.

9.1.1.3. Configuration of importance factor calculations

• Target, times, uncertinties : cf. probabilities calculation

• Computation type : specifies the importance factors to compute.

– Birnbaum (MIF)

User Manual 86 / 133

 – Critical (CIF)

– Fussel-Vesely (DIF)

– Risk Achievement Worth (RAW)

– Risk Reduction Worth (RRW)

– Barlow Proschan (BP)

The manual configuration of MIF computation allows you to chose MIF algorithm.

• Partial derivative: Uses quick algorithm based on partial derivative. To be used with coherent fault trees only)
• Exclusive Cofactor: Uses (less quick) algorithm using Exclusive cofactor S#. It stays valid with non-coherent
fault trees.
• BDD: Uses algorithm using BDD (only for coherent fault trees)

With automatic mode, the Partial derivative algorithm is used, execpt for non-coherent fault tree (Negation,
XOR, IfThenElse ...) where S# is used.

User Manual 87 / 133

9.1.1.4. Configurating computations' options

The options of the computations allow to inform some additional options, on the three parts seen previously:

• Do truncated computation at order: allows to not take into account the elements which have an order greater
than the given order. For example, a AND gate with five sons will not be taken into account if we give four
as the truncated computation order.

• Do truncating during: allows to inform when computations will be truncated. It can be during the BDD
Construction, so on the probabilities, or during the ZBDD Construction, so on the cuts. The Back
computation allows, when the truncation is on the BDD, to make a Back Computation, which means to compute
for all the targets the probabilities from the cuts of the ZBDD. This allows to have a better accuracy of the target
probability when the BDD is truncated.

• Indexation heuristic: allows to inform which algorithm will be used by ALBIZIA to order the variables in the
dataset. (cf. Doc Albizia)

• Maximum risk in risk matrices: allows to have on the risk matrices in the ordinates the medium frequencies
(if not selected) or the maximum frequencies (if selected).

• Simplified dormant exponential allows to simplify the dormant exponential laws into constant laws, with
parameter q equals to the maximum between the test period and the maximum of mission time.

• Options of uncertainty law Observation: allows to configurate the uncertainty laws of type Observation of
the parameters in the document.

User Manual 88 / 133

• Options of uncertainty law Periodic observation: allows to configurate the uncertainty laws of type Periodic
observation of the parameters in the document.

• Options for Beta-Total CCF: allows to configure all the CCF of Beta-Total type in the document. The option
Simplified CCF for periodic tests allows to set to 0 all the parameters of the tests for the CCF (Gamma, Pi,
X, Sigma and the Omegas). The Computation of lambda for Beta-TOTAL CCF: allows to inform how the
Lambda will be calculated : Minimal Lambda which is not recommended since there is a lost of precision,
Maximal Lambda which allows to keep the precision, and the differents Medium Lambda.

• BFR CCF generation allows to inform which algorithm will be used to decompose the BFR CCFs.

The algorithm NUREG/CR-5485 will take into account during the lethal/non lethal failure every impacted
elements by the CCF. These elements will then be under a new gate OR (in the case of without concat function),
or under a new gate Concat (in the case of with concat function).

The algorithm Atwood 1986 allows to decompose an impacted event by a CCF in three parts: An intrinsic part,
a lethal part and a no lethal part (made out of two parts : the non lethal part intrinsic of the event, and the non
lethal part linked to the CCF)

• Do calculation in another JVM allows, when the computations has to be done on a huge model (and so going
to take a lot of times), to launch the computations on a new process independent of GRIF. It is then possible
to continue working on GRIF on the meantime. The Options of the other JVM allow to inform the options of
the JVM, for example the given space allowed (-mx"Memory size").

9.1.1.5. Configuration of mean times

To obtain mean times results it means: MTTF, MDT, MUT, MTBF, number of failures, mean up time and mean
down time, it is enough to check the box Computation of mean times in Mean times tab.

The different mathematical magnitude computed are these following:

• MTTF: Mean Time To Failure: time before the item fails. It is used to describe the time
– to failure for a non-repairable item;
– to the first failure for a repairable item.

• MDT:Mean Down Time: average time that a system is non-operational.

• MUT: Mean Up Time: average time that a system is working.

• MTBF: Mean Time Between Failure: time between successive failures of a repairable item.

• Number of failure: number of failure over mission time.

User Manual 89 / 133

• Up time: duration of system is working.

• Down time: duration of system is non-operationnal.

9.1.1.6. UFI computation configuration

GRIF (with Albizia engine) enables to compute UFI on non-coherent fault tree. The automatic mode takes into
account almost cases, but user can select which algorithm to use. There is two way for UFI computation:

• UFI computation with MIF: It is "usual" method. Let be a System S made of many components c, the UFI
(also called w) of S is equal to UFI S = w S Σ MIF(S,c)*w c . This algotithme is less performant than the one
based on BDD, but it works for non-coherent fault tree (if the MIF is well computed).
• UFI computation with BDD: It is the "fastest" methode which is base on BDD. This method doesn't work for
non-coherent fault trees, except in the particular case of initiator events (cf. option below).

In order to exmplain the Take failure order into account "not-initiator" then "initiator" option, lets take a
simple example: un system made of one safety barrier which set the system in a safety state if an initator event is
detected. The top event is an initator event which is not detected by the barrier. The frequency of this top event
is the result of two cases:

• The barrier is already out of order (with some probability) and the initiator event happens (with some frequency)
• the initiator event is already here (with some probability) and the barriers fails (with some frequency)

The second case doesn't matter because the system is set in a safe mode. That why this case can be removed
from UFI computation. It is what is done if user check Take failure order into account "not-initiator" then
"initiator" option. This options works the both algorithms. Moreover, this options allows you to use UFI
computation with BDD if initiato part is coherent.

9.1.1.7. Ordering choices

It is possible to choose among various algorithms the indexation heuristics to order B.D.D. construction.

By default, the algorithm used is FKK88.

9.1.1.8. Configuration of Lambda computation method for CCF

When using common cause failure, the software must compute a lambdaCCF that will be used for CCF. It is the
one that will be multiplied by Beta. Assuming each component impacted bay a CCF has a different lambda, there
are many methods to compute the lambdaCCF from the list of lambdas. Five methods are available:

• Minimum: This method uses the minimum value of lambdas. Not recommanded.
• Maximum: Uses the maximum value of lambdas to be concervativ. This method was used in GRIF 2013 and
previous version. It can be penalizing when lambda of components are very different.
• Average: This method uses the artimetic mean of lambdas.
• Geometric mean (Method detailed in PDS): This method uses the geometric mean of lambdas. It is PDS Method
recommanded by SINTEF. It works fine with very different lambdas.

User Manual 90 / 133

• Quadratic mean: This method uses the quadratic mean of lambdas.

9.1.2. Albizia Results

Results window is divided into 5 tabs:

• Probability
• Importance Factors
• Products
• Mean times
• Results
• Info

User Manual 91 / 133

The Probability tab gathers all probability computations. The top part displays the percentage of time spent in
each zone (if needed). Then a synthesis table displays minimum, maximum, mean/average and sum. If it is a
computation with propagation of uncertainties, a column displays the confidence range of the average.

Importance factors tab displays importance factors for each event and for each system.

Products shows results of cuts/products computations. In synthesis, a cut with a "0" order, means that the top
event is always true. It may happen if some parts are "forced to 1".

Mean times tab give the different calculations of mean times (MTTF, MDT, ...).

Results tab contains Albizia output.

Info tab contains information about algorithm used. This information can be copied / pasted for any other use.

9.2. MOCA computations

The computations using MOCA-RP V14 are performed in three main steps:

• general configuration of parameters;

User Manual 92 / 133

• the launch itself;
• reading the results file.

9.2.1. Configuring the computations

The computation configuration window can be accessed in two different ways: either via menu Data and
Computations - Moca Data or via Data and Computations - Launch Moca ... . The difference between the two
is that, in the second case, the configuration step is directly followed by the computation launch step.

The configuration window which opens is called General Information :

This configuration window is divided into five parts:

1. Title : allows you to give a title to the results file.

2. Default computation times for statistic states :

• Iterate From A to B step C: the computations will be performed for values of t ranging from A to B with
a step of C.
• List of times : the computations will be performed for the values of t given in this list.
• Computation made at : by default, computations are made immediately after transition triggering, but you
can do computation at t-Epsilon (just before triggering), or at both.
• Unit : default times unit is "hour". You can choose a unit that will be used for computation times. N.b. results
are always in hours.

3. General :

• Number of histories : Number of histories (NH) to be simulated (each history has a time t indicated below).

User Manual 93 / 133

 • First random number : It is the seed of random number generator.
• Maximum computation time (MT): The computations are stopped and the results are printed even if the
requested number of histories has not been reached.

the unit of time (MT) is the second.

• Automatic history duration : If this box is checked, GRIF will compute history duration using computation
time of variables and statistical states. If not, user can choose a specific History duration
• Multi-processors computing Enables (or not) the multi-processor computing (when available).

4. Advanced options : used to configure the advanced options.

• Loop detected when the number of transitions firing at the same time is grater than : You can choose
the limit of transitions fired at the same time before loop detection.
• Max number of loops while() : if using in a transition.
• Continue calculation if errors : If an error is detected, the current history is stopped and we pass to the
following one without stopping the calculations.
• Display seed history : Display or not the seed used by the random number generator.
• Use old seed management (version < 2018) : From 2019, a new random number generator was developed
to increase the number of playable story without seed repetition. It is recommended that you use this option
only for backward compatibility for your old documents.
• Computes every nodes : Useful option in the boolean modules to have the calculations on all the nodes (by
default the calculations are performed only in the top event).
• Delay re-computation for dynamic transitions : Selects the method for recalculating the delay of
transitions marked as dynamic. For more information on the possible choices, refer to User manual
Moca14.10.3 [2.7.10. Dynamic transitions]

5. Statistics
• Confidence interval : Allow to choose the confidence interval at 90%, 95%, 99%, 99.9% and 99.99% (by
default 90% is checked). .
• Disable statistics on places and transitions : Allow not to display the statistics on places and transitions.
• unlimited histogram : In case of histogram all the stories are taken into account not only the 1000 first ones.
• Do not save 0 value in history : Option to not save the historic if the statistic value is 0.
• Activate uncertainty propagation Enables (or not) the uncertainty propagation computations (two-stage
simulation): in this case we must specify the number of sets of parameters "played" (the real number of
histories thus simulated will be the "number of sets of parameters x number of histories to be simulated" and
will be displayed in the "Total number of histories" field).
• Histogram with every history of the tries (with uncertainty propagation) : Allows to display the
histogram with every history of the tries.

6. Variables : This tabs reminds computing configuration of variables. If document contains some statistical
states, another tab is available.

7. Output options : used to configure the output.

• Print censured delays : Prints the censored delays (or not).

• Verbose : Give internal information of Moca RP (launching, compilation, ...).

9.2.1.1. Sequence generation computations

The MocaRP computation engine allows to perform sequence generation. In this computation mode, it is possible
to list all the sequences of transition fire which leads to undesirable event. However, statistical computation will
not be made.

User Manual 94 / 133

To activate this computation mode, in the option in the computation launching, select Sequence Generation in
Computation mode. Statistics tab disappears in favour of Sequence Generation tab.

In the Sequence Generation tab, it is necessary to indicate the name of the Undesirable event. This event is a
variable defined by a boolean expression. A true value indicates that the undesirable event has occurred during
the current story.

Sequences that result in the undesirable event are grouped into an equivalence class. It is possible to choose the
algorithm used to define this equivalence class:

• None : All transition sequences leading to the undesirable event will be returned. (no minimization)

• Sub-words : The minimality consists to search a common prefix, factor or suffix.

• Minimal cut sets : only the transitions are interested, without duplicates and without order, which led to the
undesirable event. A minimal cut set includes all the sequences that include it in the same equivalence class.

See Manuel utilisateur Moca14.10.3 [3.4.5. Lancement d'une génération de séquences] for more information.

The computations options Save seeds allows to save the history seed and the occurrence time when undesirable
event occurs.

Only the transitions with the flag SEQGEN with a true value are considered in the sequence. All others transitions
are not taken into account. They generally correspond to transitions that don't contribute to the sequence generation
(such as instantaneous reconfiguration transitions).

9.2.2. Reading the results

The results are presented in a window with different tabs and tables.

9.2.2.1. Moca Results

Moca results atre displayed in a window containing 6 main tabs: variables, places, transitions, XML, stantard
output, info.

User Manual 95 / 133

9.2.2.1.1. Tab of Variables

The Variables tab contains all the information computed for each variable (or statistical state).

• Value: Contains every value of a variable for every type of statistic.

• History (at the end of histories): contains historical values for each computed statistic.
• Fixed size Histogram: Contains histograms computed by Moca (cf. chapter about histograms for Simulation
package module)
• Equiprobable classes Histogram: Contains histograms computed by Moca (cf. chapter about histograms for
Simulation package module)
• User defined Histogram: Contains histograms computed by Moca (cf. chapter about histograms for Simulation
package module)
• Timeline: Contains a timeline for each variable. Times are automatically computed by Moca.

9.2.2.1.2. Tab of Places

It contains sojourn duration and mean mark for each place of Petri Net.

9.2.2.1.3. Tab of Transitions

It contains firing frequencies for each transition, and firing history for each history.

9.2.2.1.4. Other tabs

Other tabs display "raw" results. XML tab contains XML output of Moca, it is the file used to retrieve data. This
file can be used for further post-treatments.

Standard output displays the standard output of Moca (available only after computing).

Info tab contains useful information about computation (simulation time, number of histories that have been
done ...). This information can be copied / pasted for any other use.

9.3. Tables and Panels to display results

9.3.1. Result-tables

Result-tables are made of data and a top part to set table up.

User Manual 96 / 133

Columns can be sort by clicking on their header. The filter icon activates a filter set-up with the following
window:

When filter is activated, a small (+) is diplayed near column title. Filter can be remove with button.

9.3.2. Export data

Values that are visible in this table can be exported in CSV file format with button.

Results can also be displayed with a Curve by clicking on . Data used for x-axe and y-axe must be specified
in the following window:

Then, chart is displayed in a window:

User Manual 97 / 133

Chart can be saved in the current document with the button at the bottom.

When chart is in document, points are no more modifiable.

9.3.3. Result-Panels

9.3.3.1. Tab Probability

9.3.3.1.1. Time spent in each zones

The fisrt part shows for each target time spent in each zone. This parts displays only if the calculation is selected
in the calculaption parameters.

9.3.3.1.2. Synthesis

In this part, for each target and for each calculation asked, table shows mean, maximum value, the average and
the integral. Each calculation is displayed in different table.

9.3.3.1.3. Global Results

Result-panels have been created to facilitate data access in tables with many columns. The aim is to make a prior
filter to keep wanted data.

This panel is made of a combo-box in the upper-left corner which enables to remove the column from the table
and creates a list on the left which contains every value in the removed column. When you select a value in the
left list, it modifies the table in order to show lines whose removed column contains the selected value.

The combo-box in the upper-right corner enables to choose which column C will be used to cut table. The table
will be cut in many tables, each one in a tab whose title is equal to the value used to filter the C column. Then C
column is removed since it contains only the one value in a given tab.

allows to select the different formats of display.

User Manual 98 / 133

Alloc tab allows to user to define Probability allocated by user can be defined for each event.

Margin corresponds to the ration between Allocated probability and Computed probability.

In documents option it is possible to specify if this information are dispayed on the events.

This option is in Additional information to specifiy if the allocation and the percentage (marge) Which separates
it from thecomputed probability is wanted.

This information ca be also displayed in a graphic area.

9.3.3.2. Minimal cut sets

9.3.3.2.1. Products synthesis

First tab shows the number of minimal cut sets and the number in function of the order.

9.3.3.2.2. List of products

Second tab gives minimal cut sets details with associated probability. Products can be sorted out following:

• Order;
• Order/alphanumeric;
• Order/probability;
• Order/probability/alphanumeric;
• Probability/order;
• Probability/order/alphanumeric.

User Manual 99 / 133

It is also possible to limit the display of products, either with digital way (reveal the X first ones), or display the
dominating products (display those which represent XX % of the probability of all the cut sets).

for each cutset, its probability and frequency of occurrence is given.

The frequency formula is :

icon exports in dag format un fault tree made up with all the minimal cut sets. This fault tree is created with
a gate OR of all the cuts.

The sum of probabilities of all minimal cutsets and the sum of probabilities of filtered minimal cutsets are displayed
at the bottom of the tab.

9.3.3.2.3. Products details

The third tab gives the minimal cups with the detail of the laws (Type of laws, failure rate, period tests) of the
events. As the previous tab, it can be sorted out of different way and it is also possible to limit the display of

User Manual 100 / 133

products either with digital way (reveal the X first ones), or display the dominating products (display those which
represent XX % of the probability of all the cut sets).

9.3.3.2.4. Minimum order

The fourth tab gives for each event the level of the lowest minimal cut set order in which it appears.

9.3.3.3. Mean times

The fourth tab gives the details of mean times.

User Manual 101 / 133

9.4. Batch computation
In order to do fast sensibility analysis or to compare some results with different parameters, it can be very useful to
do calculation one after another automatically. To do this, use the Data and Computation / Batch computation ...
menu.

The batch launching window is made of two part, the first is for the name of the batch and the number of
computations in the batch. Then each computation can be set up:

• Name of computation: for identification in results

• Computation options: contains every option related to this computation (times, types ...)
• Modifications on the model: specifies modifications that will be made on the model before computation
launching. You can add as many modifications as you want with the + button. Each modification is made of
4 parts:
1. 1 drop-down menu for object type
2. 1 drop-down menu for the object that will be modified
3. 1 drop-down menu to specify what will be modified on this object (value for a parameter, law for other
object ...)
4. Then you must enter the new value in the cell

The above example shows a batch with 2 computations, the first is made with a lambda parameter with 1.0E-5
value and a mu parameter with 0.1 value.

After a computation, the model is always reset up to an initial state without modification.

User Manual 102 / 133

9.5. Result Bank
Every GRIF computation is stored in result bank which is available on the right of the module.

You can display a result with a double-click on it. There is a default result for each computation engine, it is the
place where "standard" computations are stored. Then, each is a batch computation directory, it contains as
many results as computations asked for the batch. Finally, the directory contains results for curves that have
been frozen.

9.6. Compute manager

Compute manager shows the calculations. That are currently running or already performed.

Compute manager is automatically displayed when calculations are performed. User can display the window

using the following icon .

This tab is made of 6 columns:

• Time: The hour of calculation launch;

• CPU: number of CPU used;
• Document: document name;
• Computation name: name of results file;
• Progress: progress bar;

User Manual 103 / 133

• Status: finished in green, in progress in yellow, error in red;

In Compute Manager some actions are available:

•
: allow to reorganize the calculations order;
•
: display the following windows for computation settings:

•
: stop selected compute;
•
: suspend selected compute;
•
: resume compute in suspend;
•
: display results of selected compute;
•
: details errors;
•
: remove selected compute;
•
: clear all compute;

When a task is added to Compute manager, user is not blocked until the task is ended. He can continue to work
on his model. He can even relaunch a calculation. The various tasks accumulate and are treated sequentially.

User Manual 104 / 133

10. Curves
The curves can be drawn to study the model and the results better. To do this, click left on the corresponding icon
on the vertical task bar then draw a box. This box will be the space assigned to displaying the curve(s). Initially
it is only a white box with two axes without graduation.

Charts icon:

We must now define the curves to be drawn. To do this, click right on the box to display the Charts Edit window.

10.1. Edit curves window

The edit curves window is the same for all the GRIF modules.

The window is divided into several sections:

1. Charts title: enters a title for the graph.

2. Data list: this part includes a table with several columns in which the different curves on the graph are listed
(name, description, display, curve colour, curve style, curve thickness, display average). A number of different
buttons are available above this table.

User Manual 105 / 133

 •
: Selects a result of computations to display. It sends the user back to the Select results window to add a
curve plot to the graph (see. Section 10.2.1, “Curves from data in result-bank”).
•
: Compares several results from different calculations for the same data. It sends the user to the Compare
results window to add a curve plot to the graph (see Section 10.2.2, “Comparative curves from data in results
bank ”).
• Edit: edits the plot of the selected curve.
•
Delete : deletes the plot of the curve selected on the graph.
•
Up : moves up the plot of the curve selected in the list.
•
Down : moves down the plot of the curve selected in the list.
• Save: saves the list of points calculated to plot the selected curves in .csv format. This export does not contain
the generic values. To obtain an export with the generic values, right click on the curve and select Individual
export.
• Duplicate: creates a new curve identical to the curve selected.
•
Freeze : freezes the display of the curve, which will no longer be updated automatically according
computation results.

For each curve, the user can specify the colour, point style, line thickness and display.

3. Computation options: enables the user to enter settings for the computation (optional depending on the
module).

4. Style: this section concerns the curve display.

• Type of style: specifies the type of all the curves on the graph (line, histogram, etc.). N.B. In the case of a
histogram, the bars that exceed the display area will be displayed in shading to show the user that s/he must
change the display intervals so that the entire bar can be displayed.
• Intervals defines the display limits for the curve. Automatic without peak: the graph will not display the
"peaks" of specific cases of exceptional values which would make the graph illegible. Even if the peaks
are not displayed on the graph, the user can display their values using the choices proposed in the option
Display peak values.
• X and Y intervals: specification of the display interval on the X and Y axes (default intervals or intervals
defined by the user). The last function enables users to "zoom in" on the most interesting parts of the graph.
• The axis unit can be selected according to the type of computation result. For example for units of time, the
user can enter hours, days, months or years.
•
The button determines whether or not the unit is displayed on the graph.
• The log boxes are used to activate the logarithmic scale on the axis in question. N.B. 0 cannot be represented
on a log scale, remember to enter a start value that is strictly positive (e.g. E-10). If 0 is entered, the log
scale will begin at an arbitrary value E-15. Where the computation engine allows, the trust interval can be
displayed by ticking the corresponding box.
• Areas: distinguishes a range of values on a coloured background.
• In the histogram style, a box can be ticked to create a cumulative histogram.

5. Display options: activates the Display title function (display graph title) and the Display generic values
function (display min, max and average for each curve).

When a curve is edited, the edit curve window often includes 3 parts: the times at which the computations are
performed, what has been calculated and the extra information (generic values) that should or should not be
displayed below the curve.

Comment: it is sometimes necessary to refresh all the graphs in a document. This can be done using the Tools /

Refresh command, or the keyboard shortcut F5 or the icon.

User Manual 106 / 133

10.2. Selection of results window

10.2.1. Curves from data in result-bank

When you click the Add button in the Data list part you reach a window for curves setup. Each curve displays
data stored in the result-bank. The following window helps users to specify how to retrieve data.

• Legend: legend of the curve.

• Computation selection: select the computation in the result-bank.

• Result to be displayed: each computation contains many results. Select the one you want to be drawn.

• You can display a list a point whose X and Y will be taken from the data selected in the combo-boxes; or you
can display the time spent in each zone.

• Axes: When a result is selected, select what must be in X-Axe and what must be in Y-Axe.

• Value to be displayed: Then you can display additional information about the result (min, max, average ....)

10.2.2. Comparative curves from data in results bank

When the user clicks on Compare in the Data list section, a window opens enabling the user to specify the curve
to be plotted. S/he can then choose whether or not to display a result from several different computations. The
following window is used to indicate the way in which the information is to be recovered.

• Legend: curve legend.

• Computation selection: the user can select the different computations to be used from the results bank. Hold
down the Ctrl button to select several different computations.

• Result to be displayed: a computation often contains several results and this file tree structure is used to specify
the result that the user wants to display.

• Information to show: indicates which data are to be displayed on the y-axis.

• For which point?: indicates which point of the computation is to be compared to the others.

• Display x-axis values according to: indicates which data must be displayed on the x-axis.

• Value to be displayed: finally, certain extra data can be displayed (min, max, average, etc.)

User Manual 107 / 133

10.3. Quick curves creation

It is possible to create a curve directly with a right clock on the event or gates by selecting the icon

it is possible to choose 3 different curves:

• Unavailability: U(t) ;
• Unconditional failure intensity: W(t) ;
• Conditional failure intensity: λ eq(t).

User Manual 108 / 133

11. Database of parameters
In every GRIF module, a connection can be established with a database of parameters, to import parameters in
GRIF. There are three ways to connect to a different database:

• connection to a .csv file

• connection to a .xls file
• other connection (via JDBC).

11.1. Format of the databases

The database must contain the identifier, the name and the value of the parameter. It is possible to add to the
parameters more information, as the unit, the dimension and the description of the parameter. So we can have
three to six columns, inquiring:

Data's type: Possible values:

Parameter's identifier Numbre, Text
Parameter's name Text
Parameter's value Number
Parameter's description Text
HOUR : hours
DAY : days
MONTH : months
YEAR : years
Parameter's unit HOUR_1 : hours-1
DAY_1 : days-1
MONTH_1 : month-1
YEAR_1 : years-1
FIT : Failure In Time (= 10-9 hours-1)
Parameter's dimension BOOLEAN, FACTOR, PROBABILITY, RATE, TIME, OTHER

11.2. Connect to a database

To access to the window to create the connections to databases, go to the menu Data and Computations ->
Parameters database -> Connections .... A window appears then:

From this window, it is possible to :

User Manual 109 / 133

 Add a connection to a database.

Modify a connection to an existing database. It opens the same window when adding a connection,
but the fields are already filled by the data previously entered.
Delete the selected connections of the databases.

11.2.1. Connection to a CSV file

11.2.1.1. Form of the database

This type of connection is the simplest. The CSV file has for extension ".csv". It is a simple text file where the
different fields are separated by commas, tabulations or semicolons.

11.2.1.2. Connection

Once clicked on the button "Add a connection to a database", a window opens up:

This window has as a common base, the selection of the database, the fields for "ID", "name", "value",
"description", "dimension" and "unit", and a button Test Connection. By clicking on this button, GRIF tries to
connect to the database and so verifies the configuration provided by the user.

When adding a CSV database, the type CSV must be selected. A new field appears: the separators between the
data. To sum up, there are three steps to add a connection to a CSV database:

• First, fill the path of the CSV file in. A file explorer is at your disposal (button ...).

• Then, specify the type of the separators used in the CSV file.

• Finally, enter the six fields names of the CSV file. (Or only the ID, name and value fields) (Uppercase letters
are taken into account as lowercase)

Warning : It's important to note that when creating a connection to a CSV database, you must have all
of the data on a single sheet.

User Manual 110 / 133

11.2.2. Connection to a XLS file

11.2.2.1. Form of the database

The databases of the .xls or .xlsx extensions correspond to EXCEL files. Here is an example of an EXCEL
Database :

11.2.2.2. Connection

To connect GRIF to this database, select the XLS type in the connection window. The window is now as followed:

Sheet is the sheet's name where the data are located, and will be filled once a valid path to an EXCEL file has
been entered.

User Manual 111 / 133

11.2.3. Connection to a database (with a JDBC connection)

GRIF can connect to any database with JDBC, as long as the database follows the same rules of the databases seen
earlier. The window for that kind of connection has multiples fields to fill:

1. Driver JDBC is the name of the JDBC driver (ex : sun.jdbc.odbc.JdbcOdbcDriver)

2. Connection URL is the URL of the database.

3. The fields Login and Password can be left empty.

4. The SQL request SELECT id,name,value,description,dimension,unit FROM REX is used to gather the
dates.

5. Option field inform of all of the database's options: separator, ...

Once a connection with a database is ready, GRIF can now import a set of parameters from the database, but
also updates these parameters when modifications has been made in the databases, or recreate the links of these
parameters so they can now take the values of another database.

User Manual 112 / 133

11.3. Import parameters from a connected database
Once a database is connected, GRIF can import a set of parameters from the database, via the window reachable
by the Data and computations -> Parameters database -> Copy parameters from database ... menu.

Select the parameters you want to import, and click on OK. The parameters are now created and imported in
GRIF. The created parameters have the same names than the database's parameters, and the fields "Description"
or "Dimension" are identical of those found in the database.

It is important to underline that it is possible to manually create a parameter in GRIF, and then with its Add-On
menu, assign the parameter's value of the connected database. This operation is detailed in this link.

User Manual 113 / 133

11.4. Update of the parameters from the database
When an user, who has updated some of his data in his database, wants to have these modifications done on his
parameters in GRIF too, he can then use the update action, from the Data and Computations -> Parameters
database -> Update from database ... menu:

This window shows the parameters in GRIF which are connected to parameters from the databases. The red lines
correspond to data which have been modified in the database. If the user wants to update some of his parameters
in GRIF, he must select the lines of the wanted parameters, and then press the OK button. The parameters are
now updated.

User Manual 114 / 133

11.5. Rebuild of the links to the database
It is possible to modify an existing parameter's connection in GRIF, by changing the database of its associated
parameter. However the parameter can only connect to the parameters with the same name. This action is available
by the Data and Computations -> Parameters database -> Rebuild links to the database menu.

Here we can see the different parameters of the databases, which are imported in GRIF, and which are on multiples
databases. So on the line of the parameters you want to rebuild the links, select the right database, and then validate
your modifications by clicking on OK. GRIF then update the values of the parameters by rebuilding the links.

User Manual 115 / 133

12. Save
Here is a summary of all the data which can be saved from a same model.

12.1. Document template

It is possible to use an existing document as base to create a new document or as a part of a document. This
functionality is accessible in File - Document template menu.

New (from template)... menu allows to open a new document and to initialize it with data from a model already
build. A window appears to select the existing model.

Import a template... menu allows to add to the current document data from a model already build.

User Manual 116 / 133

Save as template allows to save the current document as template in the Template directory of the module. Once
saved as a template, the document appears in the Template tree of the GRIF window as well as in the Template
Manager.

It is possible to create new files from this model using New (from a template)... action. A drag and drop to the
templates from the input area allows to import the model quickly.

Save as default template menu allows to save the current document as default model in the module template
directory. This model will also be the default model of the module. It will be used as base for creating a new
document when File - New (default) action is used.

User Manual 117 / 133

Template manager menu opens a window to manage the template of the document. New document libraries can
be added/deleted. To add a new library it is necessary to select a directory of the file system. The tool analyzes
the documents in this directory and builds a library that can be used by GRIF based on the compatible documents
found.

12.2. Save as (Confidential)

GRIF gives the opportunity to "Save as" in a confidential way. This allows to create a new tree with parts tagged
as "Confidential" deleted, in a new document, so the user can disclose his work, without the confidentials parts.

12.2.1. Confidentiality of the gates

To make a gate confidential, there are three ways to do it:

• Access to the edit window of the gate, and tick the box associated to the label Confidential gate.

• By a right click on the gate(s), select the menu Confidentiality, and then Make confidential.

• In the Gate's table, tick the box located in the Confidentiality column. If this column does not appear in the
table, then in the Column manager, tick the box Confidentiality to make it appear.

A gate is confidential when, on the graphical view, the icon is next to the gate, or when the box of
the Confidentiality column is ticked. Once every wanted gates are confidentials, then the user can launch the
command Save as... (Confidential), reachable from the menu File -> Save as ... (Confidentiel).

User Manual 118 / 133

12.2.2. Save as confidentially

The command Save as... (Confidential) supress every subtree which has as a parent a confidential gate, and
then replace these confidential gates by events, with a Constante law, with the parameter q equals to the same
probability calculated on this gate before the suppression.

In the example above, the events Evt1, Evt2 and Evt3 will be removed, and the gate And2 will be replaced by
an event (with the same name), giving this example below:

However, there are some requirements to respect before launching this command.

• Every event or gate taken from the descendants of a confidential gate, must have in their ancentry a confidential
gate, before reaching the root of the tree (except if the root is confidential). To illustrate this requirement, the
example given below shows the case where Evt3 has an ancentry of confidentials gates and nonconfidential

User Manual 119 / 133

 gates. This example returns an error: If the Evt3 is suppressed, the gate And3 loose one of his child, which
is not possible.

The Evt3 has for ancestry the gate And2 and And3. But any of the ancestry of the gate And3 are confidential.

In this example (see below), the Evt3 has always a confidential gate in his ancestry. This is what we want, since
its suppression will not affect any others gates (And4 is going to be removed since And3 is confidential).

The result of the command in this example gives a tree with And1 as the root, with the events And2 and And3
as childs of the root.

User Manual 120 / 133

• The confidential gates must have an assigned probability, necessary to create the event's law, after the gate
has been replaced by an event. Just launch the computations on the tree, to update the probabilities on the
confidential gates.

12.3. RTF File

A model can also be saved in RTF format. This allows the saved model to be reloaded in WORD to insert the
graphical part of the model in any document. To do this, go into menu File - Save in RTF file....

There is another way to insert model in a report.

Select the part of the model, copy it, and paste it in Microsoft WORD or other software.

12.4. Input data

When the input data for the computation engine is generated, it can be saved. This type of file has the ".don"
extension. These files can therefore be modified using a text editor then reloaded to launch computations on them
(for example). This action should be made only by advanced user.

12.5. Results
Computation results can be saved in different formats:

User Manual 121 / 133

1. Export of a table in particular in .csv format:

2. Export entire set of results:

• Save result file: saves the contents of the Results tab (.xml format).
• Advanced report: generates reports using style sheets.
• Save standard output: saves the contents of the Info tab (.txt format).
User Manual 122 / 133
 • Save engine data file: saves the data file sent to the computation engine (.txt format).
• Save as XML spreadsheet 2003 (XMLSS): saves all the results tables in an XML format compatible with
Microsoft(r) Excel 2003 and later versions.

12.6. Curves
For each curve drawn, the points which have been computed in CSV format can be saved. This list of points can
then be used to draw new curves or to perform further computations.

User Manual 123 / 133

13. Printing
For printing, you have several commands at your disposal in the File menu File:

• Page setup

• Print

• Save in RTF file

13.1. Page setup

The Page setup function allows you to choose the page orientation, the size of the margins, etc.

13.2. Print
The Print function allows you to export .pdf document pages. Graphics are exports in a vector graphics format
in order to scale it without deterioration. All data table and the results of calculations can be also exported. Here
is the window of configuration of the printing:

User Manual 124 / 133

1. Printing properties

Printing properties tab gives the possibility of configuring what will be visible on all the printed pages. This
tab contains three parts: the header, the body and footers. Below here is an example which illustrates the various
zones on the PDF:

Each of three text fields is configurable. The user can so modify the police, the style, the color and the positioning
of the text in the zone. He can also configure the zone itself by allocating a background color and a frame. A click-
right on the text field shows a contextual menu: Display settings

User Manual 125 / 133

Several options are added:

• Print file name in the header at the left top.

• Print date in the header at the right top.

• Print a border in the graphic pages allows to bound visually the pages of graphs besides of the page of
printing. Warning: this frame can be in conflict with a possible frame defines in the zone of body of page

• Watermark allows to seize an image to be printed on a background with colors which will be limited. The
image can go out of the zone of body of page

• Print number of page in the footer in the lower right. The first number can be chosen to start not at 1.

2. Pages

Pages tab allows to select the page will be printed.

User Manual 126 / 133

• Print all the page : all the pages will be printed

• Print current page :only the current page will be printed.

• Print selection : select pages and groups will be printed. Select recursively the pages option is a help in order
to select quickly sub-pages.

3. Data

Data tab allows to select date will be printed.

Each sub-tab will represent a table in the PDF document. The title and the print order of these tables can be
modified.

By default all the types of data are represented (one by sub-tab). The upper right buttons allow to add it or to delete
it. To note that we can print several times of the same data type in different tables. The data table can be filter
using the usual filter. The Column manager can be also used.

4. Calculation

Calculation allows to select the calculation will be printed.

User Manual 127 / 133

Each sub-tab will represent a part containing the various tables present in the results of the calculation. This part
has a modifiable title and order which is the order of printing of the various results.

By default all the calculation results are represented (one by sub-tab). The upper right buttons allow to add to it
or to delete it.

5. Example

To give an overview of a PDF printing:

User Manual 128 / 133

13.3. Save in RTF file
The Save in RTF file... function initially gives access to a window called Printing properties . Then to another
called Information . And thirdly, a window is displayed allowing you to choose the folder in which the RTF file
is to be saved.

When you select the Save in RTF file function, the first box to appear is that shown above. You can then select
your preference: Print border, Print filename, Print page number and/or Print date.

Secondly, an Information window appears. It allows you to indicate whether you wish to print the current view,
print the current page or print the whole document.

User Manual 129 / 133

14. Options of GRIF - Fault Tree
Tools - Application Options menu opens a window containing the following tabs:

14.1. Executables
Executables tab enables to specify path to external executables :

• Mail client : Enable you to set the mail client to use

• Automatically open PDF files : Specifies if PDF reports must be opened with generation.
• Moca-RPC path : Specifies Moca version 12 path.

14.2. Options
Options tab enables to tune application behavior :

• Save the options of the current document as default options in the application : Save options of current
doc as application default options.
• The application manages the default options of the documents, apply the default options to the current
document : Apply -Application options- to current document.
• Delay of automatic document saving (in minutes) : Delay of automatic document saving (in minutes). A null
value disables automatic saving.
• Number of undo : Specifies number of possible undo/redo.
• Number of recent files : Specifies number of files in recent files list.
• Window display : Enables separate tables (external) or linked tables (internal).
• Columns to be resized in tables : Enables to specify the columns on which space will be taken for resizing.
• Ask for confirmation before deletion outside the input area : When deleting an element in the graphic tree
or in the table date, a dialog box will be displayed.
• Manage new names to avoid name conflict : Tries to avoid name conflict, creating new objects whose name
is unique (when pasting for example).
• Synchronize view with tables : Select objects in tables (on the right) when they are selected in view.
• Synchronize view with explorer : Select objects in explorer (on the left) when they are selected in view.
• Ask for confirmation if closing with close button : When closing with the button at the top-right of a dialog
box, the software will ask for a confirmation. Use OK or CANCEL buttons if you don't want to confirm closing.
• Modification tracking when saving : When saving, if tacking is activated, you can add a comment about
modifications made on the document.
• In results window, display description instead of default name : Enable displaying of Comment/Description
of objects in results window. I can be better than a default name may be without meaning.

14.3. Graphics
Graphics tab enables to modify GUI look :

• Use Windows look and feel : Use the look and feel of your operating system instead of java look and feel
(GRIF restart is needed).
• Element Zoom : Changes graphics size.
• Outline for dynamic fields : Object outline configuration (line color, line width, background color, ...).
• Font for dynamic fields : Enables font configuration (color, size, italic ...) for information that are displayed
under objects.
• Outline for commentaries : Object outline configuration (line color, line width, background color, ...).
• Font for commentaries : Enables font configuration (color, size, italic ...) for information that are displayed
under objects.
• Font for groups : Enables font configuration (color, size, italic ...) for information that are displayed under
objects.
• Activate cross hair : Activate cross hair which enables object alignment.
• Activate smoothing for texts : Activate anti-aliasing (smoothing) for texts, it can slow the display.
• Activate smoothing for images : Activate anti-aliasing (smoothing) for images, it can slow the display.

User Manual 130 / 133

• Activate tooltips : Activate tooltip-system.
• Hide not computed additional info : Additional information under nodes won't be displayed if it is related to
a not computed result. It prevents from multiple "?" display.
• Condensed display in rectangles : Description, ID and probability will be displayed in the remark rectangle.
• Automatic layout after resize : Apply the automatic layout command after each remark resizing command.
• Use gate symbol for automatic layout : Use only symbol of gates to center during auto-layout, and not the
total gate (the area dashed if selected).

14.4. Digital format

Digital format tab enables to customize digits display :

• Display of parameters : Specifies the display of parameters (number of digits, ...).

• Use this digit formatter for the result. : Use this digit formatter for the saving or the display of the result.

14.5. Laws
Laws :

• Apply modification factor on laws : Enables probability modification factor. If checked, an "Apply factor"
check-box will be available at the bottom of law editing panel.
• Unit choice for law parameters. : Activate unit selection for each parameter in law edition windows.

14.6. Computations / Results

Computations / Results :

• Light Batch : Deletes files used for each computation of batch computations, it decreases memory/disk use.
• Limit the numbers of points stored in the results : Limit the numbers of points stored in the result file.
Consecutive points will be deleted if they have the same values.
• Preferred frequency unit : Unit that will be used for displaying result which dimension is "frequency" in -
main view, - data tables, - and some result synthesis.If no unit is displayed (especially in detailed results) the
unit is (h-1).
• Preferred duration unit : Unit that will be used for displaying result which dimension is "duration" in - main
view, - data tables, - and some result synthesis.If no unit is displayed (especially in detailed results) the unit is (h).

14.7. Events
Events tab enables to change gates/reports display. :

• Font set-up : Enables font configuration (color, size, italic ...) for information that are displayed under objects.
• Font set-up for commentaries : Font used to draw text in the commentaries rectangle above the symbol.
• Outline set-up : Object outline configuration (line color, line width, background color, ...).
• Outline set-up when allocation is not respected : Object outline configuration (line color, line width,
background color, ...).
• Display name : Enables to display name or not
• Display number : Enables to display number or not.
• Display description : Enables to display description or not.
• Display attributes : Enables to display attributes or not.
• Display allocation : Display allocation and percentage compare to the "true" probability at the last computation
time.
• Display target : Display target in information of the object.
• Display default value for attributes : It displays the default value of attribute for which no value is defined.
• Display law : Enables to display law or not.
• Display CCF : Enables to display or not commons causes failures.
• Use a default law : Enables the specification of a law that will be used when creating objects (instead of built-
in Exponential 1E-3).
• Default law : Default law that will be used when creating objects.
• Additional information : Enables to display additional information (results of computation)

User Manual 131 / 133

• Outline of reference rectangle : Thickness of the rectangle drawn on events that have repeated events. Selecting
0 draws nothing.
• Repeated event transparency : Transparency of the grey layer applied on repeated event. Value between 0
and 0.5. 0 means no grey layer.
• Remark height : Height (in pixels) of the remark-frame at the top of events. Default value is 40.
• Remark width : Width (in pixels) of the remark-frame at the top of events. Default value is 100.
• Max event threshold for auto layout : Maximum number of event per line. If more than that, the automatic
layout will create 2 lines of events under the gates.

14.8. Gates/Shortcuts
Gates/Shortcuts tab enables to change gates/reports display. :

• Font set-up : Enables font configuration (color, size, italic ...) for information that are displayed under objects.
• Font set-up for commentaries : Font used to draw text in the commentaries rectangle above the symbol.
• Outline set-up : Object outline configuration (line color, line width, background color, ...).
• Outline set-up when allocation is not respected : Object outline configuration (line color, line width,
background color, ...).
• Display name : Enables to display name or not
• Display number : Enables to display number or not.
• Display description : Enables to display description or not.
• Display K/N : Enables to display K/N or not.
• Display shortcut location : Display the set of reports for a gate.
• Display allocation : Display allocation and percentage compare to the "true" probability at the last computation
time.
• Display target : Display target in information of the object.
• Display attributes : Enables to display attributes or not.
• Display default value for attributes : It displays the default value of attribute for which no value is defined.
• Display shortcut source page : Display page of the matching gate/event under shortcut.
• Additional information : Enables to display additional information (results of computation)
• Remark height : Height (in pixels) of the remark-frame at the top of gates. Default value is 40.
• Remark width : Width (in pixels) of the remark-frame at the top of gates. Default value is 100.

14.9. Curves
Charts tab enables to change charts drawing :

• Set graphics borders : Add borders to charts.

• Set generic values borders : Add borders to generic values under charts.
• Display grid : Display grid on curves area.
• Display legends : Display legends under curves.
• Drawing zone transparency : Activate curves area transparency.
• Graphic transparency : Activate charts transparency.
• Title size : Specifies charts title font size.
• Generic values size : Specifies generic values font size.
• Point size : Specifies point size on curves.
• Coordinates size : Specifies coordinates font size.
• Legend size : Specifies legends font size.

14.10. Import
The Import tab contains options that configure the import of data or models :

• Automatic cutting of imported files : Automatically cuts of tree when a new file is imported (*.xml or *.dag)
• Automatic cutting when length greater than : When automatic cutting, N is the number of gates after which
the link is cut.
• Use ID as key for conflict management : Use the ID instead of the name as key to detect conflicts. If an event
of the current document has the same ID as an imported event, its name will be updated to the name of the
imported one.

User Manual 132 / 133

User Manual 133 / 133