scispace - formally typeset
Search or ask a question

Showing papers on "Enterprise systems engineering published in 2003"


Journal Article
TL;DR: Based on ERP research, five factors for successful implementation are identified and it is found that a projects position on the maturity curve can influence the implementation route.
Abstract: Highly complex enterprise software packages have become a standard way of competing in many industries. By the late 1990s, enterprise resource planning (ERP) systems had enabled Fortune 500 firms to present one face to their customers via integrated cross-functional business processes, centralized databases, and point-and-click access to real-time operational data across the business. Today, enterprise systems for supply chain management (SCM) and customer relationship management (CRM) are following in the steps of ERP, and, in many cases, providing a foundation for e-business. Supplier relationship management systems are on the horizon. Based on our ERP research, we have identified five factors for successful implementation: (1) top management is engaged in the project, not just involved; (2) project leaders are veterans, and team members are decision makers; (3) third parties fill gaps in expertise and transfer their knowledge; (4) change management goes hand-in-hand with project planning; (5) A satisficing mindset prevails. Furthermore, we found that a projects position on the maturity curve (early adopter, early majority, or late majority) can influence the implementation route. These five success factors and three maturity curve positions are illustrated in three anonymous cases. The result is lessons for managing the complexities of the next wave of enterprise systems.

256 citations


Journal ArticleDOI
TL;DR: The empirical findings indicate that the extent of BPR, competitive strategy, adequacy of end-user training, role of steering committee, package functionality, integration of IT, and manufacturing decisions related to technology, workforce, quality, production planning and organization are important determinants of managements perceptions of system value.

193 citations


Journal ArticleDOI
TL;DR: The paper is a summary of the main work carried out in Europe to elaborate interoperability development roadmaps and to prepare forthcoming R&D projects under the Six Framework Programme (FP6).

187 citations


Journal ArticleDOI
TL;DR: This paper emphasises that a Holonic Manufacturing Execution System Engineering ( HMESE) approach should be a relevant B2M SE approach along with other relevant scientific, industrial and educational areas dealing with information and intelligence control and management issues in agile automation.

153 citations


Patent
03 Oct 2003
TL;DR: In this article, a multiple level business model is used to define business processes and control, regulate, or synchronize those processes, where actual processes are generally executed at lower levels, while control of the processes is carried out one level higher.
Abstract: Methods and systems of controlling an enterprise and for providing a control architecture. In some embodiments, a multiple level business model is used to define business processes, and control, regulate, or synchronize those processes. Actual processes are generally executed at lower levels, while control of the processes is carried out one level higher. At an echelon two levels higher, coordination of the processes based on objectives and available shared assets is carried out. A fourth level may be used to provide planning and development, and a fifth level may be used to set the objectives of an enterprise or enterprise unit. Implementation of this model provides control and monitoring of value production, performance measurement, and timely exchange of information and instructions.

116 citations


Book ChapterDOI
13 Oct 2003
TL;DR: In this article, an enterprise privacy policy often reflects different legal regulations, promises made to customers, as well as more restrictive internal practices of the enterprise, and it may allow customer preferences Hence it may be authored, maintained, and audited in a distributed fashion.
Abstract: Enterprise privacy enforcement allows enterprises to internally enforce a privacy policy that the enterprise has decided to comply to An enterprise privacy policy often reflects different legal regulations, promises made to customers, as well as more restrictive internal practices of the enterprise Further, it may allow customer preferences Hence it may be authored, maintained, and audited in a distributed fashion

97 citations


Journal ArticleDOI
01 May 2003
TL;DR: A discussion of the scope of systems engineering, which seems to cover everything and therefore, in a way, to cover nothing.
Abstract: A discussion of the scope of systems engineering, which seems to cover everything and therefore, in a way, to cover nothing. Systems engineering crosses the boundaries of other disciplines. It is the exploration, understanding, and design of how everything fits together.

87 citations


Patent
13 Jun 2003
TL;DR: A context aware enterprise system includes a network, an enterprise service coupled to the network, and a plurality of information sources that include enterprise information related to one or more activities of the enterprise system as mentioned in this paper.
Abstract: A context aware enterprise system includes a network, an enterprise service coupled to the network, and a plurality of information sources that include enterprise information related to one or more activities of the enterprise system. The enterprise system also includes a plurality of clients with user interfaces by which a user may access the enterprise service over the network. A context determination service determines context information describing a multi-dimensional context based on the enterprise information. The context information determined by the context determination service includes a user identification, an identification of a client selected by the user, a user role, a user expertise related to the enterprise service, and a user expertise related to the selected client. Based on the context information, an interface adaptation service adapts the user interface of the client.

84 citations


Journal ArticleDOI
TL;DR: This paper details the management of Texas Instruments' multi-stakeholder ERP system from a process-oriented perspective and the lessons learned help to support and further the academic and practitioner literature especially in the area of large-scale information systems management.

83 citations


Patent
30 Sep 2003
TL;DR: In this paper, an enterprise business planning system includes an application server to execute an enterprise planning session for a set of enterprise contributors in accordance with an enterprise model, which defines hierarchically arranged nodes, and associates the enterprise contributors with the nodes.
Abstract: An enterprise business planning system includes an application server to execute an enterprise planning session for a set of enterprise contributors in accordance with an enterprise model. The enterprise model defines hierarchically arranged nodes, and associates the enterprise contributors with the nodes. The system further comprises an administration console that supports node-level modification of the enterprise planning model without preventing execution of the enterprise planning session by the application server.

79 citations


Journal Article
TL;DR: In this book, the editors have assembled some of the world’s best research on ERP systems, with a view to providing a foundation for second wave improvements to enterprise systems.
Abstract: The focus of this book is on the most important class of enterprise system, namely Enterprise Resource Planning (ERP) systems. Organisations typically take the decision to employ ERP systems in an attempt to streamline existing processes. Once these systems are in place, however, their success depends on the effectiveness of the implementation, and on the additional benefits that can be obtained by further leveraging the technology. In this book, the editors have assembled some of the world's best research on ERP systems, with a view to providing a foundation for second wave improvements to enterprise systems. Written primarily for managers and consultants, this book is also an ideal reference for business schools and researchers.

Journal ArticleDOI
TL;DR: This paper aims to provide a basic background to conceptual ideas of enterprise mobility, and a framework for understanding the development of enterprise Mobility in organisations.
Abstract: Although the literature on wireless applications has predominantly focused on business-to-consumer markets, following the patterns in the media and e-commerce research, it is now becoming clear that mobile networking will provide a tremendous impetus to the development of other strategic applications for businesses. This paper explores this emerging area of wireless applications in the business, focusing specifically on enterprise mobility. It aims to provide a basic background to conceptual ideas of enterprise mobility, and a framework for understanding the development of enterprise mobility in organisations. Moreover, the paper also begins to apply these conceptual ideas in a number of original case studies. The paper rounds off with a summary and some conclusions regarding the future of enterprise mobility.

Patent
19 Sep 2003
TL;DR: In this paper, the administrator console adjusts the deployment map based on approaching deadlines for the enterprise planning activities to meet the current needs within the organizational hierarchy, by breaking the task associated with an enterprise planning activity into a number of jobs.
Abstract: An enterprise planning system includes a plurality of application servers, and an administration console to generate a deployment map that associates each of a set of enterprise planning models with a respective set of the application servers. The administration console, either automatically or in response to input from a system administrator, may finely control the allocation of computing resources to enterprise planning. The administrator console may adjust the deployment map based on approaching deadlines for the enterprise planning activities. When administrating a task associated with an enterprise planning activity, the administration console may break the task into a number of jobs, each job associated with a different slice of the model in accordance with the organizational hierarchy defined by the model. Consequently, allocation of computing resources to enterprise planning may be finely controlled, and may be adjusted to meet the current needs within the organizational hierarchy.

Patent
09 Jun 2003
TL;DR: In this article, the authors present a technique for the development of a software-based business solution using a blueprint, which is a collection of artifacts that relate to an enterprise, and to the processes that an enterprise may perform.
Abstract: The present invention provides a technique for the development of a software-based business solution using blueprint. A blueprint is a collection of artifacts that relate to an enterprise, and to the processes that an enterprise may perform. The blueprint may contain artifacts describing general business goals for a particular type of enterprise (e.g., a transportation company), as well as descriptions of processes typically performed by such an enterprise. The blueprint may be customized to fit a particular enterprise, and may be used as a basis to select and/or create software component, combine components into software applications, and deploy the applications on an infrastructure.

Journal ArticleDOI
Peter Bernus1
TL;DR: A pragmatic definition of model completeness is given, based on situated interpretation of meaning and theory of communication, and new requirements for Enterprise Modelling Tools are also discussed.

Journal ArticleDOI
TL;DR: The modifications applied to ARDIN (Spanish acronyrn of Reference Architecture for INtegrated Development) are shown to help in the design and management of an efficient and flexible virtual enterprise.

Journal ArticleDOI
TL;DR: In this article, a study of social enterprise providing work integration in 12 European countries is presented, specifically concerned with the different types of social enterprises for integration (SEI), also known as work integration social enterprise (WISE).
Abstract: This paper covers the findings of a study of social enterprise providing work integration in 12 European countries. It is specifically concerned with the different types of social enterprise for integration (SEI), also known as work integration social enterprise (WISE). The study has identified and described their main characteristics as social enterprises, the type of work integration they provide, their numbers, and how they have developed and are supported. One outcome of the project is the development of a database on WISE in Europe, accessible on internet.

Patent
09 Apr 2003
TL;DR: Application view control as discussed by the authors allows users of a software tool to interact with enterprise applications using simple Java APIs, which can allow a user who is not an expert in the use of a given Enterprise system to utilize its capabilities in a manner a Java programmer can understand.
Abstract: An application view control can allow users of a software tool to interact with Enterprise applications using simple Java APIs. This can allow a user who is not an expert in the use of a given Enterprise system to utilize its capabilities in a manner a Java programmer can understand. A developer can invoke application view services both synchronously and asynchronously, and can subscribe to application view events. The developer can use simple Java objects in both the service and event cases. The developer need not understand XML, or the particular protocol or client API for the Enterprise application, such as an Enterprise Information System (EIS).

Journal ArticleDOI
01 Jan 2003
TL;DR: In this article, the authors explored the process of rigorously setting supersystem targets in an enterprise context as a model-based approach termed "analytical target setting" and demonstrated the effectiveness of linking analytical target setting and target cascading in a hybrid electric automotive truck vehicle example.
Abstract: In this article the process of rigorously setting supersystem targets in an enterprise context is explored as a model-based approach termed “analytical target setting.” Engineering design decisions have more value and lasting impact if they are made in the context of the enterprise that produces the designed product. Setting targets that the designer must meet is often done at a high level within the enterprise, however, with inadequate consideration of the engineering design embodiment and associated cost. For complex artifacts produced by compartmentalized hierarchical enterprises, the challenge of linking the target setting rationale with the product instantiation is particularly demanding. The previously developed analytical target cascading process addresses the problem of translating top level design targets into design targets for all systems in a multilevel hierarchically structured product, so that local targets are consistent with each other and top targets can be met as closely as possible. The effectiveness of linking analytical target setting and target cascading is demonstrated in a hybrid electric automotive truck vehicle example. The manufacturer introduces a new product (hybrid electric truck) in the market under uncertainty in fuel prices during the life cycle of the vehicle. The example demonstrates a clear interaction between the enterprise decision making and the engineering product development. DOI: 10.1115/1.2125972

Patent
09 Dec 2003
TL;DR: In this article, the authors present a technique for the development of a software-based business solution using a blueprint, a collection of artifacts that relate to an enterprise, and to the processes that an enterprise may perform.
Abstract: The present invention provides a technique for the development of a software-based business solution using blueprint. A blueprint is a collection of artifacts that relate to an enterprise, and to the processes that an enterprise may perform. The blueprint may contain artifacts describing general business goals for a particular type of enterprise (e.g., a transportation company), as well as descriptions of processes typically performed by such an enterprise. The descriptions may provide sufficient detail to enable traceability between elements of the blueprint in the event of changes. The blueprint may be customized to fit a particular enterprise, and may be used as a basis to select and/or create software component, combine components into software applications, and deploy the applications on an infrastructure.

Proceedings ArticleDOI
01 Dec 2003
TL;DR: In this article, the authors focus on production decisions, where discrete-event simulation models perform that evaluation, and propose integrating these discrete event models with system dynamic models and show the potential benefits of such an integration using an example of semiconductor enterprise.
Abstract: Manufacturing enterprise decisions can be classified into four groups: business decisions, design decisions, engineering decisions, and production decisions. Numerous physical and software simulation techniques have been used to evaluate specific decisions by predicting their impact on the system as measured by one or more performance measures. We focus on production decisions, where discrete-event simulation models perform that evaluation. We argue that such an evaluation is limited in time and scope, and does not capture the potential impact of these decisions on the whole enterprise. We propose integrating these discrete-event models with system dynamic models and we show the potential benefits of such an integration using an example of semiconductor enterprise.

Journal ArticleDOI
TL;DR: A fuzzy multi-criteria decision support procedure for enhancing information delivery within extended enterprise networks complemented with a case study in mold and die industry is introduced.

Journal ArticleDOI
TL;DR: The discussion principally centres on the fundamental concepts of self-organisation that underpins the emerging concepts of holonic, bionic and fractal manufacturing to name a few.

Book ChapterDOI
01 Sep 2003
TL;DR: In this article, the authors present a comprehensive framework of benefits that organizations may be able to achieve from their use of enterprise systems, which is based on business benefits only, not on costs.
Abstract: Introduction According to AMR Research, total revenue in the enterprise application and services market in 1999 was US$18.3bn. (Gilbert, 2000). Enterprise application software implementation costs are often reported to be five to ten times the cost of software licenses (Davenport, 2000). If so, organizations worldwide spent something like US$90–180bn. on enterprise systems in 1999. Most organizations that have implemented enterprise systems expect to continue using them for many years. Enterprise systems are integrated, enterprise-wide, packaged software applications that impound deep knowledge of business practices accumulated from vendor implementations in many organizations. Today, enterprise systems are evolving to incorporate new technologies, such as e-commerce and the internet, data warehousing, and customer relationship management. Enterprise software is a semi-finished product with tables and parameters that user organizations and their implementation partners configure to their business needs. Implementation of enterprise systems therefore involves both business and IT managers who work together to define new operational and managerial processes. The question we ask in this chapter is as follows: If organizations around the world spent US$100bn. or more on enterprise systems in 1999, what sorts of benefits did they, or can they , achieve? To answer this question, we present a comprehensive framework of benefits that organizations may be able to achieve from their use of enterprise systems. Our focus is on business benefits only, not on costs. Our framework establishes a base for managing the implementation and operation of enterprise systems.

Dissertation
01 Jan 2003
TL;DR: This thesis provides insights into the nature of Enterprise Systems by developing an integrated framework addressing the implications of Enterprise System artifacts for information systems development and evaluation.
Abstract: Enterprise Systems are one of the most important developments in corporate information systems during the last decade. These integrated information systems are characterized by a number of features which include a very broad scope and functionality, as well as being generic, master data, and business-process orientated. Together, these features make Enterprise Systems unique vis-a-vis other information systems and have a profound impact on information systems development and evaluation. For instance, analysis, design, and realization during traditional information system development is replaced by the selection of a system and the evaluation of an underlying reference model, as well as the setting of configuration parameters. The focus of the study is the Enterprise Systems artifact and its impact on information systems development and evaluation. The aims are 1) to improve our understanding of the key characteristics of Enterprise System artifacts, leading to changes in information systems development and the increased importance of evaluation and 2) to develop methods and evaluation approaches for Enterprise Systems. The main research approach applied in gaining an increased understanding has been artifact evaluation, belonging to constructive research. The research reported upon in the thesis is presented in two parts. The first part synthesizes the text of part one with the seven included papers. The included papers address Enterprise Systems, information system development and evaluation in complementary ways leading up to the conclusion of part one. The concluding output of the thesis is an integrated framework addressing the implications of Enterprise System artifacts for information systems development and evaluation. The framework includes several causally-related components, including the Enterprise System artifact and its key characteristics, an Enterprise System life cycle (including the four interrelated tasks of selection, configuration, implementation and use & operation), COTS implementation methods, and the changing purpose of evaluation. In a sense, the conclusion is a theorizing of the nature of Enterprise System artifacts. Despite the fact that this thesis provides insights into the nature of Enterprise Systems, it is evident that more research is needed.

Book
03 Feb 2003
TL;DR: In this paper, the authors present a prescient, authoritative reference for anyone concerned with harvesting, creating, distributing, or analyzing company information, including roles and responsibilities that will ensure long-term efficacy and relevance.
Abstract: Far beyond simple data archives and streamlined access, enterprise knowledge portals represent the future of corporate information management. Seamlessly interweaving three essential principles -- people, content, and technology -- an effective portal is the ultimate roadmap to every conceivable permutation of the components in a business's landscape. This prescient, authoritative book is a vital reference for anyone concerned with harvesting, creating, distributing, or analyzing company information. HR executives and IT professionals will learn not only how to create the atlas to their company's universe but also how to define and assign the roles and responsibilities that will ensure long-term efficacy and relevance. Companies will have the ability to: * Build technology around knowledge requirements, not the other way around * Customize desktop access around individual requirements and workstyles * Make better decisions as a result of quick access to crucial information * Maximize speed, efficiency, accuracy, and flexibility of knowledge transfer.

Journal ArticleDOI
TL;DR: The issues of creating and managing intangible assets in virtual enterprise are examined, and the applicability and adaptability of various tools and methodologies studied and developed in the industry projects to enable seamless operation of the virtual enterprise during these global projects are discussed.

Journal ArticleDOI
TL;DR: An integrated methodology for planning and implementation of best manufacturing practice has been developed and is being carried out in order to create reference models, methodologies and tools for the implementation of the concept of extended enterprise in Mexican SMEs.


Journal ArticleDOI
TL;DR: Four generic elements of a virtual enterprise total business system are discussed: the physical, information, decision and knowledge components, and tools that provide a framework for consistently reaching a common understanding of a particular business process that is part of the total system.