DRAFT WAAS Integrity Resolution Process Pat Reddan 22 June 2005 ZETA ASSOCIATES.

Slides:



Advertisements
Similar presentations
Ways to Improve the Hazard Management Process
Advertisements

COSO I COSO II. Meycor COSO, a Comprehensive Solution for Enterprise Risk Management (ERM)
Building a Cradle-to-Grave Approach with Your Design Documentation and Data Denise D. Dion, EduQuest, Inc. and Gina To, Breathe Technologies, Inc.
Integra Consult A/S Safety Assessment. Integra Consult A/S SAFETY ASSESSMENT Objective Objective –Demonstrate that an acceptable level of safety will.
Risk Analysis Fundamentals and Application Robert L. Griffin International Plant Protection Convention Food and Agriculture Organization of the UN.
Andrea M. Landis, PhD, RN UW LEAH
Agency for Healthcare Research and Quality (AHRQ)
Comparative Emergency Management
Victorian Curriculum and Assessment Authority
PROJECT RISK MANAGEMENT
Information Risk Management Key Component for HIPAA Security Compliance Ann Geyer Tunitas Group
1. Introduction Consistency of learning processes To explain when a learning machine that minimizes empirical risk can achieve a small value of actual.
SWE Introduction to Software Engineering
Chapter 13: Audit Sampling Spring Overview of Sampling.
1 Risk evaluation Risk treatment. 2 Risk Management Process Risk Management Process.
SQM - 1DCS - ANULECTURE Software Quality Management Software Quality Management Processes V & V of Critical Software & Systems Ian Hirst.
Clinical Trials Hanyan Yang
Title slide PIPELINE QRA SEMINAR. PIPELINE RISK ASSESSMENT INTRODUCTION TO GENERAL RISK MANAGEMENT 2.
Surveillance. Definition Continuous and systematic process of collection, analysis, interpretation, and dissemination of descriptive information for monitoring.
Lucas Phillips Anurag Nanajipuram FAILURE MODE AND EFFECT ANALYSIS.
Hartley, Project Management: Integrating Strategy, Operations and Change, 3e Tilde Publishing Chapter 12 Integration Management Practising a common, coordinated.
Copyright © 2007 Pearson Education Canada 1 Chapter 12: Audit Sampling Concepts.
Codex Guidelines for the Application of HACCP
Project Risk Management
System Certification (Safety Assurance) of WAAS
Key changes and transition process
Key changes from OHSAS 18001:1999
Software Project Management
High Potential Incident Intervention. Background 2 The principle policy of Downer Blasting Services regarding to our staff is “Zero Harm” The success.
Basics of OHSAS Occupational Health & Safety Management System
Study Design. Study Designs Descriptive Studies Record events, observations or activities,documentaries No comparison group or intervention Describe.
Epidemiology The Basics Only… Adapted with permission from a class presentation developed by Dr. Charles Lynch – University of Iowa, Iowa City.
Risk Management - the process of identifying and controlling hazards to protect the force.  It’s five steps represent a logical thought process from.
Presented to: SBAS Technical Interoperability Working Group Date: 21 June 2005 Federal Aviation Administration Certification of the Wide Area Augmentation.
WHAT IS SYSTEM SAFETY? The field of safety analysis in which systems are evaluated using a number of different techniques to improve safety. There are.
Page 1 SQM: SBAS Workshop ZETA ASSOCIATES 21 June 2005.
Evaluation of software engineering. Software engineering research : Research in SE aims to achieve two main goals: 1) To increase the knowledge about.
Preventing Surgical Complications Prevent Harm from High Alert Medication- Anticoagulants in Primary Care Insert Date here Presenter:
WAAS Test Program Overview & In-service Monitoring Tom McHugh, ATO-P (ACB-430) DOT/FAA W.J.H. Technical Center WAAS Technical Director
Software Project Management
Survey of Medical Informatics CS 493 – Fall 2004 November 8, 2004 V. “Juggy” Jagannathan.
Inductive Generalizations Induction is the basis for our commonsense beliefs about the world. In the most general sense, inductive reasoning, is that in.
FAULT TREE ANALYSIS (FTA). QUANTITATIVE RISK ANALYSIS Some of the commonly used quantitative risk assessment methods are; 1.Fault tree analysis (FTA)
Método de NASA
Safety-Critical Systems T Ilkka Herttua. Safety Context Diagram HUMANPROCESS SYSTEM - Hardware - Software - Operating Rules.
Gile Sampling1 Sampling. Fundamental principles. Daniel Gile
Ch 10 - Risk Management Learning Objectives You should be able to: List and describe risk management processes, inputs, outputs, and tools List and describe.
Determining the Size of a Sample 1 Copyright © 2014 Pearson Education, Inc.
Search Engine Optimization © HiTech Institute. All rights reserved. Slide 1 What is Solution Assessment & Validation?
ILLINOIS COMMERCE COMMISSION Darin Burk Manager – Pipeline Safety 1.
Safety-Critical Systems 7 Summary T V - Lifecycle model System Acceptance System Integration & Test Module Integration & Test Requirements Analysis.
Building Simulation Model In this lecture, we are interested in whether a simulation model is accurate representation of the real system. We are interested.
Software Engineering B.Tech IT/II Sem-II Term: Unit-7 PPT SLIDES Text Books:1.Software Engineering, A practitioner’s approach Roger s. Pressman.
Loran Integrity Performance Panel The Loran Integrity Performance Panel (LORIPP) The LORIPP Team Loran Team Meeting McLean, VA July 30, 2002.
The Risk Management Process
Session 1 Module 1: Introduction to Data Integrity
Surveillance Key Points Dr. Oswaldo S. Medina Gómez.
Chapter 9 Audit Sampling – Part a.
Quality Control Copyright © 2015 McGraw-Hill Education. All rights reserved. No reproduction or distribution without the prior written consent of McGraw-Hill.
OHS RISK ASSESSMENT PROCEDURE Title: OHS Risk Assessment Procedure Document Unique Identifier: (Revision 2) Effective date: July 2014.
Research design By Dr.Ali Almesrawi asst. professor Ph.D.
ON “SOFTWARE ENGINEERING” SUBJECT TOPIC “RISK ANALYSIS AND MANAGEMENT” MASTER OF COMPUTER APPLICATION (5th Semester) Presented by: ANOOP GANGWAR SRMSCET,
Risk Assessment: A Practical Guide to Assessing Operational Risk
An Integrated Model-Based Approach to System Safety and Aircraft System Architecture Development Eric Villhauer – Systems Engineer Brian Jenkins – System.
Software Engineering B.Tech Ii csE Sem-II
Flooding Walkdown Guidance
Quality Risk Management
SCSC April 2018 A model for including cyber threat in safety cases
Quantitative Risk Assessment
A New Concept for Laboratory Quality Management Systems
Presentation transcript:

DRAFT WAAS Integrity Resolution Process Pat Reddan 22 June 2005 ZETA ASSOCIATES

Z01225/2004 Page 2 ZETA ASSOCIATES WIRP Objectives “Purpose of the WIRP is to assess the validity of a threat against the fielded WAAS by providing an evaluation of the threat for the fault tree and, in the event that the probability exceeds the margin in the fault tree, determine an acceptable exposure time to the threat. ” The WAAS Integrity Resolution Process (WIRP) provides means to address integrity threats against fielded WAAS —Integrity threats assigned to nodes on fault tree —Mitigation of threat is lengthy, complex —All changes must adhere to WAAS Change Control Process (WCCP) Evaluation of threats against operational system introduces complexity in PASS/FAIL criteria as well as action or response —Response options are Service shutdown, switch to emergency mode, place a GEO in test mode, revert to previous system build —Acceptable or tolerable exposure time is THE key factor in dealing with operational system —Focus of WIPP investigation of such threats is exposure time

Z01225/2004 Page 3 ZETA ASSOCIATES WIRP

Z01225/2004 Page 4 ZETA ASSOCIATES WIRP Process initiated by either Integrity Hazard Record or WAAS Integrity Problem Report —WAAS Safety Team reviews all hazard records & problem reports (WPRs) in context of fault tree WIPP review determines whether hazard is an ‘acceptable risk’ & if not, performs hazard assessment analysis —‘acceptable risk’ finding supported with WIPP assertion (used in HMI analysis document) that reflects characteristic of WAAS which is known to be true along with rationale —Hazard assessment determines a P(HMI) allocation for the threat & the exposure time –Result is an acceptable risk for a specific time period

Z01225/2004 Page 5 ZETA ASSOCIATES Hazard Assessment Guidelines Each integrity threat evaluated on case by case basis, NO definitive set of rules to be applied in Hazard Assessment Models --- can base on empirical data (IOC 30-day HMI set, FLP HMI sets, offline monitoring data from FAATC, field data) —Level D generated results mean additional data necessary Single fault at a time -- directly affects exposure time, should only be invoked for truly rare, random & uncorrelated events Exposure time – set to zero UNLESS HMI analysis allocation has margin to accommodate the specific threat —WIPP collective judgment & rationale forms basis for non-zero exposure period on case by case basis

Z01225/2004 Page 6 ZETA ASSOCIATES Types of Integrity Threats

Z01225/2004 Page 7 ZETA ASSOCIATES WIRP Example Range Domain Monitor – algorithm equation error unearthed during review of changes associated with GIVE monitor WAAS Integrity Fault Tress Resolution – node 10R, RDM Algorithm performance fails, cannot be justified Temporary Assertion – probability of C&V CP L1/L2 bias or station clock error causing 5.33 sigma error is neglibile WIRP Probability Allocation – 4.50E-8 Rationale – actual range domain monitor threat not observed since RDM was fielded, analysis of this observed performance shows event likelihood of …. Exposure Time – six months if RDM is needed to mitigate HMI