Friday, December 26, 2025



Functional Hazard Analysis with Mil-Std-882E
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
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
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
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
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
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/


Consultation, Cooperation & Coordination CoP
Consultation, Cooperation & Coordination CoP
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.

https://youtu.be/CARK4tJnX28
This is the three-minute demo of the full, 30-minute video.

see the full-length video here

Consultation, Cooperation & Coordination CoP: 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.

Consultation, Cooperation & Coordination CoP: Transcript

Click Here for the Transcript
Consultation, Cooperation & Coordination CoP

Hello, everyone, and welcome to The Safety Artisan. I'm Simon and today we're going to be talking about a very useful subject, which is Codes of Practice. And one Code of Practice in particular, which is the Code of Practice for Consultation, Cooperation and Coordination. And it doesn't sound like the most exciting subject, I'll admit, but this is one of only two Codes of Practice that you must be aware of if operating in Australia, or exporting to Australia, or importing stuff to Australia, whatever it might be. The other Code of Practice that you must be aware of is the Risk Management Code of Practice. There are a lot more Code of Practices than these two, but they don't always apply. So, I mean if you're not doing anything to do with asbestos, you don't have to worry about what it says in the Asbestos Code of Practice. But this one you do because it applies to everything.

Topics for this Session

And I've used this Code of Practice to help clients and to do particular things and help everybody understand what we have to do, and it’s very useful. And in this session, I will be explaining how to get the best out of this Code of Practice and, at the end, where to get more information. So, I hope you'll find that useful. So we're going to be talking about the - I'm just going to call it the C, C & C CoP for short because it's a dreadful mouthful, isn't it? We're going to be looking at the federal or Commonwealth Code of Practice and then we're going to look at some extras in the Model Code of Practice. So just to explain that briefly, the Model Code of Practice is on the Safe Work Australia website, and that is the Model from which all other CoPs are developed. However, Safe Work Australia is not a regulator. So individual regulators and the example I'm using is the Commonwealth one- or Comcare, as it's known- they have chosen to edit the Model CoP and change it and remove quite a bit of material. Now, why they chose to do that, I do not know. So, you have to be careful which jurisdiction you're operating in, in Australia. If you are in a Commonwealth workplace, then you need to apply the Commonwealth or the federal version of WHS, including this CoP. And if you're in a state or territory workplace, or a commercial workplace in a state or territory, you need to apply the relevant one there. And just to complicate matters, Western Australia has not yet introduced WHS and Victoria has no plans to do so. So, of course, in Australia, we like to make life simple for ourselves, don't we? Oh no, we don't!

So after I've gone through some basics of what's in the CoP, because you'll see there's an awful lot of material in there that I'm not going to talk about. I produced some commentary that I think you will find helpful and where to get more information, as I promised. So, let's get on with it!

When to Consult

So, first of all- and you'll notice that I'm only including those bits really that say when you must do something. So, this is quoting Section 49 of the WHS Act, which says that if you're conducting a business or some kind of undertaking- so it's not just a commercial business, but anything- you must consult with your workers when identifying hazards and assessing risks, making decisions about how you're going to control those risks, making decisions about the adequacy of facilities for welfare, proposing changes that affect health and safety, and making decisions about procedures for consulting with workers, providing information and training, and so on and so forth. So, there's a whole raft of things that you have to consult your workers on. So, this is all workplace so far. Now, in my role as a safety consultant, I'm often working with people who are introducing they're buying bits of kit, or designing or importing bits of kit, and there is no work yet, so there's no workers. But we always try and get a representative of the end-user involved because that really does help you do good quality safety work and avoid- to be honest- wasting time and money on things that are theoretically possible or theoretically sound problematic but in reality, it just doesn't arise for whatever reason. So, I really do recommend getting those end-user representatives involved.

Effective Consultation

And if we go on to Section 48- for some reason, the cop quotes these things in reverse order- to be effective in consultation, we require information to be shared. Workers have got to have a reasonable opportunity to express their views. They've got to have a reasonable opportunity to contribute to decisions. Their views must be taken into account and they must be advised of the outcomes of consultation. So, all good common-sense stuff, I would think. Nothing controversial about this and that- to be honest- that's a feature of CoPs. They tell you to do things that you think, “Yeah, I really ought to be doing that!”.

Consultation Procedures

Continuing with the countdown, we're on to Section 47. Consultation procedures, again more basic common sense. If you’ve agreed to procedures for consultation, you must follow those procedures. It's not rocket science, is it, folks? Let's move on.

Sections 16 & 46

OK, now this is a bit more interesting, I think. This is getting into the real guts of this Code of Practice because where consultation, cooperation and coordination really come into play is where you've got multiple stakeholders, multiple duty holders- that is to say, those with a duty to protect the health and safety of people. Where multiple stakeholders, duty holders, have to get together and work together in order to come up with a solution. So the law says- Section 16 says where more than one person has a duty for the same thing, for the same matter, each person retains that responsibility. You cannot wriggle out of your responsibility just because you only control a bit over here and not over here. So, the two duty holders who have control here and here, they have to work together. The law says so. And so this is really the guts of this Code of Practice. And they must work together to discharge their duties to the extent to which they can. And the extent to which you can is the extent to which you influence and control the matter. So, WHS law is very big about control. If you have control of the bit, you've got to do your bit and you must work with people who have control of other things. You might be designing or buying a piece of kit. Other people might control the workplace. There might be another group of people who represent the operators, and then another group who represent the maintainers, and so on and so forth. They've all got to be involved if they're relevant to managing risk. And of course, as risk in WHS is cradle to grave, then pretty much everyone is involved.

So, Section 46, and in these situations where you have got multiple duty holders, each person with a duty must, so far as is reasonably practicable, consult, cooperate and coordinate with all other persons. And I'm going to do a session quite soon on so far as is reasonably practicable, or SOFARP, and in it, I will tell you that SOFARP is an objective test and the law sets objective expectations for what a reasonable person would do. So, you can't just say, “Well, I'll decide what is reasonable or not reasonable.”. The law has already done it for you and there's guidance out there to help you so follow it. So, we will do something on that guidance, about what is reasonable and what is reasonably practicable. But we've got to work with each other SOFARP. For the greater good! Sorry, that's a quote from one of my favourite comedy films, by the way.

CoP Appendices

So, appendices to the CoP. If we look at the appendices in the federal or Commonwealth CoP, there are only three. So, they've got some examples of arrangements. They've got a consultation checklist, and they've got an appendix on C, C and C activities, which is all good. That's all good stuff. In addition, if you go back to the Model Code of Practice, you will find that there's also a glossary. Yes, they've got the consultation checklist. And then in Appendix E, you've got a summary of all the consultation requirements in the WHS regulations, which is really useful. So even if in the CoP that applies to you, your version of the CoP doesn't have the appendix, I would recommend going and having a look in the Model CoP. And if you're not aware what you got, if you've got a high-risk business, then you're going to find some extra requirements in the regulations. So, I would go and have a look at Appendix E if you're doing anything that could kill one or more people. So, if you're dealing with more serious risks, then I would go and have a look at that just to- as a good lead in to the regulations. If you already know the regulations backwards, then great, you don't need to bother. But there are over 600 regulations in WHS, so it's always worth checking up to make sure you haven't missed anything.

Extras in the Model CoP

We've kind of started already, but now we've really started we're going to talk about the extras in the Model Code of Practice.

Further Duties of PCBUs

In the modal Code of Practice, we get a reminder that designers, manufacturers, importers and suppliers have got safety responsibilities to ensure, so far as is reasonably practicable, that the plant's substance or structure that they are designing, etc, etc, is without risks to health and safety. And they've got a duty to carry out testing and analysis and to provide specific safety-related information about plant or substance. So there's a good reminder in there that we all, wherever we are in the supply chain, we've all got these responsibilities. And to assist in meeting these duties, the WHS regulations require manufacturers to consult with designers, importers to consult with designers and manufacturers, and whoever commissions construction work to consult with the designer of the structure, for example. There's a lot of useful extra pointers in the Model Code of Practice, which may not be in the version that, technically speaking/strictly speaking, you have to follow. So, worth a look.

Officers (of the PCBU)

And then there's also a reminder to officers of the business or undertaking. Basically, officers says- for example, company directors, those kinds of people, have a duty to exercise due diligence. And you have to go look at due diligence to see what that is. There are basically six bullet points in the act that describe due diligence. Again, it's all good common-sense stuff. There’s nothing esoteric in there or objectionable. And that due diligence includes taking reasonable steps to ensure that you've got appropriate processes for complying with the duty to consult as well as to duty- with workers sorry, as well as consulting, cooperating and coordinating with other duty holders. And there's further guidance on what's an officer in that interpretive guideline and under Section 27 of the law.

Principal Contractors

And then here is one I picked out. I've not got all of the requirements, but here's a useful one. There’s a particular regulation, number 309, that says if you're doing construction work the principal contractor for a construction project has a specific duty under WHS regulations to document in their WHS management plan the arrangements for consultation, cooperation and coordination. Now that's not unique, as we've just seen, to construction, but there is a specific requirement in there for a principal contractor. And WHS assumes a particular structure where you've got a prime contractor, or a principal contractor, who is leading the construction for the customer. So, have a look at that. There's also a CoP on the construction of structures so if you're in that game you'll find that useful too.

Major Hazard Facilities

And then I've got one slide on major hazard facilities. Now, a major hazard facility, strictly speaking, is a facility where you've got enough of a dangerous chemical- and it might be flammable, it might be toxic, it might be explosive, whatever it is. There's a whole list of chemicals in the regulations and it says if you've got so many tons of this or that, you've hit the threshold and you are operating a major hazard facility. There's a whole raft of extra regulations that apply to MHFs. And it says, for example, regulation 552 requires a major facility- sorry, a major hazard facilities safety case outline- so a safety case report by another name- to include a description of the consultation with workers that's been undertaken in the preparation of the safety case. Again, you've got a very specific requirement to consult with workers and to document it. Which, interestingly enough, generally, you don't have a duty to do that. It's not mandatory to document consultation. It's recommended. It's a good idea but you don't, strictly speaking, have to do it unless you're operating an MHF. And as it says there, there's a whole bunch of regulations that cover consultation about MHFs. But as I said, if you look at Appendix E of the Model Code of Practice, it's got them all listed, which is very helpful.

Detailed Requirements

A quick word about detailed requirements. Every Code of Practice contains detailed requirements that follow this formula. So, there are three words that indicate a legal requirement that must be complied with. And those three words are ‘must’, ‘requires’- or variations on that word-, and ‘mandatory’. So, any instances of those words- Probably not always, because they occasionally you come across a usage of ‘must’ or ‘requires’ where you go “Actually, that's just an English use-“ (if you know what I mean)-  “That’s just an English use of those words! It’s not really indicating a mandatory requirement”. But most of them do. So, in the Commonwealth Code of Practice, we have 41 instances of ‘must’. So, you've got to comply with those. You have 46 instances of ‘require’ and you've got to comply with those by law. Now, interestingly, in the Model Code of Practice, those numbers go up to 71 and 58, respectively. So, there're a lot more requirements in the Model Code of Practice. So, again, do make sure you've got the right Code of Practice that's been issued by the regulator for your jurisdiction. Because otherwise you might miss something you need to comply with or you might be complying with something that, strictly speaking, you don't have to. Although, of course, it's not a bad thing to do that but you don't have to.

Then there's the use of the word ‘should’, which is a recommended course of action, and ‘may’, suggests something that is optional. And again, in the Commonwealth Code of Practice, there are 62 instances of ‘should’ and 86 of ‘may’. Although I note that one of those instances of may, at least one, refers to the month of May when that Code of Practice was published. So, you've got to go through and make sure that they are relevant. And then it's slightly more in the Model Code of Practice. It’s 66 and 90, respectively. But the difference is not so great for the mandatory stuff. Now as I've said before, and in the risk management Code of Practice, my advice to you is you must comply with ‘musts’ and ‘required’s. ‘Should’ is recommendation so I would suggest complying with that unless you've got a good reason not to. In which case, I would document the fact that you've got a good reason not to and why you're not going to. And then ‘may’ is optional. You can do it if you want to and you can record the fact that you've considered those things and reject them if you want to but they are only options. So, I think there's- effectively we've got three tiers here. We've got ‘must comply’, ‘recommended’, and ‘you can do this if you think it's a good idea’.

And so the comment at the bottom, CoPs are not huge documents that typically a few tens of pages long. They will repay careful reading because you do have to comply with quite a lot of stuff that's in there and that's very clearly signposted, by the way. And also, of course, this particular Code of Practice is very useful for safety management plans. If you've got to write a safety management plan and you want to know what you have to include in it, then look in this Code of Practice and look in the Risk Management Code of Practice and make sure you include everything that is mandatory or ‘must’ or ‘requires’ and look at all the other stuff as well. And why not? If the copyright permits you to do so, which it usually does- not always, but usually. If the copyright permits you to do so and just copy and paste the stuff into your plan and then you know that you've got what you need. Then you can change the wording if you need to. But it will save you a lot of bother if you've got to write a safety management plan. It'll help you to make sure you've got everything you need to and it will save you a lot of effort. So, I recommend that I've done that myself.

Commentary #1

I think I've just got a couple of slides of commentary. It's worth reiterating that Codes of Practice are for all Australian industry. Whether it be a sole trader like myself operating out of our study or their garage or something, or whether it be a small operation- a family-run garage or shop, or whether it be the biggest corporation in Australia, whoever that is- if you're running a major mining operation. So, Codes of Practice provide minimum requirements. These are the things that you must comply with. In high-risk industries, you're probably going to have to do a lot more. And they do have a workplace application. So, they are written for the workplace. They're not really written for the designer, manufacturer, importer, supplier, etc. But nevertheless, it is very, very helpful if you are those people to look at the CoP in order to get an idea of what your customers have got to comply with and therefore what you're going to have to supply.

And as I've already said, CoP will repay careful reading because whilst they are guidance, they are really more than guidance. If you are ignorant of CoP and you don't do what they say you are exposing yourself to prosecution. So, see my introduction to Codes of Practice where I talk about that. There are three reasons why you must be aware of Codes of Practice. And this is one of those two Codes of Practice that everyone must be aware of. The others- if you're working with asbestos or welding or whatever it might be then there are specific Codes of Practice that you must be aware of for those activities. But this is one of those ones that applies to absolutely everybody, potentially. And as I've said before, the Model CoP has more detail than maybe some of the regulator-enforced Codes of Practice, which you will, I think, find helpful for higher risk applications. Whether legally you've got an MHF or not.

Commentary #2

And in fact, that's my point in slide two. So, not everyone is required to have a formal safety management system for managing safety risk in a- while something is in service, while it's being used. So, this CoP does not require us to have a formal safety management system, but it is required for major hazard facilities.
#AustralianWHS #CodesofPractice #Consult #Cooperate #Coordinate #coursesafetyengineering #engineersafety #ineedsafety #knowledgeofsafety #learnsafety #needforsafety #safetyblog #safetydo #safetyengineer #safetyengineerskills #safetyengineertraining #safetyengineeringcourse #safetyprinciples #softwaresafety #theneedforsafety #WHSCodeofPractice
Simon Di Nucci https://www.safetyartisan.com/2020/11/21/consultation-cooperation-coordination-cop/

The 2023 Digest The 2023 Digest brings you all The Safety Artisan's blog posts from last year. I hope that you find this a useful resou...