Sobah Abbas Petersen

1
TDT4252Modelling of Information SystemsAdvanced
Course

• Sobah Abbas Petersen
• Adjunct Associate Professor
• sap_at_idi.ntnu.no

2
This Lecture

• Enterprise Modelling Frameworks and reference
  Architectures
• Based on
• A13 GERAM Generalised Enterprise Reference
  Architecture and Methodology, http//www.ict.griff
  ith.edu.au/bernus/taskforce/geram/versions/geram1
  -6-3/v1.6.3.html
• A14 PERA Enterprise Integration Website provides
  an overview of several methodologies, including
  the ones covered in this lecture.
  http//www.pera.net/
• Additional reading
• Vernadat, F. B. (1996), Chapter 3 Enterprise
  Modelling. Chapman and Hall, pp. 69-117. ISBN 0
  412 60550 3.
• A11 Fox, M. S. and Gruninger, M. 1998.
  Enterprise Modelling. AI Magazine, Fall.109-121.
• Lillehagen and Krogstie (2008), Chapter 4 State
  of the Art of Enterprise Modelling.
  Springer-Verlag, Berlin, Heidelberg. pp. 91-118.

3
Presentation Overview

• Provide an overview of the main enterprise
  reference architectures and frameworks.
• CIMOSA
• GRAI GIM
• ARIS
• PERA
• GERAM

4
Enterprise Integration (1)

• It is concerned with providing seamless
  communication, cooperation and coordination
  between enterprises as well as among different
  functionalities within a single enterprise.
• It is aimed towards improved interoperability.
• It is concerned with facilitating information,
  control and material flows across organisational
  boundaries by connecting all the necessary
  functions and heterogeneous functional entities
  in order to improve communication, cooperation
  and coordination within the enterprise, such that
  the enterprise behaves as a whole.

5
Enterprise Integration (1)

• One of the most important characteristics of
  today's enterprises is that they are facing a
  rapidly changing environment and can no longer
  make predictable long term provisions. To adapt
  to this change enterprises themselves need to
  evolve and be reactive so that change and
  adaptation should be a natural dynamic state
  rather then something occasionally forced onto
  the enterprise. This necessitates the integration
  of the enterprise operation and the development
  of a discipline that organises all knowledge that
  is needed to identify the need for change in
  enterprises and to carry out that change
  expediently and professionally.
• This discipline is called Enterprise Engineering.

6
What is a Reference Architecture?

• A reference architecture is a generalised
  framework for describing the components needed in
  all types of enterprise engineering (Bernus
  Nemes).
• A framework is a fundamental structure that
  allows defining the main sets of concepts to
  model and build an enterprise (Lillehagen and
  Krogstie 2008).

7
CIMOSA

• CIMOSA "Computer Integrated Manufacturing Open
  System Architecture.
• It is an enterprise modeling framework, which
  aims to support the enterprise integration of
  machines, computers and people.
• The framework is based on the system life cycle
  concept, and offers a modelling language,
  methodology and supporting technology to support
  these goals.

8
CIMOSA Reference Architecture
View Dimensions
Lifecycle Dimensions
Generecity
9
CIMOSA Description (1)

• The original aim of CIMOSA (1992) has been "to
  elaborate an open system architecture for CIM and
  to define a set of concepts and rules to
  facilitate the building of future CIM system.
• One of the main idea of CIMOSA is the
  categorization of manufacturing operations in
• Generic functions Generic parts of every
  enterprise, independent of its organisation-struct
  ure or business area.
• Examples Control of workflow, administration of
  information management of communication.
• Generic functions should be performed by Generic
  system services.
• Specific (Partial and Particular) functions
  Specific for individual enterprises.
• Examples design of products and production
  processes, generation of production plans,
  scheduling of production, processing of orders,
  etc.
• Specific functions may be performed by machines,
  humans, and computers.

10
CIMOSA Description (2)

• The development of CIMOSA has resulted in two key
  items
• Modeling Framework This framework supports "all
  phases of the CIM system lifecycle from
  requirements definition, through design
  specification, implementation description and
  execution of the daily enterprise operation".
• Integrating Infrastructure This infrastructure
  provides "specific information technology
  services for the execution of the Particular
  Implementation Model.
• It is effectively the communication system which
  interconnects all of the functions in the CIM
  system.

11
CIMOSA Description (3)

• CIMOSA aims at integrating enterprise operations
  by means of efficient information exchange within
  the enterprise. CIMOSA models enterprises using
  four perspectives
• the function view describes the functional
  structure required to satisfy the objectives of
  an enterprise and related control structures
  (workflows)
• the information view describes the information
  required by each function (Humans, machines, and
  control and information systems)
• the resource view describes the resources and
  their relations to functional and control
  structures and
• the organization view describes the
  responsibilities assigned to individuals for
  functional and control structures.

12
CIMOSA Advantages Disadvantages

• Advantages
• Covers both functional and behavioural aspects of
  CIM systems.
• Fully supports system design specification and
  implementation description issues according to
  user requirements.
• It constraints the range of available building
  blocks, forcing vendors to provide standard
  components.
• Satisfies the Principles of separation of
  concern, genericity, reusability, functional
  decomposition, separation of functionality and
  behaviour, separation of processes and resources
  and conformity.
• Disadvantages
• Its inherent complexity.
• Lack of computer tools to support the whole
  methodology.

13
GRAI GIM

• Focused on the decision making process.
• GRAI-GIM contains a user-oriented method and a
  technically-oriented one.
• The user-oriented method transforms user
  requirements into user specification in terms of
  function, information, decisions and resources.
• The technically-oriented method transforms the
  user specification into technical specifications
  in terms of information and manufacturing
  technology components and the organization. The
  technical specification must allow the
  implementor to choose (buy, commission, or
  develop) all the components needed to implement
  the system.

Ref http//www.pera.net/Methodologies/GRAI.html
14
GRAI GIM
15
GRAI GIM

• 3 levels of abstraction
• Conceptual level Without any technical or
  organisational consideration. Aims at asking the
  question what?
• Structural level Integrates and organisational
  point of view and asks the questions Who?,
  When? and Where?
• Realisation level most specific level.
  Integrates the technical constraints and enables
  the choice of real components.

16
GRAI GIM Domain Decomposition

• A domain is a selective perception of a
  manufacturing system.
• A production system may be split into three
  systems
• The physical system, decision system and
  information system.
• These three systems lead to three domains
• Functional, process and resource views.

17
GRAI GIM Advantages Disadvantages

• Advantages
• Provides a systematic approach for modelling the
  decision system of manufacturing enterprises.
• Disadvantages
• Only provides support for requirements definition
  and analysis, but not a tool for system design.
• Makes use of redundant models, i.e. same concepts
  are modelled twice.
• Incomplete no resource view.
• Produces a paper model and not a computerised
  model.
• Dos not support detailed design.

18
ARIS

• ARIS Architecture of Integrated Information
  Systems
• The objective is to reduce the complexity by
  dividing the enterprise into individual views.
• The conceptual design of ARIS is based on an
  integration concept that is derived from an
  analysis of business processes.
• It forms the framework for the development and
  optimisation of integrated information systems as
  well as a description of their implementation.
• ARIS focuses on the analysis and requirements
  definition phase during the design of managerial
  information systems, not on the execution of
  business processes.

19
ARIS Architecture Views
Different modelling languages are allocated to
model the different views.
Ref http//www.pera.net/Methodologies/ARIS/ARIS.h
tml
20
ARIS Views Description

• Functional View
• The processes transforming input into output are
  grouped in this view.
• Organisation View
• Presents the hierarchical organisation structure.
  Groups responsible entities or devices executing
  the same work object.
• Data View
• The data processing environment and the message
  triggering functions.
• Process View
• Relationships among the views and the entire
  business processes are documented in this view.

Additional reference Williams, T. Workflow
Management within the ARIS Framework,
http//www.pera.net/Methodologies/ARIS/ARIS_Paper_
by_Ted_Williams.html
21
ARISDifferent modelling languages are allocated
to model the different views.

• Organisational charts
• ER diagrams
• Function trees
• Etc.

Not CIM-focused, focus on business processes and
management
22
PERA
If you don't know where you are going, you
probably won't get there. http//www.pera.net/

• Purdue Enterprise Reference Architecture
• PERA provides a formal methodology for Enterprise
  Master Planning.
• PERA encompasses existing methodologies for
  Engineering Design, Construction, Operations,
  etc.
• Since PERA represents the full life cycle of the
  Enterprise, all existing Enterprise documents and
  tools can be fitted within its structure.

23
PERA Components of an Enterprise

• There are only 3 major components of any
  enterprise
• Physical Plant
• People
• Information Systems
• PERA provides a life cycle model which
  demonstrates how to integrate Enterprise Systems,
  Physical Plant Engineering and Organizational
  Development from enterprise concept to
  dissolution.
• PERA clearly defines the roles and relationships
  among physical plant, people, and information
  systems.

24
PERA and Lifecycle aspects

• The PERA Model breaks the enterprise life cycle
  into "phases" as follows.
• Define clear "deliverables" at the end of each
  phase
• PERA model indicates there are also interfaces
  within the phase.

25
PERA

• It is vitally important that the interfaces
  between groups who are designing the enterprise
  are clearly understood and coordinated.

26
GERAM
The IFIP/IFAC Task Force analysed these
architectures and concluded that even if there
were some overlaps, none of the existing
reference architectures subsumed the others each
of them had something unique to offer. The
recognition of the need to define a generalised
architecture is the outcome of the work of the
Task Force.
27
GERAMGeneric Enterprise Reference Architecture
and Methodology

• GERAM is about those methods, models and tools
  which are needed to build and maintain the
  integrated enterprise, be it a part of an
  enterprise, a single enterprise or a network of
  enterprises (virtual enterprise or extended
  enterprise).
• It defines a tool-kit of concepts for designing
  and maintaining enterprises for their entire
  life-history. GERAM is not yet-another-proposal
  for an enterprise reference architecture, but is
  meant to organise existing enterprise integration
  knowledge.

28
GERAM

• One aspect of the GERAM framework is that it
  unifies the two distinct approaches of enterprise
  integration, those based on product models and
  those based on business process design. It also
  offers new insights into the project management
  of enterprise integration and the relationship of
  integration with other strategic activities in an
  enterprise.

29
GERAM
30
GERA

• GERA defines the enterprise related generic
  concepts recommended for use in enterprise
  engineering and integration projects. These
  concepts can be categorised as
• a) Human oriented concepts
• to describe the role of humans as an integral
  part of the organisation and operation of an
  enterprise.
• to support humans during enterprise design,
  construction and change.
• b) Process oriented concepts for the description
  of the business processes of the enterprise
• c) Technology oriented concepts for the
  description of the business process supporting
  technology involved in both enterprise operation
  and enterprise engineering efforts (modelling and
  model use support).

31
Human oriented Concepts

• The role of humans in the enterprise remains
  fundamental. Therefore, capturing this knowledge
  in enterprise models will prove to be very useful
  and enable flexible reaction to environmental
  changes.
• They cover human aspects such as capabilities,
  skills, know-how and competencies as well as
  roles of humans in the enterprise o
• Modelling constructs will be required to
  facilitate the description of human roles as an
  integral part of the organisation and operation
  of an enterprise. The constructs should
  facilitate the capture of enterprise models that
  describe
• Human roles.
• The way in which human roles are organised so
  that they interoperate with other human and
  technology elements when realising enterprise
  operations.
• The capabilities and qualities of humans as
  enterprise resource elements.

32
Process Oriented Concepts

• Aims at describing the processes in the
  enterprise capturing both their functionality
  (that is what has to be done ) and their
  behaviour (that is when things are done and in
  which sequence).
• The process-oriented concepts defined in GERA
  are
• Enterprise entity life-cycle and life-cycle
  phases.
• Life history.
• Enterprise entity types.
• Enterprise modelling with integrated model
  representation and model views.
• Life History
• The life history of a business entity is the
  representation in time of tasks carried out on
  the particular entity during its entire life
  span. Relating to the life-cycle concept
  described above, the concept of life history
  allows to identify the tasks pertaining to these
  different phases as activity types.

33
GERA Lifecycle phases
Life History
34
Technology Oriented Concepts

• Both the enterprise engineering process and the
  operational environment employ a significant
  amount of technology.
• Technology is either production oriented and
  therefore involved in producing the enterprise
  products and customer services, or management and
  control oriented,? providing the necessary means
  for communication and information processing and
  information sharing.
• Technology oriented concepts have to provide
  descriptions of the technology involved in both
  the enterprise operation and the enterprise
  engineering efforts.

35
GERA Modelling Framework

• GERA provides an analysis and modelling framework
  that is based on the life-cycle concept and
  identifies three dimensions for defining the
  scope and content of enterprise modelling.
• Life-Cycle Dimension providing for the
  controlled modelling process of enterprise
  entities according to the life-cycle activities.
• Genericity Dimension providing for the
  controlled particularisation (instantiation)
  process from generic and partial to particular.
• View Dimension providing for the controlled
  visualisation of specific views of the enterprise
  entity.

36
GERA Modelling Framework with Modelling Views
37
GERA Views

• view concept that allows the operational
  processes to be described as an integrated model,
  but to be presented to the user in different
  sub-sets (model views) of an integrated model
• Views identified in GERA
• Entity Model Contents Views function,
  information, resource, organisation.
• Entity Purpose Views customer service and
  product, management and control.
• Entity Implementation View human implemented
  tasks, automated tasks (mission support
  technology, and management and control
  technology).
• Entity Physical Manifestation Views software,
  hardware.
• Additional views may be defined according to
  specific user needs.

38
Summary

• We have looked at several different Enterprise
  Reference Architectures and Frameworks.
• CIMOSA and PERA take into account the lifecycle
  perspective.
• ARIS for management systems.
• GRAI GIM - Focused on decision support.
• PERA Enterprise Master Planning.
• GERAM aimed at subsuming the others.

39
How do the other frameworks fit into GERAM?

• Lifecycle view CIMOSA, PERA
• Genericty View CIMOSA
• Process design and modelling CIMOSA (functional
  view), GRAI-GIM, ARIS
• Organisation view CIMOSA (functional view),
  GRAI-GIM, ARIS, PERA (human aspects)
• Resource view CIMOSA (functional view), ARIS,
  PERA

40
Next Lecture

• Introduction to AKM
• Brief overview Monday 14 March, 1500hrs, F3
• Friday, 18 March, 1400hrs, F4
• Based on Lillehagen and Krogstie (2008), Chapter
  1 State of the Art of Enterprise Modelling.
  Springer-Verlag, Berlin, Heidelberg. pp. 1-25.
• There will be an exercise class this afternoon,
  1500-1700hrs, where you can ask questions
  related to the assignment and Metis modelling.