Re: [SystemSafety] Functional hazard analysis, does it work?

From: SPRIGGS, John J < >
Date: Tue, 19 Jan 2016 08:20:03 +0000


Matthew,
In my opinion, if you have one of those FHA procedures that start with, “What can go wrong in my system and what is the effect if it does?” then you need to augment it with something else. I think it would be better to start with, “What do we not want to happen?” and then explore whether those things can arise from your system (considering people, procedures, not just ‘platforms’ and the environment).

John
https://www.linkedin.com/pulse/accidents-twenty-five-year-old-cheese-john-spriggs

From: systemsafety-bounces_at_xxxxxx Sent: 19 January 2016 00:43
To: systemsafety_at_xxxxxx Subject: [SystemSafety] Functional hazard analysis, does it work?

A question to the list.

Does the process of functional hazard analysis 'work' in terms of identifying all functional hazards that we are, or should be, interested in?

The way the FHA process is defined in the various standards seems IMO to be very reductionist in nature, fine for identifying the specific consequences of a single functional failure mode, but what about functional interactions, multiple functional failures, the interaction of modes with functions and so on.

The background to this is that the project I'm working with is about to commit to a significant campaign of 'FHA'-ing. So we're engaged in a little bit of professional navel gazing about the efficacy of the technique before we commit to the campaign.

--
Matthew Squair

BEng (Mech) MSysEng
MIEAust CPEng

Mob: +61 488770655<tel:%2B61%20488770655> Email: MattSquair_at_xxxxxx Website: www.criticaluncertainties.com<http://criticaluncertainties.com/>



If you are not the intended recipient, please notify our Help Desk at Email information.solutions_at_xxxxxx immediately. You should not copy or use this email or attachment(s) for any purpose nor disclose their contents to any other person.

NATS computer systems may be monitored and communications carried on them recorded, to secure the effective operation of the system.

Please note that neither NATS nor the sender accepts any responsibility for viruses or any losses caused as a result of viruses and it is your responsibility to scan or otherwise check this email and any attachments.

NATS means NATS (En Route) plc (company number: 4129273), NATS (Services) Ltd (company number 4129270), NATSNAV Ltd (company number: 4164590) or NATS Ltd (company number 3155567) or NATS Holdings Ltd (company number 4138218). All companies are registered in England and their registered office is at 4000 Parkway, Whiteley, Fareham, Hampshire, PO15 7FL.





The System Safety Mailing List
systemsafety_at_xxxxxx Received on Tue Jan 19 2016 - 09:20:29 CET

This archive was generated by hypermail 2.3.0 : Tue Jun 04 2019 - 21:17:07 CEST