[SystemSafety] Another Bloomberg article

Fri Nov 15 15:30:48 CET 2019

 Hi Bertrand.>>What about 1oo2D architectures ?Great question.   Can you point me to a working group focusing on real-time diagnostics, analytics, and reporting? :)
    On Thursday, November 14, 2019, 04:13:20 a.m. EST, RICQUE Bertrand (SAFRAN ELECTRONICS & DEFENSE) <bertrand.ricque at safrangroup.com> wrote:  

What about 1oo2D architectures ?

| 
RESTRICTED
  |

| 
Bertrand RICQUE
Safety and security standardisation Expert
Customer Support Manager
Optronics and Defence Division/Customer Support 
Safran Electronics & Defense 

P +33 (0)1 58 11 96 82 � M +33 (0)6 87 47 84 64
bertrand.ricque at safrangroup.com
102 Avenue de Paris
91300 MASSY FRANCE 
www.safran-electronics-defense.com
  |

| 

  |
| 
| 

  | 

  | 

  | 

  |

 |

De : systemsafety [mailto:systemsafety-bounces at lists.techfak.uni-bielefeld.de]De la part de Brent Kimberley
Envoyé : jeudi 14 novembre 2019 00:59
À : systemsafety at lists.techfak.uni-bielefeld.de; Eric Burger <Eric.Burger at georgetown.edu>
Objet : Re: [SystemSafety] Another Bloomberg article

Two element systems tend to scan for match and trip on mismatch.  It's the operator's job to execute contingencies such as steering-around/voting-out failed element(s).  i.e. train the operator(s) and ensure they remain in control.

On Wednesday, November 13, 2019, 12:47:58 p.m. EST, Eric Burger <eric.burger at georgetown.edu> wrote:

I’m hoping again the reporter got it wrong. Two systems? Space shuttle had four so you could have a 3-against-1 vote. I suppose having three to have a 2-against-1 vote is OK for non-space applications. However, two is insane. A failure of the backup system results in the primary being taken down? Really?

On Nov 13, 2019, at 4:06 AM, Peter Bishop <pgb at adelard.com> wrote:

Quote from Bloomberg article:  "Delays in Boeing Max return began with near crash in simulator"

https://www.bloomberg.com/news/articles/2019-11-08/delays-in-boeing-max-return-began-with-near-crash-in-simulator?fbclid=IwAR1R6_y2DtwhHi5wq9kaOCRLMEcwE2cxIeAu_-aivpR2k_swaZZxYTQr5ok

-------

By contrast, the 737 Max had two separate computers. One operated the flight systems and another was available if the first one failed, with the roles switching on each flight. But they interacted only minimally.

Boeing decided to make the two systems monitor each other so that each computer can halt an erroneous action by the other. This change is an important modernization that brings the plane more in line with the latest safety technology but raised highly complex software and hardware issues..

--------

I don't think this change is a good idea at all.

Who trusts whom when two computers think each other is wrong?
How do you address the fact that each computer is asynchronous with slightly different sensor values and timing which might cause the two computers to diverge at decision thresholds?

Either:

1) Change the hardware to improve fault detection within each computer
(i.e. it fails silent if it gets scrambled) e.g. each computer is upgraded to a lockstep processor pair with hardware cross-comparison.

2) Change the system to a TMR design so failure of a single processor can be tolerated.

The first option would be the easiest from a software perspective.

Peter Bishop
 --     Peter Bishop Chief Scientist Adelard LLP 24 Waterside, 44-48 Wharf Road, London N1 7UX    Email: pgb at adelard.com Tel:  +44-(0)20-7832 5850    Registered office: 5th Floor, Ashford Commercial Quarter, 1 Dover Place, Ashford, Kent TN23 1FB Registered in England & Wales no. OC 304551. VAT no. 454 489808    This e-mail, and any attachments, is confidential and for the use of the addressee only. If you are not the intended recipient, please telephone 020 7832 5850. We do not accept legal responsibility for this e-mail or any viruses. 
_______________________________________________
The System Safety Mailing List
systemsafety at TechFak.Uni-Bielefeld.DE
Manage your subscription: https://lists.techfak.uni-bielefeld.de/mailman/listinfo/systemsafety

_______________________________________________
The System Safety Mailing List
systemsafety at TechFak.Uni-Bielefeld.DE
Manage your subscription: https://lists.techfak.uni-bielefeld.de/mailman/listinfo/systemsafety
 #
" Ce courriel et les documents qui lui sont joints peuvent contenir des informations confidentielles, être soumis aux règlementations relatives au contrôle des exportations ou ayant un caractère privé. S'ils ne vous sont pas destinés, nous vous signalons qu'il est strictement interdit de les divulguer, de les reproduire ou d'en utiliser de quelque manière que ce soit le contenu. Toute exportation ou réexportation non autorisée est interdite Si ce message vous a été transmis par erreur, merci d'en informer l'expéditeur et de supprimer immédiatement de votre système informatique ce courriel ainsi que tous les documents qui y sont attachés."
******
" This e-mail and any attached documents may contain confidential or proprietary information and may be subject to export control laws and regulations. If you are not the intended recipient, you are notified that any dissemination, copying of this e-mail and any attachments thereto or use of their contents by any means whatsoever is strictly prohibited. Unauthorized export or re-export is prohibited. If you have received this e-mail in error, please advise the sender immediately and delete this e-mail and all attached documents from your computer system."
#

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.techfak.uni-bielefeld.de/mailman/private/systemsafety/attachments/20191115/5a4f34c8/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.gif
Type: image/gif
Size: 623 bytes
Desc: not available
URL: <https://lists.techfak.uni-bielefeld.de/mailman/private/systemsafety/attachments/20191115/5a4f34c8/attachment-0006.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.gif
Type: image/gif
Size: 1349 bytes
Desc: not available
URL: <https://lists.techfak.uni-bielefeld.de/mailman/private/systemsafety/attachments/20191115/5a4f34c8/attachment-0007.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image005.gif
Type: image/gif
Size: 1310 bytes
Desc: not available
URL: <https://lists.techfak.uni-bielefeld.de/mailman/private/systemsafety/attachments/20191115/5a4f34c8/attachment-0008.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image006.gif
Type: image/gif
Size: 1374 bytes
Desc: not available
URL: <https://lists.techfak.uni-bielefeld.de/mailman/private/systemsafety/attachments/20191115/5a4f34c8/attachment-0009.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.gif
Type: image/gif
Size: 1477 bytes
Desc: not available
URL: <https://lists.techfak.uni-bielefeld.de/mailman/private/systemsafety/attachments/20191115/5a4f34c8/attachment-0010.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.gif
Type: image/gif
Size: 448 bytes
Desc: not available
URL: <https://lists.techfak.uni-bielefeld.de/mailman/private/systemsafety/attachments/20191115/5a4f34c8/attachment-0011.gif>