Generalised Enterprise Reference Architecture Research Articles

Skills for Industry 4.0: a structured repository grounded on a generalized enterprise reference architecture and methodology-based framework

ABSTRACT This paper outlines a conceptual framework and a repository of skills for Industry 4.0 that manufacturing managers and other stakeholders can use for training, hiring and developing human resources. The framework and the repository of Industry 4.0 skills were developed by involving industrial practitioners, technology providers, recruitment agencies, research and education organizations in scenario-based focus groups and semi-structured interviews. The results of this study contribute to improving our current understanding of the skills required for Industry 4.0, and they can be used for the identification and assessment of workers’ skills as well as the design of skill development programs that match the needs of the industry and for the definition of policies that support the development of human capital to improve the employability of individuals and the performance of manufacturing companies.

Production System Modelling Methodologies of an Open Pit Mine

Open pit mines experience several challenges and constraints in the management of mining operations and processes. The heterogeneity of the infrastructures and the complexity of the physical and managerial systems highlight these various challenges. The creation of a generic system that can drive but at the same time models in a dynamic logic all these constraints and elements assume a major complexity. In addition, the modelling allows the implementation of real-time decision-making components and increases the responsiveness of the system. This paper presents six modelling methodologies of the production system, namely Open System Architecture for Computer Integrated Manufacturing, GRAI Integrated Methodology, Purdue Enterprise Reference Architecture, Generalized Enterprise Reference Architecture and Methodology, Zachman and Model Based System Engineering. Based on the multi-criteria analysis, we have shown that the Modelling Based System Engineering is the most adapted methodology in the case of open pit mines but this method knows a lack of agility in the system. Our system will use a methodology based on Model Based System Engineering and will consider the agility of the system.

Development of Transportation Management System with the Use of Ontological and Architectural Approaches to Ensure Trucking Reliability

With the wide variety of information systems and applications for motor transport and transport logistics control we have today, one may think we are already living in the digital era of general welfare, and digital tools would easily ensure sustainable development and prosperity of businesses. However, the experience of deployment and introduction of such solutions shows that their value for transport business is significantly lower than expected. Moreover, in some projects, business performance of transport companies had no correlation with introduction of information systems. In the best-case scenario, they provided for a slight decrease in document flow transaction costs. The change of the strategic status of a company in the transportation service market is a fairly complicated task, which, as analysis of literary sources shows, is achievable for few enterprises, primarily small and medium-sized businesses. Such situations show that information solutions were introduced without analyzing or assessing the business models of certain companies which could be used a basis for digital landscape of business as a whole. In recent years, the basic concept of forming a single information space of an enterprise has been the enterprise architecture. It provided for coordination between all the business processes in order to achieve a company’s strategic goals. The fundamentals of the concept were developed by J. Zachman in his famous Zachman Framework, and it was later developed with numerous models of enterprise architecture (e.g., TOGAF (Department of Defense Architecture Framework), GERAM (Generalised Enterprise Reference Architecture and Methodology), DoDAF (Department of Defense Architecture Framework)). However, currently some researchers note that sustainable corporate development should stem not only from a “correct assembly” of all its business elements, which was the purpose of enterprise architecture, but also from the interaction of these elements when reaching the emergence effect. In this context, one should pay attention to comprehensive activity analysis of a transport and logistics business using ontological and architecture approaches.

Enterprise Architecture: Twenty Years of the GERAM Framework

Apart from the 20-year anniversary in 2014 of the first publication of the GERAM ('Generalised Enterprise Reference Architecture and Methodology') Enterprise Architecture Framework, the timeliness of this paper lies in the new interest in the use of systems theory in Enterprise Architecture (EA), and consequently, 'light-weight' architecture frameworks (AFs). Thus, this paper is about the use of systems thinking and systems theory in EA and about how it is possible to reconcile and understand, based on a single overarching framework, the interplay of two major enterprise change endeavours: on the one hand enterprise engineering (i.e. deliberate change) and on the other hand evolutionary, organic change. The paper also attempts to show how such change processes can be illustrated by employing systems thinking to construct dynamic business models: the evolution of these concepts is exemplified with some past applications in networked enterprise building and more recent proposals in environmental, disaster and healthcare management. Finally, the paper attempts to plot the way GERAM will continue to contribute to society in the context of future challenges and emerging opportunities.

Developing life-cycle phases for the DoDAF using ISO15704 Annex A (GERAM)

This paper presents a development of the US Department of Defense Architecture Framework (DoDAF) based on life-cycle concept of the Generalized Enterprise Reference Architecture and Methodology (GERAM) framework/ISO 15704:2000 requirements. Previous research has identified areas of concern within DoDAF by analyzing and evaluating DoDAF against GERAM and potentially assisting in its future development. This paper aims to extend existing architecture description process and artifacts within DoDAF that match the scope of the GERAM life-cycle phases. For this development we use life-cycle aspect of three well-known reference architectures (including PERA, CIMOSA, and GRAI-GIM) that were the basis in formation of GERAM.

A systematic evaluation of the C4ISR AF using ISO15704 Annex A (GERAM)

This paper presents an analytical mapping of the US Department of Defence (DoD) Command, Control, Communications, Computers, Intelligence, Surveillance and Reconnaissance (C4ISR) AF onto the Generalised Enterprise Reference Architecture and Methodology (GERAM) framework. The analysis aims to find artefacts within C4ISR that match the scope of the GERAM components. The scope of the study covers reference architectures (including life cycle/life history concepts and modelling framework) and associated modelling methodologies, languages and reference models, modelling tools and generic modelling concepts. The analysis identifies areas of concern within C4ISR and proposes some solutions as necessary, thus demonstrating the use of GERAM in evaluating AFs and potentially assisting in their future development.

An analysis of the Zachman framework for enterprise architecture from the GERAM perspective

This article presents an analysis of the Zachman framework for enterprise architecture and its mapping onto the Generalised Enterprise Reference Architecture and Methodology (GERAM) framework/ISO IS15704:2000 requirements. Aspects covered concern the ability of the Zachman framework to cover the complete scope of the GERAM metamodel, such as life cycle/life history concepts, modelling framework, enterprise entities and entity recursion, associated enterprise engineering methodologies, modelling languages and reference models.

DESIGNING MANUFACTURING SYSTEMS: CONTRIBUTION TO THE DEVELOPMENT OF AN ENTERPRISE ENGINEERING METHODOLOGY (EEM) WITHIN THE FRAME OF GERAM

Within the frame of the GERAM (Generalised Enterprise Reference Architecture and Methodology) developed by the IFAC/IFIP Task on Architecture for Enterprise integration, this paper presents a preliminary approach for the development of an Enterprise Engineering Methodology (EEM). The approach is currently limited to Entity requirements and Entity design phases of the GERA (Generic Enterprise Reference Architecture) system life cycle. It tentatively proposes a process to follow to identify user's requirements and to perform system design. The approach of the proposal is based on the GRAI methodology. Relevant concepts and principles from CIMOSA and PERA also take part in the approach.

The task force specification for GERAM and its fulfillment by PERA

The IFAC/IFIP Task Force on Architectures for Enterprise Integration has established a specification and set of requirements for a Generalized Enterprise Reference Architecture and Methodology (GERAM) as a class of complete enterprise architecture systems. These can be used to judge whether a specific enterprise reference architecture and methodology fulfills such requirements and can itself be classified as a GERAM. This paper describes the development of these requirements by the Task Force and shows how the Purdue Enterprise Reference Architecture and Methodology (PERA) fulfills them and can be labeled as a GERAM.

The Task Force Specification for GERAM and its Fulfillment by PERA

The IFAC/IFIP Task Force on Architectures for Enterprise Integration has established a specification and set of requirements for a Generalized Enterprise Reference Architecture and Methodology (GERAM) as a class of complete enterprise architecture systems. These can be used to judge whether a specific enterprise reference architecture and methodology fulfills such requirements and can itself be classified as a GERAM. This paper describes the development of these requirements by the Task Force and shows how the Purdue Enterprise Reference Architecture and Methodology (PERA) fulfills them and can be labeled as a GERAM.