Introduction to System Safety Risk Assessment
In this 'Introduction to System Safety Risk Assessment', we will pull together several key ideas.

First, we'll talk about System Safety. This is safety engineering done in a Systems Engineering Framework. We are doing safety within a rigorous process.

Second, we're talking about Risk Assessment. This is a term for putting together different activities within another process. This process may be basic, or it might be quite sophisticated, as illustrated, below.

The Risk Assessment Process

Third, and finally, we will put all this together into a System Safety Program. This is hinted at in the diagram, above, but a real system safety program needs to do a lot more than this. It needs to tie into the project it supports, to systems engineering, to resources, quality, V&V, etc. Designing such a program is complex, so we typically follow a standard, like Mil-Std-882E.

You can hear more about this in the introductory video, below.

https://youtu.be/80irBJjmzxI
Introduction Video

This post is part of a series:

- This Post is the Intro to the System Safety Risk Assessment Programs Course.

- Start of System Safety Risk Assessment

- Hazard & Risk Basics (SSRAP Module 1)

- System safety risk analysis (SSRAP Module 2)

Transcript:

Introduction

Hello,

Welcome to this course on Systems Safety Risk Analysis Programs. I'm Simon Di Nucci, The Safety Artisan, and I've been a safety engineer and consultant for over 20 years. I've worked on a wide range of safety programs doing risk analysis on all kinds of things. Ships, planes, trains, air traffic management systems, software systems, you name it.

I've worked in the U.K., in Australia, and on many systems from the U.S. I've also spent hundreds of hours training hundreds of people on safety. And now I've got the opportunity to share some of that knowledge with you online.

So, what are the benefits of this course?

First of all, you will learn about basic concepts. About system safety, what it is and what it does. You will know how to apply a risk analysis program to a very complex system and how to manage that complexity. So, that's what you'll know.

At the end of the course, you will also be able to do things that you might not have been able to do before. You will be able to take the elements of a risk analysis program and the different tasks. You can select the right tasks and form a program to suit your application, whatever it might be. Whether you might:

- Have a full, high-risk bespoke development system,

- Be taking a commercial system off the shelf and doing something new with it, or

- Take a product and use it in a new application or a new location.

Whatever it might be, you will learn how to tailor your risk analysis program. This program will give you the analyses you need. And to meet your legal and regulatory requirements. Once you've learned how to do this, you can apply it to almost any system.

Finally, you will feel confident doing this. I will be interpreting the terminology used in the tasks and applying my experience. So, instead of reading the standard and being unsure of your interpretation, you can be sure of what you need to do. Also, I will show you how you can get good results and avoid some of the pitfalls.

These are the three benefits of the Course

- You will know what to do.

- You will be able to perform risk program tasks, and

- You'll feel confident doing those tasks.

At the end of the course, I will also show you where to find further resources. There are free resources to choose from. But there are also paid resources for those who want to take your studies to the next level. I hope you enjoy the course.

This is Module 1 of SSRAP

This is Module 1 from the System Safety Risk Assessment Program (SSRAP) Course. Risk Analysis Programs – Design a System Safety Program for any system in any application.

The full course comprises 15 lessons and 1.5 hours of video content, plus resources. It's on pre-sale at HALF PRICE until September 1st, 2024. Check out all the free preview videos here and order using the coupon “Pre-order-Half-Price-SSRAP”. But don't leave it too long because there are only 100 half-price courses available!

Meet the Author

Learn safety engineering with me, an industry professional with 25 years of experience, I have:

•Worked on aircraft, ships, submarines, ATMS, trains, and software;

•Tiny programs to some of the biggest (Eurofighter, Future Submarine);

•In the UK and Australia, on US and European programs;

•Taught safety to hundreds of people in the classroom, and thousands online;

•Presented on safety topics at several international conferences.
#AdvancedSafetyRiskAnalysis #ComprehensiveSafetyEngineeringCourse #DesigningaRiskAnalysisProgram #ExpertSafetyManagementTraining #HazardAnalysisTasks #LearnSystemSafetyRiskAnalysis #OnlineTraininginSystemSafety #ProfessionalSafetyRiskAnalysisCourse #RiskAnalysisProgramDesign #RiskAnalysisProgramforComplexSystems #RiskAnalysisTraining #SafetyEngineeringCourses #SafetyManagementTraining #SafetyProgramStandardTraining #SafetyRiskAnalysisforBeginners #SafetyRiskAnalysisPrograms #SystemSafetyRiskAnalysis #SystemSafetyTrainingOnline #TailorYourRiskAnalysisProgram #UnderstandingSystemSafetyStandards
Simon Di Nucci https://www.safetyartisan.com/2024/07/10/introduction-to-system-safety-risk-assessment/

Functional Hazard Analysis with Mil-Std-882E
In this video, I look at Functional Hazard Analysis with Mil-Std-882E (FHA, which is Task 208 in Mil-Std-882E). FHA analyses software, complex electronic hardware, and human interactions. I explore the aim, description, and contracting requirements of this Task, and provide extensive commentary on it. (I refer to other lessons for special techniques for software safety and Human Factors.)

This video, and the related webinar 'Identify & Analyze Functional Hazards', deal with an important topic. Programmable electronics and software now run so much of our modern world. They control many safety-related products and services. If they go wrong, they can hurt people.

I've been working with software-intensive systems since 1994. Functional hazards are often misunderstood or overlooked, as they are hidden. However, the accidents that they can cause are very real. If you want to expand your analysis skills beyond just physical hazards, I will show you how.

https://youtu.be/f4jDnnqYhus
This is the seven-minute demo; the full version is 40 minutes long.

clikc here to get the course: Identify & analyze functional hazards

Functional Hazard Analysis: Context

So how do we analyze software safety?

Before we even start, we need to identify those system functions that may impact safety. We can do this by performing a Functional Failure Analysis (FFA) of all system requirements that might credibly lead to human harm.

An FFA looks at functional requirements (the system should do 'this' or 'that') and examines what could go wrong:

- Does the function work when needed?

- Does the function work when not required?

- Does the function work incorrectly? (There may be more than one version of this.)

(A variation of this technique is explained here.)

If the function could lead to a hazard then it is marked for further analysis. This is where we apply the FHA, Task 208.

Functional Hazard Analysis: The Lesson

Topics: Functional Hazard Analysis

- Task 208 Purpose;

- Task Description;

- Update & Reporting

- Contracting; and

- Commentary.

Transcript: Functional Hazard Analysis

Introduction

Hello, everyone, and welcome to the Safety Artisan; Home of Safety Engineering Training. I'm Simon and today we're going to be looking at how you analyze the safety of functions of complex hardware and software. We'll see what that's all about in just a second.

Functional Hazard Analysis

I'm just going to get to the right page. This, as you can see, functional hazard analysis is Task 208 in Mil. Standard 882E.

Topics for this Session

What we've got for today: we have three slides on the purpose of functional hazard analysis, and these are all taken from the standard. We've got six slides of task description. That's the text from the standard plus we've got two tables that show you how it's done from another part of the standard, not from Task 208. Then we've got update and recording, another two slides. Contracting, two slides. And five slides of commentary, which again include a couple of tables to illustrate what we're talking about.

Functional Purpose HA #1

What we're going to talk about is, as I say, functional hazard analysis. So, first of all, what's the purpose of it? In classic 882 style, Task 208 is to perform this functional hazard analysis on a system or subsystem or more than one. Again, as with all the other tasks, we use it to identify and classify system functions and the safety consequences of functional failure or malfunction. In other words, hazards.

Now, I should point out at this stage that the standard is focused on malfunctions of the system. In the real world, lots of software-intensive systems cause accidents that have killed people, even when they're functioning as intended. That's one of the shortcomings of this Military Standard - it focuses on failure. But even if something performs as specified, either:

- The specification might be wrong, or

- The system might do something that the human operator does not expects.

Mil-Std-882E just doesn't recognize that. So, it's not very good in that respect. However, bearing that in mind, let's carry on with looking at the task.

Functional HA Purpose #2

We're going to look at these consequences in terms of severity – severity only, we'll come back to that – to identify what they call safety-critical functions, safety-critical items, safety-related functions, and safety-related items. And a quick word on that, I hate the term ‘safety-critical’ because it suggests a sort of binary “Either it's safety-critical. Yes. Or it's not safety-critical. No.” And lots of people take that to mean if it's “safety-critical, no,” then it's got nothing to do with safety. They don't recognize that there's a sliding scale between maximum safety criticality and none whatsoever. And that's led to a lot of bad thinking and bad behavior over the years where people do everything they can to pretend that something isn't safety-related by saying, “Oh, it's not safety-critical, therefore we don't have to do anything.” And that kind of laziness kills people.

Anyway, moving on. So, we've got these SCFs, SCIs, SRFs, SRIs and they're supposed to be allocated or mapped to a system design architecture. The presumption in this – the assumption in this task is that we're doing early – We'll see that later – and that system design, system architecture, is still up for grabs. We can still influence it.

COTS and MOTS Software

Often that is not the case these days. This standard was written many years ago when the military used to buy loads of bespoke equipment and have it all developed from new. That doesn't happen anymore so much in the military and it certainly doesn't happen in many other walks of life – But we'll talk about how you deal with the realities later.

And they're allocating these functions and these items of interest to hardware, software, and human interfaces. And I should point out, when we're talking about all that, all these things are complex. Software is complex, human is complex, and we're talking about complex hardware. So, we're talking about components where you can't just say, “Oh, it's got a reliability of X, and that's how often it goes wrong” because those types of simple components are only really subject to random failure, that's not what we're talking about here.

We're talking about complex stuff where we're talking about systematic failure dominating over random, simple hardware failure. So, that's the focus of this task and what we're talking about. That's not explained in the standard, but that's what's going on.

Functional HA Purpose #3

Now, our third slide is on purpose; so, we use the FHA to identify the consequences of malfunction, functional failure, or lack of function. As I said just now, we need to do this as early as possible in the systems engineering process to enable us to influence the design. Of course, this is assuming that there is a system engineering process – that's not always the case. We'll talk about that at the end as well.

Also, we're going to identify and document these functions and items and allocate and it says to partition them in the software design architecture. When we say partition, that's jargon for separating them into independent functions. We'll see the value of that later on. Then we're going to identify requirements and constraints to put on the design team to say, “To achieve this allocation in this partitioning, this is what you must do and this is what you must not do”. So again, the assumption is we're doing this early. There's a significant amount of bespoke design yet to be done....

Then What?

Once the FFA has identified the required 'Level or Rigor', we need to translate that into a suitable software development standard. This might be:

- RTCA DO-178C (also know as ED-12C) for civil aviation;

- The US Joint Software System Safety Engineering Handbook (JSSEH) for military systems;

- IEC 61508 (functional safety) for the process industry;

- CENELEC-50128 for the rail industry; and

- ISO 26262 for automotive applications.

Such standards use Safety Integrity Levels (SILs) or Development Assurance Levels (DALs) to enforce appropriate Levels of Rigor. You can learn about those in my course, Principles of Safe Software Development.

Meet the Author

My name’s Simon Di Nucci. I’m a practicing system safety engineer, and I have been, for the last 25 years; I’ve worked in all kinds of domains, aircraft, ships, submarines, sensors, and command and control systems, and some work on rail air traffic management systems, and lots of software safety. So, I’ve done a lot of different things!
#functionalhazard #functionalhazardindigitalelectronics #functionalriskassessment #functionalriskexample #functionalsafety #functionalsafetyanalysis #functionalsafetycourse #functionalsafetyonlinecourse #functionalsafetyppt #functionalsafetyrequirements #functionalsafetystandards #functionalsafetytechniquelearnfunctionalsafety #functionalsafetytraining #functionalsafetytrainingAustralia #functionalsafetytutorial #functionalsafetyvideo #hazardfunctiondefinition #howtodofunctionalsafety #Milstd882Technique #Milstd882Training #Milstd882tutorial #Milstd882Video #MilStd882E #whatisfunctionalrisk
Simon Di Nucci https://www.safetyartisan.com/2024/03/20/functional-hazard-analysis-task-208/

My CISSP Exam Journey
Here is a video about my CISSP exam journey.

https://youtu.be/zGof2cB9VW8
I've just passed the Certified Information Systems Security Professional (CISSP) Exam...

Get the full 'My CISSP Exam Journey' free video here.

I've just passed the Certified Information Systems Security Professional (CISSP) Exam, which was significantly updated on 1st May 2021. In this 30-minute video, I will cover:

- The official CISSP course and course guide;

- The 8 Domains of CISSP, and how to take stock of your knowledge of them;

- The official practice questions and the Study Guide;

- The CISSP Exam itself; and

- Lessons learned from my journey.

I wish you every success in your CISSP journey: it's tough, but you can do it!

Transcript: My CISSP Exam Journey

Hi, Everyone,

My name is Simon Di Nucci and I've just passed the new CISSP exam; for those of you who don't know what that is, that's the Certified Information Systems Security professional. It's new because the exams have been around a long time, but the syllabus and the exam itself have undergone a significant change as of the 1st of May this year. I’m probably one of the first people to pass the new exam, which I have to tell you was a great relief because it was really it was a tough exam and it was tough preparing for it.

It was a big mountain to climb. I am very, very relieved to have passed. Now, I hope to share some lessons with you. When I mentioned that I passed on the cybersecurity groups on Facebook and LinkedIn, I got a huge response from people who appreciated how difficult it is to do this and also lots of questions. And whilst I can't talk about the specifics of the exam, that's not allowed, I can share some really useful lessons learned from my journey.

Introduction

So I'm going to be talking about what I did:

- The Official Course, and the Student Guide;

- How I took stock at the start of the revision process;

- How I revised using the practice questions and the Study Guide;

- Something about the exam itself; and

- Lessons learned.

The Official Course

So let's get on with it.  My journey was that two or three years ago, the firm that I worked for decided that they wanted me to take the CISSP exam in order to improve our credibility when doing cybersecurity, and my credibility.

I was sent on a five-day course, which was very intense, and it was the official book.is the official ISC2 course. And that was several hundred slides a day for five days. It was very intense. And as you can see, the guy that you get with a pretty hefty eight hundred pages of closely packed and high-quality material. I was taught by someone who was clearly a very experienced expert in the field.

It was a good quality course. It cost about $3,700 (Australian). I think that's about $2,500 (US). In terms of the investment, I think it was worth it because it covered a lot of ground, and I was very rusty on a lot of this stuff. It was it was a useful ‘crammer’ to get back into this stuff. As I said, 800 pages long. I've done a lot of revising!

Practical Things

Let's put that to one side. The course was very good, but of course, it takes some time out of your schedule to do it. You need the money and the support from your workplace to be able to do that. There are now online courses, which I haven't been on; I can't say how good they are, but they are cheaper, and they're spread out. I think you do a day or two per week for a period of several weeks.

And I think that's got to be really good because you're going to have more time to consolidate this huge amount of information in your head. No disrespect to the face-to-face course. It was very good. I think the online courses could be even better and a lot more accessible.  That was the course. Now, I did that in November twenty nineteen and I intended to do some revision and then take the exam probably in early.

In March, April 2020, global events got in the way of that, and all the exam centers were closed down. I couldn't do that. Basically, I sort of forgot about it for a period of months. And then at the tail end of 2020, as things began to improve here in Australia at least, we've been very lucky here, exam centers reopened, and I thought, well, I really should get back and, you know, try and schedule the exam and do some revision and get on with it.

Exam Preparation

So I did. And starting in January of this year, I got my management agreement that I would spend one day a week working from home, revising, and that's what I did. Given that I took the exam in the middle of May, that's probably 18 full days of revision going through the material, and I needed it! Originally, I was going to take the exam, I think, in early April, but I realized at the end of March that I was not ready and I needed more time.

So I put the exam date back to the middle of May. And it was only after I'd done that that it was announced that the syllabus of the exam was changing quite significantly. That was a, you know, extra work then. And fortunately. They. They brought out the official guide to the new exam, and I realized that quite a lot of material to learn. I went through, and for example, there are eight domains in CISSP.

And for example, here's domain number two, asset security. In the pink, I have highlighted all the new things that are in the 1st of May Edition syllabus that were not in the 2018 syllabus.  I went through all of these things, and there are quite a few in almost every domain except the first one. There are significant changes.  I had to do a lot of extra revision because the syllabus had changed, but nevertheless, it was doable.

To get regular updates from The Safety Artisan, Click Here. For more introductory lessons Start Here.
#CISSP #CISSP2021 #CISSP2021Exam #cisspisanexampleofasecuritycertification #cisspobjectives #cissppearson #cisspqualification #cisspwhatisit #coursesafetyengineering #Cybersecurity #engineersafety #ineedsafety #knowledgeofsafety #learnsafety #needforsafety #safetyblog #safetydo #safetyengineer #safetyengineerskills #safetyengineertraining #safetyengineeringcourse #safetyprinciples #softwaresafety #theneedforsafety
Simon Di Nucci https://www.safetyartisan.com/2023/09/27/my-cissp-exam-journey/

Software Safety Principles Conclusions and References
Software Safety Principles Conclusions and References is the sixth and final blog post on Principles of Software Safety Assurance. In them, we look at the 4+1 principles that underlie all software safety standards. (The previous post in the series is here.)

Read on to Benefit From...

The conclusions of this paper are brief and readable, but very valuable. It's important for us - as professionals and team players - to be able to express these things to managers and other stakeholders clearly. Talking to non-specialists is something that most technical people could do better.

The references include links to the standards covered by the paper. Unsurprisingly, these are some of the most popular and widely used processes in software engineering. The other links take us to the key case studies that support the conclusions.

Content

We outline common software safety assurance principles that are evident in software safety standards and best practices. You can think of these guidelines as the unchanging foundation of any software safety argument because they hold true across projects and domains.

The principles serve as a guide for cross-sector certification and aid in maintaining comprehension of the “big picture” of software safety issues while evaluating and negotiating the specifics of individual standards.

Conclusion

These six blog posts have presented the 4+1 model of foundational principles of software safety assurance. The principles strongly connect to elements of current software safety assurance standards and they act as a common benchmark against which standards can be measured.

Through the examples provided, it's also clear that, although these concepts can be stated clearly, they haven't always been put into practice. There may still be difficulties with their application by current standards. Particularly, there is still a great deal of research and discussion going on about the management of confidence with respect to software safety assurance (Principle 4+1).

Standards and References

RTCA/EUROCAE, Software Considerations in Airborne Systems and Equipment Certification, DO-178C/ED-12C, 2011.

CENELEC, EN-50128:2011 - Railway applications - Communication, signaling and processing systems - Software for railway control and protection systems, 2011.

ISO-26262 Road vehicles – Functional safety, FDIS, International Organization for Standardization (ISO), 2011

IEC-61508 – Functional Safety of Electrical / Electronic / Programmable Electronic Safety-Related Systems. International Electrotechnical Commission (IEC), 1998

FDA, Examples of Reported Infusion Pump Problems, Accessed on 27 September 2012,

http://www.fda.gov/MedicalDevices/ProductsandMedicalProcedures/GeneralHospitalDevicesandSupplies/InfusionPumps/ucm202496.htm

FDA, FDA Issues Statement on Baxter’s Recall of Colleague Infusion Pumps, Accessed on 27 September 2012, http://www.fda.gov/NewsEvents/Newsroom/PressAnnouncements/ucm210664.htm

FDA, Total Product Life Cycle: Infusion Pump - Premarket Notification 510(k) Submissions, Draft Guidance, April 23, 2010.

“Report on the Accident to Airbus A320-211 Aircraft in Warsaw on 14 September 1993”, Main Commission Aircraft Accident Investigation Warsaw, March 1994, http://www.rvs.unibielefeld.de/publications/Incidents/DOCS/ComAndRep/Warsaw/warsaw-report.html  Accessed on 1st October 2012.

JPL Special Review Board, "Report on the Loss of the Mars Polar Lander and Deep Space 2 Missions", Jet Propulsion Laboratory”, March 2000.

Australian Transport Safety Bureau. In-Flight Upset Event 240Km North-West of Perth, WA, Boeing Company 777-2000, 9M-MRG. Aviation Occurrence Report 200503722, 2007.

H. Wolpe, General Accounting Office Report on Patriot Missile Software Problem, February 4, 1992, Accessed on 1st October 2012, Available at: http://www.fas.org/spp/starwars/gao/im92026.htm

Y.C. Yeh, Triple-Triple Redundant 777 Primary Flight Computer, IEEE Aerospace Applications Conference pg 293-307, 1996.

D.M. Hunns and N. Wainwright, Software-based protection for Sizewell B: the regulator’s perspective. Nuclear Engineering International, September 1991.

R.D. Hawkins, T.P. Kelly, A Framework for Determining the Sufficiency of Software Safety Assurance. IET System Safety Conference, 2012.

SAE. ARP 4754 - Guidelines for Development of Civil Aircraft and Systems. 1996.

Software Safety Principles: End of the Series

This blog post series was derived from ‘The Principles of Software Safety Assurance’, by RD Hawkins, I Habli & TP Kelly, University of York. The original paper is available for free here. I was privileged to be taught safety engineering by Tim Kelly, and others, at the University of York. I am pleased to share their valuable work in a more accessible format.

Meet the Author

My name’s Simon Di Nucci. I’m a practicing system safety engineer, and I have been, for the last 25 years; I’ve worked in all kinds of domains, aircraft, ships, submarines, sensors, and command and control systems, and some work on rail air traffic management systems, and lots of software safety. So, I’ve done a lot of different things!

Principles of Software Safety Training

Learn more about this subject in my course 'Principles of Safe Software' here.

My course on Udemy, 'Principles of Software Safety Standards' is a cut-down version of the full Principles Course. Nevertheless, it still scores 4.42 out of 5.00 and attracts comments like:

- "It gives me an idea of standards as to how they are developed and the downward pyramid model of it." 4* Niveditha V.

- "This was really good course for starting the software safety standareds, comparing and reviewing strengths and weakness of them. Loved the how he try to fit each standared with4+1 principles. Highly recommend to anyone that want get into software safety." 4.5* Amila R.

- "The information provides a good overview. Perfect for someone like me who has worked with the standards but did not necessarily understand how the framework works." 5* Mahesh Koonath V.

- "Really good overview of key software standards and their strengths and weaknesses against the 4+1 Safety Principles." 4.5* Ann H.
#basicprinciplesofsafety #issafetyimportant #principlesforsoftwaredesign #principlesofsoftwareengineering #principlesofsoftwarevalidation #safeprinciplesexplained #safesystemprinciples #safetyassessmentprinciples #safetyprinciples #safetyprinciplesandpractices #softwareanalysisprinciples #softwaredesignprinciplesexamples #softwaredevelopmentprinciple #softwaredevelopmentprinciplesandpractices #softwareengineeringprinciplesarebasedon #softwareengineeringprinciplesppt #softwareprinciples #softwareprinciplesinsoftwareengineering #softwarequalityprinciples #softwaresafetycertification #softwaresafetydefinition #softwaresafetyengineering #softwaresafetyexamples #softwaresafetyprinciples #softwaresafetyrequirements #softwaresafetyrequirementsexample #softwaresafetystandards #softwaresafetytesting #softwaresystemsafety #whataresoftwaredesignprinciples
Simon Di Nucci https://www.safetyartisan.com/2022/11/23/sw-safety-principles-conclusions-and-references/

Australian WHS Course
In this Australian WHS Course, we show you how to practically and pragmatically implement the essential elements of Australian Work Health and Safety Legislation. In particular, we look at the so-called 'upstream' WHS duties. These are the elements you need to safely introduce systems and services into the Australian market.

Lessons in This Course

A Guide to the Australian WHS Act

Image by Wendy Van Zyl, from Pexels

This Guide to the WHS Act covers many topics of interest to system safety and design safety specialists, this full-length video covers key sections (§) of the Act:

- § 3, Object ;

- § 4-8, Definitions;

- § 12A, Exclusions;

- § 18, Reasonably Practicable;

- § 19, Primary Duty of Care;

- § 22-26, Duties of Designers, Manufacturers, Importers, Suppliers & those who Install/Construct/Commission;

- § 27, Officers & Due Diligence;

- § 46-49, Consult, Cooperate & Coordinate;

- § 152, Function of the Regulator; and

- § 274-276, WHS Regulations and CoP.

The Consultation, Cooperation & Coordination Code of Practice

Photo by August de Richelieu from Pexels.com

In this 30-minute session, we look at the Consultation, Cooperation & Coordination Code of Practice (CC&C CoP). We cover the Commonwealth and Model versions of the CoP, appendices & a summary of detailed requirements; and further commentary. This CoP is one of the two that are generally applicable.

Topics:

- CC&C in the Federal or Commonwealth CoP;

- Extra CC&C in the Model CoP;

- (Watch out for Jurisdiction);

- Further commentary; and

- Where to get more information.

The Risk Management CoP

Photo by Marta Branco from Pexels

In this 40-minute session, we look at the Risk Management Code of Practice (CoP). We cover: who has WHS duties; the four-step process; keeping records, appendices & a summary of detailed requirements; and further commentary. This CoP is the other one of the two that are generally applicable.

Topics:

- Who has WHS duties;

- The four-step process;

- Keeping records, appendices & summary of detailed requirements;

- Further commentary; and

- Where to get more information.

Safe Design

Karolina Grabowska STAFFAGE from Pexels

Want some good guidance on Safe Design? In this 52-minute video from the Safety Artisan, you will find it. We take the official guidance from Safe Work Australia and provide a value-added commentary on it. The guidance integrates seamlessly with Australian law and regulations, but it is genuinely useful in any jurisdiction.

Topics:

- A safe design approach;

- Five principles of safe design;

- Ergonomics and good work design;

- Responsibility for safe design;

- Product lifecycle;

- Benefits of safe design;

- Legal obligations; and

- Our national approach.

How to Demonstrate SFARP

Photo by Sondre Dahl from Pexels.com

So our learning objectives for this session at the end of this session, you should understand the SFARP concept: what it’s all about. You should understand the variety of techniques that are available to you. Most importantly, you will be able to apply these techniques in the correct order, because that’s important in the real world.

Topics

- Introduction – Reasonably Practicable;

- How to SFARP with:

- Codes, Standards & Regulations; and

- Controls, or groups of controls.

- Some practical hints on good practice;

- Examples; and

- Source information.
#demonstrateSFARP #reasonablypracticable #reasonablypracticablecaselaw #reasonablypracticabledefinition #reasonablypracticablehealthandsafety #reasonablypracticablemeaning #reasonablypracticablewhs #sfairp #sfairphealthandsafety #SFARP #sfarpsafety #showSFARP #whatdoesreasonablypracticablemean #whatisthebesthealthandsafetycoursetodo #whatisthepurposeofwhs #whsclasses #Whscourse #whscourseonline #whscourses #whstrainingformanagers
Simon Di Nucci https://www.safetyartisan.com/2022/07/06/australian-whs-course/

Learn How to Perform System Safety Analysis
In this 'super post', we will Learn How to Perform System Safety Analysis. I will show you thirteen lessons that explain each of the ten analysis tasks, the analysis process, and how to combine those tasks into a program!

Follow the links to sample and buy lessons on individual tasks.

Introduction

Military Standard 882, or Mil-Std-882 for short, is one of the most widely used system-safety standards. As the name implies, this standard is used on US military systems, but it has found its way, sometimes in disguise, into many other programs around the world. It’s been around for a long time and is now in its fifth incarnation: 882E.

Unfortunately, 882 has also been widely misunderstood and misapplied. This is probably not the fault of the standard and is just another facet of its popularity. The truth is that any standard can be applied blindly – no standard is a substitute for competent decision-making.

In this series of posts, we will: provide awareness of this standard; explain how to use it; and discuss how to manage, tailor, and implement it. Links to each training session and to each section of the standard are provided in the following sections.

Mil-Std-882E Training Sessions

System Safety Process, full post here

Photo by Bonneval Sebastien on Unsplash

In this full-length (50 minutes) video, you will learn to:

- Know the system safety process according to Mil-Std-882E;

- List and order the eight elements;

- Understand how they are applied;

- Skilfully apply system safety using realistic processes; and

- Feel more confident dealing with multiple standards.

In System Safety Process, we look a the general requirements of Mil-Std-882E. We cover the Applicability of the 882E tasks; the General requirements; the Process with eight elements; and the application of process theory to the real world.

Design Your System Safety Analysis Program

Photo by Christina Morillo from Pexels

Learn how to Design a System Safety Program for any system in any application.

Learning Objectives. At the end of this course, you will be able to:

- Define what a risk analysis program is;

- List the hazard analysis tasks that make up a program;

- Select tasks to meet your needs; and

- Design a tailored risk analysis program for any application.

Analysis: 200-series Tasks

Preliminary Hazard Identification, Task 201

Identify Hazards.

In this video, we find out how to create a Preliminary Hazard List, the first step in safety assessment. We look at three classic complementary techniques to identify hazards and their pros and cons. This includes all the content from Task 201, and also practical insights from my 25 years of experience with Mil-Std-882.

You can buy the full video, plus lots of bonus material, here.

Preliminary Hazard Analysis, Task 202

See More Clearly.

In this 45-minute session, The Safety Artisan looks at Preliminary Hazard Analysis, or PHA, which is Task 202 in Mil-Std-882E. We explore Task 202’s aim, description, scope, and contracting requirements. We also provide value-adding commentary and explain the issues with PHA – how to do it well and avoid the pitfalls.

System Requirements Hazard Analysis, Task 203

Law, Regulations, Codes of Practice, Guidance, Standards & Recognised Good Practice.

In this 45-minute session, The Safety Artisan looks at Safety Requirements Hazard Analysis, or SRHA, which is Task 203 in the Mil-Std-882E standard. We explore Task 203’s aim, description, scope, and contracting requirements. SRHA is an important and complex task, which needs to be done on several levels to be successful. This video explains the issues and discusses how to perform SRHA well.

Sub-system Hazard Analysis, Task 204

Breaking it down to the constituent parts.

In this video lesson, The Safety Artisan looks at Sub-System Hazard Analysis, or SSHA, which is Task 204 in Mil-Std-882E. We explore Task 204’s aim, description, scope, and contracting requirements. We also provide value-adding commentary and explain the issues with SSHA – how to do it well and avoid the pitfalls.

System Hazard Analysis, Task 205

Putting the pieces of the puzzle together.

In this 45-minute session, The Safety Artisan looks at System Hazard Analysis, or SHA, which is Task 205 in Mil-Std-882E. We explore Task 205’s aim, description, scope, and contracting requirements. We also provide value-adding commentary, which explains SHA – how to use it to complement Sub-System Hazard Analysis (SSHA, Task 204) to get the maximum benefits for your System Safety Program.

Operating and Support Hazard Analysis, Task 206

Operate it, maintain it, supply it, dispose of it.

In this full-length session, The Safety Artisan looks at Operating & Support Hazard Analysis, or O&SHA, which is Task 206 in Mil-Std-882E. We explore Task 205’s aim, description, scope, and contracting requirements. We also provide value-adding commentary, which explains O&SHA: how to use it with other tasks; how to apply it effectively on different products; and some of the pitfalls to avoid. We refer to other lessons for specific tools and techniques, such as Human Factors analysis methods.

Health Hazard Analysis, Task 207

Hazards to human health are many and various.

In this full-length (55-minute) session, The Safety Artisan looks at Health Hazard Analysis, or HHA, which is Task 207 in Mil-Std-882E. We explore the aim, description, and contracting requirements of this complex Task, which covers: physical, chemical & biological hazards; Hazardous Materials (HAZMAT); ergonomics, aka Human Factors; the Operational Environment; and non/ionizing radiation. We outline how to implement Task 207 in compliance with Australian WHS. 

Functional Hazard Analysis, Task 208

Components where systemic failure dominates random failure.

In this full-length (40-minute) session, The Safety Artisan looks at Functional Hazard Analysis, or FHA, which is Task 208 in Mil-Std-882E. FHA analyses software, complex electronic hardware, and human interactions. We explore the aim, description, and contracting requirements of this Task, and provide extensive commentary on it. 

System-Of-Systems Hazard Analysis, Task 209

Existing systems are often combined to create a new capability.

In this full-length (38-minute) session, The Safety Artisan looks at Systems-of-Systems Hazard Analysis, or SoSHA, which is Task 209 in Mil-Std-882E. SoSHA analyses collections of systems, which are often put together to create a new capability, which is enabled by human brokering between the different systems. We explore the aim, description, and contracting requirements of this Task, and an extended example to illustrate SoSHA. (We refer to other lessons for special techniques for Human Factors analysis.)

Environmental Hazard Analysis, Task 210

Environmental requirements in the USA, UK, and Australia.

This is the full, one-hour session on Environmental Hazard Analysis (EHA), which is Task 210 in Mil-Std-882E. We explore the aim, task description, and contracting requirements of this Task, but this is only half the video. We then look at environmental requirements in the USA, UK, and Australia, before examining how to apply EHA in detail under the Australian/international regime. This uses my practical experience of applying EHA. 
#Milstd882Technique #Milstd882Training #Milstd882tutorial #Milstd882Video #Milstd882eTechnique #Milstd882eTraining #Milstd882etutorial #Milstd882eVideo #SafetystandardTechnique #SafetystandardTraining #Safetystandardtutorial #SafetystandardVideo #SubsystemhazardanalysisTechnique #SubsystemhazardanalysisTraining #Subsystemhazardanalysistutorial #SubsystemhazardanalysisVideo #SystemsafetyengineeringTechnique #systemsafetyengineeringtraining #Systemsafetyengineeringtutorial #SystemsafetyengineeringVideo
Simon Di Nucci https://www.safetyartisan.com/2021/10/20/learn-how-to-perform-system-safety-analysis/

Learn How to Perform System Safety Analysis
In this 'super post', we will Learn How to Perform System Safety Analysis. I will show you thirteen lessons that explain each of the ten analysis tasks, the analysis process, and how to combine those tasks into a program!

Follow the links to sample and buy lessons on individual tasks.

Introduction

Military Standard 882, or Mil-Std-882 for short, is one of the most widely used system-safety standards. As the name implies, this standard is used on US military systems, but it has found its way, sometimes in disguise, into many other programs around the world. It’s been around for a long time and is now in its fifth incarnation: 882E.

Unfortunately, 882 has also been widely misunderstood and misapplied. This is probably not the fault of the standard and is just another facet of its popularity. The truth is that any standard can be applied blindly – no standard is a substitute for competent decision-making.

In this series of posts, we will: provide awareness of this standard; explain how to use it; and discuss how to manage, tailor, and implement it. Links to each training session and to each section of the standard are provided in the following sections.

Mil-Std-882E Training Sessions

System Safety Process, full post here

Photo by Bonneval Sebastien on Unsplash

In this full-length (50 minutes) video, you will learn to:

- Know the system safety process according to Mil-Std-882E;

- List and order the eight elements;

- Understand how they are applied;

- Skilfully apply system safety using realistic processes; and

- Feel more confident dealing with multiple standards.

In System Safety Process, we look a the general requirements of Mil-Std-882E. We cover the Applicability of the 882E tasks; the General requirements; the Process with eight elements; and the application of process theory to the real world.

Design Your System Safety Analysis Program

Photo by Christina Morillo from Pexels

Learn how to Design a System Safety Program for any system in any application.

Learning Objectives. At the end of this course, you will be able to:

- Define what a risk analysis program is;

- List the hazard analysis tasks that make up a program;

- Select tasks to meet your needs; and

- Design a tailored risk analysis program for any application.

Analysis: 200-series Tasks

Preliminary Hazard Identification, Task 201

Identify Hazards.

In this video, we find out how to create a Preliminary Hazard List, the first step in safety assessment. We look at three classic complementary techniques to identify hazards and their pros and cons. This includes all the content from Task 201, and also practical insights from my 25 years of experience with Mil-Std-882.

You can buy the full video, plus lots of bonus material, here. There are 19 bite-sized lessons, with two hours of video content.

Preliminary Hazard Analysis, Task 202

See More Clearly.

In this 45-minute session, The Safety Artisan looks at Preliminary Hazard Analysis, or PHA, which is Task 202 in Mil-Std-882E. We explore Task 202’s aim, description, scope, and contracting requirements. We also provide value-adding commentary and explain the issues with PHA – how to do it well and avoid the pitfalls.

System Requirements Hazard Analysis, Task 203

Law, Regulations, Codes of Practice, Guidance, Standards & Recognised Good Practice.

In this 45-minute session, The Safety Artisan looks at Safety Requirements Hazard Analysis, or SRHA, which is Task 203 in the Mil-Std-882E standard. We explore Task 203’s aim, description, scope, and contracting requirements. SRHA is an important and complex task, which needs to be done on several levels to be successful. This video explains the issues and discusses how to perform SRHA well.

Bundle Offer #1

Click here to buy these three essential tasks - and bonus material - together:

- Preliminary Hazard Identification (T201),

- Preliminary Hazard Analysis (T202), and

- Safety Requirements Hazard Analysis (T203).

Sub-system Hazard Analysis, Task 204

Breaking it down to the constituent parts.

In this video lesson, The Safety Artisan looks at Sub-System Hazard Analysis, or SSHA, which is Task 204 in Mil-Std-882E. We explore Task 204’s aim, description, scope, and contracting requirements. We also provide value-adding commentary and explain the issues with SSHA – how to do it well and avoid the pitfalls.

System Hazard Analysis, Task 205

Putting the pieces of the puzzle together.

In this 45-minute session, The Safety Artisan looks at System Hazard Analysis, or SHA, which is Task 205 in Mil-Std-882E. We explore Task 205’s aim, description, scope, and contracting requirements. We also provide value-adding commentary, which explains SHA – how to use it to complement Sub-System Hazard Analysis (SSHA, Task 204) to get the maximum benefits for your System Safety Program.

Operating and Support Hazard Analysis, Task 206

Operate it, maintain it, supply it, dispose of it.

In this full-length session, The Safety Artisan looks at Operating & Support Hazard Analysis, or O&SHA, which is Task 206 in Mil-Std-882E. We explore Task 205’s aim, description, scope, and contracting requirements. We also provide value-adding commentary, which explains O&SHA: how to use it with other tasks; how to apply it effectively on different products; and some of the pitfalls to avoid. We refer to other lessons for specific tools and techniques, such as Human Factors analysis methods.

Health Hazard Analysis, Task 207

Hazards to human health are many and various.

In this full-length (55-minute) session, The Safety Artisan looks at Health Hazard Analysis, or HHA, which is Task 207 in Mil-Std-882E. We explore the aim, description, and contracting requirements of this complex Task, which covers: physical, chemical & biological hazards; Hazardous Materials (HAZMAT); ergonomics, aka Human Factors; the Operational Environment; and non/ionizing radiation. We outline how to implement Task 207 in compliance with Australian WHS. 

Bundle Offer #2

Click here to buy these two tasks - and bonus material - together:

- Operating & Support Hazard Analysis (T206), and

- Health Hazard Analysis (T207).

Functional Hazard Analysis, Task 208

Components where systemic failure dominates random failure.

In this full-length (40-minute) session, The Safety Artisan looks at Functional Hazard Analysis, or FHA, which is Task 208 in Mil-Std-882E. FHA analyses software, complex electronic hardware, and human interactions. We explore the aim, description, and contracting requirements of this Task, and provide extensive commentary on it. 

Bundle Offer #3

Click here to buy these two tasks, and bonus material, together:

- Preliminary Hazard Identification (T201), and

- Functional Hazard Analysis (T209).

System-Of-Systems Hazard Analysis, Task 209

Existing systems are often combined to create a new capability.

In this full-length (38-minute) session, The Safety Artisan looks at Systems-of-Systems Hazard Analysis, or SoSHA, which is Task 209 in Mil-Std-882E. SoSHA analyses collections of systems, which are often put together to create a new capability, which is enabled by human brokering between the different systems. We explore the aim, description, and contracting requirements of this Task, and an extended example to illustrate SoSHA. (We refer to other lessons for special techniques for Human Factors analysis.)

Course Bundle Offer #4

Click here to buy these three essential tasks together:

- Sub-system Hazard Analysis (T204),

- System Hazard Analysis (T205), and

- System of System Hazard Analysis (T209).

Environmental Hazard Analysis, Task 210

Environmental requirements in the USA, UK, and Australia.

This is the full, one-hour session on Environmental Hazard Analysis (EHA), which is Task 210 in Mil-Std-882E. We explore the aim, task description, and contracting requirements of this Task, but this is only half the video. We then look at environmental requirements in the USA, UK, and Australia, before examining how to apply EHA in detail under the Australian/international regime. This uses my practical experience of applying EHA. 

The Package Deal

Click here for a bumper deal on all twelve+one lessons:

- System Safety Process;

- Design your System Safety Program; and

- All ten System Safety Analysis tasks.
#Milstd882Technique #Milstd882Training #Milstd882tutorial #Milstd882Video #Milstd882eTechnique #Milstd882eTraining #Milstd882etutorial #Milstd882eVideo #SafetystandardTechnique #SafetystandardTraining #Safetystandardtutorial #SafetystandardVideo #SubsystemhazardanalysisTechnique #SubsystemhazardanalysisTraining #Subsystemhazardanalysistutorial #SubsystemhazardanalysisVideo #SystemsafetyengineeringTechnique #systemsafetyengineeringtraining #Systemsafetyengineeringtutorial #SystemsafetyengineeringVideo
Simon Di Nucci https://www.safetyartisan.com/2021/10/20/learn-how-to-perform-system-safety-analysis/