<div dir="auto"><div dir="auto">New York Times audio:</div><div dir="auto"><span style="font-family:sans-serif"><a href="https://dts.podtrac.com/redirect.mp3/rss.art19.com/episodes/b01d6007-c8be-4d9b-8650-b9fa930d4802.mp3">https://dts.podtrac.com/redirect.mp3/rss.art19.com/episodes/b01d6007-c8be-4d9b-8650-b9fa930d4802.mp3</a></span><br></div><div dir="auto"><br></div><div dir="auto">Quote:</div><div dir="auto"><br></div><div dir="auto">In testimony before a House committee on Wednesday, Dennis A. Muilenburg, Boeing’s chief executive, said, “If we knew everything back then that we know now, we would have made a different decision.” Congress is investigating two crashes of Boeing 737 Max jets which killed 346 people, cost the company billions of dollars and raised new questions about government oversight of aviation. So what did Boeing executives know about the dangers of the automated system implicated in the crashes — and when</div><div dir="auto"><br></div><div dir="auto">* Published: 10/31/19 2:54:29 AM</div><div dir="auto"><br></div><div dir="auto">* Episode feed: The Daily - <a href="http://rss.art19.com/the-daily">http://rss.art19.com/the-daily</a></div><div dir="auto"><br></div><div dir="auto"><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Jul 9, 2019, 8:42 AM <a href="mailto:paulz@ieee.org">paulz@ieee.org</a> <<a href="mailto:paulz@ieee.org">paulz@ieee.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div style="font-family:Helvetica Neue,Helvetica,Arial,sans-serif;font-size:13px"><div id="m_-1292360670179223030ydp1f899ebeyqtfd43337">
<div dir="ltr"><div><p style="margin-bottom:0in;line-height:100%">
The saga at Boeing is portrays a very different mindset from my
experience with makers of medical devices.</p>
<p style="margin-bottom:0in;line-height:100%">Every one is very
aware that patients lives are effected for bettor or worse by the
company product. If that isn’t enough, bad outcomes result in lots
of lawyers. I’m sure you have seen ads on television, “If you or
a family member was injured...”</p>
<p style="margin-bottom:0in;line-height:100%">First every
significant step in the development from original requirements to
production testing must be carefully documented. Makes it very easy
to go back and figure out what happened. If the company does not
have a good documentation system, FDA will not approve the product.
The whole design process will need to be repeated with better
documentation.</p>
<p style="margin-bottom:0in;line-height:100%">Another important
part of the process is FMEA, Failure Modes and Effects Analysis.
Lots of brainstorming to try to list every possible thing that could
go wrong, the consequences and how severe it is to the patient.
Items with any small possibility of serious problems to the patient,
the doctor or the equipment must be analyzed and ways found to
mitigate it.
</p>
<p style="margin-bottom:0in;line-height:100%">To use a
hypothetical example from the airline industry. Some planes have a
thing called angle of attack sensor. If the sensor just gives an
indication to the pilot, and the plane has lots of other
instruments, perhaps pilot training can tell him when to ignore AoA
and how to use other information to safely fly the plane. And the
documentation system will track the training requirement to the
actual training.</p>
<p style="margin-bottom:0in;line-height:100%">Just speaking, not
that this would happen, but suppose the AoA sensor was connected to
an automated flight control system and a bad sensor input could
possibly, under remote circumstances, cause the plane to crash. This
is not acceptable.
</p>
<p style="margin-bottom:0in;line-height:100%">Mediation would
require multiple sensors, using different technologies. There might
be an undiscovered weakness in one kind of sensor. Software will
have a requirement that a bad sensor input will not cause the plane
to crash. Maybe the requirement includes checking the altitude
before pointing to the ground. Again the documentation system will
track this from software requirements to final validation.</p><br clear="none"></div></div></div><div id="m_-1292360670179223030ydp1f899ebeyahoo_quoted_3209447985"><div style="font-family:'Helvetica Neue',Helvetica,Arial,sans-serif;font-size:13px;color:#26282a">
</div>
</div></div></div>_______________________________________________<br>
conspire mailing list<br>
<a href="mailto:conspire@linuxmafia.com" target="_blank" rel="noreferrer">conspire@linuxmafia.com</a><br>
<a href="http://linuxmafia.com/mailman/listinfo/conspire" rel="noreferrer noreferrer" target="_blank">http://linuxmafia.com/mailman/listinfo/conspire</a><br>
</blockquote></div>