• Like
Upcoming SlideShare
Loading in...5

Thanks for flagging this SlideShare!

Oops! An error has occurred.




Published in Technology , Business
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads


Total Views
On SlideShare
From Embeds
Number of Embeds



Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

    No notes for slide


  • 1. Reference Architecture for Enterprise Integration CIMOSA GRAI/GIM PERA Dima Nazzal
  • 2. 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
  • 3. 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
  • 4. 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.
  • 5. 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
  • 6. 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
  • 7. 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
  • 8. CIMOSA Enterprise RA
  • 9. CIMOSA Enterprise Modeling Constructs ( building blocks)
  • 10. CIMOSA Process Based Enterprise Modeling Domains with interacting Domain Processes
  • 11. CIMOSA Process Based Enterprise Modeling
  • 12. CIMOSA Process Based Enterprise Modeling Decomposition of a Domain Process into Business Processes and Enterprise Activities
  • 13. CIMOSA Process Based Enterprise Modeling
  • 14. CIMOSA Process Based Enterprise Modeling Domain Process Representation as a network of Enterprise Activities
  • 15. CIMOSA Process Based Enterprise Modeling
  • 16. CIMOSA Process Based Enterprise Modeling Functional Operations executed by Functional Entities (Resources)
  • 17. CIMOSA Process Based Enterprise Modeling X X X FE1: vehicle controller FO3: pull up vehicle FO2: clasp the lot FO1: set down vehicle
  • 18. CIMOSA Integrating Infrastructure
    • The Integrating Infrastructure provides a set of service entities for model engineering and enterprise operation control.
  • 19. Relations between the Enterprise System Life Cycle and the progress of the modeling process
  • 20. 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.
  • 21. GIM Conceptual Model
  • 22. GIM Modeling Framework and RA
  • 23. GIM Structured Approach
  • 24. GIM Modeling Formalisms
  • 25. Purdue Enterprise Reference Architecture - PERA
    • PERA was developed at Purdue University during the period 1989-91.
    • 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)
  • 26. PERA - Enterprise Integration Project Phases
    • Identify human tasks, initial choice and specification of human organization
    • Identify information and control equipment and mission fulfillment equipment
    Project Specification or Preliminary Design 4
    • Identify requirements, tasks and modules
    • Develop flow diagram or other models
    • of the Enterprise Entity
    Project Definition 3
    • Mission, vision and values
    • Operational policies
    Project Concept 2 Identity and boundaries of the enterprise Identification of the Enterprise Business 1 Description Title Phase The master plan
  • 27. PERA - Enterprise Integration Project Phases Enterprise has come to the end of its economic life Decommissioning 8 Detailed design of human and organizational information, control, customer product and service components of the enterprise Completion of all detailed design needed for construction phase 5 Conversion of detailed design to actual plant elements, testing, operational trials and acceptance or commissioning Implementation,test and commissioning phase 6 The enterprise is carrying out its mission Operations phase 7 Description Title Phase
  • 28. PERA RA
  • 29. PERA- Models and tools involved at each phase of the life cycle
  • 30. 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 1990.
    • 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.
  • 31. Components of the GERAM Framework
  • 32.  
  • 33. Comments on CIMOSA
    • Constructs definitions are not very clear.
    • Requirements definition level modeling is not well defined
    • No reference models to design the system
    • 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.
    Did not like liked
  • 34. Comments on GIM-GRAI
    • Requirements definition level modeling is not well defined.
    • Addition of the decisional view.
    • Some reference models have been developed
    Did not like Liked
  • 35. Comments on PERA
    • lack of modeling formalisms.
    • methodology is not clearly defined
    • The focus on preparing the master plan
    • Emphasis on defining the role of human
    • covers all phases of the enterprise life cycle
    Did not like Liked
  • 36. References
    • T. J. Williams. 1998. “PERA and GERAM – Enterprise Reference Architecture for Enterprise Integration”. iies.www.ecn.purdue.edu/IIES/PLAIC/PERA-GERAM_10-98.pdf
    • http:// cimosa . cnt .pl/Docs/Primer/primer0. htm
    • D. Chen, B. Vallespir and G. Doumeingts. 1997. “GRAI integrated methodology and its mapping onto generic enterprise reference architecture and methodology” Computers in Industry . V33 p387-394.
    • G. Doumeingts B. Vallespir, and D. Chen. 1995. “Methodologies for designing CIM systems: A survey”. V25 p263-280
    • http://www.cit.gu.edu.au/~bernus/taskforce/geram/versions/geram1-6-3/v1.6.3.html