Jump to content

Fail-safe: Revision history


For any version listed below, click on its date to view it. For more help, see Help:Page history and Help:Edit summary. (cur) = difference from current version, (prev) = difference from preceding version, m = minor edit, → = section edit, ← = automatic edit summary

(newest | oldest) View (newer 50 | ) (20 | 50 | 100 | 250 | 500)

12 June 2024

1 May 2024

10 April 2024

20 March 2024

13 March 2024

13 January 2024

  • curprev 17:3317:33, 13 January 202447.36.95.241 talk 18,495 bytes +5 Changed reference to a “specific failure” in the first sentence to failure of “the design feature”. The concept of fail-safe is NOT specific failure related. To be fail safe the protection must occur in ALL cases of the design feature failing. This provides for the analysis of the system to break it into its smallest individual features as well as combinations of fundamental features which result in higher level features and fail safe each. undo

16 December 2023

25 November 2023

14 October 2023

25 September 2023

24 September 2023

12 July 2023

22 May 2023

7 April 2023

28 January 2023

17 January 2023

16 December 2022

2 August 2022

15 June 2022

6 May 2022

12 April 2022

9 November 2021

7 November 2021

12 October 2021

12 June 2021

12 April 2021

15 December 2020

28 November 2020

24 November 2020

29 July 2020

24 June 2020

  • curprev 22:3522:35, 24 June 2020Quercus solaris talk contribs 17,840 bytes +2 Really "recovery procedures" in the context of this sentence, as a third choice besides the first two, has to mean contingency plans; it doesn't mean "system recovery" of the failed system, for example, in this context. (That may happen too, but Plan B starts happening first.) undo

18 June 2020

1 April 2020

30 March 2020

2 February 2020

30 November 2019

17 November 2019

16 November 2019

19 September 2019

3 September 2019

(newest | oldest) View (newer 50 | ) (20 | 50 | 100 | 250 | 500)