Generalised Enterprise Reference Architecture and Methodology: Difference between revisions

Revision as of 17:28, 19 November 2019

Latest revision as of 03:05, 12 August 2025

(4 intermediate revisions by 4 users not shown)

Line 8:

* Enterprise modelling tools (GEMT) to support the enterprise integration process.

* Ontological theories (OT),

* Generic enterprise models (GEMs) and

* Generic modules (GMs)

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

The resulting enterprise model (EM) represents all or part of the enterprise operation. These models will allow simulation of operational alternatives and thereby their evaluation leading. GERAM provides a generic description of all the elements recommended in enterprise engineering and integration.

Line 17:

== History ==

Generalised Enterprise Reference Architecture and Methodology (GERAM) was 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 establishmentestablished in 1990 and hadhas 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>

The task force established the requirements to be satisfied by candidate enterprise-reference architectures and their associated methodologies to fulfill the needs of [[Private industry|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 fulfilfulfill 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 27:

=== Components ===

The 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.

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

Line 38 ⟶ 37:

=== 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 [[wikt:entity|entity typetypes]]s, [[enterprise modelling]] with [[business process modelling]]; integrated model representation in different [[view model|model viewviews]]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.]]

==== Life-Cycle Concept ====

Provides for the identification of the life-cycle phases for any enterprise entity from entity conception to its final end. The Figure 2: GERA Life-Cycle Concept, shows the GERA life cycle phases of enterprise entities. A total of 9 life cycle phases has been defined.

* Identification phase allows the identification of the enterprise business or any part of it in terms of its relation to both its internal and external environment. This includes the definition general commitments of the integration or engineering activities to be carried out in relevant projects.

* Concept phase provides for the presentation of the management visions, missions, values, operational concepts (build/buy, etc.), policies, plus others.

* Identification phase allows the identification of the enterprise business or any part of it in terms of its relation to both its internal and external environment. This includes the definition general commitments of the integration or engineering activities to be carried out in relevant projects.

* Requirement phase allows the description of operational processes and collection of all their functional, behavioural, informational and capability requirements.

* Concept phase provides for the presentation of the management visions, missions, values, operational concepts (build/buy, etc.), policies, plus others.

* Design phase is the specification of operational system with all its components satisfying the above requirements. Process and resources alternatives may be specified which provide operational alternatives to be used during the operation.

* Requirement phase allows the description of operational processes and collection of all their functional, behavioural, informational and capability requirements.

* Implementation phase describes the real operational system which may deviate from the designed system due to enterprise preferences or availability of components.

* Design phase is the specification of operational system with all its components satisfying the above requirements. Process and resources alternatives may be specified which provide operational alternatives to be used during the operation.

* Build phase supports the system manifestation, physical implementation of resources, testing and validation for the designed processes and the subsequent release for operation.

* Implementation phase describes the real operational system which may deviate from the designed system due to enterprise preferences or availability of components.

* BuildOperation phase supportsemploys the systemreleased manifestation,operational physicalprocesses implementationand ofthe provided resources, testingto andsupport validationthe forlife thecycle designedphases processes andof the subsequententerprise release for operationproducts.

* System Change/Re-Engineering phase allows to modify or re-engineer the operational processes according to newly identified needs or capabilities provided by new technologies.

* Operation phase employs the released operational processes and the provided resources to support the life cycle phases of the enterprise products.

* System Change/Re-Engineering phase allows to modify or re-engineer the operational processes according to newly identified needs or capabilities provided by new technologies.

* End of Life phase supports the recycling or disposal of the operational system at the ending of its use in the enterprise operation. This phase has to provide concepts for recycling and/or disposal of all or part of the system.

Line 58 ⟶ 56:

==== Enterprise Entity Type Concept ====

Identifies entity types to be used in enterprise engineering and enterprise integration. Adopting a recursive view of integration altogether five entity types with their associated life-cycles can be identified. The recursiveness of the first four entity types can be demonstrated by identifying the role of the different entities, their products and the relations between them. Figure 3: GERA Enterprise Entity Concept, shows the GERA life cycle phases of enterprise entities. A total of 9 life cycle phases has been defined.

* Strategic Enterprise Management Entity (type 1): defines the necessity and the starting of any enterprise engineering effort.

* Strategic Enterprise ManagementEngineering/Integration Entity (type 12): definesprovides the necessitymeans to carry out the enterprise entity type 1. It employs methodologies (type 5 entity) to define, design, implement and build the startingoperation of anythe enterprise engineeringentity effort.(type 3 entity).

* Enterprise Engineering/Integration Entity (type 23): providesis the meansresult to carry outof the enterpriseoperation of entity type 12. It employsuses methodologies (entity type 5) and the operational system provided by entity) type 2 to define, design, implement and build the operationproducts (services) of the enterprise entity (type 34 entity).

* EnterpriseProduct Entity (type 34): is the result of the operation of entity type 23. It usesrepresents methodologies (entity type 5) and the operational system provided by entity type 2 to define, design, implement and build theall products (services) of the enterprise (type 4 entity).

* Product Entity (type 4): is the result of the operation of entity type 3. It represents all products (services) of the enterprise.

* Methodology Entity (type 5): represents the methodology to be employed in any enterprise entity type.

Line 137 ⟶ 134:

== External links ==

{{Commons category|GERAM}}

* [http://www.cit.gu.edu.au/~bernus/taskforce/geram/versions/geram1-6-3/v1.6.3.html GERAM: Generalised Enterprise Reference Architecture and Methodology Version 1.6.3] {{Webarchive|url=https://web.archive.org/web/20081010224903/http://www.cit.gu.edu.au/~bernus/taskforce/geram/versions/geram1-6-3/v1.6.3.html |date=2008-10-10 }}. by [[Peter Bernus]], March 1999.

[[Category:Enterprise modelling]]