LECTURE 28. Course: “Design of Systems: Structural Approach” Dept. “Communication Networks &Systems”, Faculty of Radioengineering & Cybernetics Moscow.

Slides:



Advertisements
Similar presentations
5 december 2011 Living Probabilistic Asset Management Dr.ir. J.A. van den Bogaard.
Advertisements

TALOS Total ATM Life-cycle operational Solution. The Cost equation Life cycle costs are high Life cycle costs are complex Life cycle costs involve all.
COURSE “SYSTEM DESIGN: STRUCTURAL APPROACH” DETC Inst. for Information Transmission Problems Russian Academy of Sciences, Moscow , Russia.
R R R CSE870: Advanced Software Engineering (Cheng): Intro to Software Engineering1 Advanced Software Engineering Dr. Cheng Overview of Software Engineering.
Chapter 6 Database Design
REAL-TIME SOFTWARE SYSTEMS DEVELOPMENT Instructor: Dr. Hany H. Ammar Dept. of Computer Science and Electrical Engineering, WVU.
Health Informatics Series
7.2 System Development Life Cycle (SDLC)
Towards Modelling Information Security with Key-Challenge Petri Nets Teijo Venäläinen
Predictive Maintenance: Condition monitoring Tools and Systems for asset management September 19, 2007.
By : Alanoud Al Saleh. What is PACS quality control ? The PACS monitor quality control (QC) program objectives are:  to ensure consistent display performance.
LECTURE 1. Course: “Design of Systems: Structural Approach” Dept. “Communication Networks &Systems”, Faculty of Radioengineering & Cybernetics Moscow Inst.
LECTURE 29. Course: “Design of Systems: Structural Approach” Dept. “Communication Networks &Systems”, Faculty of Radioengineering & Cybernetics Moscow.
Term 2, 2011 Week 3. CONTENTS The physical design of a network Network diagrams People who develop and support networks Developing a network Supporting.
 The software systems must do what they are supposed to do. “do the right things”  They must perform these specific tasks correctly or satisfactorily.
LECTURE 5-6. Course: “Design of Systems: Structural Approach” Dept. “Communication Networks &Systems”, Faculty of Radioengineering & Cybernetics Moscow.
REAL-TIME SOFTWARE SYSTEMS DEVELOPMENT Instructor: Dr. Hany H. Ammar Dept. of Computer Science and Electrical Engineering, WVU.
CPIS 357 Software Quality & Testing
Version 4.0. Objectives Describe how networks impact our daily lives. Describe the role of data networking in the human network. Identify the key components.
1 Chapter 9 Database Design. 2 2 In this chapter, you will learn: That successful database design must reflect the information system of which the database.
Week 4 Lecture Part 3 of 3 Database Design Samuel ConnSamuel Conn, Faculty Suggestions for using the Lecture Slides.
Module N° 8 – SSP implementation plan. SSP – A structured approach Module 2 Basic safety management concepts Module 2 Basic safety management concepts.
ECARE+ FP7 Workshop “Seamless aircraft health management for a permanent serviceable fleet” PARAGON LTD Company Presentation Expression of Interest Harry.
LECTURE 8-9. Course: “Design of Systems: Structural Approach” Dept. “Communication Networks &Systems”, Faculty of Radioengineering & Cybernetics Moscow.
LECTURE (compressed version). Course: “Design of Systems: Structural Approach” Dept. “Communication Networks &Systems”, Faculty of Radioengineering.
Planning and Analysis Tools to Evaluate Distribution Automation Implementation and Benefits Anil Pahwa Kansas State University Power Systems Conference.
Future & Emerging Technologies in the Information Society Technologies programme of European Commission Future & Emerging Technologies in the Information.
TOWARDS HIERARCHICAL CLUSTERING
LECTURE 19. Course: “Design of Systems: Structural Approach” Dept. “Communication Networks &Systems”, Faculty of Radioengineering & Cybernetics Moscow.
The Grid System Design Liu Xiangrui Beijing Institute of Technology.
LECTURE Course: “Design of Systems: Structural Approach” Dept. “Communication Networks &Systems”, Faculty of Radioengineering & Cybernetics Moscow.
Middleware for FIs Apeego House 4B, Tardeo Rd. Mumbai Tel: Fax:
LECTURE 13. Course: “Design of Systems: Structural Approach” Dept. “Communication Networks &Systems”, Faculty of Radioengineering & Cybernetics Moscow.
LECTURE 26. Course: “Design of Systems: Structural Approach” Dept. “Communication Networks &Systems”, Faculty of Radioengineering & Cybernetics Moscow.
CE Operating Systems Lecture 3 Overview of OS functions and structure.
Towards Communication Network Development (structural systems issues, combinatorial models) Mark Sh. Levin Inst. for Inform. Transmission Problems, Russian.
Glen Fields - Final Project Presentation. What Sets CSI Apart... GBA 573 Consultants Company Background Located in San Diego, CA 5 Engineering Consultants.
Business Data Communications, Fourth Edition Chapter 11: Network Management.
 2001 Prentice Hall Business Publishing, Accounting Information Systems, 8/E, Bodnar/Hopwood Systems Implementation, Operation, and Control Chapter.
LECTURE 4. Course: “Design of Systems: Structural Approach” Dept. “Communication Networks &Systems”, Faculty of Radioengineering & Cybernetics Moscow Inst.
PM4WAT Preventive Maintenance for Water Utilities LEONARDO DA VINCI - Multilateral Project Development of Innovation Started in November 2009 Duration:
LECTURE 16. Course: “Design of Systems: Structural Approach” Dept. “Communication Networks &Systems”, Faculty of Radioengineering & Cybernetics Moscow.
STUDENT RESEARCH PROJECTS IN SYSTEM DESIGN Inst. for Information Transmission Problems Russian Academy of Sciences, Moscow , Russia
LECTURE Course: “Design of Systems: Structural Approach” Dept. “Communication Networks &Systems”, Faculty of Radioengineering & Cybernetics Moscow.
LECTURE 2-3. Course: “Design of Systems: Structural Approach” Dept. “Communication Networks &Systems”, Faculty of Radioengineering & Cybernetics Moscow.
Saad Haj Bakry, PhD, CEng, FIEE 1 Network Management Support Saad Haj Bakry, PhD, CEng, FIEE P RESENTATIONS IN N ETWORK M ANAGEMENT.
LECTURE 10. Course: “Design of Systems: Structural Approach” Dept. “Communication Networks &Systems”, Faculty of Radioengineering & Cybernetics Moscow.
ISECON Columbus, Ohio - October 7, 2005 Whither IS? Issues and Problems in Classifying CC2005 Programs Using CIP Codes Paul Leidig, George Nezlek,
LECTURE 27. Course: “Design of Systems: Structural Approach” Dept. “Communication Networks &Systems”, Faculty of Radioengineering & Cybernetics Moscow.
Erman Taşkın. Information security aspects of business continuity management Objective: To counteract interruptions to business activities and to protect.
LECTURE Course: “Design of Systems: Structural Approach” Dept. “Communication Networks &Systems”, Faculty of Radioengineering & Cybernetics Moscow.
DeSIRE Workshop, Pisa, 25-26/11/2002 1/7 A Case Study in Air Traffic Control Alberto Pasquini Deep Blue Srl.
Maintenance Management [14]
LECTURE 7. Course: “Design of Systems: Structural Approach” Dept. “Communication Networks &Systems”, Faculty of Radioengineering & Cybernetics Moscow Inst.
SYSTEMSDESIGNANALYSIS 1 Chapter 21 Implementation Jerry Post Copyright © 1997.
Retrofitting and Maintenance. Regular Maintenance is Necessary Failure to Perform Maintenance Leads to….. Diminished Performance Deterioration Failure.
Maintenance Management
Software Design and Architecture
1.3 Operating system services An operating system provide services to programs and to the users of the program. It provides an environment for the execution.
Control Systems Design Slovak University of Technology Faculty of Material Science and Technology in Trnava 2007.
TOWARDS FOUR-LAYER FRAMEWORK OF COMBINATORIAL PROBLEMS
Maintenance strategies
TOPIC: THE VALUE OF BIOMEDICAL ENGINEERS AND TECHNICIANS IN HOSPITAL PRESANTED BY: KWIZERA ABRAHAM STUDENT IN: BMET /FINALIST STU INSTITUTION: IPRC KIGALI.
Chapter 18 Maintaining Information Systems
Chapter 6 Database Design
Enterprise Systems Management – ESM821S
Operations Management
Systems Design, Implementation, and Operation
Operations Management
Operations Management
Presentation transcript:

LECTURE 28. Course: “Design of Systems: Structural Approach” Dept. “Communication Networks &Systems”, Faculty of Radioengineering & Cybernetics Moscow Institute of Physics and Technology (University) / Mark Sh. Levin Inst. for Information Transmission Problems, RAS Nov. 19, 2004 PLAN: 1.Preliminaries: life cycle, systems, utilization, personnel, maintenance, roles 2.Framework of maintenance process: *basic framework, *systems under maintenance *maintenance operations (inspection as testing/analysis/diagnosis, repair, *replacement) *etc. 3.Illustrations: basic analogue (monitoring system), trajectory of fault.

1.Preliminaries R & D t ManufacturingTestingMarketing Utilization & Maintenance Recycling 0 T NOW: HERE SYSTEM PERSONNEL

1.Preliminaries R & D t ManufacturingTestingMarketing Utilization & Maintenance Recycling 0 T NOW: HERE SYSTEM UTILIZATION (e.g., driver, pilot, operator) MAINTENANCE (support of system & personnel) MAINTENANCE ACTIONS: *system installation *training of personnel *regular testing of personnel *planning / scheduling of maintenance operations *execution of operations (inspection, repair, replacement) *analysis of the system, accumulation of data, prediction

1.Preliminaries EXAMPLES: SYSTEM UTILIZATION MAINTENANCE 1.Car Driver, passengers Maintenance personnel 2.Airlane Pilot, passengers Maintenance personnel 3.Human Human Doctor, human 4.House Owner Maintenance personnel, owner 5.Computer User(s) Maintenance personnel, special software, user(s)

2.Framework TYPICAL FAILURE RATE CURVE: Failure rate Time Useful period Infant mortality Wear out period

2.Framework AN ORDINAL SCALE FOR FAULTS: 1.OK 2.Small fault 3.Significant fault 4.Damage (destriction)

2.Framework OBJECT UNDER MAINTENANCE: 1.System and / or system part (component, unit) 2.System state 3.System function or function cluster (as a group of interrelated functions)

2.Framework MAINTENANCE FRAMEWORK (problems): 1.System analysis / evaluation (systems, its part, etc.) 2.System prediction 3.Operational management / preventive maintenance: *testing *evaluation *additional information *repair / replacement 4.Design of information model for system and each part (object) 5.System strategy: *selection of object under maintenance *selection of operation (i.e., inspection, repair, replacement) *assignment of time for operation(s) *execution of the operation(s)

2.Framework SYSTEM Planning Models for system, faults, prediction Maintenance operations (scanning, repair, replacement) MODELS: *selection, *knapsack, *routing, *assignment / allocation, etc. *probabilistic models, Markov processes *reliability evaluation / analysis *safety analysis *simulation *etc. Analysis, accumulation, processing, integration (fusion), distribution of information

2.Framework SYSTEMS UNDER MAINTENANCE: 1.Whole system 2.Multi-component (modular) system: *one-layer modular system *hierarchical (multi-layer) system *multi-layer modular system with complex module interrelation (including interrelation between different layers and branches) 3.Developping systems (e.g., upgrade of components, structure, interconnection) 4.Change of external environment

2.Framework KINDS OF MAINTENANCE: 1.BASIC MAINTENANCE: faults => operation 2.PREVENTIVE MAINTENANCE: prediction of faults => preliminary maintenance operation 3.SELF-MAINTENANCE

2.Framework SYSTEM CHARACTERISTICS: 1.Reliability (stability, etc.) 2.Safety 3.Viability, survivability 4.Robustness 4.Performance

2.Framework PROBLEMS & MODELS OF PREVENTIVE MAINTENANCE: 1.REVELATION (ALLOCATION) OF TEST POINTS Models: multicriteria selection, knapsack-like problems, allocation problems, etc. 2.PLANNING TEST OPERATIONS Models: multicriteria selection, knapsack-like problems, scheduling, etc.

2.Framework MODELING & INFORMATION PROCESSING: 1.Modeling of faults 2.Diagnosis of faults 3.Monitoring of faults 4.Tracking of faults 5.Integration (fusion) of information on local faults 6.Distribution of information on faults for various information systems and specialists

2.Framework BASIC ACTIONS 1.Scanning 2.Small repair / replacement 3.Essencial repair / replacement SYSTEM LAYERS 1.System 2.System parts (group of states, group of functions) 3.Components (state, function) SYSTEM

3.Basic analogue: Monitoring systems R Control Integration (fusion), analysis SENSORS ACTUATORS

Illustration: Accumulation of information Normal situation T 0 Small fault Medium fault Trajectory of faults (for components) SYSTEM System component Small fault FAULT/ DAMAGE