Of course CAPEX will effect OPEX, or it should…or will it? The idea makes sense, however, at what point will a piece of equipment cost you more to maintain than it would cost to simply replace that piece of equipment? Should a refurbish be considered? How should a new plant be configured for the highest cost benefit? Not properly designing a system or not being willing to spend the money to replace equipment at the right interval could be costing you. By modelling your system in easy to use tools you can make logical decisions as well as justifying these decisions.
Although some might have superstitious feelings about Friday the 13th. We have chosen to hold a webinar to get you away from all the coffee talk. For Friday the 13th we have come up with a special preview of our next version of Reliability Workbench which is also version 13 (specifically 13.0.2). Join us for this special webinar, on Friday October 13th at 12 PM Eastern Time, to get an early look at the new features that have been added. We have added significant changes to the report viewer interface, updated Prediction stands, data linking to the Allocation module, new DLL functions, expanded IEC 61508 calculations for both the Fault Tree and FMECA modules, a new Fault Tree failure model, and a brand-new results dialog for the FMECA module, complete with ISO 26262 functionality. There’s plenty to get excited about.
Please register by clicking: HERE
As always if you have any questions, comments or feedback please let me know.
Best Regards, Jeremy
Although we post a lot of web demos that cover analytical topics related to the Reliability Workbench let’s remember that the Availability Workbench is probably the most powerful tool of its kind on the market. There is a good chance someone you know is using the Availability Workbench!
Availability Workbench is used to optimise maintenance and spares policies, predict system availability and throughput and estimate life cycle costs. It includes well known modelling methods such as FMECA, Reliability Block Diagram Analysis and Fault Tree Analysis.
The following web demo is a high level overview of the software, if you have any questions or need more information on the software please let me know:
Following feedback from users, it seems as though we can never post enough FaultTree+ web demonstrations. Included is general overview of our popular FaultTree+ software. In addition to an explanation on how the tool is used we have also added some useful information on import/export, search functions, customising the grid view, calculation options, approximation methods, Markov….ext.
As always if you have any questions on the web demonstration or need additional informaiton on our software products please feel free to contact me.
For anyone that has spent a bit of time in reliability the term Weibull distribution has probably come up, or should have come up. It is named after Swedish mathematician Waloddi Weibull, who was the first to describe Weibull in length in 1951. Although Waloddi didn’t actually come up with the math for Webiull, the formulas and even an application had been applied years before, he was the first to describe it and won the honour of having the Weibull distribution named after him.
Weibull Analysis is used to analyse historical failure data and produces failure distributions that we use during a system simulation.
The Weibull Analysis module of Availability Workbench analyses historical failure and repair data by assigning probability distributions which represent the failure or repair characteristics of a given failure mode.
The failure distribution assigned to a given set of times to failure (known as a Weibull set) may be assigned to locations in the RCMCost location hierarchy or failure models in the AvSim module.
The Weibull Analysis Module analyses times-to-failure and time-to-repair data using the following distributions:
1-Parameter Weibull Distribution
2-Parameter Weibull Distribution
3-Parameter Weibull Distribution
I have included a recorded webinar giving a general Webull overview. We of course do not go into detail on the formulas used. If you would like additional information please contact me: email@example.com
Secret might be the wrong word to use here, it could be a matter of just asking myself or technical support the right questions. Even if you’ve been using Reliability Workbench, Availability Workbench, AttackTree+, or Network Availability Prediction for years, you’re probably still finding new features and tips and tricks to help you out in the software. Maybe one day you discovered a time-saver and thought to your self “what else can this software do to make my day easier?”
While there are plenty of helpful features in Isograph’s software to make your day easier, perhaps none is so powerful, incredibly useful, and so under-utilized as Plugins and the DLL. These features allow you to extend the power of Reliability Workbench, Availability Workbench, Attack Tree, and NAP tools to absurd heights. From creating macros for accomplishing tedious tasks, to automating fault tree construction, and even adding new features to the software that we haven’t even thought about, the Plugins and DLL can do it.
As always if you have any questions or need additional information on our products please feel free to contact me
801 610 0045
SAP can be a great tool for collecting data, however, that data often gets over looked or instances get looked at one by one. Often engineers wonder what to do with all of that great data collected in SAP? Using the Availability Workbench’s certified SAP portal one can import data regarding PM intervals, spares, labour or any other fields that are applicable to the availability, maintenance or reliability of your system.
I have recorded a recent internal meeting regarding the options and benefits offered by Availability Workbench SAP portal. As always please let me know if you have any questions or need additional information on the portal, firstname.lastname@example.org
We have collected commonly asked questions by our 1000’s of users. Some of the questions that we’ll answer along the way include:
Why do my cut sets show gate names with an asterisk next to them?
OK, so I enter a “failure rate.” Is that failures per… hour? Year? Geological epoch? What are the units?
This fault tree takes ages to calculate. Can I speed it up?
Fault tree uses approximation methods for solving the tree? Do I have any control over that?
My computer crashed and I lost 3 hours of work! Can I create automatic backups of my project?
What if I want to see MTTF on my fault tree, instead of Q?
I have a plotter. How do I print the whole tree on one piece of paper?
Can I force scientific notation in the results?
What if I don’t want to delete the inputs to a gate when I delete the gate?
I really love the font Comic Sans. Can I use that in my fault tree?
Also, chartreuse is my favorite color. How do I set that as default?
How do I set default options, so I don’t have to reset these every time I start a new project?
We’ll also look at the useful and often-overlooked Report Options. Did you know that you can force the diagram to be black & white for printouts? Or make the fault tree symbols bigger? Or change the order of the pages?
If you are looking for LOPA information chances are you probably already know what a LOPA is. For any of you are not familiar with a LOPA study, it could mean any number of things. However, for us a LOPA is an acronym meaning: Layer Of Protection Analysis. A LOPA can be a good and logical beginning, or addition, to your PHA (Probabilistic Hazard Analysis) studies. Which leads us to our next acronym ETA (Event Tree Analysis). Event tree analysis diagrams can be an effective approach to tackling your LOPA studies. Since this is probably easier viewed than described please take the time to watch our webinar addressing this topic: