The Context of Reliability Theory in Engineering Systems David Blockley University of Bristol Bristol UK by.

Slides:



Advertisements
Similar presentations
BLADE SEMINAR 7th February 2001 RISK - HARD & SOFT David Blockley.
Advertisements

System Integration Verification and Validation
Software Engineering 1. Software development – the grand view 2. Requirements engineering.
IT Requirements Capture Process. Motivation for this seminar Discovering system requirements is hard. Formally testing use case conformance is hard. We.
Project management Project manager must;
Introduzione ai casi d’uso  Adriano Comai 1999 Pag. 1 Use Cases: an Introduction  Adriano Comai 1999.
The Miner… ’s - Lord Robens, Chairman of the NCB, concerned at the high absenteeism, asked a miner: “Why do you regularly work 4 shifts in stead.
Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 8 Slide 1 System models.
SWE Introduction to Software Engineering
1 SOFTWARE QUALITY ASSURANCE Basic Principles. 2 Requirements System Design Detailed Design Implementation Installation & Testing Maintenance SW Quality:
AAEC 3315 Agricultural Price Theory
Introduction Project Management Erol İnelmen Makro.
Project Management Hoang Huu Hanh, Hue University hanh-at-hueuni.edu.vn.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 5 Slide 1 Project management.
Introduction to Project Management The Basics for Sustainability Management Students.
Strategic Financial Decision-Making Framework
Project Management Body of Knowledge PMBOK
CSR Project, 3 cr. Corporate Responsibility, C-module (15 cr.) or free-choise studies Introduction to Corporate responsibility, 1,5-3 cr. (depending on.
 1. Introduction  2. Development Life-Cycle  3. Current Component Technologies  4. Component Quality Assurance  5. Advantages and Disadvantages.
QUALITY MANAGEMENT SYSTEM ACCORDING TO ISO
MethodGXP The Solution for the Confusion.
Magnox Swarf Storage Silos Programme Decommissioning Delivery Partnership Requirements February 2014 Gavin Askew.
PEIP National workshop in Montenegro: developing environmental infrastructure projects in the water sector Feasibility Study Preparation Venelina Varbova.
Information ITIL Technology Infrastructure Library ITIL.
Software Models (Cont.) 9/22/2015ICS 413 – Software Engineering1 -Component-based software engineering -Formal Development Model.
A framework to assess project technical progress.
 CS 5380 Software Engineering Chapter 8 Testing.
1 Human Performance in Reactor Safety George E. Apostolakis Massachusetts Institute of Technology Presented at the Quality Colloquium,
Total Quality Management. INTRODUCTION Total Quality Management (TQM) is customer oriented management philosophy and strategy. It is centered on quality.
CS 4310: Software Engineering Lecture 4 System Modeling The Analysis Stage.
M. Frize, Winter 2003 Reliability and Medical Devices Prof. Monique Frize, P. Eng., O.C. ELG5123/ February 2003.
Lecture 7 Risk Analysis CSCI – 3350 Software Engineering II Fall 2014 Bill Pine.
SIPI61508 Soft computing based qualitative method for determination of SILs István Ajtonyi 1 – László Ormos 2 1 University of Miskolc, Institute of Electric.
1 Advanced Software Architecture Muhammad Bilal Bashir PhD Scholar (Computer Science) Mohammad Ali Jinnah University.
Chapter 3 Project Management Chapter 3 Project Management Organising, planning and scheduling software projects.
Yarmouk University Department of Computer Information Systems CIS 499 Yarmouk University Department of Computer Information Systems CIS 499 Yarmouk University.
Main Requirements on Different Stages of the Licensing Process for New Nuclear Facilities Module 4.5/1 Design Geoff Vaughan University of Central Lancashire,
ATOS Analysis of Technical & Organisational Safety for major-accident prevention Risk analysis method integrating both technical and organisational factors.
Slide 1 Systems Analysis and Design With UML 2.0 An Object-Oriented Approach, Second Edition Chapter 1: Introduction to Systems Analysis and Design Alan.
Learning Objectives LO1 Understand the traditional approach to dealing with accounting uncertainty and going concern. LO2 Describe the main concepts of.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 9 Slide 1 Critical Systems Specification 1.
Safety Driven Performance Conference 2013 Integrating ModuSpec and WEST Engineering Services to advance excellence in drilling safety, integrity and performance.
+ The use of modeling in a Fatigue Risk Management System A Critical Review Drew Dawson, Torbjorn Akerstedt, Greg Belenky, Ian Noy.
Impact of evaluations matters IDEAS Conference 2011, Amman “Evidence to Policy: Lessons Learnt from Influential Impact Evaluations” Presenter: Daniel Svoboda,
Copyright 2013 John Wiley & Sons, Inc. Chapter 3 Monitoring and Controlling the Transformation System.
1 Criteria for a Successful FMEA Design & Process.
RLV Reliability Analysis Guidelines Terry Hardy AST-300/Systems Engineering and Training Division October 26, 2004.
International Atomic Energy Agency Regulatory Review of Safety Cases for Radioactive Waste Disposal Facilities David G Bennett 7 April 2014.
©Ian Sommerville 2000Software Engineering, 6th edition. Chapter 4 Slide 1 Project management l Organising, planning and scheduling software projects.
Comparing Designs By Chris McCall. Comparing Designs A decision-making method for deciding between many designs for a single specification Provides a.
Developed by Cool Pictures & MultiMedia PresentationsCopyright © 2004 by South-Western, a division of Thomson Learning. All rights reserved. Fundamentals.
Quality and reliability management in projects (seminar)
ISO 9001:2015 Subject: Quality Management System Clause 8 - Operation
Dolly Dhamodiwala CEO, Business Beacon Management Consultants
QUTE’98 Workshop Heidelberg, October 1998 A framework for the determination of user’s QoS requirements by Antony P Oodan of Telecommunications Quality.
1 Software Requirements Descriptions and specifications of a system.
1 Project management Organising, planning and scheduling software projects.
Information ITIL Technology Infrastructure Library ITIL.
An Overview on Risk Management
Software Engineering Lecture 4 System Modeling The Analysis Stage.
MAXIMISING VALUE FOR MONEY SUBJECT TO COST CONTAINMENT
Change Management V.N.Bhaskar Rao Engineering & Construction Director Amec Foster Wheeler India Operations.
Software Verification and Validation
11.1 Plan Risk Management The process of defining how to conduct risk management activities for a project Detailed risk planning enhances the overall probability.
Summer Pack IT Level 3.
TOTAL QUALITY MANAGEMENT
Presented By: Daniel J. Brown, CQA
CAYMAN ISLANDS MONETARY AUTHORITY
ENGINEERING ECONOMICS
Presentation transcript:

The Context of Reliability Theory in Engineering Systems David Blockley University of Bristol Bristol UK by

Contents Introduction Quality Process Holons BCIOD+R Evidence through Italian Flag Example Conclusions

Introduction  Reliability theory take up around world is patchy  Various approaches to uncertainty  Uncertainty has three components: FIR  Need for reliability theory to be set in context  Need for more general approach bring 'soft' and 'hard' together.

Quality ‘The totality of characteristics of an entity that bear upon its ability to satisfy stated and implied needs.’ ISO Too often used to refer only to functionality, not including safety, economy, sustainability Quality is a measure of how is the totality of what we are getting relative to what we want. Reliability and safety are part of quality. Reliability calculations are a small part of safety and of quality. Systems/modelling uncertainty Human factors Must not undervalue formal calculations Need to understand context

Hard & Soft' Systems hard physical system does not involve people action and reaction soft system involves people action, reaction, intention Treatment traditionally quite separate Engineering - objective Management - subjective Reliability calculations and QA systems are not independent Failures often at the interface How to take into account wider issues? Systems approach needed

Process  Interacting processes levels of precision of definition output is a product - a new process processes interact products are processes  Processes are the things that we do  The advantage of thinking about process is there in front of you clarity sub-processes

Quality The totality of the characteristics of a process which has, as its product, a new process. BCIOD+R  Business  Customer  Integrating  Operating  Delivery  Regulatory

0S n (E)S p (E)1

Past Present Future Soft & Hard Hazards Preconditions, trends patterns of concern Alternative Futures (Scenarios) Soft & Hard Identification of future hazards events with risk = chances + consequences + context Evidence Remove Change process Transfer Redesign etc Reduce (Strategic) What if questions share, redesign etc Remedy (Tactics) retain, redesign make acceptable contingency plans Managing systems to success based on evidence Time

PROCURING A NEW BUILDING FOR A PUMP PLANT Success: procure a building for the pump plant on time within the specifications of the client with an adequate level of safety and built within the available budget

PROCURING A NEW BUILDING FOR A PUMP PLANT

PERFORMING DETAILED DESIGN Success: Producing the detailed design of the pump building with an adequate level of safety on time through the appropriate specs and drawings

PERFORMING DETAILED DESIGN