What’s New

Reliability Workbench 15.0.2

1. The FMECA module now has an option in the project view tab to show the full FMECA structure in
the left-hand window. There is also an option to show or hide effects in both windows.
2. New FMECA standard templates have been added to project options. They are:
AIAG/VDA(Design), AIAG/VDA(Process), AIAD/VDA(MSR) and Hazard Assessment.
3. Users may now create diagrams in the FMECA module. Diagrams may be organised using diagram
groups. Diagram elements and connections may have a block or function assigned to them.
4. The FMECA module now has an option in the project view tab to show or hide the causes text field in
dialogs.
5. Requirements may now be assigned to blocks and functions as well as failure modes.
6. Higher function links and lower function links reports fields have been added for FMECA failure
modes.
7. An importance precision cut-off field has been added to project options for RBD/FT/ET. The
Importance cut-off value determines the precision of Fussell-Vesely and Birnbaum importance
values. If the calculated importance value does not meet the specified cut-off criteria, then the
importance value is set to zero. Note that for the Birnbaum importance measure the cut-off value is
compared to an event's Birnbaum value divided by the system probability value.
8. DAL and ASIL values may now be set for CCF Models. This allows DAL or ASIL decomposition in the
SSA module to consider CCF events.
9. 1 / k0 for 61709 prediction standard is now calculated to full precision.
10. The SN29500 prediction standard has 2 new parameters added for capacitors and inductors allowing
a self-heating temperature rise to be directly entered by the user rather than using the Rja x P
formula.
11. Requirements may now be attached to functions in the SSA module.

Reliability Workbench 15

1. A verification tab has been added to the ‘End effects’ dialog in FMECA.
End effects may represent system hazards and users may now verify that a safety system has been designed to achieve a tolerable hazard rate.
Verification can be performed by RBD, fault tree analysis or Markov.
Tolerable hazard rates are determined by the severity ranking (or for non-ranking FMECA the severity category).
For severity rankings the project options allow user to specify a tolerable accident rate.
The tolerable hazard rate = tolerable accident rate * mitigation parameters.
For the severity category the tolerable accident rate = target risk / weight.
A SIL value is determined based on the tolerable hazard rate only (independent of failure mode frequency) (EN50129 railway standard). SIL boundaries are set in the project options.

2. For FMECA ranking preference users can now set an option in the verification tab to force the program to set the end effect action results occurrence rank based on the verified hazard rate.

3. In the Failure mode and end effects dialogs calculated data should actively change as users make changes to dependent parameters. For example selecting the ‘Use verified hazard rate…’ check box should change the results occurrence ranking. Changes to mitigation parameters or linking a verification object should change the SIL. For component modes changing the occurrence rank should change the criticality rank where appropriate.

4. A responsibility field has been added to the new requirements objects in FMECA.

5. FMECA Hazard Assessment and FMEA Hazard Assessment default grid layouts have been added.

6. FMECA criticality matrix plots have a new option to display only end effects. These plots now cater for < 10 rankings being set by the user.

7. In the FMECA module users may now enter failure rates at the component level when using the ranking preference methods. The ‘Use rates for occurrence ranking’ option is selected in the project options dialog.

8. FMECA text fields have been made multiline and larger in dialogs.

9. FMEA (AIAG/VDA) action priority values are now automatically calculated for failure modes. Users may also set a MSR preference in the project options dialog. Detection is renamed Monitoring if this option is selected.

10. An additional option has been added to the FMECA View options allowing users to show Ids in failure
net and function net trees.

11. A requirements object has been added to the FMECA module. Requirements may be attached to failure modes.

12. Options have been added to the FMECA ‘Library’ menu to transfer severities and requirements to and from a project.

13. A ‘Local Effects’ field (2000 characters long) has been added to the failure mode properties. A new phrase category of ‘Local Effect’ has been created. Local effects phrases (max 255 characters) may overwrite or append the existing local effects text in the failure mode dialog.

14. The ‘Save Phrase’ facility (FMECA and SSA modules) now allows the user to select a sub-section of the text in a field before hitting the Save Phrase button. The selected text will then be used for the phrase.

15. Batch append of projects and paste operations from libraries will now maintain external datalinks for the failure models of source failure models (RBD, fault tree and event tree).

16. A Residual probability analysis function has been added for both the RBD and FT modules. This analysis method is based on the EASA CS-25 standard.

17. Modifications have been made to the Prediction module to allow users to comply with the IEC 61709 standard. Two new project options have been added that allow users to apply the 61709 piT constant and dormant failure method when using the SN 29500 standard. The SN 29500 standard now allows users to enter reference failure rates for individual components as an option.

18. A FMECA dangerous failure rate preference option has been added to the SSA project options verification tab. If selected, this option uses dangerous failure rates from FMECA blocks and modes for verification. Also, if the ‘rank preference’ option in FMECA is selected the failure rate used will be the failure rate associated with the rank in the project options.

19. Selection of a verification object link in the grid control (SSA and FMECA module) to navigate to the fault tree/rbd etc. no longer keeps a hand cursor showing after the link has been activated.

Report Designer
1. A SQL query header can be added to all custom queries using SQL Server data sources. This allows
the user to create common table expressions, table variables and DECLARE variables for use in the
SQL main query.
2. PDF files created by the Report Designer now meet the PDF/A-2 standard. This requires that the fonts
used in a published report can be embedded in the PDF file.
A dialog has been provided to display the fonts on a machine that support font embedding in PDF files,
these fonts can be filtered by supported character set.
A warning is issued at completion of the publication process to show which fonts (if any) could not be
embedded.
3. Value labels can now be displayed on graph data points. This applies to all graph types apart from pie
and pareto types.
The value label appearance is fully configurable, including alignment, border, font, fill and data format.
4. The query controls now display the SQL Server version for SQL Server data sources.
5. A warning is issued when a query will fail because it is processed as a derived table wrapped by a
further SELECT query.
This extra SELECT query is to enable the correct functioning of the column filters.
6. The Syntax Check and Format Query function in the SQL Wizard now performs the query validation
step prior to performing the format of the query. N.B The query validation step checks for incorrect
column names and T-SQL functions - these are not validated by the syntax check.
7. A warning is issued when using the SQL Wizard Syntax Check and Format Query function that an
comments will be removed when the format is performed. This warning is only issued when there are
comments in the query.
8. The Syntax Check and Format Query function in the SQL Wizard now performs the syntax check and
format according to the version of the connected SQL Server version.
9. The Publish to PDF settings dialog has been simplified by removing the WinAnsi encoding option. This
has been made possible by improving the performance of processing Unicode fonts.