IFAC/IFIP TASK FORCE ARCHITECTURES FOR ENTERPRISE INTEGRATION
GERAM GENERALISED ENTERPRISE REFERENCE ARCHITECTURE AND METHODOLOGY David Chen IMS-LAPS, University Bordeaux 1
GERAM OBJECTIVE
- Define components of enterprise engineering and integration - Define relationship between these components - Provide a standard terminology in the enterprise engineering domain
Framework Components in GERAM EEM
GERA Generalised Enterprise Reference Architecture identifies concepts of enterprise integration
Enterprise Engineering Methodology describe process of enterprise engineering
EMLs Enterprise Modelling Languages provide modelling constructs for modelling of human role, processes and technologies
utilise
employs
implemented in
GEMCs
PEMs
Generic Enterprise Modelling Concepts (Theories and Definitions) define the meaning of enterprise modelling constructs
Partial Enterprise Models provide reusable reference models and designs of human roles, processes and technologies
EETs Enterprise Engineering Tools support enterprise engineering
support used to build
EMs Enterprise Models enterprise designs, and models to
EMOs Enterprise Modules provide implementable modules of human professions, operational processes, technologies
support analysis and operation used to implement
EOS Enterprise s Operational Systems support the operation of the particular enterprise
Generalised Enterprise Reference Architecture (GERA) • Define the enterprise related generic concepts recommended for use in enterprise engineering and integration project • These concepts include system life cycle, Business Process modelling, model views etc. • Example of GERA: CIMOSA modelling framework
GERA Architecture Concept Views
Generic Partial Particular
Instantiation Identification Concept Requirements Preliminary design Design Detailed design Implementation Operation Decommission
Life-cycle phases
Reference Architecture
Particular Architecture
Enterprise Engineering Methodology (EEM) • Describe the generic processes of enterprise engineering and integration • These methodologies may be described in terms of process models with detailed instruction for each step of the engineering and integration process • Example: GRAI structured approach, PERA approach
System life cycle concept
System life history
Enterprise Modelling Languages (EMLs) • Define the generic constructs (Building blocks) for enterprise modelling adapted to different needs of people creating and using enterprise models • Examples of EML can be found in GRAI, IDEF, CIMOSA, etc.
Enterprise Engineering Tools (EETs) • Supporting modelling languages, including the analysis, design and use of enterprise models, • These tools may also incorporate support for enterprise engineering and integration methodologies • Examples of EET: GRAI tool, ARIS toolset, IDEF0 tool etc.
Partial Enterprise Models (PEMs) • Identify reference models (partial models) which capture concepts common to many enterprises • PEMs will be used in enterprise modelling to increase modelling process efficiency • Examples of PEMs: GRAI grid reference model, CIMOSA partial models, SCOR Reference model, etc.
Generic Enterprise Modelling Concepts (GEMCs) • Formalize the most generic aspects of enterprise concepts in terms of essential properties and axioms • Include ontology and meta models as they consider facts and rules of enterprise models • Example of a enterprise ontology: TOVE
Enterprise Modules (EMOs) • Enterprise modules are generally commercial products which can be used in enterprise integration or by enterprise itself. • Enterprise modules implement one or more enterprise partial models. • Example of EMOs are: ERP packages, AGVs, NC controllers etc.
Enterprise Models (EMs) • Represent particular enterprise systems or sub-systems. • Enterprise models will be elaborated using EMLs with the support of EETs and PEMs. • Example of EMs: FIAT model, IBM model etc.
Enterprise Operation Systems (EOS) • They are implemented operational systems (both physical and management) running in particular companies. • Enterprise Operation systems are designed, implemented and controlled using model driven approach defined in GERAM.
Entity Concepts Example of the relationship between life cycles of two entities: When entity A is operating, it supports the design and detailed design activities of entity B
Entity A Entity B Identification Concept Requirements
Operation
{
Preliminary design Design Detailed design Implementation Operation Decommission
Enterprise Entity Concept Entity Type 2 Engineering Implementation Entity
Entity Type 3
Entity Type 1 Strategic Management Entity
Identification
Initiates, defines, supports
Entity Type 4
Concept
Product Entity
Requirements
Identification
Preliminary design Design
Concept
Detailed design
Requirements
Identification
Implementation
Preliminary design Design
Concept
Detailed design
Requirements
Implementation
Preliminary design Design Detailed design
Operation Entity Type 5
Enterprise Entity
Develops, builds
Decommissioning
Methodology Entity
Operation Decommissioning
Develops, builds
Implementation
Identification
Operation
Concept
Decommissioning
Requirements Preliminary design Design Detailed design
Supports
Implementation Operation
Task 2 Establishes
Task 4
Task 1 Task 3
Decommissioning
