How: System Requirements Hazard Analysis with Mil-Std-882E
What you'll learn
- Recognize the Elements of System Requirements Hazard Analysis
- Understand Task 203's Purpose and Vital Importance
- Understand Task 203's Description; Reporting & Contracting Requirements
- Apply Lessons Learned to Enhance Task 203's Value and Effectiveness
Requirements
- No prior experience needed, although you will benefit from understanding basic concepts of System Safety.
Description
System Requirements Hazard Analysis
We're talking about system requirements hazard analysis, as part of our series on Mil-Std-882E. It's a very widely used system safety engineering standard and its influence is found in many places, not just on military procurement programs.
Topics for this Session
We're going to look at this task, which is very important, possibly the most important task of all, as we'll see. We'll talk about the purpose of the task, which is word for word from the task description itself. We're going to talk about in the task description, the three aims of this task, which are to determine or work out requirements, incorporate them, and then assess the compliance of the system with those requirements, because, of course, it may not be a simple read-across. We’ve got six slides on that. That's most of the task. Then we’ve just got one slide on contracting, which if you've seen any of the others in this series, will seem very familiar. We've got a little bit of a chat about Section 4.2 from the standard and some commentary, and the reason for that will become clear. So, let's crack on.
System Requirements Hazard Analysis: Purpose
Task 203.1, the purpose of Task 203 is to perform and document a System Requirements Hazard Analysis or SRHA. And as we've already said, this aims to determine the design requirements. We're going to focus on design rather than buying stuff off the shelf – we'll talk about the implications of that a little bit later. Design requirements to eliminate or reduce hazards and risks, incorporate those requirements, into a says, into the documentation, but what it should say is incorporate risk reduction measures into the system itself and then document it. And then finally, to assess compliance of the system with these requirements. Then it says the SRHA address addresses all life-cycle phases, so not just meant for you to think about certain phases of the program. What are the requirements for the system throughout life? And in all modes. Whether it's in operation, whether it's in maintenance or refit, whether it's being repaired or disposed of, whatever it might be.
Who this course is for:
- Beginners in Hazard Analysis, Safety Risk Assessment, Designers, Managers.
Instructor
Hi, I'm Simon Di Nucci, and I have spent 25+ years as a system safety engineer. I have always sought to pass on my expertise to others.
I was part of the team that taught the official safety engineering courses to all UK Ministry of Defence staff. I then went on to create bespoke safety courses for several different clients, including the UK Military Aviation Authority. I'm now teaching safety online, to anyone who wants to do Safety, Just Right.
To do this, I have drawn on my wide and deep experience in safety consulting and engineering. Much of my career has been working for governments or consulting to the public sector on Australian, UK, US, and European programs.
I am a Fellow of Engineers Australia (FIE(Aust)) and on the National Engineering Register, so studying my courses will count for EA CPD. I have an MSc in Safety-Critical Systems Engineering.