Greg_Deckler's avatar
Greg_Deckler
Icon for Community Champion rankCommunity Champion
7 years ago

Mean Time Between Failure (MTBF)

This Quick Measure is an update to my Mean Time Between Failure (MTBF) measure that I developed in this article: https://community.powerbi.com/t5/Community-Blog/Mean-Time-Between-Failure-MTBF-and-P...
Mathematical
Other
Totals
Anonymous's avatar
Anonymous
Not applicable
6 years ago

Hi Greg_Deckler, 

 

Thanks for the awesome post. 

However, with the previous calculated column for uptime, MTBF measure can be filter by period. Let's say for example, I don't want machine7 MTBF for the whole period, I just want machine7 MTBF for a particular peiord only. How can I tweak your codes to suit my needs?

Also, is it possible to get separate measure for just Uptime, which is the same as Uptime calculated column?

  • Greg_Deckler's avatar
    Greg_Deckler
    Icon for Community Champion rankCommunity Champion
    6 years ago

    Should be possible, would need more information. Definitely been through a lot of edits with this one, the best version is in my book which fixed a bunch of bugs and other little things that I found annoying. I can reference that version but I believe some of the fixes were related to being able to properly slice the metric by things like date ranges, etc.

    • Anonymous's avatar
      Anonymous
      Not applicable
      6 years ago

      Hi Greg_Deckler 

       

      Thanks for the reply. Please find the sample attached. 

      You are right, 

      • MTBF measure is dynamic (react to particular causes) but not to date ranges.
      • The original MTBF is based on calculated column of uptime, not dynamic (doesn't react to particular causes) but respond to date ranges. 
      • I am assuming MTBF measure1 is similar to original one? It responds to date ranges but I don't get the same value as original MTBF. 

      I think my issue could be solved if I can create a separate uptime measure (the one I created is not right?).

       

      Another separate issue in my data is eliminating multiple alarms. My data source is the daily csv logs which contain thousands of events. Some sites' event duration last more than a day (>24hr) but they are captured as separate entry in the next-day csv logs. I kind of manage to eliminate those events (via Critical Alarm v2) but I am not sure that is fail safe outside of this sample data. 

      There are also dummy events (downtime 0hr) which I'd like to eliminate as well. Eliminating them would reduce the total critical alarm, which is vital in calculating correct mtbf and availability.