Peter Bernus

Last updated

Peter Bernus (born 1949) is a Hungarian Australian scientist and Associate Professor of Enterprise Architecture at the School of Information and Communication Technology, Griffith University, Brisbane, Australia. [1]

Contents

Biography

Peter Bernus graduated from Budapest Technical University as an engineer in electronic technology in 1976. He started working at the Mechanical Engineering Automation Division Computer and Automation Institute of the Hungarian Academy of Sciences. In 1990 he became a research officer at the Computer Science Department of the University of Queensland in Australia. He is currently an associate professor at Griffith University teaching in the Masters of Enterprise Architecture program.

Since 1976 he worked internationally on various aspects of enterprise integration as researcher, consultant and project leader for Industry, Government and Defense. In 2000–2003 Bernus was the Australian leader of the Enterprise Engineering work package of the Globemen International consortium, working with over 20 companies, that include ERP vendors, shipbuilding and engineering companies, among others. [2]

Bernus is the past chair of the IFAC/IFIP Task Force on Architectures for Enterprise Integration which developed GERAM, the Generalised Enterprise Reference Architecture and Methodology (ISO 15704:2000) and foundation chair of Working Group 5.12 on Enterprise Integration of the International Federation of Information Processing (IFIP), currently working on the harmonisation of EA Frameworks, systems engineering and software engineering standards. [2]

Bernus is also series editor for Springer Verlag and Managing Editor of the "Handbook on Enterprise Architecture", and is member of the editorial boards of several international journals. [2]

Work

Peter Bernus' research interests are in Enterprise Modelling, Enterprise Integration and Architectures for Enterprise Integration. [1] Special interests include inter- and intra-organisational management, global enterprise networks, and dynamic project enterprises. He also has special interest in computer-mediated communication between people and ways to achieve common understanding. [2]

GERAM Enterprise Architecture Framework

Generalised Enterprise Reference Architecture and Methodology (GERAM) is developed in the 1990s by an IFAC/IFIP Task Force on Architectures for Enterprise Integration with Peter Bernus, James G. Nell and others. The IFAC/IFIP Task Force on Architectures for Enterprise Integration was established in 1990 and had studied enterprise-reference architectures ever since. [3]

The development of GERAM started with the evaluation of the earlier enterprise-reference architectures and their associated methodologies, such as CIMOSA, GRAI/GIM and the Purdue Enterprise Reference Architecture (PERA). [4] Further, requirements were established about the needs of industry for such aids to enterprise integration, which led to an overall definition of generalised architecture.

The result has been called GERAM, for "Generalized Enterprise-Reference Architecture and Methodology". 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. [3]

Handbook on Enterprise Architecture

In the 2003 "Handbook on Enterprise Architecture" Bernus and others introduce the GERAM Framework, indicate how it relates to other existing frameworks, [5] and describe "how to design the architecture for an enterprise by considering all life cycle aspects of Enterprise Entities, such as individual enterprises, enterprise networks, virtual enterprises, projects, and other complex systems including a mixture of automated and human processes." [6] For this the book is divided into five parts.

  1. Architecture Frameworks – Organising Enterprise Architecture Knowledge
  2. Strategy Making and Business Planning
  3. Defining the Requirements for Enterprise Change
  4. Developing the Master Plan – Architectural Design of the Changed Enterprise
  5. Case Studies

According to Martin et al (2004) "Bernus et al. [Bernus, 2003] give several thorough case studies (along with an extensive discussion of enterprise architecture issues). Whether the frameworks address manufacturing operations, process control, information systems, or government bureaucracy, the artifacts produced to describe the enterprise comprise a valuable asset requiring its own distinct management. Managing and gaining full value from that asset is the reason enterprise architecture frameworks are conceived, built, and used." [7]

Publications

Bernus has published over sixty refereed papers and book chapters, several edited books. [8] [9]

Related Research Articles

<span class="mw-page-title-main">CIMOSA</span> Enterprise modeling framework

CIMOSA, standing for "Computer Integrated Manufacturing Open System Architecture", is an enterprise modeling framework, which aims to support the enterprise integration of machines, computers and people. The framework is based on the system life cycle concept, and offers a modelling language, methodology and supporting technology to support these goals.

<span class="mw-page-title-main">Enterprise integration</span>

Enterprise integration is a technical field of enterprise architecture, which is focused on the study of topics such as system interconnection, electronic data interchange, product data exchange and distributed computing environments.

A reference architecture in the field of software architecture or enterprise architecture provides a template solution for an architecture for a particular domain. It also provides a common vocabulary with which to discuss implementations, often with the aim to stress commonality. A software reference architecture is a software architecture where the structures and respective elements and relations provide templates for concrete architectures in a particular domain or in a family of software systems.

<span class="mw-page-title-main">Enterprise architecture framework</span> Frame in which the architecture of a company is defined

An enterprise architecture framework defines how to create and use an enterprise architecture. An architecture framework provides principles and practices for creating and using the architecture description of a system. It structures architects' thinking by dividing the architecture description into domains, layers, or views, and offers models - typically matrices and diagrams - for documenting each view. This allows for making systemic design decisions on all the components of the system and making long-term decisions around new design requirements, sustainability, and support.

Enterprise engineering is the body of knowledge, principles, and practices used to design all or part of an enterprise. An enterprise is a complex socio-technical system that comprises people, information, and technology that interact with each other and their environment in support of a common mission. One definition is: "an enterprise life-cycle oriented discipline for the identification, design, and implementation of enterprises and their continuous evolution", supported by enterprise modelling. The discipline examines each aspect of the enterprise, including business processes, information flows, material flows, and organizational structure. Enterprise engineering may focus on the design of the enterprise as a whole, or on the design and integration of certain business components.

<span class="mw-page-title-main">Enterprise life cycle</span> Process of changing an enterprise over time

Enterprise life cycle (ELC) in enterprise architecture is the dynamic, iterative process of changing the enterprise over time by incorporating new business processes, new technology, and new capabilities, as well as maintenance, disposition and disposal of existing elements of the enterprise.

<span class="mw-page-title-main">Generalised Enterprise Reference Architecture and Methodology</span>

Generalised Enterprise Reference Architecture and Methodology (GERAM) is a generalised enterprise architecture framework for enterprise integration and business process engineering. It identifies the set of components recommended for use in enterprise engineering.

François B. Vernadat is a French and Canadian computer scientist, who has contributed to Enterprise Modelling, Enterprise Integration and Networking over the last 40 years specialising in Enterprise Architectures, business process modelling, information systems design and analysis, systems integration and interoperability and systems analysis using Petri nets.

<span class="mw-page-title-main">James G. Nell</span> American engineer (born 1938)

James G. "Jim" Nell is an American engineer. He was the principal investigator of the Manufacturing Enterprise Integration Project at the National Institute of Standards and Technology (NIST), and is known for his work on enterprise integration.

<span class="mw-page-title-main">ISO 19439</span> International standard for enterprise modelling and enterprise integration

ISO 19439:2006 Enterprise integration—Framework for enterprise modelling, is an international standard for enterprise modelling and enterprise integration developed by the International Organization for Standardization, based on CIMOSA and GERAM.

Enterprise interoperability is the ability of an enterprise—a company or other large organization—to functionally link activities, such as product design, supply chains, manufacturing, in an efficient and competitive way.

Model Driven Interoperability (MDI) is a methodological framework, which provides a conceptual and technical support to make interoperable enterprises using ontologies and semantic annotations, following model driven development (MDD) principles.

IFIP Working Group WG 2.10 on Software Architecture is a working group of the International Federation for Information Processing (IFIP).

Mark Stephen Fox is a Canadian computer scientist, Professor of Industrial Engineering and Distinguished Professor of Urban Systems Engineering at the University of Toronto, known for the development of Constraint Directed Scheduling in the 1980s and the TOVE Project to develop an ontological framework for enterprise modeling and enterprise integration in the 1990s.

Kurt Kosanke is a German engineer, retired IBM manager, director of the AMICE Consortium and consultant, known for his work in the field of enterprise engineering, Enterprise integration and CIMOSA.

<span class="mw-page-title-main">Purdue Enterprise Reference Architecture</span>

Purdue Enterprise Reference Architecture (PERA), or the Purdue model, is a 1990s reference model for enterprise architecture, developed by Theodore J. Williams and members of the Industry-Purdue University Consortium for Computer Integrated Manufacturing.

Theodore Joseph Williams was an American engineer and Professor of Engineering at Purdue University, known for the development of the Purdue Enterprise Reference Architecture.

Guy Doumeingts is a French engineer, Emeritus professor at the University of Bordeaux 1 and former Director of "Laboratoire d’Automatique, Productique Signal et Image" control theory, known for the development of the GRAI method and his contributions to the field of Enterprise modelling.

Bruno Vallespir is a French engineer, and Professor of Enterprise Modelling at the University of Bordeaux, working in the fields of production management, performance evaluation and enterprise modeling.

The history of business architecture has its origins in the 1980s. In the next decades business architecture has developed into a discipline of "cross-organizational design of the business as a whole" closely related to enterprise architecture. The concept of business architecture has been proposed as a blueprint of the enterprise, as a business strategy, and also as the representation of a business design.

References

  1. 1 2 Peter Bernus. Accessed 10 January 2009.
  2. 1 2 3 4 Short bio. Accessed 10 January 2009
  3. 1 2 J.G. Nell (2006). "Requirements and Methodology for Enterprise-Reference Architectures: A New Work Item Proposal". updated 20 May 1996.
  4. ↑ Generalised Enterprise Reference Architecture and Methodology. Version 1.6.3 (March 1999). Accessed 10 January 2009.
  5. ↑ Deborah J. Nightingale and Donna H. Rhodes (2004) "Enterprise Systems Architecting: Emerging Art and Science within Engineering Systems". MIT Engineering systems symposium 2004. p. 2
  6. ↑ Peter Bernus, Laszlo Nemes and Günter Schmidt (ed.) (2003). Handbook on enterprise architecture.
  7. ↑ Richard A. Martin et al (2004) "Architectural Principles for Enterprise Frameworks: Guidance for Interoperability". ICEIMT 2004. p. 4
  8. ↑ Peter Bernus at DBLP Bibliography Server OOjs UI icon edit-ltr-progressive.svg
  9. ↑ Peter Bernus publications indexed by Google Scholar OOjs UI icon edit-ltr-progressive.svg
This page is based on this Wikipedia article
Text is available under the CC BY-SA 4.0 license; additional terms may apply.
Images, videos and audio are available under their respective licenses.