Generalised Enterprise Reference Architecture and Methodology: Difference between revisions

Revision as of 15:44, 22 August 2016

Revision as of 15:48, 22 August 2016

Line 23:

The development of enterprise-reference architecture has evolved from the development of Design Methodology for Advanced Manufacturing Systems in the 1980s,<ref>[[Guy Doumeingts|Doumeingts, G.]], [[Bruno Vallespir|Vallespir]], B., Darracar, D., M., "Design Methodology for Advanced Manufacturing Systems", Computers in Industry, Vol. 9, pp. 271-296, December 1987.</ref> such as [[CIMOSA]], the Open System Architecture for CIM.<ref>[[AMICE Consortium]] (1989). ''Open System Architecture for CIM, Research Report of ESPRIT Project 688'', Vol. 1, Springer-Verlag.</ref><ref>[[AMICE Consortium]] (1991), ''Open System Architecture, CIMOSA, AD 1.0, Architecture Description'', ESPRIT Consortium AMICE, Brussels, Belgium.</ref> The GERAM framework was first published by [[Peter Bernus]] and Laszlo Nemes in 1994.<ref name="BN94"/>

== GERAM Topics ==

=== GERAM Components ===

The Generalised Enterprise Reference Architecture and Methodology (GERAM) consists of a series of eight main components, as shown in figure 1:

* ''Generic Enterprise Reference Architecture (GERA)'' : Defines the enterprise related generic concepts recommended for use in enterprise integration projects. These concepts include enterprise systems life cycle; business process modeling; modeling languages for different users of the architecture (business users, system designers, IT modeling specialists, others); integrated model representation in different model views.

* ''Generic Enterprise Engineering Methodologies (GEEM)'' : Describe the generic processes of enterprise integration. These methodologies may be described in terms of process models with detailed instruction for each step of the integration process.

* ''Generic Enterprise Modeling Languages (GEML)'' : Define the generic constructs (building blocks) for enterprise modeling adapted to the different needs of people creating and using enterprise models.

* ''Generic Enterprise Modeling Tools (GEMT)'' : Define the generic implementation of enterprise-integration methodologies and modeling languages and other support for creation and use of enterprise models.

* ''Enterprise Models (EM)'' : Represents the enterprise operation. These models will be represented using generic modeling language constructs.

* ''Ontological Theories (OT)'' : Formalise the most generic aspects of enterprise-related concepts in terms of essential properties and axioms.

* ''Generic Enterprise Models (GEMs)'' : Identify reference models (partial models) which capture concepts common to many enterprises. GEMs will be used in enterprise modeling to increase modeling process efficiency.

* ''Generic Modules (GMs)'' : Identify generally applicable products to be employed in enterprise integration (e.g. tools, integrating infrastructures, others.).

=== Generic Enterprise Reference Architecture ===

Line 76:

Enterprise Modelling concept provides process models of enterprise operations. Process oriented modelling allows to represent the operation of enterprise entities and entity types in all its aspects: functional, behaviour, information, resources and organisation. Models which can be used for decision support by evaluating operational alternatives or for model driven operation control and monitoring.

To hide complexity of the resulting model it will be presented to the user in different sub-sets (views). This view concept is shown in Figure 5 : GERA Generic Reference Architecture Concept. It is applicable during all phases of the life cycle. Please note that the views will be generated from the underlying integrated model and any model manipulation. That means any change being done in one particular view will be reflected in all relevant aspects of the model. The GERA life cycle model has defined four different views: function, information, decision/organisation and resource/structure. Other views may be defined if needed and supported by the modelling tool. In addition, the life cycle model of GERA provides for two different categories of modelling: operation control and customer-service related.

==== Modelling Language concept ====