Search
this site: 


While
mathematically being simpler than FTA and RBD, markov requires
more abstraction from the reliability analyst: Instead of breaking the system down into evident pieces (functional blocks or faults), markov requires the system to be divided into so called states. Every markov state represents the complete system in a specific system state. Like RBD, markov diagrams consist of blocks. Each block represents a specific system state. System states should be named as precisely as possible. The quantitative information, namely the transition rates (# of transitions per time unit) is kept in the connectors (arrows). A twin engine aircraft is a very good example in order to demonstrate the strength of markov. This example is also used in the FTA and the RBD paragraphs for the purpose of showing the limitations of these methods. It is worthwhile to look a little bit closer to the markov twin engine aircraft diagram. All transition rates are in units of [per hour]. 