Showing papers on "Enterprise systems engineering published in 2005"
01 Jan 2005
281 citations
TL;DR: The aim of this model is to compile present ES concepts into a comprehensive outline of ERP II, thus composing a generic map and taxonomy for corporate‐wide enterprise systems.
Abstract: Purpose – The purpose of this paper is to frame next‐generation enterprise systems (ES).Design/methodology/approach – The model is based on a retrospective analysis of the evolution of enterprise systems, enterprise resource planning (ERP) research and emerging business requirements.Findings – The paper proposes a conceptual framework for extended enterprise resource planning (ERP II). The aim of this model is to compile present ES concepts into a comprehensive outline of ERP II, thus composing a generic map and taxonomy for corporate‐wide enterprise systems.Research limitations/implications – The paper concludes that the ERP research needs to broaden its perspective in order to accommodate itself to the new issues of next‐generation enterprise systems.Practical implications – The model is seen as a first step towards a tool to analyse and design complex enterprise systems architecture.Originality/value – This paper is the first attempt to formalize and capture the ERP II concept and the next‐generation e...
281 citations
IBM1
TL;DR: The need to redesign the existing organizational models is raised, and the Human Services Bus (HSB) is proposed, a new organizational structure that optimizes the workforce and streamlines cross-unit processes to leverage the new IT systems.
Abstract: In the fast-paced global economy, a corporation must be flexible and agile to meet the shifting needs of operating in an on demand environment. Aligning information technology (IT) systems using service-oriented architecture (SOA) to provide end-to-end enterprise integration and virtualized IT services is a critical step. To be truly effective, however, the SOA paradigm also needs to be extended to transmute organizational structures and behavioral practices. In this paper, we first explore the governance, economic, and enterprise challenges to SOA-based IT transformation. Next, we raise the need to redesign the existing organizational models, and we propose the Human Services Bus (HSB), a new organizational structure that optimizes the workforce and streamlines cross-unit processes to leverage the new IT systems. Finally, we discuss the cultural transformation that is required to support the HSB transition and induce the changes required in management and behavioral practices. The issues and insights at all three layers-IT systems, organizational structures, and cultural practices-are based on IBM's experience with adopting on demand methods.
274 citations
03 Jan 2005
TL;DR: This paper surveys a number of critical challenges and problems of enterprise architecture in an attempt to provide a platform for a discussion on enterprise architecture problems and possible solutions.
Abstract: An enterprise architecture (EA) identifies the main components of the organization, its information systems, the ways in which these components work together in order to achieve defined business objectives, and the way in which the information systems support the business processes of the organization. The components include staff, business processes, technology, information, financial and other resources, etc. Enterprise architecting is the set of processes, tools, and structures necessary to implement an enterprise-wide coherent and consistent IT architecture for supporting the enterprise's business operations. It takes a holistic view of the enterprise's IT resources rather than an application-by-application view. Given the size and still immature nature of many enterprise architecture efforts, a number of critical challenges and problem continue to exist. This paper surveys a number of these challenges and problems in an attempt to provide a platform for a discussion on enterprise architecture problems and possible solutions.
273 citations
TL;DR: The transition to a greater external orientation of enterprise systems is expected to include an extension in the types of organisations that will be integrated electronically into networks, and this study explores the expected future role and use of these information systems.
Abstract: To perform effectively in markets that are becoming increasingly turbulent and volatile, organisations should form information system linkages with their business partners. This study seeks to produce a 'vision' for the future of such linkages. A number of recent developments in information systems and technology (IS/IT) appear to promise the ability to make improvements in this domain. These are electronic hubs, web services, widespread adoption of common enterprise resource planning (ERP) systems and enterprise portals. This study, which is carried out by means of the Delphi technique, explores the expected future role and use of these information systems. The expert participants in the study believe that the focus of enterprise systems is shifting from an internal to an external orientation. They suggest that ERP systems may be reaching a structural limit concerning their capabilities and adjunct technologies will be required to integrate multiple inter-organisational operations. The participants expect that the three other systems and technologies considered can provide those necessary adjunct technologies, either used singly, or more likely in combination. Finally, we find that the transition to a greater external orientation is expected to include an extension in the types of organisations that will be integrated electronically into networks.
119 citations
Book•
01 Jan 2005
TL;DR: In this article, the authors proposed a model for enterprise knowledge infrastructures. But the model is not suitable for cloud-based enterprise knowledge-infrastructured networks.
Abstract: Enterprise knowledge infrastructures , Enterprise knowledge infrastructures , مرکز فناوری اطلاعات و اطلاع رسانی کشاورزی
108 citations
TL;DR: In this paper, the authors briefly outline the nature of ERP systems, noting the main lines of argument in their treatment in the accounting literature so far, and exphasising the way in which they offer a basis for re-evaluating our understanding of organisational integration and control through their detailed field work.
Abstract: Enterprise Resource Planning systems are fundamentally bound up with the work of accounting, and have been seen to have transformative implications for the nature of organisational integration and control. This introductory essay briefly outlines the nature of Enterprise Resource Planning systems, noting the main lines of argument in their treatment in the accounting literature so far. It goes on to set the scene for the distinctive contribution of the two papers that follow, exphasising the way in which they offer a basis for re-evaluating our understanding of organisational integration and control through their detailed field work.
108 citations
TL;DR: It is argued that the design and development of such systems would benefit by implementing this classical systems engineering approach in full, and provides an excellent framework for incorporating human factors (ergonomics) knowledge and integrating ergonomists in the interdisciplinary development of health information systems.
94 citations
Book•
01 May 2005
87 citations
10 Oct 2005
TL;DR: A three-axis taxonomy that can guide design method development and use for systems of systems is presented and two experimental methods applications are presented for SoS problems.
Abstract: The phrase "system of systems "(SoS) has been in use for at least the past ten years. As customers of the aerospace and defense industries began asking for broad capabilities rather than for single systems to meet specific requirements, the notion of a system comprised of multiple, independently operating systems has become more important as the way to meet the desired set of capabilities. Recently, systems of systems have been identified in many other domains, such as health care, energy, logistics, and transportation. Because individual systems can operate independently within an SoS, many engineering methods and tools used to design large-scale, but monolithic, systems do not appear to work for designing systems of systems. This paper presents a three-axis taxonomy that can guide design method development and use for systems of systems. Based on this perspective, two experimental methods applications are presented for SoS problems.
Patent•
07 Jan 2005
TL;DR: In this paper, the authors describe a vertical enterprise system and methods for integrating applications from one or more enterprises into a single interface for presentation to a user, which is called active integration enterprise.
Abstract: Vertical enterprise systems and methods for integrating applications from one or more enterprises into a single interface for presentation to a user are disclosed. A vertical enterprise system in accordance with an illustrative embodiment of the present invention may include one or more client enterprises, one or more partner enterprises, and an active integration enterprise in communication with the one or more client and partner enterprises. The active integration enterprise may include a central integration platform operating on an application integration network adapted to host a number of core components including a portal system, a collaboration system, a database system, and/or a business system. In certain embodiments, the active integration enterprise can be configured to host a number of user-specific applications that provide specific functionality for a particular client. In use, the active integration enterprise can be configured to permit the one or more client and/or partner enterprises to be utilized in a distributed fashion. A single sign-on interface of the portal system can provide the user with application data from multiple enterprises as a single view.
TL;DR: This paper provides an overview of architectures, methods and tools for EE and points out substantial results achieved so far as well as presents a methodology and a related tool in more detail, which supports all phases and aspects of EE.
01 Jan 2005
TL;DR: This paper proposes an EA framework and an associated tool that provide alignment checking along the functional and organizational hierarchies and illustrates this approach with the Sun Microsystems industrial example of the Pet Store.
Abstract: Enterprise architects seek to align enterprise processes and structure with their supporting IT systems so that enterprises can flourish in their environment. The enterprise architecture (EA) discipline has emerged from business best practices. EA frameworks are therefore mostly informal. As a result there is a lack of EA tools that can help enterprise architects to check this alignment. Most notably, current EA tools do not help enterprise architects to formalize the alignment of the multiple levels that constitute an enterprise model. In this paper we propose an EA framework and an associated tool that provide alignment checking along the functional and organizational hierarchies. We illustrate this approach with the Sun Microsystems industrial example of the Pet Store.
TL;DR: The Lean Enterprise Architecture (LEA) as mentioned in this paper is an architectural framework for enterprise reengineering in the design, construction, integration, and implementation of a lean enterprise using systems engineering methods.
Abstract: Purpose – Increasing global competition, free trade agreements, low cost foreign labor, and customer expectations are causing manufacturing enterprises to implement aggressive transformation plans. Should these transformations be incremental or enterprise‐wide? This paper aims to address the question by developing a Lean Enterprise Architecture (LEA) concept for an enterprise‐wide transformation.Design/methodology/approach – The LEA is an architectural framework for enterprise reengineering in the design, construction, integration, and implementation of a lean enterprise using systems engineering methods. The architecture uses a multiphase approach structured on the transformation life cycle phases.Findings – Viewing lean implementation across the entire enterprise minimizes the possibility of overlooking opportunities for further performance improvement. A silo view of lean implementation may allow gaps in performance to persist, with no one assuming responsibility for the entire enterprise. Employing th...
12 Sep 2005
TL;DR: The problem of mastering the ripple effects of a proposed change is addressed, which allows architects to assess the consequences of a particular change to the enterprise, in order to identify potential impacts of a change before it actually takes place.
Abstract: An enterprise architecture is a high-level description intended to capture the vision of an enterprise integrating all its dimensions: organization structure, business processes, and infrastructure. Every single part of an enterprise is subject to change, and each change may have significant consequences within all domains of the enterprise. A lot of effort is therefore devoted to maintaining the integrity of an architectural description. In this paper we address the problem of mastering the ripple effects of a proposed change. This allows architects to assess the consequences of a particular change to the enterprise, in order to identify potential impacts of a change before it actually takes place.
TL;DR: The identified common knowledge enterprise model represents an original combination between the previous projects on enterprise architectures and the Object Management Group (OMG) models and standards and has been designed using the OMG's Model-Driven Architecture and Common Warehouse MetaModel.
Abstract: This paper deals with the conceptual design and development of an enterprise modeling and integration framework using knowledge discovery and data mining. First, the paper briefly presents the background and current state-of-the-art of knowledge discovery in databases and data mining systems and projects. Next, enterprise knowledge engineering is dealt with. The paper suggests a novel approach of utilizing existing enterprise reference architectures, integration and modeling frameworks by the introduction of new enterprise views such as mining and knowledge views. An extension and a generic exploration of the information view that already exists within some enterprise models are also proposed. The Zachman Framework for Enterprise Architecture is also outlined versus the existing architectures and the proposed enterprise framework. The main contribution of this paper is the identification and definition of a common knowledge enterprise model which represents an original combination between the previous pro...
TL;DR: A deeper look at mandates is offered and is intended to surface features not evident when mandates are regarded simply as another type of directive or order from top management, which illuminates the politics of enterprise system implementation from the perspective of the negotiation of meaning and responsibilities.
Abstract: Enterprise information systems are usually mandatory. However, surprisingly little research has been directed to the nature and operation of mandates in research on enterprise systems and on information technology implementation. This study takes a closer look at mandates and their role in the implementation and acceptance of enterprise technologies. Our analysis focuses on the implementation of two enterprise level systems in a major state-funded university system in the US: (1) a state-wide financial management information system that is mandated for use by a large university system; and (2) a system-wide financial and administrative information system that is designed at the university system level and mandated for the individual units of the university system. The analysis offers a deeper look at mandates and is intended to surface features not evident when mandates are regarded simply as another type of directive or order from top management. It also illuminates the politics of enterprise system implementation from the perspective of the negotiation of meaning and responsibilities.
01 Jan 2005
TL;DR: This work presents some of the traditional techniques used for the development of an enterprise model (value system, BPMN, UML) and compares them with a systemic method (SEAM), showing that the concepts of goals, strategies and needs correspond to interpretations of the stakeholders of the enterprise model.
Abstract: Aligning business with IT requires understanding goals, strategies and needs. To be able to express them, an enterprise model can be developed. We present some of the traditional techniques used for the development of an enterprise model (value system, BPMN, UML) and compare them with a systemic method (SEAM). This comparison is done by presenting a real project done at the Swiss Federal Statistical Office. We also show that the concepts of goals, strategies and needs correspond to interpretations of the stakeholders of the enterprise model.
TL;DR: A performance measurement system is a decision support system that through a set of indicators allows an analysis of the current state of an enterprise and comparison with the strategic objectives and is a fundamental tool for management control in business.
Abstract: A performance measurement system is a decision support system that through a set of indicators allows an analysis of the current state of an enterprise and comparison with the strategic objectives It is therefore a fundamental tool for management control in business
TL;DR: A model-driven approach to target this problem is presented and several configuration patterns that describe generic patterns of configuration alternatives are proposed, in order to understand what situations can occur during business process configuration.
Abstract: The configuration of comprehensive enterprise systems to meet the specific requirements of an organisation up to today is consuming significant resources. The results of failing or delayed enterprise system implementation projects are severe and may even threaten the organisation’s existence. One of the main drivers for implementing comprehensive enterprise systems is to streamline business processes. However, an intuitive conceptual support for business process configuration is insufficiently addressed by enterprise system vendors and inadequately researched in academia. This paper presents a model-driven approach to target this problem and proposes several configuration patterns that describe generic patterns of configuration alternatives, in order to understand what situations can occur during business process configuration. Based on these configuration patterns, a configuration notation is introduced that allows for visually highlighting configuration alternatives. Finally, we will sketch how configurable Event Driven Process Chains and the configuration of business processes can be supported using relational databases.
TL;DR: This research has uncovered an alternative process‐driven and document‐based approach that may offer a simpler and more flexible solution compared with technology‐driven ERP.
Abstract: Purpose – Enterprise resource planning (ERP), a technological approach for enterprise information systems, has many recorded case examples of lengthy and expensive implementations reported in literature This research has uncovered an alternative process‐driven and document‐based approach that may offer a simpler and more flexible solution compared with technology‐driven ERP This paper investigates the differences and similarities of the two approaches, and also answers a related question: Is the enterprise system implementation an information systems effort performed to support the business processes, or is it a process re‐engineering effort required to implement the pre‐packaged software system?Design/methodology/approach – To investigate the advantages and disadvantages of the two approaches to an enterprise information system, this research developed a unified modeling language (UML) process model of a manufactured housing company and used it as a basis for a conceptual level UML model for both an ER
Patent•
29 Apr 2005
TL;DR: In this paper, an enhanced enterprise system integrates enterprise application functionality and collaboration functionality of a conventional collaboration system to provide a centralized project or team space for managing and capturing the collaborative activity inherent in the enterprise application processes.
Abstract: An enhanced enterprise system integrates enterprise application functionality of a conventional enterprise system and collaboration functionality of a conventional collaboration system to provide a centralized project or team space for managing and capturing the collaborative activity that is inherent in the enterprise application processes. For example, the enhanced enterprise system allows a user to access an enterprise application object and to create a shared team space for the enterprise application object. This causes the enhanced enterprise system to provision a collaborative site or team space within the integrated collaboration system, and associate the team space to the enterprise application object through which the team space was provisioned.
Patent•
31 Oct 2005TL;DR: In this paper, a system for analyzing an enterprise environment comprises a modeling module that determines possible accesses to enterprise network services from a plurality of entities; and a validation module that determine whether a possible access to an enterprise service by a particular entity violates an enterprise policy, the enterprise policy governing which entities are authorized to access one or more enterprise services.
Abstract: Embodiments of the present disclosure provide systems and methods for analyzing an enterprise environment. Briefly described, one embodiment of the system for analyzing an enterprise environment comprises a modeling module that determines possible accesses to enterprise network services from a plurality of entities; and a validation module that determines whether a possible access to an enterprise service by a particular entity violates an enterprise policy, the enterprise policy governing which entities are authorized to access one or more enterprise services.
04 Nov 2005
TL;DR: There are identified and established different types of alignment relationships between the artifacts composing an Enterprise Architecture.
Abstract: This article states the importance of Enterprise Architectures as a way to identify interoperability problems. Enterprise Architectures provide a common view of the primary resources of any enterprise (people, processes and technology) and how they integrate to provide the primary drivers of the enterprise. The authors of this work sketch an example where different kinds of integration problems are detected. Tracing enterprise information is mandatory to manage enterprises. Therefore, in this work there are identified and established different types of alignment relationships between the artifacts composing an Enterprise Architecture.
03 Jan 2005
TL;DR: A modeling language for building hierarchical object-oriented representations of the enterprises and an example of an enterprise model developed with the authors' web-based CAD tool is presented.
Abstract: In enterprise architecture, the goal is to integrate business resources and IT resources in order to improve an enterprise's competitiveness. In an enterprise architecture project, the development team usually constructs a model that represents the enterprise: the enterprise model. In this paper, we present a modeling language for building such enterprise models. Our enterprise models are hierarchical object-oriented representations of the enterprises. This paper presents the foundations of our language (i.e. the Living System Theory and the RM-ODP standard), the definition of the language and ends by presenting an example of an enterprise model developed with our web-based CAD tool.
Proceedings Article•
01 May 2005
TL;DR: It is found that both the individual and organisational benefits that enterprise portals can offer appear to have been recognised, and coherent sets of services addressing each of these perspectives are being developed.
Abstract: Enterprise portals are being viewed as the next generation application platform of choice, offering benefits over both client/server and thin client arrangements. By providing a mediating layer between the information applications and resources of the organisation and the individuals using them, enterprise portals appear to provide a unique context to allow both the organisational and individual perspectives of information systems to be addressed. This study seeks to examine these often competing perspectives of information systems by using an exploratory empirical survey to investigate the actual deployment of enterprise portals within a range of different organisations. It is found that both the individual and organisational benefits that enterprise portals can offer appear to have been recognised, and coherent sets of services addressing each of these perspectives are being developed. Consistent with diffusion and acceptance of technology models, organisations appear to be commencing their portal developments with services that will ensure utilisation by individuals, and are subsequently seeking to realise organisational level benefits.
TL;DR: The resulting framework for Enterprise modelling and Knowledge-based IS engineering - Enterprise meta-model (EMM) - is developed and presented in this paper.
Abstract: The paper deals with Knowledge-based Information Systems (IS) engineering. The Enterprise management functions, processes and their interactions are considered as the major components of the domain knowledge. This is the peculiarity of this approach to Enterprise modelling for IS engineering. The resulting framework for Enterprise modelling and Knowledge-based IS engineering - Enterprise meta-model (EMM) - is developed and presented in this paper. The architecture of the advanced CASE system is also discussed in this paper.
01 Jan 2005
TL;DR: The main reason for poor resource utilization is that today's value-added chains are geared toward product and unit quantities as discussed by the authors, which can only be achieved with a considerable trade-off in resource utilization.
Abstract: The dynamics of market demands require manufacturers to be flexible. Currently, however, more flexibility can only be achieved with a considerable trade-off in resource utilization. Under-utilization of resources in many companies presently lies at between 20–50%, resulting in massive cost disadvantages. This particularly applies to the field of machine and plant engineering. The main reason for poor resource utilization is that today’s value-added chains are geared toward product and unit quantities. To a large extent, flexibility and efficiency have only been optimized at the level of the individual enterprise. In part, this is due to product complexity and the shortening of delivery times in recent years by almost 50% (Eggers/Kinkel 2002). Since the potential within companies for rationalization and flexibility has largely been exhausted, the most promising avenue for responding to the need for further dynamics in the creation of value today is considered to be the reorganization of the entire value-added chain across company boundaries. At the center of attention is production that takes place in dynamic, quickly adaptable networks. Complementary and partially overlapping production competencies in a value-added network permit the metamorphosis from rigid value-added chains to highly dynamic networks (Zahn/Foschiani 2002). Interaction within dynamic production networks
01 Jan 2005
TL;DR: This chapter presents a discussion on the VEI issue as a contribution to a better understanding of theVEI phenomenon, and it could be seen as a contributions to an eventual framework for VEi science, engineering, development, and implementation.
Abstract: Virtual enterprise integration (VEI) is virtually the most critical success factor for making virtual enterprise (VE) a real, competitive, and widely implemented organizational and management concept. However, according to many authors, the present solutions for VEI are either insufficient or inexistent. One of the reasons for the situation is the failure of the approach of “traditional” information systems and organizations to dealing with the nowadays turbulent market and organizations’ requirements, where actual VEI solutions are mainly sought. This chapter presents a discussion on the VEI issue as a contribution to a better understanding of the VEI phenomenon, and it could be seen as a contribution to an eventual framework for VEI science, engineering, development, and implementation. Also, two metatheoretical structures for VEI research and development are proposed: VEI abstractions hierarchy and VEI semiotics. IDEA GROUP PUBLISHING This chapter appears in the book, Virtual Enterprise Integration: Technological and Organizational Perspectives edited by Goran Putnik and Maria Manuela Cunha. © 2005, Idea Group Inc. 701 E. Chocolate Avenue, Suite 200, Hershey PA 17033-1240, USA Tel: 717/533-8845; Fax 717/533-8661; URL-http://www.idea-group.com ITB10931