Prof. Ing. M. Dassisti Enterprise modelling for networked enterprise: interaction aspects for a training organisation 16th IFAC World Congress, Prague.

Slides:



Advertisements
Similar presentations
HOW TO FORM A PARTNERSHIP Training Unit 3.2 National, transnational and local networks.
Advertisements

Module N° 4 – ICAO SSP framework
Lecture 6: Software Design (Part I)
Applying the Human Views for MODAF to the conception of energy-saving work solutions Dr Anne Bruseberg Systems Engineering & Assessment Ltd, UK on behalf.
Database Systems: Design, Implementation, and Management Tenth Edition
FANRPAN Adding Value in Agricultural and Natural Resources Policies and Processes in Southern Africa.
Managing informal aspects of decision processes for improving reactivity of industrial systems Aline CAUVIN, Riad MEGARTSI DIAM-IMS Domaine Universitaire.
OOAD Using the UML - Use-Case Analysis, v 4.2 Copyright  Rational Software, all rights reserved 1/18 Use Case Analysis – continued Control Classes.
Systems Engineering in a System of Systems Context
DYNAMIC MODEL DY.MO.VO.TRA. A NEW WAY TO SUPPORT TEACHERS’ PROFESSIONALISM FOR IMPROVING THE QUALITY OF EUROPEAN SCHOOL IN THE KNOWLEDGE SOCIETY KEY ACTION.
Knowledge Acquisitioning. Definition The transfer and transformation of potential problem solving expertise from some knowledge source to a program.
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.
UML Sequence Diagrams Eileen Kraemer CSE 335 Michigan State University.
Chapter 2: IS Building Blocks Objectives
Supplement 02 (a)Systems Theory1 Supplement 02 (a) Systems Theory And Franchise Colleges By MANSHA NAWAZ.
IWRM PLAN PREPARED AND APPROVED. CONTENT Writing an IWRM plan The content of a plan Ensuring political and public participation Timeframe Who writes the.
UML - Development Process 1 Software Development Process Using UML (2)
U NITED N ATIONS C ENTRE F OR T RADE F ACILITATION A ND E LECTRONIC B USINESS United Nations Economic Commission for Europe UN/CEFACT Information Technology.
Mullins: Management and Organisational Behaviour, 7th edition © Pearson Education Limited 2005 Management and Organisational Behaviour 7th Edition CHAPTER.
TDT4252/DT8802 Exam 2013 Guidelines to answers
SOFTWARE ENGINEERING BIT-8 APRIL, 16,2008 Introduction to UML.
Changing Perspective From Structured to Object-oriented.
CB1004 Modelling Business Systems 71 Modelling Business Systems 7 Systems Methods.
Architecture Business Cycle
2 1 Chapter 2 Data Models Database Systems: Design, Implementation, and Management, Seventh Edition, Rob and Coronel.
EQARF Applying EQARF Framework and Guidelines to the Development and Testing of Eduplan.
PPA 502 – Program Evaluation Lecture 2c – Process Evaluation.
1 Introduction to Software Engineering Lecture 1.
Illustrations and Answers for TDT4252 exam, June
An Ontological Framework for Web Service Processes By Claus Pahl and Ronan Barrett.
Design Concepts and Principles Instructor: Dr. Jerry Gao.
Information Systems Engineering. Lecture Outline Information Systems Architecture Information System Architecture components Information Engineering Phases.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 14 Slide 1 Object-oriented Design.
Dimension 5. Social dialogue and workplace relationships Prepared by Judit Lakatos and Elizabeth Lindner Hungarian Central Statistical Office.
Copyright © 2013 Curt Hill UML Unified Modeling Language.
 The need for a formal methodology description  SPEM for describing an agent oriented methodology  PASSI: an example  The needed extension  Discussion.
UML as a Specification Language for Embedded Systems. By, Mir Ahmed Ali, Asst. Professor, ECM department, SNIST. By, Prof. Narsiah sir, Director of School.
© 2008, Tod O' Dot Productions EUROPEAN UNIVERSITY – ENTERPRISE COOPERATION NETWORK Socrates Erasmus Programme Project No: Ref LLP
Organizations & Systems Sept. 12, Outline What is an Organization? Interaction of IT with the Organization Network Effects & Economics Classifying.
ORGANIZING CHAPTER 5. INTRODUCTION Organizing means arranging the activities of the enterprise in such a way that they systematically contribute to the.
1 Introduction to Design. 2 Outline Basics of design Design approaches.
Foundations of Information Systems in Business. System ® System  A system is an interrelated set of business procedures used within one business unit.
Kathy Corbiere Service Delivery and Performance Commission
Lecture 13.  Failure mode: when team understands requirements but is unable to meet them.  To ensure that you are building the right system Continually.
Chapter 16 Managing costs and quality
1 The Subject Is Organizations I. What is a Formal Organization? Special type of secondary group designated to allow a relatively large number of people.
SCOPE DEFINITION,VERIFICATION AND CONTROL Ashima Wadhwa.
Chapter 2 Database Environment.
UTA/ARRI. Enterprise Engineering for The Agile Enterprise Don Liles The University of Texas at Arlington.
The collection of phases that are performed in completing a project. Each project phase is marked by completion of one or more deliverables. The conclusion.
Castlebridge associates | | Castlebridge changing how people think about information How to Implement the.
CS 501: Software Engineering Fall 1999 Lecture 15 Object-Oriented Design I.
OUTCOMES OBJECTIVES FUNCTIONS ACTIONS TERRITORIES LOCATIONS MARKET SEGMENTS TIME LINESCHALLENGE IMPACT RESOURCESACTIVITIESCHANNELS RELATIONS PARTNERS CUSTOMERS.
C ONCEPTS OF ORGANISING Static concept Dynamic concept.
Carmela Tuccillo Orlando Troisi Università degli Studi di Salerno
UML (Unified Modeling Language)
Model Checking Early Requirements Specifications in Tropos Presented by Chin-Yi Tsai.
An Overview of Requirements Engineering Tools and Methodologies*
Object-Oriented Analysis and Design
Architecture Concept Documents
Unified Modeling Language
CV-1: Vision The overall vision for transformational endeavors, which provides a strategic context for the capabilities described and a high-level scope.
Chapter 2 Database Environment Pearson Education © 2009.
CS223: Software Engineering
Software Design Lecture : 15.
CHAPTER 9 (part a) BASIC INFORMATION SYSTEMS CONCEPTS
Chapter 2 Database Environment Pearson Education © 2014.
Stumpf and Teague Object-Oriented Systems Analysis and Design with UML
Stumpf and Teague Object-Oriented Systems Analysis and Design with UML
Presentation transcript:

Prof. Ing. M. Dassisti Enterprise modelling for networked enterprise: interaction aspects for a training organisation 16th IFAC World Congress, Prague July 5, 2005

Michele Dassisti Focus of the work Analyse interaction aspects for modelling networked enterprises Case study concerning an Italian training organisation

Michele Dassisti Outline of the presentation Fundamental concepts related to NE; Fundamental concepts related to NE; Modelling principles of a NE; Modelling principles of a NE; The case study The case study Interaction model via I.E.M. (specific enterprise modelling methodology) for the case study; Interaction model via I.E.M. (specific enterprise modelling methodology) for the case study; Discussion and future research scenarios Discussion and future research scenarios

Michele Dassisti Networked Enterprise “the system of recognisable and multiple connections and structures within operate high-level self- regulation nodes able to cooperate for a common goal or shared results” Our extended definition Nodes= parts of the same enterprise, sharing the same business goal Availability of autonomous and independent entities NE are able to modify the connections between the nodes COMMON GOAL

Michele Dassisti Networked enterprise: classification Hierarchical net: –the gravity centre is responsible for the core business –the internal hierarchical structure is dominant –there is a strong relationships of influence and negotiate with other nodes net with an Assembled Gravity Centre: –the gravity centre is responsible for the financial control of the participating nodes net with Multiple Gravity Centres: –the singular systems rotates around different strategic agencies, with complex and mobile relationships of influence, that cyclically rotate around the most greater nodes; net Without Centre: –a nodes leader doesn't exist, –the singular systems are based upon their own territorial area, as districts.

Michele Dassisti Modelling principles for analysing NE 1.Clear definition of NE components (nodes) 2.Modelling of the interaction mechanisms between nodes Recognising internal and external interactions may allow a better understanding of the NE Any network is a “sum” of nodes and their interactions DECOMPOSITION PRINCIPLE

Michele Dassisti ۞ Inter-action Classification criteria: identification of the scope of an interaction 1.Communication [Asynch. Directed]  to inform participants –exchanged information should have a semantic content useful for the success of the communicative process. 2.Collaboration [Synch. Undirect]  to pursue a specific goal, not clearly formalised –underlying activities of nodes are group oriented, and the goal of each node could be different. 3.Co-operation  synchronisation of activities to pursue a specific goal –interaction is formally managed: roles, phases and goals are rigidly pre-arranged. –coordinator node manages the cooperation process.

Michele Dassisti The nature of connections NODE 1NODE 2 1.orders and procedures (functional interactions) ; 2.rules and practices of the whole working environment (operative interactions); 3.formalized information sending by informative nets (informational interactions); 4.written communications, recorded or not (bureaucratic interactions); 5.costs and prices of commodities and exchanged services (economical or administrative interactions)

Michele Dassisti The case study ADMINISTRATION OFFICE responsible for the core business OPERATIVE OFFICE Vertical interaction horizontal interaction responsible of the production of the services Net with an Assembled Gravity Centre bureaucratic and formalized information formalized information and written communication Gravity Centre

Michele Dassisti Horizontal interaction General schema of the interaction OPERATIVE OFFICE horizontal interaction Information flow Information, data Physical and human resources Operative office Scope: to deliver a defined training service to the customer Nature of the interaction: communication to achieve the specific goal Exchanged objects: informative material Explicative example

Michele Dassisti Vertical interaction ADMINISTRATION OFFICE OPERATIVE OFFICES Vertical interaction Gravity Centre Decisional (support) flow Control flow Improvement flow Scope: assuring a continuous improvement of the training organisation. Nature of the interaction: co-operation Exchanged objects: written feedback information from customers + operating rules. Details about the improvement flow Operative office administratio n office Feedback information Operating rules

Michele Dassisti Interaction model via enterprise modelling STEPS 1.Identification of nodes 2.Modelling of the relationships among them 3.Modelling of the objects exchanged Real system elements Model nodes Model actors, actions and contents How enterprise modelling could support vertical and horizontal interactions? IEM methodology

Michele Dassisti I.E.M. interaction model OUTPUT INPUT ADMINISTRATION OFFICE OPERATIVE OFFICE

Michele Dassisti Interaction model via I.E.M. OPERATIVE OFFICE LEVEL 0 0 LEVEL 1 ORIENTATION ADMINISTRATIVE OFFICE Control flow Information about non conformity Information for orientation process OPERATIVE OFFICE LEVEL 0 0 LEVEL 1 ORIENTATION ADMINISTRATIVE OFFICE Control flow Information about non conformity Information for orientation process OPERATIVE OFFICE

Michele Dassisti Discussion: pro EXPLICITING RULES OF INTERACTION: the method proposed explicits the relational nature of the NE EXPLICITING RULES OF INTERACTION: the method proposed explicits the relational nature of the NE MEASURABILITY: performances of interaction processes are now prone to be measures (expliciting causal links) MEASURABILITY: performances of interaction processes are now prone to be measures (expliciting causal links)

Michele Dassisti Discussion: cons STATIC CONSTRAINTS: Modelling networked enterprises means to represent a static picture of what is going on or what should be done STATIC CONSTRAINTS: Modelling networked enterprises means to represent a static picture of what is going on or what should be done NON FEATURING: it is not easy to capture the interoperability feature of the systems NON FEATURING: it is not easy to capture the interoperability feature of the systems VISION-SHARING CONSTRAINTS: personnel rearely understand the pictorial logical representation of their own reality VISION-SHARING CONSTRAINTS: personnel rearely understand the pictorial logical representation of their own reality

Michele Dassisti Conclusions Modelling networked enterprises means to represent the components and the nature of their interactions Modelling networked enterprises means to represent the components and the nature of their interactions The true interest of the paper is to devise a methodology for representing interoperability using the enterprise engineering constructs The true interest of the paper is to devise a methodology for representing interoperability using the enterprise engineering constructs The value added of the paper is to give a testimonial of an application to a real case of a small company The value added of the paper is to give a testimonial of an application to a real case of a small company