Showing papers on "Enterprise software published in 2005"
TL;DR: Most IT experts agree that software failures occur far more often than they should despite the fact that, for the most part, they are predictable and avoidable as mentioned in this paper. But most organizations don't see preventing failure as an urgent matter, even though that view risks harming the organization and maybe even destroying it.
Abstract: Most IT experts agree that software failures occur far more often than they should despite the fact that, for the most part, they are predictable and avoidable. It is unfortunate that most organizations don't see preventing failure as an urgent matter, even though that view risks harming the organization and maybe even destroying it. Because software failure has tremendous implications for business and society, it is important to understand why this attitude persists.
440 citations
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
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: Uncertainty avoidance cultural control and intrinsic motivation as self-control are the important antecedents of ERP systems adoption and the result helps the systems manager understand that informal controls should be applied to the ERP system implementation to enhance tacit and social aspects of IS management.
Abstract: Enterprise systems are gaining interest from both practitioners and researchers because of their potential linkages to organizational and individual user's productivity. Information systems (IS) researchers have been investigating the implementation and adoption issues of enterprise systems based on the organizational IS management perspectives. However, there are few papers that investigate enterprise systems management and implementation issues based on the informal control mechanisms, although the enterprise systems are control tools in the organization. Specifically, this paper applies Enterprise Resource Planning (ERP) adoption and implementation to the informal controls, such as cultural control and self-control, which can be viewed as a tacit perspective in knowledge management. Uncertainty avoidance and perceived enjoyment are used as informal controls in the ERP implementation in this paper, and are linked to the technology acceptance variables to investigate the relationships among them. Sociotechnical design, organizational control mechanism, knowledge management, and individual motivation are reviewed to support this potential linkage in the model. Field data via the online survey of ERP systems user group (n= 101) are analyzed with partial least squares and supported our hypotheses. Uncertainty avoidance cultural control and intrinsic motivation as self-control are the important antecedents of ERP systems adoption. Furthermore, the result helps the systems manager understand that informal controls should be applied to the ERP systems implementation to enhance tacit and social aspects of IS management.
265 citations
TL;DR: The results of a detailed numerical and sensitivity analysis based on previously published models for supply chain cooperation and joint optimal ordering and shipment policies for the buyer and supplier can be used in enterprise software to measure the potential monetary value of policy coordination and minimize the total supply chain system cost.
246 citations
01 Nov 2005
TL;DR: This new taxonomy is made up of two distinct kinds of sets, which the authors're stealing from biology: a phylum (a type of coding error, such as illegal pointer value) and a kingdom (a collection of phyla that shares a common theme,such as input validation and representation).
Abstract: Taxonomies can help software developers and security practitioners understand the common coding mistakes that affect security. The goal is to help developers avoid making these mistakes and more readily identify security problems whenever possible. Because developers today are by and large unaware of the security problems they can (unknowingly) introduce into code, a taxonomy of coding errors should provide a real tangible benefit to the software security community. Although the taxonomy proposed here is incomplete and imperfect, it provides an important first step. It focuses on collecting common errors and explaining them in a way that makes sense to programmers. This new taxonomy is made up of two distinct kinds of sets, which we're stealing from biology: a phylum (a type of coding error, such as illegal pointer value) and a kingdom (a collection of phyla that shares a common theme, such as input validation and representation). Both kingdoms and phyla naturally emerge from a soup of coding rules relevant to enterprise software, and it's for this reason that this taxonomy is likely to be incomplete and might lack certain coding errors. In some cases, it's easier and more effective to talk about a category of errors than to talk about any particular attack. Although categories are certainly related to attacks, they aren't the same as attack patterns.
215 citations
01 Dec 2005
TL;DR: A concise reference to the state of the art in software interoperability, Interoperability of Enterprise Software and Applications will be of great value to engineers and computer scientists working in manufacturing and other process industries and to software engineers and electronic and manufacturing engineers working in the academic environment.
Abstract: Interoperability: the ability of a system or a product to work with other systems or products without special effort from the user is a key issue in manufacturing and industrial enterprise generally. It is fundamental to the production of goods and services quickly and at low cost at the same time as maintaining levels of quality and customisation. While data exchange and IT applications are vital contributions to successful interoperability, communications and common semantics can be just as important between businesses. Composed of more than 40 papers of international authorship, Interoperability of Enterprise Software and Applications ranges from academic research through case studies to industrial experience of interoperability. Many of the papers have examples and illustrations calculated to deepen understanding and generate new ideas. The INTEROP-ESA’05 conference from which this book is drawn was sponsored by the European Union and the Swiss federal government under the IST research program and was further supported by International Society for Information Processing and the Association for Computing Machinery. A concise reference to the state of the art in software interoperability, Interoperability of Enterprise Software and Applications will be of great value to engineers and computer scientists working in manufacturing and other process industries and to software engineers and electronic and manufacturing engineers working in the academic environment.
132 citations
03 Jan 2005
TL;DR: Comparing the concept of ECM with related research on information resource management, electronic document management, and knowledge management, it is argued that ECM represents a modern, integrated perspective on information management.
Abstract: Enterprise Content Management (ECM) is an emerging concept involving numerous software vendors, consultants, and information management practitioners around increasing market potential. However, there exist yet few academic reports on ECM from the viewpoint of organizational system implementations. This article analyses 58, mainly practitioner-oriented, case narratives of ECM projects and implementations to identify a framework of major issues that require managerial attention in organizations. The main areas covered by the framework are: objectives/impacts sought with ECM, enterprise model to be supported by ECM, content model, technological infrastructure, administrative resources and practices, and change management issues. The issues identified in this framework serve information management practitioners to facilitate ECM development from the viewpoint of the enterprise. Comparing the concept of ECM with related research on information resource management, electronic document management, and knowledge management, we argue that ECM represents a modern, integrated perspective on information management.
129 citations
TL;DR: In this article, the authors describe a framework for measuring costs and performance in new forms of business organization that are evolving to meet the competitive challenges of the 21st century, which is based on a literature review on cost management and performance measures.
126 citations
13 Mar 2005
TL;DR: It is shown how the alignment between Business and IT can be disaggregated into four different dimensions and some heuristics to ensure such alignment are presented.
Abstract: Organizations have existing systems infrastructure that are the result of decades of one-by-one implementations of specific solutions. As organizations, products, customers and technologies continue to change at an increasingly rapid rate, managers have sought overviews that will allow them to understand how Business and IT within their organization fits together. Enterprise Architecture is a representation of the organization to enable the planning of the organization changes. It includes the current and future business objectives, goals, visions, strategies, informational entities, business processes, people, organization structures, application systems, technological infrastructures, and so on.In this paper, we show how the alignment between Business and IT can be disaggregated into four different dimensions and we present some heuristics to ensure such alignment.
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 , مرکز فناوری اطلاعات و اطلاع رسانی کشاورزی
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.
TL;DR: How systems-thinking could provide a framework to identify events that should be considered during risk assessment by creating a map of the organization's value chain that specifies relationships among the atomic components of the business model and using a taxonomy of categories to analyze those relationships and identifies events that could threaten business process performance is described.
Proceedings Article•
01 Jan 2005TL;DR: This study categorizes and describes the usability issues encountered by one division of a Fortune 500 company in the first years of its large-scale ERP implementation and demonstrates the promise of using collaboration theory to evaluate usability characteristics of existing systems and to design new systems.
Abstract: Enterprise Resource Planning (ERP) systems hold great promise for integrating business processes and have proven their worth in a variety of organizations. Yet the gains that they have enabled in terms of increased productivity and cost savings are often achieved in the face of daunting usability problems. While one frequently hears anecdotes about the difficulties involved in using ERP systems, there is little documentation of the types of problems typically faced by users. The purpose of this study is to begin addressing this gap by categorizing and describing the usability issues encountered by one division of a Fortune 500 company in the first years of its large-scale ERP implementation. This study also demonstrates the promise of using collaboration theory to evaluate usability characteristics of existing systems and to design new systems. Given the impressive results already achieved by some corporations with these systems, imagine how much more would be possible if understanding how to use them weren’t such an
TL;DR: The enterprise model is described and a description of the policy instruments that the government, as owner, has for exercising power and control vis-à-vis the health enterprises are given.
Abstract: This essay focuses on the balance between governmental control and enterprise autonomy by examining the Norwegian hospital reform. We describe the enterprise model and give a description of the policy instruments that the govern- ment, as owner, has for exercising power and control vis-a-vis the health enterprises. How the trade-off between autonomy and control is experienced and practiced is analyzed from an instrumental, an institutional, and an environmental perspective. The database comprises a survey collected from health enterprise executives and illustrative cases. The trade-off can be characterized as ambiguous and unstable and we ask whether it is possible to achieve a strategy to more appropriately balance the goals of control and autonomy.
TL;DR: Looking at the history of enterprise computing, the author illustrates why this new wave in computing models represents a natural evolution in technology and helps the reader better evaluate the trade-offs between licensed and hosted software.
Abstract: This paper introduces readers to the concept of software as a service (SaaS) and helps them evaluate a business case for where to use SaaS in the enterprise. While the underlying concept behind SaaS — renting your business application as a service — is not new, changes in technology and the software landscape now make this model a viable and smart alternative to licensed software. By looking at the history of enterprise computing, the author illustrates why this new wave in computing models represents a natural evolution in technology. More importantly, by examining the hidden costs behind licensed software or the total cost of ownership, the author helps the reader better evaluate the trade-offs between licensed and hosted software.
TL;DR: The paper concludes by pointing out the need for extended enterprise performance management to balance the developments outlined here, via two performance measurement frameworks: the structural extended enterprise balanced scorecard and the procedural framework for the selection and implementation of measures.
Abstract: This paper discusses the development of a performance measurement system specifically designed for the requirements of the extended enterprise, via two performance measurement frameworks: the structural extended enterprise balanced scorecard and the procedural framework for the selection and implementation of measures. The extended enterprise balanced scorecard offers a four-perspective framework, implemented at each node, that provides a generic structure for the management of performance measures in the extended enterprise; while the procedural framework operates at both the local and holistic levels, to provide a step-by-step generic process towards performance measure selection and implementation. When combined, the two frameworks produce the basic extended enterprise performance measurement (EEPM) system, which was subsequently tested at a first-tier supplier in the European automotive industry. The characteristics of the extended enterprise are taken as a given starting point, and the paper conclude...
Patent•
22 Apr 2005
TL;DR: In this paper, the authors present a method and system for providing services in an enterprise content management network-attached system, where the content management functions are provided as an integral part of a storage system.
Abstract: The present invention discloses a method and system for providing services in an enterprise content management network-attached system, where the enterprise content management functions are provided as an integral part of a storage system. An integrated enterprise content management network-attached system provides a single, unified approach to the entire range of enterprise content management functions from storage management to content and business process management. The result is a robust and reliable complete enterprise content management solution with a lower total cost of ownership than existing products.
TL;DR: A requirement-driven approach, which benefits from reusing the business process design without being restricted by predefined solutions and criteria is proposed, whose encouraging results demonstrate the ability of the approach to provide a satisfactory solution to the problem of aligning an ERP software package with an enterprise business model.
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: Most FIRMS of any size are in some stage of implementing enterprise resources planning systems or other similar multifunctional enterprise systems, giving consideration to the very substantial implementation costs, perhaps ten times the cost of the system itself.
Abstract: MOST FIRMS OF ANY SIGNIFIcant size are in some stage of implementing enterprise resources planning (ERP) systems or other similar multifunctional enterprise systems. Some are in the early stages of the process, giving consideration to the very substantial implementation costs, perhaps ten times the cost of the system itself. Others have successfully implemented ERP and are tying these systems in with supply-chain management (SCM) and customer relationship management (CRM) systems to have “end-to-end” integrated systems.
Proceedings Article•
01 Jan 2005
TL;DR: This work describes a framework to implement Enterprise Content Management (ECM) and helps to select content objects that can be brought under ECM to create business value and guide the IT investments needed to realize ECM.
Abstract: Today, many organizations maintain a variety of systems and databases in a complex ad-hoc architecture that does not seem to fulfill the needs for company-wide unstructured information management in business processes, business functions, and the extended enterprise. We describe a framework to implement Enterprise Content Management (ECM) in order to address this problem. ECM refers to the technologies, tools, and methods used to capture, manage, store, preserve, and deliver content (e.g. documents, graphics, drawings, web pages) across an enterprise. The framework helps to select content objects that can be brought under ECM to create business value and guide the IT investments needed to realize ECM. The framework was tested in a large high tech organization.
TL;DR: It is demonstrated how the proposed prototype MAERP system takes advantage of existing information systems among various functional areas to achieve the system integration of commercially available enterprise resource planning (ERP) systems, while avoiding numerous problems encountered during a typical ERP implementation.
03 Jan 2005
TL;DR: The findings of the study suggest that instead of considering small and medium-sized enterprises as one homogenous group, the differences between these two groups of companies should be acknowledged in the future research.
Abstract: This paper investigates the relationship of enterprise size to the constraints and objectives of Enterprise Resource Planning (ERP) systems adoption. The survey data based on the responses of 44 companies indicates that significant differences exist between small, medium-sized and large enterprises in ERP system adoption. Specifically, the findings suggest that small companies experience more knowledge constraints than their larger counterparts in ERP adoption. Further, while being the most prevalent objective for ERP adoption in all the company groups, business development through ERP adoption is considered especially important by the medium-sized and large enterprises. Finally, the findings of the study suggest that instead of considering small and medium-sized enterprises as one homogenous group, the differences between these two groups of companies should be acknowledged in the future research.
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...
TL;DR: This paper discusses how the FBI's $170 million Virtual Case File (VCF) IT project became one of the most highly publicized software failure in history.
Abstract: This paper discusses how the FBI's $170 million Virtual Case File (VCF) IT project became one of the most highly publicized software failure in history. According to a report by the US Department of Justice's inspector general, VCF's failure may be attributed to several factors including poorly defined and slowly evolving design requirements, overly ambitious schedules, and the lack of a plan to guide hardware purchases, network deployments and software development for the bureau. The paper also includes interviews with people directly involved with the VCF to gain a better picture of an enterprise IT project that fell into the most basic traps of software development, from poor planning to bad communication.
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.