Managing informal aspects of decision processes for improving reactivity of industrial systems Aline CAUVIN, Riad MEGARTSI DIAM-IMS Domaine Universitaire.

Slides:



Advertisements
Similar presentations
Software Modeling SWE5441 Lecture 3 Eng. Mohammed Timraz
Advertisements

ITIL: Service Transition
Prof. Ing. M. Dassisti Enterprise modelling for networked enterprise: interaction aspects for a training organisation 16th IFAC World Congress, Prague.
Introduction To System Analysis and Design
Supporting Design Managing complexity of designing Expressing ideas Testing ideas Quality assurance.
Chapter 1 Assuming the Role of the Systems Analyst
Lecture 13 Revision IMS Systems Analysis and Design.
Requirements Analysis Concepts & Principles
Fundamentals of Information Systems, Second Edition 1 Information and Decision Support Systems Chapter 6.
Analysis Concepts and Principles
Lesson-7 Players in the Systems Game
Chapter 1 Assuming the Role of the Systems Analyst
Chapter 2: IS Building Blocks Objectives
SE 555 – Software Requirements & Specifications Introduction
IS550: Software requirements engineering Dr. Azeddine Chikh 4. Validation and management.
Lead Black Slide. © 2001 Business & Information Systems 2/e2 Chapter 13 Developing and Managing Information Systems.
A Design Process Introduction © 2011 Project Lead The Way, Inc.
1 Objective of today’s lesson S oftware engineering occurs as a consequence of a process called system engineering. Instead of concentrating solely on.
System Engineering Instructor: Dr. Jerry Gao. System Engineering Jerry Gao, Ph.D. Jan System Engineering Hierarchy - System Modeling - Information.
The database development process
The Software Development Cycle Defining and understanding the problem.
CIS 321—IS Analysis & Design Chapter 1: The World of the Modern Systems Analyst.
Katanosh Morovat.   This concept is a formal approach for identifying the rules that encapsulate the structure, constraint, and control of the operation.
1 - 1 Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
A Design Process.
CSI315 Web Applications and Technology Overview of Systems Development (342)
Information System and Management
© 2001 Business & Information Systems 2/e1 Chapter 13 Developing and Managing Information Systems.
CB1004 Modelling Business Systems 71 Modelling Business Systems 7 Systems Methods.
Business Analysis and Essential Competencies
Topic (1)Software Engineering (601321)1 Introduction Complex and large SW. SW crises Expensive HW. Custom SW. Batch execution.
Chapter 10 Information Systems Analysis and Design
OBJECT ORIENTED SYSTEM ANALYSIS AND DESIGN. COURSE OUTLINE The world of the Information Systems Analyst Approaches to System Development The Analyst as.
Rev. 0 CONFIDENTIAL Mod.19 02/00 Rev.2 Mobile Terminals S.p.A. Trieste Author: M.Fragiacomo, D.Protti, M.Torelli 31 Project Idea Feasibility.
Software Requirements Engineering: What, Why, Who, When, and How
1-1 System Development Process System development process – a set of activities, methods, best practices, deliverables, and automated tools that stakeholders.
Project Life Cycles.
Chapter 7 Applying UML and Patterns Craig Larman
Chapter 7 System models.
1 CIM OSA CIMOSA Computer Integrated Manufacturing Open System Architecture 1 David CHEN IMS-LAPS, University Bordeaux 1.
Sommerville 2004,Mejia-Alvarez 2009Software Engineering, 7th edition. Chapter 8 Slide 1 System models.
Computers Are Your Future © 2008 Prentice Hall, Inc.
Illustrations and Answers for TDT4252 exam, June
Information Systems Engineering. Lecture Outline Information Systems Architecture Information System Architecture components Information Engineering Phases.
Ken Youssefi Mechanical Engineering department 1 Introduction to Concurrent Engineering Computer Aided Design (CAD) Computer Aided Manufacturing (CAM)
2-1 A Federation of Information Systems. 2-2 Information System Applications.
Chapter 4 Decision Support System & Artificial Intelligence.
© 2013, published by Flat World Knowledge Chapter 10 Understanding Software: A Primer for Managers 10-1.
Foundations of Information Systems in Business. System ® System  A system is an interrelated set of business procedures used within one business unit.
 An Information System (IS) is a collection of interrelated components that collect, process, store, and provide as output the information needed to.
A Design Process Introduction to Engineering Design
Requirement engineering & Requirement tasks/Management. 1Prepared By:Jay A.Dave.
21/1/ Analysis - Model of real-world situation - What ? System Design - Overall architecture (sub-systems) Object Design - Refinement of Design.
UTA/ARRI. Enterprise Engineering for The Agile Enterprise Don Liles The University of Texas at Arlington.
Metadata Driven Aspect Specification Ricardo Ferreira, Ricardo Raminhos Uninova, Portugal Ana Moreira Universidade Nova de Lisboa, Portugal 7th International.
 The processes used for RE vary widely depending on the application domain, the people involved and the organisation developing the requirements.  However,
Chapter 1 Assuming the Role of the Systems Analyst.
Product Development Chapter 12. Vocabulary Research and development (R&D): the process of gathering information and using that information to develop.
Elaboration popo.
ITIL: Service Transition
CHAPTER 1 FOUNDATIONS OF IS Subject Name: MANGEMENT INFORMATION SYSTEM
Object-Oriented Software Engineering Using UML, Patterns, and Java,
Architecture Components
Technological Systems
Concepts of Information Systems
Information System and Management
Introduction to information systems
King Saud University College of Engineering IE – 462: “Industrial Information Systems” Fall – 2018 (1st Sem H) Introduction (Chapter 1) part.
Information Systems in Organizations
Presentation transcript:

Managing informal aspects of decision processes for improving reactivity of industrial systems Aline CAUVIN, Riad MEGARTSI DIAM-IMS Domaine Universitaire de St-Jérôme Avenue Escadrille Normandie-Niemen MARSEILLE CEDEX 20 FRANCE

Control system of the firm Production process Idea of product Process models Product models Raw material Finished product Controlling enterprise processes Objectives & constraints Quality, cost, time Objectives & constraints Quality, cost, time Objectives & constraints Quality, cost, time Design control system Production control system Design process Problematics ( 2 )Proposals ( 6 )Implementation ( 5 )

Defining enterprise processes Modelling enterprise processes Elaborating common representation Defining mechanisms to process disturbances Analysing disturbances Modelling reaction processes Modelling communication networks between actors Designing a support to aid enterprise processes control An approach in disturbed context Problematics ( 2 )Proposals ( 6 )Implementation ( 5 )

Analysing processes in usual context Input Code Verb Human resources Technical resources Type (S, I, E) Performance Indicators quality cost time required effective Output Problematics ( 2 )Proposals ( 6 )Implementation ( 5 )

Detecting disturbance Reaction process to disturbances Actor ReactingCharacterizingClassifying Identifying Storing Tool for analysing disturbances Disturbance classification Actor relay Representation of decision making processes Problematics ( 2 )Proposals ( 6 )Implementation ( 5 )

Disturbance classification : an example Problematics ( 2 )Proposals ( 6 )Implementation ( 5 ) CriteriaCategories Frequency Importance Causality Control Low : disturbance seldom occurs Medium : disturbance occurs from time to time High : disturbance often occurs Low : consequences of disturbance are not important for production system or its control Medium : production plans may be modified High : consequences of disturbance are important or sometimes catastrophic for production First : causes of disturbance are identified Second : causes are consequences of previous disturbances. It is necessary to identify initial causes Total : disturbance is completely controlled Partial : disturbance is not completely controlled but reaction rules are available and usable No control : there are no algorithms, rules or methods to face disturbance

Disturbance Representation of actor relay Project manager Production manager Dialogue relationship Operator Quality manager Formal communication Informal communication Order (1) (4) (3) (2) (0) Problematics ( 2 )Proposals ( 6 )Implementation ( 5 ) Dialogue relationship Order Formal communication Informal communication

Identified Disturbance Modelling reaction processes Normal functioning Normal functioning Disturbed functioning Process Flow / Defining involved actors Processed Rejected solution Selected solution Process Flow / Selecting solutions Problematics ( 2 )Proposals ( 6 )Implementation ( 5 ) Resolved disturbance Process Flow / Performing solutions

disturbance Actor involved Control aided support Problematics ( 2 )Proposals ( 6 )Implementation ( 5 ) Informing Deciding Storing Functions Updating Solving Solving rules Database Consulting Identifying Consulting Disturbance database New disturbance Classifying

Implementing our approach : an example Mechanical engineeringElectronic engineering Computer engineering Prototype Conceptual elaboration Virtual/physical modelling Evaluation of Concepts Definition of technical specifications Detailed design Prototyping EE ME Coordination information exchanges Decision making Conceptual elaboration Virtual/physical modelling Evaluation of Concepts Definition of technical specifications Detailed design Prototyping Problematics ( 2 )Proposals ( 6 )Implementation ( 5 ) disturbances

Problematics ( 2 )Proposals ( 6 )Implementation ( 5 ) Design process

Problematics ( 2 )Proposals ( 6 )Implementation ( 5 ) Actor relay Project manager Customer Supplier Technician 0 1 Manager of electronics Dpt Manager of mechanics Dpt Purchasing officer Sales executive External Environment Internal Environment Computer manager Disturbance 6 7 3

Problematics ( 2 )Proposals ( 6 )Implementation ( 5 ) Reaction process Integration performed Integration validated Process Flow/ Testing intégration Integration nonvalidated Soft re-programmed Process Flow / Selecting solution Goto / Designing Soft Assemblying E&S Goto/ / Integrating Changed chip Not available Ordered Received / Process Flow / Selecting supplier Process Flow / Requesting component Available Goto Integrating

Problematics ( 2 )Proposals ( 6 )Implementation ( 5 ) Proposal for improving actor relay Project manager Customer Supplier Technician 0 1 Manager of electronics Dpt Manager of mechanics Dpt Purchasing officer Sales executive Computer manager Disturbance 3 5

 Management of reactions to disturbances  Analyzing and characterizing disturbances to evolve reactions  Capitalizing decision processes in order to reuse them for future reactions To conclude : interests of the approach  Improving structure and functioning of industrial organizations  Improving knowledge management  Improving communication between actors