Reference Architecture for Enterprise Integration CIMOSA GRAI/GIM PERA Dima Nazzal.

Slides:



Advertisements
Similar presentations
Ch:8 Design Concepts S.W Design should have following quality attribute: Functionality Usability Reliability Performance Supportability (extensibility,
Advertisements

Course: e-Governance Project Lifecycle Day 1
Applying the SOA RA Utah Public Safety ESB Project Utah Department of Technology Services April 10, 2008 Prepared by Robert Woolley.
Ch 3 System Development Environment
Information Systems Analysis and Design
e-Framework Components and Responsibilities.
Overview of OASIS SOA Reference Architecture Foundation (SOA-RAF)
Harmonisation of Standards for Enterprise Integration – an urgent need
Introduction To System Analysis and Design
Soft. Eng. I, Spring 07Dr Driss Kettani, from I. Sommerville1 CSC-3324: Chapter 5 Requirements Engineering Reading: Chap. 6, 7 + annex.
Knowledge Acquisitioning. Definition The transfer and transformation of potential problem solving expertise from some knowledge source to a program.
- 1 - Component Based Development R&D SDM Theo Schouten.
The Use of Zachman Framework Primitives for Enterprise Modeling
1 Introduction to System Engineering G. Nacouzi ME 155B.
Systems Engineering Management
TECH 101 Product Design and Manufacturing. TECH 1012 System Life-Cycle Engineering 2 Major phases in almost all products and in many cases services –Acquisition.
System Engineering Instructor: Dr. Jerry Gao. System Engineering Jerry Gao, Ph.D. Jan System Engineering Hierarchy - System Modeling - Information.
Open System Architecture For CIM - CIMOSA Presented By: Vijay Ravichandran.
Extended Enterprise Architecture Framework (E2AF)
Enterprise Architecture
Basic Concepts The Unified Modeling Language (UML) SYSC System Analysis and Design.
TDT4252 Modelling of Information Systems Advanced Course
T5: Enterprise Architecture and Methodology Fall 2013 Chin-Sheng Chen Florida International University.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 18 Slide 1 Software Reuse.
Chapter 6 System Engineering - Computer-based system - System engineering process - “Business process” engineering - Product engineering (Source: Pressman,
1/19 Component Design On-demand Learning Series Software Engineering of Web Application - Principles of Good Component Design Hunan University, Software.
EENG 1920 Chapter 1 The Engineering Design Process 1.
P Bernus, 1999 The Generalised Enterprise Reference Architecture and Methodology GERAM P Bernus.
PERA Methodology.
Introduction To System Analysis and Design
Odyssey A Reuse Environment based on Domain Models Prepared By: Mahmud Gabareen Eliad Cohen.
SOFTWARE DESIGN.
1-1 System Development Process System development process – a set of activities, methods, best practices, deliverables, and automated tools that stakeholders.
1 Systems Analysis and Design in a Changing World, Thursday, January 18, 2007.
1 CIM OSA CIMOSA Computer Integrated Manufacturing Open System Architecture 1 David CHEN IMS-LAPS, University Bordeaux 1.
1 Introduction to Software Engineering Lecture 1.
Illustrations and Answers for TDT4252 exam, June
Enterprise Systems Architectures EGN 5621 Enterprise Systems Collaboration (Professional MSEM) Fall, 2012.
Information Systems Engineering. Lecture Outline Information Systems Architecture Information System Architecture components Information Engineering Phases.
EI2N2008 © O. Noran, P. Bernus 2008 Service Oriented Architecture vs. Enterprise Architecture: Competition or Synergy? Ovidiu Noran, Peter Bernus EI2N.
Design Concepts By Deepika Chaudhary.
 What is Modeling What is Modeling  Why do we Model Why do we Model  Models in OMT Models in OMT  Principles of Modeling Principles of Modeling 
Computing and SE II Chapter 9: Design Methods and Design Models Er-Yu Ding Software Institute, NJU.
EIN 6133 Enterprise Engineering Chin-Sheng Chen Florida International University.
ISD2008 © O. Noran, P. Bernus 2008 EM GERA Generalised Reference Architecture EEM Enterprise Engineering Methodology EML Enterprise Modelling Language.
CSC480 Software Engineering Lecture 10 September 25, 2002.
ICT EMMSAD’05 13/ Assessing Business Process Modeling Languages Using a Generic Quality Framework Anna Gunhild Nysetvold* John Krogstie *, § IDI,
Enterprise Architecture HOW COMPANIES ARE EXPLOITING INFORMATION TO THROUGH IT.
Architecture View Models A model is a complete, simplified description of a system from a particular perspective or viewpoint. There is no single view.
Week 04 Object Oriented Analysis and Designing. What is a model? A model is quicker and easier to build A model can be used in simulations, to learn more.
Smart Home Technologies
Modern Systems Analysis and Design Third Edition Chapter 2 Succeeding as a Systems Analyst 2.1.
Software Engineering Lecture 10: System Engineering.
LECTURE 5 Nangwonvuma M/ Byansi D. Components, interfaces and integration Infrastructure, Middleware and Platforms Techniques – Data warehouses, extending.
Enterprise Architectures Course Code : CPIS-352 King Abdul Aziz University, Jeddah Saudi Arabia.
Information System Applications
Understanding Enterprise Architecture
Introduction to Project Management
EI Architecture Overview/Current Assessment/Technical Architecture
The Components of Information Systems
IC Conceptual Data Model (CDM)
Achieving Justice Information Interoperability
CV-1: Vision The overall vision for transformational endeavors, which provides a strategic context for the capabilities described and a high-level scope.
The Components of Information Systems
Information Systems in Organizations 2
Enterprise Integration
Introduction to Systems Analysis and Design Stefano Moshi Memorial University College System Analysis & Design BIT
Information System Building Blocks
System architecture, Def.
Presentation transcript:

Reference Architecture for Enterprise Integration CIMOSA GRAI/GIM PERA Dima Nazzal

Definitions Enterprise: a complex set of business processes that can be designed to accomplish a specific set of objectives. Enterprise integration ( agile manufacturing, business process reengineering, CIM): The coordination of the operation of all elements of the enterprise working together in order to achieve the optimal fulfillment of the mission of that enterprise as defined by enterprise management. 1 Architecture: A description (often graphical) of the structure of something 1. A structured plan, a framework on the basis of which a product or an organization of an enterprise can be constructed 2

Definitions Reference model: a general model that can be used as a base to derive other models from. Reference Architecture: is a structured set of models which represent the building blocks of the system. 3 Enterprise Integration Reference Architecture: is a framework in which enterprise related concepts are organized. The most known reference architectures are: CIMOSA, GRAI-GIM and PERA

The Enterprise Model Requirements The enterprise model which fits the specific objectives of the particular enterprise should: identify the different processes in the enterprise. contain the machines, the information, the transfer of information, the human involvement and the functions that have to be carried out. address design activities, manufacturing processes, the way materials are ordered, moved and transformed into products.

Enterprise Modeling Enterprise modeling has to fulfill several requirements to achieve efficient and effective enterprise integration: provide a modeling language easily understood by non-IT professionals, but sufficient for modeling complex industrial environments. provide a modeling framework which:  covers the life cycle of enterprise operation from requirements definition to end of life.  enables focus on different aspects of enterprise operation by hiding those parts of the model not relevant for the particular point of view.  supports re-usability of models or model parts

Open System Architecture for CIM - CIMOSA In 1985, the ESPRIT Consortium AMICE started to work on the definition and specification of a CIM architecture for enterprise integration. CIMOSA (completed in 1996) is pre- modeling solution which provides a framework based on the system life cycle concept

CIMOSA CIMOSA Reference Architecture supports the description of the enterprise, from the management level to the shop floor level CIMOSA consists of: Enterprise modeling framework (reference architecture) Enterprise modeling language Integrating infrastructure

CIMOSA Enterprise RA

CIMOSA Enterprise Modeling Constructs ( building blocks)

CIMOSA Process Based Enterprise Modeling Domains with interacting Domain Processes

CIMOSA Process Based Enterprise Modeling

Decomposition of a Domain Process into Business Processes and Enterprise Activities

CIMOSA Process Based Enterprise Modeling

Domain Process Representation as a network of Enterprise Activities

CIMOSA Process Based Enterprise Modeling

Functional Operations executed by Functional Entities (Resources)

CIMOSA Process Based Enterprise Modeling FO1: set down vehicle FO2: clasp the lot FO3: pull up vehicle FE1: vehicle controller XXX

CIMOSA Integrating Infrastructure The Integrating Infrastructure provides a set of service entities for model engineering and enterprise operation control.

Relations between the Enterprise System Life Cycle and the progress of the modeling process

GIM-GRAI Integrated Methodology Developed by the laboratory for automation and production at the university of Bordeaux- France since 1970’s. GIM is composed of the following elements: GRAI conceptual model: a representation of basic concepts of a manufacturing system decomposed into three sub-systems: physical system, decision and information system. GIM modeling framework (RA) with three dimensions: views, life cycle, and abstraction level. GIM structured approach: guide to show how to perform analysis and design of the manufacturing system in three main phases: analysis, user-oriented design, and technical- oriented design. GIM modeling formalisms (languages): GRAI grid and GRAI nets for decision system modeling, IDEF0 and stock/resource for physical system modeling, ER for information system modeling, IDEF0 for functional system modeling.

GIM Conceptual Model

GIM Modeling Framework and RA

GIM Structured Approach

GIM Modeling Formalisms

Purdue Enterprise Reference Architecture - PERA PERA was developed at Purdue University during the period The simplifying concepts of systems engineering in enterprise integration The mission Separation of functions Networks of tasks The place of the human The life cycle Planning and organization of the integration effort (the master plan)

PERA - Enterprise Integration Project Phases PhaseTitleDescription 1Identification of the Enterprise Business Identity and boundaries of the enterprise 2 Project ConceptMission, vision and values Operational policies 3 Project DefinitionIdentify requirements, tasks and modules Develop flow diagram or other models of the Enterprise Entity 4 Project Specification or Preliminary Design Identify human tasks, initial choice and specification of human organization Identify information and control equipment and mission fulfillment equipment The master plan

PERA - Enterprise Integration Project Phases PhaseTitleDescription 5 Completion of all detailed design needed for construction phase Detailed design of human and organizational information, control, customer product and service components of the enterprise 6 Implementation,test and commissioning phase Conversion of detailed design to actual plant elements, testing, operational trials and acceptance or commissioning 7 Operations phaseThe enterprise is carrying out its mission 8 DecommissioningEnterprise has come to the end of its economic life

PERA RA

PERA- Models and tools involved at each phase of the life cycle

GERAM The IFAC/IFIP Task Force on Architectures for Enterprise Integration was formed by IFAC (The International Federation of Automatic Control) and IFIP (The International Federation for Information Processing) in August The Task Force objective was to contribute a single, universally accepted architecture, framework, or model for enterprise integration. They developed the architectural specification GERAM (Generalized Enterprise Reference Architecture and Methodology). Task Force recognized three RA: CIMOSA GRAI-GIM PERA The "matrix" model for GERAM was developed by combining the distinctive characteristics of each of three studied architectures into one diagram.

Components of the GERAM Framework

Comments on CIMOSA likedDid not like Structuring of RA into generic and partial modeling levels Support for function, information, resource, and organization modeling views. Specifying the processes and exchange of information using domain processes, events, and object views. Constructs definitions are not very clear. Requirements definition level modeling is not well defined No reference models to design the system

Comments on GIM-GRAI LikedDid not like Addition of the decisional view. Some reference models have been developed Requirements definition level modeling is not well defined.

Comments on PERA LikedDid not like The focus on preparing the master plan Emphasis on defining the role of human covers all phases of the enterprise life cycle lack of modeling formalisms. methodology is not clearly defined

References 1. T. J. Williams “PERA and GERAM – Enterprise Reference Architecture for Enterprise Integration”. iies D. Chen, B. Vallespir and G. Doumeingts “GRAI integrated methodology and its mapping onto generic enterprise reference architecture and methodology” Computers in Industry. V33 p G. Doumeingts B. Vallespir, and D. Chen “Methodologies for designing CIM systems: A survey”. V25 p /geram1-6-3/v1.6.3.html