Information Aids for Diagnosis Tasks Based on Operators’ Strategies 2003. 1. 13 김 종 현.

Slides:



Advertisements
Similar presentations
Reasoning about human error with interactive systems based on formal models of behaviour Paul Curzon Queen Mary, University of London Paul Curzon Queen.
Advertisements

Intelligent systems Lecture 6 Rules, Semantic nets.
Introduction to Fault Diagnosis and Isolation(FDI) By Hariharan Kannan.
Psychological Aspects of Risk Management and Technology – G. Grote ETHZ, Fall09 Psychological Aspects of Risk Management and Technology – Overview.
Agent Mediated Grid Services in e-Learning Chun Yan, Miao School of Computer Engineering Nanyang Technological University (NTU) Singapore April,
Report on Intrusion Detection and Data Fusion By Ganesh Godavari.
1 Learning from Behavior Performances vs Abstract Behavior Descriptions Tolga Konik University of Michigan.
Mary (Missy) Cummings Humans & Automation Lab
Logical Agents Chapter 7 Feb 26, Knowledge and Reasoning Knowledge of action outcome enables problem solving –a reflex agent can only find way from.
Chapter 7 design rules.
+ Universal Access in the Information Society Journal Elspeth McKay Published Online: March 24, 2007 Planning Effective HCI to Enhance Access to Educational.
Systems Analysis – Analyzing Requirements.  Analyzing requirement stage identifies user information needs and new systems requirements  IS dev team.
Artificial Intelligence Lecture No. 15 Dr. Asad Ali Safi ​ Assistant Professor, Department of Computer Science, COMSATS Institute of Information Technology.
© 2007 Tom Beckman Features:  Are autonomous software entities that act as a user’s assistant to perform discrete tasks, simplifying or completely automating.
Comp 20 - Training & Instructional Design Unit 6 - Assessment This material was developed by Columbia University, funded by the Department of Health and.
Testing Workflow In the Unified Process and Agile/Scrum processes.
Report on Intrusion Detection and Data Fusion By Ganesh Godavari.
Synthetic Cognitive Agent Situational Awareness Components Sanford T. Freedman and Julie A. Adams Department of Electrical Engineering and Computer Science.
1 Introduction to Software Engineering Lecture 1.
AN INTELLIGENT AGENT is a software entity that senses its environment and then carries out some operations on behalf of a user, with a certain degree of.
Human-computer interaction: users, tasks & designs User modelling in user-centred system design (UCSD) Use with Human Computer Interaction by Serengul.
Allen D. Malony Department of Computer and Information Science TAU Performance Research Laboratory University of Oregon Discussion:
Human Factors Issues Chapter 8. What is Human Factors? Application of the scientific knowledge of human capabilities and limitations to the design of.
U SER I NTERFACE L ABORATORY Situation Awareness a state of knowledge, from the processes used to achieve that state (situation assessment) not encompass.
Software Engineering Saeed Akhtar The University of Lahore.
Development of Expertise. Expertise We are very good (perhaps even expert) at many things: - driving - reading - writing - talking What are some other.
Traditional Economic Model of Quality of Conformance
Beyond Chunking: Learning in Soar March 22, 2003 John E. Laird Shelley Nason, Andrew Nuxoll and a cast of many others University of Michigan.
Unclassified//For Official Use Only 1 RAPID: Representation and Analysis of Probabilistic Intelligence Data Carnegie Mellon University PI : Prof. Jaime.
Wagner Associates NCSD-ADS-DOC ARO Workshop on Cyber Situation Awareness RPD-inspired Hypothesis Reasoning for Cyber Situation Awareness.
Control-Theoretic Approaches for Dynamic Information Assurance George Vachtsevanos Georgia Tech Working Meeting U. C. Berkeley February 5, 2003.
IEEE AI - BASED POWER SYSTEM TRANSIENT SECURITY ASSESSMENT Dr. Hossam Talaat Dept. of Electrical Power & Machines Faculty of Engineering - Ain Shams.
Copyright 2006 John Wiley & Sons, Inc Chapter 5 – Cognitive Engineering HCI: Developing Effective Organizational Information Systems Dov Te’eni Jane Carey.
Human Factors in Main Control Room of Nuclear Power Plants Jong Hyun Kim.
Chapter 7 design rules. Designing for maximum usability – the goal of interaction design Principles of usability –general understanding Standards and.
Effect Estimation of the Integrated HMI Seung Jun Lee Nuclear I&C and Information Engineering Laboratory Dept. of Nuclear and Quantum Engineering KAIST.
SOFTWARE TESTING TRAINING TOOLS SUPPORT FOR SOFTWARE TESTING Chapter 6 immaculateres 1.
Nursing Process n116. The Nursing Process  Assessment  Diagnosis  Planning  Implementing  Evaluating.
Design rules.
Role of Data Quality in GIS Decision Support Tools
Transaction Processing System (TPS)
Working in the Forms Developer Environment
Decision Support Systems
Chapter 14: System Protection
PLM, Document and Workflow Management
Organizing Students for Cognitively Complex Tasks
Chapter 8 – Software Testing
Event Studio Cognos 8 BI.
Dept. of Nuclear and Quantum Engineering
AI emerging trend in QA Sanjeev Kumar Jha, Senior Consultant
Human Factors Issues Chapter 8 Paul King.
Modeling Cyberspace Operations
Transaction Processing System (TPS)
Model Based Testing Venkata Ramana Bandari, Expert Software Engineer
Fundamental Test Process
Transaction Processing System (TPS)
Computerized Decision Support for Medical Imaging
Test Case Test case Describes an input Description and an expected output Description. Test case ID Section 1: Before execution Section 2: After execution.
Subsuption Architecture
Chapter 14: Protection.
Decision Support Systems
Chapter 10 Quality Improvement.
Chapter 7 design rules.
Chapter 7 design rules.
Chapter 7 design rules.
1.3 Classifying Engineering Tasks
BBA V SEMESTER (BBA 502) DR. TABASSUM ALI
M. Kezunovic (P.I.) S. S. Luo D. Ristanovic Texas A&M University
T-FLEX DOCs PLM, Document and Workflow Management.
Chapter 7 design rules.
Presentation transcript:

Information Aids for Diagnosis Tasks Based on Operators’ Strategies 김 종 현

INFORMATION HIERARCHY Abstractive Information aid – information integration

Classes of IDSSs Input Information Overload (IIO) –Too much information –Filter the information and remove the redundant or superfluous parts Incomplete information –The information that is missing or ill-defined –Provide the missing default information or reason with incomplete information Insufficient information –The additional information exists potentially, but a separate and specific effort is required to bring it out. –Extrapolation, prediction, calculation evaluation, and trend

Information Aid Systems for MCR Operators Monitoring/ Detection Monitoring/ Detection Situation Assessment Situation Assessment Response Planning Response Planning Response Implementation Response Implementation Alarm System Instrumentation System Instrumentation System Control/Protection System Control/Protection System Plant Fault Diagnosis System Fault Diagnosis System Computer-based procedure Computer-based procedure Implementation System Implementation System Display System

Information Aid Systems for MCR Operators FeaturesDisadvantage or Problems Alarm System Need: information overload Features: alarm definition, alarm processing, alarm prioritization, alarm display, and alarm control and management Lack of positional information Fault diagnostic system Need: fault propagation, PRA, accident management Features: on-line and off-line, component and plant-wide Limitation in capability of the systems Lack of supporting operators’ diagnostic strategies Computer- based procedure system Purpose: to guide operators’ actions in performing their tasks in order to increase the likelihood that the goals of the tasks would be safely achieved Features: automatic identification of procedure, automatic calculation of procedure-referenced valued, etc. Lack of supporting operators’ dynamic operation strategies

Information Aid Systems for MCR Operators Underlying causes of the problems –Lack of understanding operators’ dynamic strategies of the tasks Providing hypotheses and computerizing procedures are not enough to support MCR operators –Ambiguity in allocating roles to operators and support systems in the tasks Defining the roles or relationship between two agents (operator and support system), that is automation level, is vague.

Paradigm Change in Decision Support Systems ProsthesisInstrumentAgent

Automation Levels of OSSs Level 0 It refers to the classical paper operation manual, computerized or not. The OSS is reduced to to a simple knowledge database Level 1 It is characterized by an OSS connected to the system being controlled. It helps by determining possible situations (contexts) which the operator then select. It is able to start a process of analytical reasoning, interacting with the operator. The operator answers the questions, applies to the procedures or not, and can stop the reasoning at any time Level 2 It determines contexts and suggests one which the operator should follow. All possible contexts are presented with a likelihood judgments. Some questions are automated, i.e., the OSS checks the truth of the corresponding request information, and presents the selected answers to the operator Level 3 It selects a context automatically. It presents procedures to apply and the operator approves or not. The OSS applies the procedure and sends the message ‘executed’ to the operator Level 4 All the questions which do not necessitate operator confirmation are totally automated. The procedures are applied automatically. The situation recognition part is totally automated. Level 5 Everything is automated.

Requirements for OSSs Building systems –Accuracy –Coverage Strategy supporting –Task analysis –Strategy analysis –Role defining –Transparency

Process to Develop Support Systems in MCRs The operational tasks that must be performed A model of human performance for these tasks A model of how control room features are intended to support performance

Operational Task: Diagnosis Normal Operation Abnormal operation Emergency operation monitoringaction Immediate response diagnosis Corrective action Immediate Response (safety parameter) diagnosis Corrective action

Operational Task: Diagnosis Diagnosis –Monitoring –Decision making (determination of the plant status and the corresponding procedure) Control –Goal-oriented tasks –Tuning plant parameters, making changes in plant mode (e.g., startup, shutdown, intermediate power change), performing switch over, etc. –The feedback is important.

Diagnostic Strategies: Two Aspects Bottom-up process –Data-driven process or Forward reasoning –Observations to hypothesis –Early in the information processing –Familiar faults Top-down process –Hypothesis (goal)-driven process or Backward reasoning –Hypothesis to observation –Novel faults

Diagnostic Strategies Topographic search

Diagnostic Strategies Symptomatic search Pattern recognition

Diagnostic Strategies Symptomatic search Decision table search

Diagnostic Strategies Symptomatic search Hypothesis-and-test strategy

Diagnostic Strategies A comparison of the resource requirements of the various diagnostic strategies Performance factor Topological search Recognition Decision table Hypothesis and test Time spent -Low-- Number of observations HighLow- Dependency on pattern perception -High-- Load of short-term memory Low High Complexity of cognitive processes Low -High Complexity of functional model Low--High General applicability of tactical rules High--Low Dependency on malfunction experience LowHigh-Low Dependency on malfunction preanalysis --high-

Information Aid Systems from the Viewpoint of Diagnostic Strategy Alarm system Fault diagnostic system

Information Aid Systems from the Viewpoint of Diagnostic Strategy

A Proposition for Information Aids in Diagnosis Tasks “Computational technology should be used to aid the operator in the process of solving his problem,” and therefore, should support the operator along with his/her diagnostic strategy FeatureProcess to be supported Alarm processing Topological search, pattern matching in symptomatic search, bottom-up process Hypothesis+model of function in hypothetical failed system + reference symptom pattern Hypothesis-and-test strategy, decision table search, top-down processing

Further Study Experiment –FISA-2/PC : Visual display unit –Alarm processing module –Fault diagnosis module