scispace - formally typeset
Search or ask a question
Journal ArticleDOI

Standards on enterprise integration and engineering—state of the art

TL;DR: A survey of relevant standards in this area is presented and some recommendations for future works are given as part of the conclusion.
Abstract: With the globalization of manufacturing activities and increasing requirements on interoperability, standardization will play an important role in R&D and day-to-day activities related to enterprise integration and engineering. The paper presents a survey of relevant standards in this area. After a brief introduction on various standardization activities carried out worldwide, the paper gives an overview of the major results achieved and work being performed so far. Comparisons between various standards are presented. A concluding summary and some recommendations for future works are given as part of the conclusion.
Citations
More filters
Journal ArticleDOI
TL;DR: The main part of the paper focuses on the recent developments on architectures for enterprise interoperability and the main initiatives and existing works are presented.

671 citations

Journal ArticleDOI
TL;DR: This research seeks to identify barriers to e‐government integration (EGI) with a set of 17 barriers which were organised into one of four categories: strategy, technology, policy and organization.
Abstract: Purpose – Integration is a critical success factor for achieving a mature level of e‐government. This research seeks to identify barriers to e‐government integration (EGI).Design/methodology/approach – Semi‐structured interviews were conducted with 14 consultants with significant experience of e‐government projects. The interview transcripts were analysed by the researcher to identify barriers in EGI.Findings – The findings resulted in a set of 17 barriers which were organised into one of four categories: strategy, technology, policy and organization. Strategy barriers include common e‐government goals and objectives, delivery timeframes, and ownership and governance. Technology barriers include architecture interoperability, data standards and legacy systems. Policy barriers include citizen privacy, data ownership and policy implications. Organization barriers include pace of government reform, legacy government processes and management and technical skills.Research limitations/implications – One of the ...

312 citations


Cites background from "Standards on enterprise integration..."

  • ...The main purpose of these EA reference standards is to facilitate integration between manufacturing applications ( Chen and Vernadat, 2004...

    [...]

Journal ArticleDOI
François B. Vernadat1
TL;DR: The paper discusses architectures and methods to build interoperable enterprise systems, advocating a mixed service and process orientation, to support synchronous and/or asynchronous operations, both at the business level and at the application level.

199 citations


Cites background from "Standards on enterprise integration..."

  • ...This requires a fair amount of open standards (Chen & Vernadat, 2004)....

    [...]

  • ...They have been surveyed in some depth by Chen and Vernadat (2004) and Giachetti (2004)....

    [...]

Journal ArticleDOI
TL;DR: A model of the information flows in Product Life cycle Management serves as the basis for understanding the role of standards in PLM support systems, and a proposal is made for using open standards and open source models for this important activity.
Abstract: This paper introduces a model of the information flows in Product Life cycle Management (PLM), serving as the basis for understanding the role of standards in PLM support systems. Support of PLM requires a set of complementary and interoperable standards that cover the full range of aspects of the products' life cycle. The paper identifies a typology of standards relevant to PLM support that addresses the hierarchy of existing and evolving standards and their usage and identifies a suite of standards supporting the exchange of product, process, operations and supply chain information. A case study illustrating the use of PLM standards in a large organization is presented. The potential role of harmonization among PLM support standards is described and a proposal is made for using open standards and open source models for this important activity.

157 citations


Cites background from "Standards on enterprise integration..."

  • ...Issues of interoperability and the current state of standards is documented in [57]....

    [...]

Journal ArticleDOI
TL;DR: In this paper, an experience feedback process model and conceptual graphs are used for the clarification of explicit knowledge and know-how, the aim of which is to get lessons learned descriptions that are significant, correct and applicable.

120 citations

References
More filters
Book
01 Jun 1992
TL;DR: This tutorial provides a tutorial on Grafcet and Petri Nets and how they are linked and the concepts are introduced with the aid of examples that progressively become more difficult.
Abstract: Provides a tutorial on Grafcet and Petri Nets and how they are linked. The concepts are introduced with the aid of examples that progressively become more difficult. Grafcet, which became an international standard in 1987, is a French tool inspired by Petri Nets to specify logic control.

480 citations


"Standards on enterprise integration..." refers background in this paper

  • ...The Petri net formalism is both a graphical and formal language for general discrete event systems modelling purpose, including manufacturing systems (David and Alla 1992)....

    [...]

DOI
01 Feb 2000
TL;DR: This document describes Version 1.0 of the Process Specification Language (PSL), an interchange format designed to help exchange process information automatically among a wide variety of manufacturing applications such as process modeling, process planning, scheduling, simulation, workflow, project management, and business process re-engineering tools.
Abstract: This document describes Version 1.0 of the Process Specification Language (PSL). PSL is an interchange format designed to help exchange process information automatically among a wide variety of manufacturing applications such as process modeling, process planning, scheduling, simulation, workflow, project management, and business process re-engineering tools. These tools would interoperate by translating between their native format and PSL. Then, any system would be able to automatically exchange process information with any other system via PSL.

257 citations


"Standards on enterprise integration..." refers methods in this paper

  • ...PSL was initially developed by NIST (Schelenoff et al. 2000) and is proposed to be standardized via a Joint Working Group between ISO/TC184/SC4 and ISO/TC184/SC5....

    [...]

Book ChapterDOI
François B. Vernadat1
24 Apr 2002
TL;DR: Modelling and integration issues to progress towards Enterprise Interoperability are discussed and how the CIMOSA architecture can be revised to host these emerging techniques and standards are shown.
Abstract: Enterprise Modelling and Integration has evolved over the last decades from entity-relationship and activity modelling to object and flow modelling as well as from pier-to-pier system integration to inter-organisational exchanges enabling various forms of electronic commerce. The next challenge is Enterprise Interoperability, i.e. seamless integration in terms of service and knowledge sharing. The paper discusses modelling and integration issues to progress towards Enterprise Interoperability and shows how the CIMOSA architecture can be revised to host these emerging techniques and standards.

220 citations

Journal ArticleDOI
TL;DR: The paper presents the rationale and principles of a unified language devoted to the area of Enterprise Modelling, which builds on previous languages and provides constructs to cover function/process, information, resource and organization/decision aspects of business entities.
Abstract: The paper presents the rationale and principles of a unified language devoted to the area of Enterprise Modelling. The language, named UEML, for Unified Enterprise Modelling Language, is not intended to replace existing languages but is intended to provide a uniform interface to enterprise modelling tools and a neutral format for exchange of enterprise models. It therefore builds on previous languages and provides constructs to cover function/process, information, resource and organization/decision aspects of business entities. It is also aligned with results of ODP, CEN TC 310, ISO TC 184 and IFAC-IFIP GERAM efforts in the area of enterprise modelling and engineering.

204 citations


"Standards on enterprise integration..." refers background or methods in this paper

  • ...The development of UEML in the area of Enterprise Modelling and Engineering is similar to what has been achieved in developing UML in the domain of software engineering (Vernadat 2001)....

    [...]

  • ...…standards reviewed in the paper are classified into three groups: (i) those dealing with enterprise modelling and engineering, (ii) those dealing with enterprise systems or sub-systems representation and (iii) those dealing with enterprise IT services and infrastructures (Chen and Vernadat 2001)....

    [...]

Book ChapterDOI
01 Jan 1996
TL;DR: The GRAI models give a generic description of a manufacturing system while focusing on the details of the control part of this system, and presents first from a global point of view and afterwards at the level of the decision center.
Abstract: The GRAI models [1–3] give a generic description of a manufacturing system while focusing on the details of the control part of this system. The control of a manufacturing system will be presented first from a global point of view and afterwards at the level of the decision center.

59 citations


"Standards on enterprise integration..." refers methods in this paper

  • ...…with the significant contributions from the Computer Integrated Manufacturing Open System Architecture (CIMOSA) (AMICE 1993), the GRAI Integrated Methodology (GRAI/GIM) (Doumeingts et al. 1998, Chen and Doumeingts 1996) and the Purdue Enterprise-Reference Architecture (PERA) (Williams et al. 1996)....

    [...]