Generalised Enterprise Reference Architecture and Methodology: Difference between revisions

Content deleted Content added
BG19bot (talk | contribs)
m GERAM Components: Remove blank line(s) between list items per WP:LISTGAP to fix an accessibility issue for users of screen readers. Do WP:GENFIXES and cleanup if needed. Discuss this at Wikipedia talk:WikiProject Accessibility#LISTGAP
Rescuing 1 sources and tagging 0 as dead.) #IABot (v2.0.9.5
 
(14 intermediate revisions by 13 users not shown)
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]] 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|IFIP]] Task Force(IFIP) 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 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 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 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>
 
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 [[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"/>
 
== 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 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 ReferenceEngineering ArchitectureMethodologies (GERAGEEM)'' : DefinesDescribe the enterprise related generic conceptsprocesses recommended for use inof enterprise integration projects. These conceptsmethodologies includemay enterprisebe systemsdescribed lifein cycle;terms businessof process modeling;models modelingwith languagesdetailed instruction for differenteach usersstep of the architectureintegration (business users, system designers, IT modeling specialists, others); integrated model representation in different model viewsprocess.
* ''Generic Enterprise EngineeringModeling MethodologiesLanguages (GEEMGEML)'' : DescribeDefine the generic processesconstructs of(building enterpriseblocks) integration.for Theseenterprise methodologiesmodeling mayadapted beto describedthe indifferent termsneeds of processpeople modelscreating withand detailedusing instructionenterprise for each step of the integration processmodels.
* ''Generic Enterprise Modeling LanguagesTools (GEMLGEMT)'' : Define the generic constructsimplementation (buildingof blocks)enterprise-integration formethodologies enterpriseand modeling adaptedlanguages toand theother differentsupport needsfor ofcreation peopleand creatinguse and usingof enterprise models.
* ''Generic Enterprise Modeling ToolsModels (GEMTEM)'' : DefineRepresents the generic implementation of enterprise-integration methodologiesoperation. andThese modelingmodels languageswill andbe otherrepresented supportusing forgeneric creationmodeling andlanguage use of enterprise modelsconstructs.
* ''Ontological Theories (OT)'' : Formalise the most generic aspects of enterprise-related concepts in terms of essential properties and axioms.
* ''Enterprise Models (EM)'' : Represents the enterprise operation. These models will be represented using generic modeling language constructs.
* ''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.
* ''Ontological Theories (OT)'' : Formalise the most generic aspects of enterprise-related concepts in terms of essential properties and axioms.
* ''Generic Enterprise ModelsModules (GEMsGMs)'' : Identify referencegenerally modelsapplicable (partial models) which capture concepts commonproducts to many enterprises. GEMs will be usedemployed in enterprise modelingintegration to(e.g. increasetools, modelingintegrating processinfrastructures, efficiencyothers.).
* ''Generic Modules (GMs)'' : Identify generally applicable products to be employed in enterprise integration (e.g. tools, integrating infrastructures, others.).
 
=== 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 59 ⟶ 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 76 ⟶ 72:
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 ====
Line 128 ⟶ 124:
 
== Further reading ==
* [[François Vernadat|F.B. Vernadat]] (1996). "Enterprise Modeling and Integration: Principles and Applications", Chapman & Hall, London. {{ISBN |0-412-60550-3}}
* [[Theodore J. Williams|T.J. Williams]] and Hong Li, ''A Specification and Statement of Requirements for GERAM (The Generalised Enterprise Reference Architecture and Methodology) with all Requirements illustrated by Examples from the [[Purdue Enterprise Reference Architecture]] and Methodology PERA'', REPORT NUMBER 159 Purdue Laboratory for Applied Industrial Control November 1995, Version 1.1
* D. Shorter, Editor, "An evaluation of CIM modelling constructs - Evaluation report of constructs for views according to ENV 40 003", In: ''Computers in Industry'' - Vol. 24, Nrs 2-3
Line 134 ⟶ 130:
* ''ENV 40 003 Computer Integrated Manufacturing'' - Systems Architecture - Framework for Enterprise Modelling CEN/CENELEC, 1990
* ''ENV 12 204 Advanced Manufacturing Technology'' - Systems Architecture - Constructs for Enterprise Modelling CEN TC 310/WG1, 1995
* Charles J. Petrie, Jr (1992). ''Enterprise Integration Modelling; ICEIMT Conference Proceedings'', The MIT Press. {{ISBN |0-262-66080-6}}
 
== 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]]