# Functional Safety Suite 7.0
User’s Guide

#### 11Menus and Commands

##### 11.1Generals

The descriptions of models or events are immediately changed whenever you type a key in the description field. All other numerical or text values are changed after pressing ‘Enter’ only.

Note that not all commands or properties will be available in a specific situation. Typically only those possibilities, that make sense and result in a valid model are offered. In the case that an error occurs when executing a command, an error message is displayed in the status bar or in the message window.

##### 11.2The File Menu

This menu contains all commands related to the project, its packages, models and libraries. Most commands are also available in pop-up menus that open when pressing the right mouse button in the project members tree.

###### 11.2.1New Project

If there is an open project this will be closed. If necessary you are asked to save data. After that a dialog will appear where you are asked for a name of the new project. Finally an empty project will be created.

###### 11.2.2Open Project

If there is an open project this will be closed. If necessary you are asked to save data. After that a dialog will appear where you can select the project to be opened. All libraries and models referred in the project file will be opened and indicated in the ‘Project Members’ tree.

###### 11.2.3Close Project

The current project is closed. If necessary you are asked to save changes in the project, libraries or models.

###### 11.2.4Project Properties

A project properties dialog window will open where you can set the project properties. Refer to section 3.4 for details.

###### 11.2.5Create new Package

A new package is created by File – Create new Package. You will be asked for the name of the new package. A sub-directory with the given name will be created in the project directory, and the local library file will be created.

###### 11.2.6Import Package

A package created in one project can be imported to the currently open project. When selecting File – Import Package, a dialog will open up where you can select the package directory, and enter a new package name, see figure 72.

Figure 72: Import package dialog

The package will be copied to the open project, using the entered name.

###### 11.2.7Create new Model

A new model is created by File – Create new Model. The Create New Model Dialog will open, where you can select the package the new model shall belong to, and the name and type of the new model, see figure 73.

Figure 73: The create new model dialog

###### 11.2.8Add existing Model

When selecting File – Add existing Model, a dialog will appear where you can select the model file to be added to the project. Per default, only model files with extension `.ignore` will be displayed. Anyhow you can also select other model files, including models already belonging to the project.

Figure 74: Add existing model dialog

You can select the package to which the model shall be added, and enter a name for it.

If not all generic basic events referred by the imported model’s basic events are available in the open project, new generic basic events with the referred names are created with default data. You will have to add correct data to these cases before the model can be evaluated. If you forget to do so, the next calculation will show wrong results.

If the model to be added refers generic basic events from another package, you should import the generic basic events before via Library – Import from other library or project, see section 11.4.6. This command should be used for the local library, since the missing generic basic events should be added to the local library. Since the import function for generic basic events will not override generic basic events already existing in the library, the import must be executed before adding the model (before creation of default generic basic events).

###### 11.2.9Remove active Member

The reference to the model presented in the active tab will be removed from the project, the tab will be closed. If necessary you are asked to save data of this model.

If there are references from other models to the one to be removed, you are asked for confirmation, since these model cannot be evaluated anymore afterwards.

###### 11.2.10Rename active Model

The model presented in the active tab can be renamed by File – Rename active Model. A dialog will appear asking you for a new name.

Figure 75: Rename model dialog

If there are links to this model, you’ll have to update the links (i. e. the generic basic event) manually.

###### 11.2.11Move active Model

The model presented in the active tab can be moved to another package by File – Move active Model. A dialog will appear asking you for a new package.

###### 11.2.12Duplicate active Model

The model presented in the active tab can be duplicated by File – Duplicate active Model. A dialog will appear asking you for the package and the name of the duplicate, see figure 76.

Figure 76: Duplicate model dialog

Note that if you duplicate the model to another package, the generic basic events of the original local package won’t be reachable anymore.

###### 11.2.13Save active member

Saves the model currently displayed in the graphics tab. If this is for the first time after creation, you’ll be asked for a location and file name. The file extension is automatically appended.

###### 11.2.14Save All

All models, the library and the project are saved if changed. Note that a project, that has not been saved after the latest modification, is marked with an asterisk ‘*’ in the window title. An unsaved model is marked with an asterisk ‘*’ in the title of its graphics frame.

###### 11.2.15Save As

The model in the active tab is saved as a new file. A dialog will appear asking you to select a location and file name. The reference in the project is replaced by the new file. The old file will remain unchanged.

###### 11.2.16List of recently used projects

A list of recently used projects is presented. Selecting one is similar to File – Open Project, only that no dialog will appear.

###### 11.2.17Exit

If necessary you are asked to save changes in the projectthe library or in models. After that the application is terminated.

##### 11.3The Edit Menu

The Edit menu contains all commands related to changing the structure of a model.

The most often needed actions are directly available as button in the menu bar. For some actions keyboard commands (short-cuts) exist, see the entries in the Edit menu.

###### 11.3.1Undo last change

The last ten actions can be withdrawn. Here an action can be either an edit-action as stated above or a change of a model or generic basic event property in the properties window on the left. So this command is not only related to the structure of a model. The tool-tip text always informs about the next action of the undo-action.

###### 11.3.2Redo last undo

All undo actions can be withdrawn.

###### 11.3.3Add condition

To add a new condition in an event tree, select the hazard or the previous conditionand press Edit – Add Condition. A new condition will be created and inserted after the marked condition.

###### 11.3.4Add case

After selecting a condition in an event tree, a case can be added to the condition by Edit – Add Case. Each case refers to a generic basic event, which determines its probability. Typically the immediate event model is used, allowing to directly enter the probability p. But also all other models that deliver a unavailability can be used, including links. When adding a case, the new case will refer to the last generic basic event in the library.

###### 11.3.5New Damage

After selecting a damage in an event tree, its generic damage can be replaced by a new generic damage. The user is asked for a name of the new generic damage.

Note: To use an already existing generic damage, just select it in the General Properties panel.

###### 11.3.6Set Select Mode

The default mode of the architecture editor. You can select one component part, or any combination of complex components and corners and lines of nets. Note that Cut/Copy and Paste is only possible if exactly one complex component is selected.

###### 11.3.7Add Component Mode

Select Add Component Mode and click to a position in the architecture. A dialog will open, see figure 77.

Figure 77: Create architecture component dialog

Select class and name of the new component.

###### 11.3.8Select Draw Net Mode

In order to connect pins of architecture components, select this mode. Start drawing by click on a pin or an existing net line or corner, and click for a new corner or at another pin, line or corner. A line can be finished by double-click at any point on the grid.

###### 11.3.9Convert to Fault Tree

Derive a fault tree for the current architecture. See section 6.6 for details.

###### 11.3.10Add Failure

In a complex component model, a new failure mode (component event) is created and added to the right.

###### 11.3.11Add Block Serial

In a reliability block diagram a new block is created and added in series to the selected block(s).

###### 11.3.12Add Block Parallel

In a reliability block diagram a new block is created and added in parallel to the selected block(s).

###### 11.3.13Add Tree Basic Event

A new basic event is created below the currently selected gate in a fault tree. By default the newest generic basic event is used therefore, hence the generic basic event created with the last call of Library – New Generic Basic Event (see section 11.4.1) or Library – Duplicate Generic Basic Event (see section 11.4.4).

###### 11.3.14Add Gate

A new default gate is created below the currently selected gate in a fault tree. You can add basic events to this gate by Edit – Add Basic Event, Library – Create Generic Basic Event or Edit –Paste.

###### 11.3.15Convert to TRANSFER-IN

The selected block of a reliability block diagram is converted to a TRANSFER-IN block.

###### 11.3.16Convert to Gate

The selected basic event in a fault tree is converted to a gate (maintaining the name and description).

Note: You should change the name of the gate to avoid multiple different events (here a basic event and a gate) having identical names.

###### 11.3.17Convert to Subtree

A new fault tree is created whose top event is the marked gate. The marked gate is replaced by a new gate of type TRANSFER-IN. The name and the description of the former gate are preserved. You can change the names of the gates and the description of the top event of the new fault tree manually. Remember to change the reference in the new TRANSFER-IN gate if you change the name of the top event of the new fault tree.

###### 11.3.18Convert Fault Tree to Reliability Block Diagram

A new reliability block diagram is created for the active fault tree. The new reliability block diagram is added to the same package. The name of the reliability block diagram will be that of the fault tree, extended by `_RBD`.

###### 11.3.19Convert Reliability Block Diagram to Fault Tree

A new fault tree is created based on the active reliability block diagram. The new fault tree is added to the same package. The name of the fault tree will be that of the reliability block diagram, extended by `_FT`.

###### 11.3.20Convert Branch to Markov Model

A Markov model is generated for the branch, topped by the selected gate. The fault tree itself remains unchanged.

The new Markov model gets the same name as the fault tree plus the name of the gate. It is directly added to the project, thus you can open it by clicking on its name in the ‘Project Members’ tree.

You will be asked whether the Markov model shall contain ‘direct chains only’ or ‘complete chains’. A complete conversion to a Markov model considers, that the system’s state can in fact “jump” from one (yet incomplete) chain to another chain, until a final state is reached. Please see section 9.5.2 for an example. The internal conversion can get quite complex even for not very large fault trees. Therefore you should consider creating the direct Markov chains only.

Converting a fault tree to a Markov model is a very complex task. For most fault trees, this function will do all the work perfectly. However it is generally not possible to model all restorations correctly, because a fault tree doesn’t provide information about the restoration strategy. This function will create restorations that usually fit to most systems, however you should check the restoration edges manually.

###### 11.3.21Convert Reliability Block Diagram to Markov Model

A new Markov model is created based on the active reliability block diagram. The new Markov model is added to the same package. The name of the Markov model will be that of the reliability block diagram, extended by `_MM`.

See section 11.3.20 for more information.

###### 11.3.22Import Markov Chains

It is possible to import previously created Markov chains. Since all states and edges of the Markov model will be deleted when importing Markov chains, this command is only available, if the active Markov model contains maximum 2 states.

The file containing the Markov chains can be created by Export – Export Markov Chains if a gate is selected in a fault tree. Since it is an XML file, it can also be created manually, or based on the export of another program.

###### 11.3.23Add Edge

In order to add an edge in a Markov model, select the source state, then select Edit – Add Edge, then click on the target state. An edge referring to the last generic basic event in the library will be created.

###### 11.3.24Add State

You can add states to a Markov model by Edit – Add State and clicking the mouse at the position you want to set the state. A state will be placed to the nearest grid point. A unique name will be automatically assigned to the new state. At each grid position, only one state can be placed, so if there is a state at the nearest position on grid already, no state will be added.

###### 11.3.25Adjust State Names and Positions to other Model

Sometimes you might want to adapt the state names and/or state positions to those of another Markov model with similar structure. This is achieved with this command: In the first step, the structure is analyzed in order to identify similar states. Two states of two Markov models are similar, if there is at least one Markov chain, that leads to both of them. A state identified as being similar gets the name of its counterpart in the reference model. However since other chains leading to these two states might differ, there might be multiple similar states, and thus multiple states that would be renamed to the same name. In this case, the new name is appended automatically by a number, so that it becomes unique. In the second step, each state having the same name as a state in the reference model is set to the position of its counterpart in the reference model.

###### 11.3.26Delete

If a case of an event tree is selected, this case will be deleted from the condition.

If a component part is selected, which is not mandatory for the class of the architecture component, and which is not connected to a net, it will be deleted.

If a s

If a condition of an event tree is selected, the condition will be deleted, but only if it doesn’t contain any cases.

In an architecture, the selected elements will be deleted. If a component part is selected, it will only be deleted if it is not connected to any net and if this is allowed according to the class of the architecture component.

If a failure mode (component event) of a complex component is selected, it will be deleted.

If a basic event of a fault tree or a block of a reliability block diagram is selected, it will be deleted if there remain enough inputs of the parent gate (see section 7.4 for how many inputs a gate of a certain type needs).

If a gate is selected, it will be deleted and its input events will be shifted to its parent gate.

If an edge is selected, it will be deleted.

If a state is selected, it will be deleted including all edges connected to it.

###### 11.3.27Delete Component or Selection

A selection of architecture components and/or nets can be deleted with Del.

If a component part is selected, the complete architecture component can be deleted by Ctrl+Del.

###### 11.3.28Delete Branch

The branch topped by the selected gate will be deleted.

###### 11.3.29Cut

The selected case, condition, component event, basic event, state or the branch topped by the selected gate will be deleted.

A deleted component event, basic event, state or branch is stored in the background so that it can be pasted somewhere later on. A case or condition cannot be pasted, therefore the ‘cut’ command is the same as a ‘delete’ for these events.

###### 11.3.30Copy

The selected damage, component event, basic event, state or the branch topped by the selected gate will be copied to a background memory. It can be pasted somewhere later on, see below.

###### 11.3.31Paste

If a event tree is active and a damage is selected, and a damage has been copied before, the generic damage of the selected damage is replaced by that of the copied damage.

If a complex component is active and a component event is selected, the component event is pasted as new event to the component.

If a fault tree is active and a gate is selected, a basic event or branch copied or cut before is pasted as new input to the selected gate.

If a Markov model is active and a state is selected, an edge copied or cut before will be added starting in the selected state. Click to another state in order to set the target of the edge just as for the Edit – Add Edge command.

If a Markov model is active, no state is selected, and a single state has been copied or cut before, it will be added after clicking to an empty position.

If a Markov model is active, no state is selected, and multiple states and edges have been cut or copied before, they will be added to the active Markov model below or at the right of the existing states.

###### 11.3.32Paste Serial

The saved block(s) will be added in series to the selected block(s) of the reliability block diagram.

###### 11.3.33Paste Parallel

The saved block(s) will be added in parallel to the selected block(s) of the reliability block diagram.

###### 11.3.34Move Left/Move Right

In an event tree the selected condition is moved one position right or left.

In a fault tree the selected basic event or the branch topped by the selected gate is moved one input to the left or to the right.

Note: This command is not available for children of inhibit gates.

In a Markov model the selected state is moved to the next free position left or right of its current position.

In a reliability block diagram the selected blocks are moved left or right. This is equivalent to changing the sequence of the inputs of an OR-gate.

###### 11.3.35Move Up

In a fault tree the selected basic event or branch topped by the selected gate is moved one level up. If the parent of the selected event is an inhibit gate or will get too few inputs the command is ignored.

In a Markov model the selected state is moved to the next free position over of its current position.

In a reliability block diagram the selected blocks are moved up. This is equivalent to changing the sequence of the inputs of an AND-gate (or another conjunction gate).

###### 11.3.36Move Down

In a Markov model the selected state is moved to the next free position under its current position.

In a reliability block diagram the selected blocks are moved down. This is equivalent to changing the sequence of the inputs of an AND-gate (or another conjunction gate).

##### 11.4The Library Menu

###### 11.4.1New Generic Basic Event

A dialog will appear, where you can enter the name of the new generic basic event. If no generic basic event with the entered name already exists, a new generic basic event will be created with default data.

If a basic event of a fault tree or an edge is marked, or a case of an event tree, the new generic basic event will be assigned to it automatically.

If a gate is marked, a new basic event referring to the new generic basic event will be created and added to the gate if possible.

###### 11.4.2Rename Generic Basic Event

If a basic event or an edge is marked, or a case of an event tree, the name of the referred generic basic event can be altered. A dialog will appear, where you can enter a new name.

If a generic basic event with the new name already exists, you are asked for another name.

The operation is executed on the existing generic basic event, no new generic basic event is created. Therefore the names of all basic events referring to this generic basic event in all models will change.

###### 11.4.3Move Generic Basic Event

Move the selected generic basic event to another package. A dialog will open where you can select the new package.

###### 11.4.4Duplicate Generic Basic Event

Duplicate the selected generic basic event to another package. A dialog will open where you can select the new package and the new name.

###### 11.4.5Remove unused Generic Basic Event (GBEs)

Generic basic events are not deleted automatically (you can see this by checking the name list in the properties panel of a basic event of a fault tree or an edge). Thus if you remove a model from a project or delete basic events from a model, it will happen, that the library contains generic basic events not used anymore in any model of the project. When this menu action is selected in the library view, these unused generic basic events are removed from the library.

###### 11.4.6Import from other library or project

If you select this action in the library view, a dialog will appear, where you can select a library file (`.lib` or `.gbes`). The generic basic events defined in the selected file will be copied to the currently shown library.

Those generic basic events with names already existing in the new library will not be copied. The messages in the output window will provide detailed information.

###### 11.4.7Export to CSV file

If you select this action in the library view, a dialog will appear, where you can enter a file name. All generic basic events of the library will be saved in a text file, one event per line. Line breaks in the description will be replaced by spaces.

##### 11.5The Zoom Menu

Selects the zoom factor of the models and exported bitmap graphics (`.png`) of the models.

##### 11.6The Calculate Menu

###### 11.6.1Calculate Model Values

The probabilistic values of the model in the active tab are calculated. This includes the calculation of all referred sub-trees or linked models. For details and parameters related to calculation, see the model type specific sections in this guide.

###### 11.6.2Calculate importances

This action is only available after successful calculation. A dialog will appear, where you can select which importances shall be calculated, see figure 78.

Figure 78: The importances dialog

For explanations of the available importances, see appendix A.

The results are shown in a separate window, see figure 79.

Figure 79: The importances window

The values can be exported as (complete) HTML file, as a HTML snippet (to be included in another HTML file) or as CSV file (in order to import it further evaluate them e. g. in a spreadsheet program).

###### 11.6.3Determine and show Prime Implicants (Minimal Cut-Sets)

This action is only available after successful calculation. The prime implicants for unavailability, occurrence rate or unreliability (depending on the selected value in the fault tree evaluation properties dialog) of the top event of the fault tree or reliability block diagram presented in the active tab are determined. After the prime implicants have been determined, they will be shown in a new window.

A prime implicant consists of one or several conjuncted basic events. The basic events are separated by asterisks ‘*’. Each implicant is stated in a separate line. For coherent fault trees, the prime implicants are identical to the minimal cut-sets. For non-coherent fault trees, prime implicants are not canonical, i. e. there are multiple equivalent sets of prime implicants in general.

As in the name fields of basic events, the first dot (‘.’) separates name and suffix. Multiple parts of the suffix created by TRANSFER-IN gates are also separated by dots. The part after the first dot is the name of the highest level TRANSFER-IN gate, followed by lower TRANSFER-IN gate names down to the original suffix of the basic event.

The values can be exported as (complete) HTML file, as a HTML snippet (to be included in another HTML file) or as CSV file (in order to import it further evaluate them e. g. in a spreadsheet program).

Note: The number of lines shown in the window and exported to a HTML file is limited to the number stated in the project properties dialog, see section 3.4.3.1. The CSV file export will include all prime implicants.

###### 11.6.4Check to SIRF Rules

The qualitative fault tree is checked against [SiRF] rules.

###### 11.6.5Show Chart

After performing a transient (time-variant) evaluation, the temporal variation of the calculated values can be visualized in a separate window.

Figure 80: A chart window

By default, the values selected in the model-specific dialog are displayed. Optionally, additional values might be available for display, depending on the type of the model and the evaluation parameters.

All axis can be scaled and zoomed.

The presented graphics can be exported to a vector graphic (`.svg`) or a bitmap (`.png`) file, select File – Export ... in the menu of the chart. Note that in vector graphics format, the graph data is exported with original resolution, so a later printout will have a very high quality (if not reduced by the later processing).

###### 11.6.6Show Component Chart

After performing the evaluation of a complex component, the temporal variation of the calculated values can be visualized in a separate window. See section 10.6 for more details.

##### 11.7The Export Menu

###### 11.7.1Create Report

Create a report, see appendix B.

###### 11.7.2Update Report

Update an existing report, see appendix B.

###### 11.7.3Export Graphic as PNG

The graphic of the currently shown model is saved as portable network graphic (`.png`) in the `graphics` sub-directory below the package directory. The selected zoom factor is applied as well as the current markings, but the output is not limited to the visible part. The resolution will be twice the resolution of the display.

###### 11.7.4Export All Graphics as PNG

The graphics of all models, for which a tab exists in the model graphics tab pane, are saved as portable network graphic files (`.png`) in the `graphics` sub-directory below the package directory.

###### 11.7.5Export Graphic as SVG

The graphic of the currently shown model is saved as scalable vector graphic (`.svg`) in the `graphics` sub-directory below the package directory. Markings are not preserved. This format can be imported by most vector graphic programs. It can also be displayed by most browsers.

###### 11.7.6Export All Graphics as PNG

The graphics of all models, for which a tab exists in the model graphics tab pane, are saved as scalable vector graphic files (`.svg`) in the `graphics` sub-directory below the package directory.

###### 11.7.7Export Basic Events List

Saves a list of all generic basic events of the currently displayed library in a text file (without parameters).

The name of each generic basic event is followed by a list of models in which it is used.

After that for each model it is stated, which of the generic basic events contained in this library it uses.

###### 11.7.8Export Transient Values

After performing a transient evaluation, the calculated data can be saved to a text file. Its extension is `.tdf`. Each time step is a line, values are separated by ‘;’. The first line in the file indicates the model, the second line the meaning of each column.

###### 11.7.9Export Final Tree

Save the final tree of the active fault tree as new model.

The final tree is the fault tree, in which all COMBINATION gates and TRANSFER-IN gates have been replaced by the adequate branch, and all REDUCED-COMBINATION gates and PRIORITY-AND gates have been replaced by a link to another (temporary) model.

Note: If the fault tree includes REDUCED-COMBINATION gates or PRIORITY-AND gates, the exported final tree cannot be evaluated, since the temporary models created for these gates are not exported.

###### 11.7.10Export Markov Chains

This function will create the Markov chains, that are equivalent to the fault tree branch topped by the selected gate. Creation of these chains is done in multiple steps. You may select, which step’s result shall be exported.

Figure 81: The dialog to select, which chains to save.

You will be asked whether the Markov chains shall contain ‘direct chains only’ or ‘complete chains’. A complete conversion to a Markov model considers, that the system’s state can in fact “jump” from one (yet incomplete) chain to another chain, until a final state is reached. Please see section 9.5.2 for an example. The internal conversion can get quite complex even for not very large fault trees.

###### 11.7.11Export States and Edges List

Saves a list of all states and edges of the Markov model in a text file, including their descriptions.

###### 11.7.12Export Final Markov Model

Exports the Markov model, that has been created internally for the last evaluation of the active Markov model. You may add the exported Markov model to the project manually by File – Add Markov Model. In that case, you might want to adjust the state names and positions to the original model by Edit – Adjust State Names and Positions to other Model, see section 11.3.25.

##### 11.8The Help and Configuration Menu

###### 11.8.1Help

The content of this document is presented in HTML format.

###### 11.8.2Set User Interface Look&Feel

Select your preferred Look&Feel, depending on which User Interface Manager are installed on your machine.

Figure 82: The dialog to select the user interface Look&Feel.

Restart of Functional Safety Suite will be necessary in order to activate the new Look&Feel.

###### 11.8.3Set License File

Specify the path to the license file here.

Note: You must restart Functional Safety Suite to load the new license file.

###### 11.8.4About

A window opens, indicating the version of Functional Safety Suite and some parameters of the license.

##### 11.9The tool bar

All frequently used commands are also available as buttons in the tool bar. The tool bar is context sensitive.

.
Table 6: Toolbar buttons
Icon | Command
| Close project and open another project
| Save active model
| Save all
| Project properties
| Create new model
| Add existing model
| Open the architecture symbol editor
| Architectures: Set select mode
| Architectures: Add a new architecture component
| Architectures: Select draw net mode
| Undo last change
| Redo last undo
| Event trees: Add condition to event tree
| Event trees: Add case to event tree
| Event trees: Create new damage for event tree
| Fault trees: Add tree basic event or component event
| Fault trees: Add gate event
| Fault trees: Convert to gate
| RBDs: Add Block Serial
| RBDs: Add Block Parallel
| Markov models: Add edge
| Markov models: Add state
| Delete event, branch or state
| Cut marked event, branch or state
| Copy marked event, branch or state
| Paste event, branch or state
| Create new generic basic event
| Rename generic basic event
| Duplicate generic basic event
| Zoom in
| Zoom out
| Calculate model values
| Calculate importance of basic events
| Show chart with transient values
| Show chart with component values
| Determine and show prime implicants (minimal cut-sets)

##### 11.10Menus and Commands of the Symbol Editor

.
Table 7: Toolbar buttons
Icon | Command
| Create a new symbol of the selected type in the selected library
| Create a new text in the symbol
| Create a new rectangle in the symbol
| Create a new ellipse or circle in the symbol
| Create a new line or polygon in the symbol

APPENDIX