A knowledge-based Assistant for real-time Planning and Execution of PSS Engineering Change Processes Michael Abramovici, Youssef Aidi IT in Mechanical.

Slides:



Advertisements
Similar presentations
ARCHITECTURES FOR ARTIFICIAL INTELLIGENCE SYSTEMS
Advertisements

Improving System Safety through Agent-Supported User/System Interfaces: Effects of Operator Behavior Model Charles SANTONI & Jean-Marc MERCANTINI (LSIS)
Mahmut Ali GÖKÇEIndustrial Systems Engineering Lecture 2 System Identification ISE102 Spring 2007.
Lecture # 2 : Process Models
Software Process Model
Adaptive Processes Software Processes Adaptive Processes.
ITIL: Service Transition
Programming Distributed Systems Lab Institute of Computer Science University of Augsburg Universitätsstraße 14, D Augsburg Tel.: (+49) 821/ ,
6/1/2015Ch.31 Defining Enterprise Architecture Bina Ramamurthy.
Realizing OPM Philosophy in the Context of Full Life- Cycle Support Avi Soffer Technion, Israel Institute of Technology Thesis Advisor: Prof. Dov Dori.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 8 Slide 1 System models.
Knowledge Acquisitioning. Definition The transfer and transformation of potential problem solving expertise from some knowledge source to a program.
Study Period Report: Metamodel for On Demand Model Selection (ODMS) Wang Jian, He Keqing, He Yangfan, Wang Chong State Key Lab of Software Engineering,
Software Engineering General Project Management Software Requirements
1 Pertemuan 14 Perencanaan, Desain dan Administrasi Databases Matakuliah: >/ > Tahun: > Versi: >
Analysis Concepts and Principles
Business Area Analysis Focus: Domain View (selected business area) Goals: –Isolate functions and procedures that allow the area to meet its goals –Define.
Nov. 14, 2007 Systems Engineering ä System ä A set or arrangement of things so related as to form a unity or organic whole. ä A set of facts, principles,
Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 8 Slide 1 System models.
CS350/550 Software Engineering Lecture 1. Class Work The main part of the class is a practical software engineering project, in teams of 3-5 people There.
System Engineering Instructor: Dr. Jerry Gao. System Engineering Jerry Gao, Ph.D. Jan System Engineering Hierarchy - System Modeling - Information.
Software Process and Product Metrics
Company LOGO Business Process Monitoring and Alignment An Approach Based on the User Requirements Notation and Business Intelligence Tools Pengfei Chen.
On the purpose of Object Oriented Analysis Geri Magne Høydalsvik and Guttorm Sindre.
Semantic Web Technologies Lecture # 2 Faculty of Computer Science, IBA.
System Analysis Overview Document functional requirements by creating models Two concepts help identify functional requirements in the traditional approach.
MDC Open Information Model West Virginia University CS486 Presentation Feb 18, 2000 Lijian Liu (OIM:
Chapter 9 Database Planning, Design, and Administration Sungchul Hong.
IS 466 ADVANCED TOPICS IN INFORMATION SYSTEMS LECTURER : NOUF ALMUJALLY 3 – 10 – 2011 College Of Computer Science and Information, Information Systems.
Chapter 2 The process Process, Methods, and Tools
-Nikhil Bhatia 28 th October What is RUP? Central Elements of RUP Project Lifecycle Phases Six Engineering Disciplines Three Supporting Disciplines.
Chapter 4 System Models A description of the various models that can be used to specify software systems.
System models Abstract descriptions of systems whose requirements are being analysed Abstract descriptions of systems whose requirements are being analysed.
Business Analysis and Essential Competencies
ITEC 3220M Using and Designing Database Systems
CHAPTER ONE Problem Solving and the Object- Oriented Paradigm.
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.
Programming in Java Unit 3. Learning outcome:  LO2:Be able to design Java solutions  LO3:Be able to implement Java solutions Assessment criteria: 
The 7 th CIRP IPSS Conference May 2015 Saint-Etienne, France by Christian Schnürmacher, Haygazun Hayka and Rainer Stark Presenting Author: Christian.
Chapter 9 요구사항 모델링: 시나리오 기반 방법론 Requirements Modeling: Scenario-Based Methods 임현승 강원대학교 Revised from the slides by Roger S. Pressman and Bruce R. Maxim.
© DATAMAT S.p.A. – Giuseppe Avellino, Stefano Beco, Barbara Cantalupo, Andrea Cavallini A Semantic Workflow Authoring Tool for Programming Grids.
Chapter 7 System models.
System models l Abstract descriptions of systems whose requirements are being analysed.
Software Engineering, 8th edition Chapter 8 1 Courtesy: ©Ian Somerville 2006 April 06 th, 2009 Lecture # 13 System models.
Sommerville 2004,Mejia-Alvarez 2009Software Engineering, 7th edition. Chapter 8 Slide 1 System models.
1 Introduction to Software Engineering Lecture 1.
Notes of Rational Related cyt. 2 Outline 3 Capturing business requirements using use cases Practical principles  Find the right boundaries for your.
Software Engineering Prof. Ing. Ivo Vondrak, CSc. Dept. of Computer Science Technical University of Ostrava
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 14 Slide 1 Object-oriented Design.
Faculty of Applied Engineering and Urban Planning Software Engineering Department Software Engineering Lab Use Cases Faculty of Information system Technology.
INTRODUCTION TO SOFTWARE ENGINEERING Authors: William M. Buchanan Joseph Picone Contact Information: ECE 4512 / 4522 Box 9571 Mississippi State University.
Object-Oriented Analysis and Design. Lesson 1: Introduction to Software Engineering.
1 Capturing Requirements As Use Cases To be discussed –Artifacts created in the requirements workflow –Workers participating in the requirements workflow.
MODEL-BASED SOFTWARE ARCHITECTURES.  Models of software are used in an increasing number of projects to handle the complexity of application domains.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 8 Slide 1 System models.
1 Chapter 8 Building the Analysis Model (1) Analysis Concepts and Principles.
Software Engineering Lecture 11: System Analysis.
Winter 2011SEG Chapter 11 Chapter 1 (Part 1) Review from previous courses Subject 1: The Software Development Process.
 To explain why the context of a system should be modelled as part of the RE process  To describe behavioural modelling, data modelling and object modelling.
MDD-Kurs / MDA Cortex Brainware Consulting & Training GmbH Copyright © 2007 Cortex Brainware GmbH Bild 1Ver.: 1.0 How does intelligent functionality implemented.
The Software Lifecycle Stuart Faulk. Definition Software Life Cycle: evolution of a software development effort from concept to retirement Life Cycle.
Engineering, 7th edition. Chapter 8 Slide 1 System models.
Process 4 Hours.
ITIL: Service Transition
Review of last class Software Engineering Modeling Problem Solving
The Movement To Objects
ITEC 3220A Using and Designing Database Systems
Chapter 9 Requirements Modeling: Scenario-Based Methods
Engineering design is the process of devising a system, component, or process to meet desired needs. It is a decision-making process in which the basic.
Verification Concepts for SysmL v2
Presentation transcript:

A knowledge-based Assistant for real-time Planning and Execution of PSS Engineering Change Processes Michael Abramovici, Youssef Aidi IT in Mechanical Engineering (ITM) Ruhr University Bochum, Germany 7 th CIRP IPSS Conference Saint-Étienne, May, 22th, 2015

ITM © Dipl.-Ing. Y. Aidi – 7th CIRP IPSS, May, 22th, Saint-Étienne1 Outline Current Situation and Requirements The Knowledge-based Engineering Change (EC) Assistant EC Modeling Assistant EC Information Assistant EC Ontology EC Change Engine Conclusion and Future Work

ITM © Dipl.-Ing. Y. Aidi – 7th CIRP IPSS, May, 22th, Saint-Étienne2 Engineering Changes (EC)  Technological  Environmental  Economic  Political  Social  …  Technological  Environmental  Economic  Political  Social  … Triggers  Improvement  Corrective  Iteration  Adaptive to new Requirements  …  Improvement  Corrective  Iteration  Adaptive to new Requirements  … Types  Whole product  Component  Software  Service  …  Whole product  Component  Software  Service  … Change Objects The Process of Requesting, Determining Attainability, Planning, Implementing, and Evaluating of Changes to a System Engineering Change Process

ITM © Dipl.-Ing. Y. Aidi – 7th CIRP IPSS, May, 22th, Saint-Étienne3 Current Engineering Change Processing Approach EC Process Manager Planning Execution  Fix planned EC Processes for all Changes  Poor Responsiveness to Unforeseeable Events  Delays and exceeded Costs  Changes occur at Provider Side during the Creation Phase  Fix planned EC Processes for all Changes  Poor Responsiveness to Unforeseeable Events  Delays and exceeded Costs  Changes occur at Provider Side during the Creation Phase

ITM © Dipl.-Ing. Y. Aidi – 7th CIRP IPSS, May, 22th, Saint-Étienne4 Customer Product-Service-Systems requires a new Engineering Change Processing approachProvider Suppliers Services  Selling “value in use” Instead Simple Products  Shared Value Creation during the Lifecycle of PSS (Provider, Customer, Supplier)  Adaptability of PSS to Changing Boundary Conditions  Selling “value in use” Instead Simple Products  Shared Value Creation during the Lifecycle of PSS (Provider, Customer, Supplier)  Adaptability of PSS to Changing Boundary Conditions Paradigms of PSS Creation Operation  Prompt Reaction to Unpredictable Changes  Consideration of Process Knowledge  Real-time Definition and Execution of Process Activities  Prompt Reaction to Unpredictable Changes  Consideration of Process Knowledge  Real-time Definition and Execution of Process Activities Requirements to EC Processing

ITM © Dipl.-Ing. Y. Aidi – 7th CIRP IPSS, May, 22th, Saint-Étienne5 Outline Current Situation and Requirements The Knowledge-based Engineering Change (EC) Assistant EC Modeling Assistant EC Information Assistant EC Ontology EC Change Engine Conclusion and Future Work

ITM © Dipl.-Ing. Y. Aidi – 7th CIRP IPSS, May, 22th, Saint-Étienne6 How can EC Process Managers be Supported by real-time Planning and Exection of EC Processes? Change Process Manager What must be achieved? How it could be achieved? Which human Resources are required? Is the Process running smoothly?  Goal-oriented Process Modeling  Adequat Defintion of Activities  Permanent Process Evaluation  Optimal Assignment to human Ressources  Information Aquisition  Goal-oriented Process Modeling  Adequat Defintion of Activities  Permanent Process Evaluation  Optimal Assignment to human Ressources  Information Aquisition A knowledge-based Assistant for Real-time Planning and Execution of PSS Engineering Change Processes Adaptive Change Process

ITM © Dipl.-Ing. Y. Aidi – 7th CIRP IPSS, May, 22th, Saint-Étienne7 Adaptability is given by the Distinction between WHAT must be achieved and HOW it is to be achieved  Company Specific Abstract EC Process Model  Hierarchy of Goals  Milestones within the EC Process  Company Specific Abstract EC Process Model  Hierarchy of Goals  Milestones within the EC Process WHAT to achieve? HOW to achieve Goal Subgoal Activity pool  Consideration of the EC Context  Selection of Appropriate Activites  Asignment to Available Ressources

ITM © Dipl.-Ing. Y. Aidi – 7th CIRP IPSS, May, 22th, Saint-Étienne8 EC Process Manager EC Process Engine Agile and intelligent Approach to tackle Changing Boundary Conditions

ITM © Dipl.-Ing. Y. Aidi – 7th CIRP IPSS, May, 22th, Saint-Étienne9 Outline Current Situation and Requirements The Knowledge-based Engineering Change (EC) Assistant EC Modeling Assistant EC Information Assistant EC Ontology EC Change Engine Conclusion and Future Work

ITM © Dipl.-Ing. Y. Aidi – 7th CIRP IPSS, May, 22th, Saint-Étienne10 Goal-oriented Requirement Language (GRL) Description of the Hierarchy of Goals, which are achieved by Execution of an EC Process  Modeling and Reasoning of Goal Structures  Higher Level of Modeling  Integration of Goals, Activities and Roles.  Modeling and Reasoning of Goal Structures  Higher Level of Modeling  Integration of Goals, Activities and Roles.  Contribution  Decomposition (AND, OR, XOR, NOR)  Dependency  Belief  Contribution  Decomposition (AND, OR, XOR, NOR)  Dependency  Belief Relationships

ITM © Dipl.-Ing. Y. Aidi – 7th CIRP IPSS, May, 22th, Saint-Étienne11 Goal-oriented Change Process Model

ITM © Dipl.-Ing. Y. Aidi – 7th CIRP IPSS, May, 22th, Saint-Étienne12 Outline Current Situation and Requirements The Knowledge-based Engineering Change (EC) Assistant EC Modeling Assistant EC Information Assistant EC Ontology EC Change Engine Conclusion and Future Work

ITM © Dipl.-Ing. Y. Aidi – 7th CIRP IPSS, May, 22th, Saint-Étienne13 Document View Activity View Goal View Information Assistant for a better EC Process Understanding (1/4) Actor View

ITM © Dipl.-Ing. Y. Aidi – 7th CIRP IPSS, May, 22th, Saint-Étienne14 Document View Actor View Activity View Goal View Information Assistant for a better EC Process Understanding (2/4)

ITM © Dipl.-Ing. Y. Aidi – 7th CIRP IPSS, May, 22th, Saint-Étienne15 Document view Actor view Activity view Goal view Information Assistant for a better EC Process Understanding (3/4)

ITM © Dipl.-Ing. Y. Aidi – 7th CIRP IPSS, May, 22th, Saint-Étienne16 Actor View Activity View Goal View Information Assistant for a better EC Process Understanding (4/4) Document View

ITM © Dipl.-Ing. Y. Aidi – 7th CIRP IPSS, May, 22th, Saint-Étienne17 Outline Current Situation and Requirements The Knowledge-based Engineering Change (EC) Assistant EC Modeling Assistant EC Information Assistant EC Ontology EC Change Engine Conclusion and Future Work

ITM © Dipl.-Ing. Y. Aidi – 7th CIRP IPSS, May, 22th, Saint-Étienne18 Ontology for EC Process related Knowledge Description Formal Representation of Knowledge as a Hierarchy of Concepts within a Domain  Description of the Elements and the Context of a Change Process  Knowledge Modeling through Complex Relationships and Rules  Integration of Instance Information  Reasoning Mechanisms Allowing the Generation of Knowledge  Description of the Elements and the Context of a Change Process  Knowledge Modeling through Complex Relationships and Rules  Integration of Instance Information  Reasoning Mechanisms Allowing the Generation of Knowledge  Classes (concepts)  Attributes  Relations  Rules  Axioms  Events  Classes (concepts)  Attributes  Relations  Rules  Axioms  Events Components Classes of the EC Process Ontology

ITM © Dipl.-Ing. Y. Aidi – 7th CIRP IPSS, May, 22th, Saint-Étienne19 The Engineering Change Process Ontology

ITM © Dipl.-Ing. Y. Aidi – 7th CIRP IPSS, May, 22th, Saint-Étienne20 Example for EC Process Knowledge Description using an Ontology Activity Goal Role Actor Document Contribute to Has role Is executed by Is generated during

ITM © Dipl.-Ing. Y. Aidi – 7th CIRP IPSS, May, 22th, Saint-Étienne21 Example for EC Process Knowledge Description using an Ontology Describe Problem Problem Report released Change Initiator Machine Operator Problem Report Contribute to Has role Is executed by Is generated during Describe Problem Problem Report released Machine Operator Problem Report Contribute to Is executed by Is generated during Is generated by Is involved by Reasoned Evidences

ITM © Dipl.-Ing. Y. Aidi – 7th CIRP IPSS, May, 22th, Saint-Étienne22 Outline Current Situation and Requirements The Knowledge-based Engineering Change (EC) Assistant EC Modeling Assistant EC Information Assistant EC Ontology EC Change Engine Conclusion and Future Work

ITM © Dipl.-Ing. Y. Aidi – 7th CIRP IPSS, May, 22th, Saint-Étienne23 Execution of EC Process Activities Engineering Change Engine Webservice Goal Activity

ITM © Dipl.-Ing. Y. Aidi – 7th CIRP IPSS, May, 22th, Saint-Étienne24 Outline Current Situation and Requirements The Knowledge-based Engineering Change (EC) Assistant EC Modeling Assistant EC Information Assistant EC Ontology EC Change Engine Conclusion and Future Work

ITM © Dipl.-Ing. Y. Aidi – 7th CIRP IPSS, May, 22th, Saint-Étienne25 Conclusion and Future Work  Modeling of Company Specific Ontology  Validation in the Industry  IT Infrastructures  Modeling of Company Specific Ontology  Validation in the Industry  IT Infrastructures Challenges The proposed EC Process Assistant provides:  Goal-oriented Process Modeling Environment  Ontology for EC Process Knowledge Representation  Permanent Evaluation of EC Processes  Navigation-based EC Process Information Provision  Standard BPEL Workflows for Real-time Execution of Process Activities The proposed EC Process Assistant provides:  Goal-oriented Process Modeling Environment  Ontology for EC Process Knowledge Representation  Permanent Evaluation of EC Processes  Navigation-based EC Process Information Provision  Standard BPEL Workflows for Real-time Execution of Process Activities Conclusion  Integrated IT Solution  Coupling of the Change Ontology to Product Ontologies  Impact and Propagation Evaluation  Integrated IT Solution  Coupling of the Change Ontology to Product Ontologies  Impact and Propagation Evaluation future work

ITM © Dipl.-Ing. Y. Aidi – 7th CIRP IPSS, May, 22th, Saint-Étienne26 Prototype PSS Structure Process Goals Available Actors Appropriate Roles Appropriate Activities Appropriate Documents Views Process Goal Decomposition Contribution Process Activity Assigned Actor Reports about Plausibility of Actions

ITM © Dipl.-Ing. Y. Aidi – 7th CIRP IPSS, May, 22th, Saint-Étienne27 Contact Dipl.-Ing. Youssef Aidi Ruhr-University Bochum Chair of IT in Mechanical Engineering (ITM) Universitätsstraße 150 D Bochum Tel: Fax: Mail: "It is not the strongest of the species that survives, nor the most intelligent that survives. It is the one that is most adaptable to change" Charles Darwin

ITM © Dipl.-Ing. Y. Aidi – 7th CIRP IPSS, May, 22th, Saint-Étienne28

ITM © Dipl.-Ing. Y. Aidi – 7th CIRP IPSS, May, 22th, Saint-Étienne29 EC process manager

ITM © Dipl.-Ing. Y. Aidi – 7th CIRP IPSS, May, 22th, Saint-Étienne30 Information Assistant Modeling Assistant

ITM © Dipl.-Ing. Y. Aidi – 7th CIRP IPSS, May, 22th, Saint-Étienne31

ITM © Dipl.-Ing. Y. Aidi – 7th CIRP IPSS, May, 22th, Saint-Étienne32 PSS to Change PSS Changed

ITM © Dipl.-Ing. Y. Aidi – 7th CIRP IPSS, May, 22th, Saint-Étienne33 Known Engineering Change Management Approaches PLM ERP Templates

ITM © Dipl.-Ing. Y. Aidi – 7th CIRP IPSS, May, 22th, Saint-Étienne34 Engineering Change Management Needs more Flexibility  Technological  Environmental  Economic  Political  Social  …  Technological  Environmental  Economic  Political  Social  … Triggers  Prompt Reaction to Unpredictable Changes  Consideration of Process Knowledge  Real-time Definition and Execution of Process Activities  Prompt Reaction to Unpredictable Changes  Consideration of Process Knowledge  Real-time Definition and Execution of Process Activities Adaptive Change Process PSS to Change PSS Changed

ITM © Dipl.-Ing. Y. Aidi – 7th CIRP IPSS, May, 22th, Saint-Étienne35

ITM © Dipl.-Ing. Y. Aidi – 7th CIRP IPSS, May, 22th, Saint-Étienne36

ITM © Dipl.-Ing. Y. Aidi – 7th CIRP IPSS, May, 22th, Saint-Étienne37

ITM © Dipl.-Ing. Y. Aidi – 7th CIRP IPSS, May, 22th, Saint-Étienne38

ITM © Dipl.-Ing. Y. Aidi – 7th CIRP IPSS, May, 22th, Saint-Étienne39