A Fault Tree is a hierarchical model used to analyze the probability that an event will occur. The event is typically a low probability, high consequence risk or outcome such as a failure of a critical system or a breach of security. DPL 9 Fault Tree provides all the tools needed to build graphic representations of large-scale problems gracefully so you can understand the risks involved in a given system and how they relate to one another. This leads to a more accurate risk assessment and a quantitative method for assessing actions that can reduce risk. The DPL Fault Tree shown graphically breaks down the breach of a secure facility.
DPL 9 Fault Tree is a Straightforward yet Powerful tool for building and analyzing Fault Trees A Fault Tree is a hierarchical model used to analyze the probability that an event will occur. The event is typically a low probability, high consequence risk or outcome such as a failure of a critical system or a breach of security. DPL 9 Fault Tree provides all the tools needed to.
Fault tree verification, traceability, minimal cut set generation, minimal cut set analysis, Common Mode Analysis (what about Common Cause Analysis. Use of CAFTA FTA Software, Laptop Computer (if held here), and Printer (if held here) Soft copy handouts (over 200 related valuable reference documents).
Fault tree analysis. CAFTA software, which is used by many of the US nuclear power plants and by a majority of US and international aerospace manufacturers. Fault trees import from CAFTA, Isograph Fault Tree + and RAM Commander. Version and revision control. Sprint galaxy s3 modem download. High level security and role-based permissions.
Powerful Fault Tree Modeling Tool
Request a free 30-day Trial of DPL 9 Fault Tree -- an intuitive yet powerful tool for building and analyzing Fault Trees
DPL Fault Tree Trial
DPL Fault Tree has all the features of our DPL Professional version, plus features for building and analyzing Fault Trees.
Fault Tree modeling constructs include:
AND gates
OR gates
NOT gates
Probability value nodes
Dependent events
Advanced Features and Outputs include:
Remington woodmaster model 742 manual. Module embedding: A fault Tree module can be embedded within a fault tree if it's convenient to split a larger, complex model into several smaller parts. Modules can also act as custom gates that can appear multiple times in the same fault tree.
In the figure shown, the DPL Fault Tree analyzes the risk of a power failure at a critical industrial site. One of the events that could affect the reliability of the power system is a failure of transmission controls (bottom left corner). The Controls event in the Power Failure fault tree will depend on a module reference to the Utility Control System (UCntrl) fault tree (inset).
A DPL Fault Tree can be standalone or incorporated into a DPL Decision Model via fault tree modules. The motivation for a fault tree analysis is usually some kind of decision. If you know how likely a system failure is, you will have a better idea of how much to spend to prepare for the consequences. Further, if you know the modes of failure, you can assess how much certain risk mitigation measures will help. When these decisions aren't simple enough to be considered implicitly, you can embed the fault tree in a decision model and use influence diagrams and decision trees to explicitly analyze the decisions. Via realtek ac97 audio drivers for mac.
Circuit diagrams: A circuit diagram is an alternative way of looking at the structure of a fault tree. The system will fail if the 'circuit' is broken -- that is, if all the lines from the 'power source' on the right to the 'light bulb' on the left are cut. A circuit diagram provides a graphical view of the qualitative aspects of the system, such as redundancies and single points of failure. In DPL, you can switch between the tree and circuit diagram views of a fault tree at the press of a button.
Sensitivity analysis based on Partial Derivatives and Maximum Impact: Partial derivatives are a form of sensitivity analysis that offers insights into the relative importance of the basic events in the fault tree. The partial derivative tells you how much a change in the probability of each basic event affects the probability of the top event. The maximum impact of each basic event shows how much the probability of the otp even can be reduced by setting the probability of a given basic event to zero.
Minimal cut sets: With a fault tree, there should be some set of basic events such that if each event in the set occurs, the top event will occur. Such a combination of events is referred to as a 'cut set'. A minimal cut set is a cut set such that if any basic event is removed the remaining events will not be a cut set. The minimal cut sets, along with their associated probabilities and costs, help identify the most likely or least costly ways for the top event to occur.
The division live wallpaper. Time series intervals: Often the probability or costs data associated with events in a fault tree evolve over time. In DPL Fault Tree you can set up time intervals and define time series events or values to capture this evolution and generate a Time Series output to visualize how risks and/or costs change over time.
You can also embed a vector valued fault tree in a multi-period decision model with uncertainty and generate a time series percentile chart that will show you the range (10th, 50th, and 90th percentiles) of the cost of risk reducing actions over a given time period.
Advanced System Safety Software
AFTV v.1 FAQ, last updated on 9/11/2008.
What is AFTV?
AFTV means Advanced Fault Tree Viewer and does just that. It works on fault tree and database files exported as text from CAFTA™ and Microsoft Access®.
Do you have screenshots of AFTV?
Yes. There are multiple screenshots in the User Manual.
Who uses AFTV?
Anybody who needs to share or view fault tree files from CAFTA™. Since CAFTA™ is mainly used for System Safety application then AFTV should be used mainly by System Safety Analysts or anyone else who needs to review their work but doesn’t need to learn or purchase CAFTA™.
What are the minimum hardware requirements?
OS: Microsoft® Windows® 98/ME/2000/XP/Vista® CPU: 1.0 GHz Pentium® 3 Processor or Equivalent Hard Drive: 5 MB available RAM: 512 MB Video: Hardware Acceleration with OpenGL® support Input: Keyboard and Wheel Mouse
Is the transition to AFTV easy when one knows CAFTA™?
Yes. AFTV uses many of the CAFTA™ shortcuts. CAFTA™ users won’t be lost. However, you'll have to learn the commands specific to AFTV.
What Operating System is supported?
AFTV is currently only available for Microsoft® Windows® 98/ME/2000/XP/Vista® but the underlying technology is designed to be cross-platform. Porting AFTV to other Operating Systems will be considered if the need arises.
AFTV does not really edit fault trees, right?
Yes, this is only a fault tree viewer. AFTER (available mid-2009) will extend AFTV to support fault tree generation, computation, simplification, and many other functions. You need AFTER if you want to create and compute fault trees or to generate reports.
How do I download and install AFTV?
Download and execute the AFTV installation file available at www.safeaircraft.com or use the link at the top of this page.
How do I uninstall AFTV?
The AFTV setup also creates an uninstallation wizard. Either select “Start” “Programs” “AFTV” or use the Control Panel “Add or Remove Programs” to run the uninstall program.
What is the license?
AFTV is distributed as a freeware program. It is available for use at no cost, for the benefit of all. The AFTV license is shown for approbation during the installation and is also installed in your main AFTV directory (typically “C:Program FilesAFTV”), see file 'license.txt'.
Francois Besnier. I have been working as a system safety engineer and consultant for the last 14 years. My resume is available at http://www.besnier.net.
How do I report a bug?
Try saving a session (Shift+Ctrl+S) right before or after the bug occurs. Then e-mail the session file, along with a description of the bug and its context to [email protected].
I can't see the text that well, what's going on?
You probably need to turn on the Full-Scene Anti-Aliasing (FSAA) of your video card. To be sure, compare any of the screenshots from the User Manual against your own view of AFTV. If FSAA is not turned on, the difference is obvious. Turning on Full-Scene Anti-Aliasing (FSAA) should not significantly slow down the GPU and the display will look much nicer. You will also be able to display more legible cells per display area. For an NVIDIA video card, click on 'NVIDIA Settings' on the right bottom corner of your screen then on menu 'Performance & Quality Settings', 'Anti-aliasing settings' to turn on the GPU multisampling. For any other video card, please refer to your video card documentation.
Why can’t I convert CAFTA™ files?
First you need to make sure that the PC used for the conversion has both CAFTA™ and Microsoft Access® installed. Once the CAFTA™ files are exported as text, they can be distributed and viewed freely with AFTV. If AFTV is installed on a PC with both CAFTA™ and Microsoft Access® installed, then importing CAFTA™ files into AFTV should be as simple as using the AFTV menu “Convert/Import a CAFTA model.. (Ctrl+I)”. However, this part of AFTV is quite dependent of your CAFTA™ and Microsoft Access® installation and has been tested only with one installation of CAFTA™ 5.2 and Microsoft Access® 2003. So, it may not properly work with some other configuration. To facilitate user customization, the CAFTA™ converter “AFTVconverter.exe” has been separated from the rest of the code and its source is provided. If you are unable to make the “Convert/Import a CAFTA model.. (Ctrl+I)” menu work, then you have two options:
Option 1
Adapt the AutoIt Script AFTVconverter.au3 located in the main AFTV directory to your own configuration, compile and replace AFTVconverter.exe. AutoIt v3 is available free of charge at http://www.autoitscript.com/autoit3/
Option 2
Manually convert the files using the following procedure: Let’s say that you want to export a fault tree file SYSTEM.caf with its associated database SYSYEM.rr or SYSTEM.mdb to an AFTV fault tree model called SYSTEM. With CAFTA™: Open SYSTEM.caf Select menu “File”, “Save as…” then type “SYSTEM.fre” and select Free-formatted file (*.fre). Clean up the database using menu “Project”, “Purge Database” With Microsoft Access®: Open SYSTEM.rr or SYSTEM.mdb. 1) Right click on the “BE” table and select “Export…”. Select the same directory as FTA.fre The file name to export to is SYSTEM_BE.txt
Cafta Tool
Save as type “Text Files (*.txt, *.csv, *.tab, *.asc)”
Cafta Fault Tree Analysis
Click 'Export' In the Export Text Wizard, make sure that the default “Delimited” is selected then click 'Next'
Still in the Export Text Wizard, make sure that the default “Comma” is selected Check “Include Field Names on First Row” Click “Finish” 2) Right click on the “GT” table and select “Export…”. The file name to export to is SYSTEM_GT.txt. Follow the same procedure as for the “BE” table. 3) Double click on the 'TC' table. If it is not empty then export the 'TC' table like you just did for tables 'BE' and 'GT'. The file name to export to is SYSTEM_TC.txt
Cafta Fault Tree Software
The set of the text files SYSTEM.fre, SYSTEM_BE.txt, SYSTEM_GT.txt, and eventually SYSTEM_TC.txt constitutes a single AFTV fault tree model that can now be opened and viewed.
Do you have examples of CAFTA™ and AFTV files?
Yes. See the “sample” directory (typically located at “C:Program FilesAFTVsample”) which has two examples of CAFTA
Fault Tree Analysis Software Free
™ files (version 5.2) with their associated exported text files to AFTV.
This FAQ does not anwer my question..
Fault Tree Analyzer
First, check that your question is not already answered in the AFTV User Manual. If so, send your question to [email protected].