Generalised Enterprise Reference Architecture and Methodology: Difference between revisions

Revision as of 15:48, 22 August 2016

Revision as of 21:00, 28 October 2016

Line 1:

[[File:GERAM Framework.jpg|thumb|360px|Fig 1. GERAM Framework: This set of components is identified in the first image and briefly described in the following. Starting from defined concepts to be used in enterprise integration (GERA), GERAM distinguishes between the methodologies for enterprise integration (GEEM) and the languages used to describe structure, contents and behaviour of the enterprise (GEML).]]

'''Generalised Enterprise Reference Architecture and Methodology''' ('''GERAM''') is a generalised [[Enterpriseenterprise Architecturearchitecture framework]] for [[enterprise integration]]integra and [[business process]] [[engineering]]. It identifies the set of components recommended for use in [[enterprise engineering]].<ref name="Nell97">[[J.G. Nell]], NIST (1997). "[https://web.archive.org/web/19990221190103/http://www.mel.nist.gov/workshop/iceimt97/ice-gera.htm An Overview of GERAM]" ICEIMT'97 International Conference on Enterprise Integration Modelling Technology 1997. Updated 30 January 1997</ref>

This framework iswas developed in the 1990s by ana joint task force of both the [[International Federation of Automatic Control|IFAC]]/ (IFAC) and the [[International Federation of Information Processing|IFIPInternational Federation of Information Processing]] Task Force(FIP]) on [[Enterpriseenterprise Architecture|Architecturesarchitecture]]s for [[Enterpriseenterprise Integration]]integration. The development started with the evaluation of then -existing frameworks for [[Enterpriseenterprise application integration|enterprise integration]], which was developed into an overall definition of a so-called "generalised architecture", which was named GERAM for "Generalised Enterprise Reference Architecture and Methodology".<ref name="BN94">[[P. Bernus]], and L. Nemes (1994). "A Framework to Define a Generic Enterprise Reference Architecture and Methodology". In: ''Proceedings of the International Conference on Automation, Robotics and Computer Vision (ICARCV'94)'', Singapore, November 10–12, 1994.</ref>

== Overview ==

Line 12:

The building blocks where designed to support the modelling process by providing means for more efficient modelling.<ref name="Nell97"/>

The modelling process will result in anresulting enterprise model (EM) which represents all or part of the [[enterprise operation]]. These models will allow simulation of operational alternatives and thereby their evaluation leading to the optimum structure, contents and behaviour of the enterprise operation. GERAM provides a generic description of all the elements recommended in enterprise engineering and integration.

Generalised Enterprise Reference Architecture and Methodology (GERAM) is an enterprise-reference architecture that models the whole life history of an enterprise integration project from its initial concept in the eyes of the entrepreneurs who initially developed it, through its definition, functional design or specification, detailed design, physical implementation or construction, and finally operation to obsolescence. The architecture aims to be a relatively simple framework upon which all the functions and activities involved in the aforementioned phases of the life of the enterprise-integration project can be mapped. It also will permit the tools used by the investigators or practitioners at each phase to be indicated. The architecture defined will apply to projects, products, and processes; as well as to enterprises.<ref name="Nell96"/>

== History ==

Generalised Enterprise Reference Architecture and Methodology (GERAM) has beenwas developed in the 1990s by an [[International Federation of Automatic Control|IFAC]]/[[International Federation of Information Processing|IFIP]] Task Force on [[Enterprise Architecture|Architectures]] for [[Enterprise Integration]], which consisted of [[Peter Bernus]], [[James G. Nell]] and others. The IFAC/IFIP Task Force on Architectures for Enterprise Integration was establishment in 1990 and had studied enterprise-reference architectures ever since.<ref name="Nell96">[[J.G. Nell]] (2006). "[http://www.mel.nist.gov/sc5wg1/np_geram.htm Requirements and Methodology for Enterprise-Reference Architectures: A New Work Item Proposal]". updated 20 May 1996.</ref>

InThe itstask work the Task Force hasforce established the requirements to be satisfied by candidate enterprise-reference architectures and their associated methodologies to fulfill the needs of [[industry]] for such aids to [[enterprise integration]]. The result has been called GERAM, for "Generalized Enterprise-Reference Architecture and Methodology", by the Task Force. The Task Force has shown that such an architecture is feasible and that several architectures presently available in the literature can already or potentially can fulfil such requirements.<ref name="Nell96"/>

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"/>

Line 26:

=== Components ===

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

* ''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.

Line 39:

=== Generic Enterprise Reference Architecture ===

''Generic Enterprise Reference Architecture'' (GERA) defines the enterprise related generic concepts recommended for use in enterprise integration projects. These concepts include [[enterprise Life Cycle|life cycle]]; enterprise [[entity type]]s, [[enterprise modelling]] with [[business process modelling]]; integrated model representation in different [[view model|model view]]s and [[modelling languages]] for different users of the [[enterprise architecture]] (business users, system designers, IT modelling specialists, among others).<ref name="Nell97"/>

[[File:GERA Life-Cycle Concept.jpg|thumb|180px|Fig 2. GERA Life-Cycle Concept.]]