Selling packaged software: an ethical analysis

Within the IS literature there is little discussion on selling software products in general and especially from the ethical point of view. Similarly, within computer ethics, although there is much interest in professionalism and professional codes, in terms of accountability and responsibility, the spotlight tends to play on safety-critical or life-critical systems, rather than on software oriented towards the more mundane aspects of work organisation and society. With this research gap in mind, we offer a preliminary ethical investigation of packaged software selling. Through an analysis of the features of competition in the market, the global nature of the packaged software market and the nature of product development we conclude that professionalism, as usually conceived in computer ethics, does not apply particularly well to software vendors. Thus, we call for a broader definition of professionalism to include software vendors, not just software developers. Moreover, we acknowledge that with intermediaries, such as implementation consultants, involved in software selling, and the packaged software industry more generally, there are even more “hands” involved. Therefore, we contend that this is an area worthy of further study, which is likely to yield more on the question of accountability

An Empirical Study of Operational Performance Parity Following Enterprise System Deployment

This paper presents an empirical investigation into whether the implementation of packaged Enterprise Systems (ES) leads to parity in operational performance. Performance change and parity in operational performance are investigated in three geographically defined operating regions of a single firm. Order lead time, the elapsed time between receipt of an order and shipment to a customer, is used as a measure of operational performance. A single ES installation was deployed across all regions of the subject firm\u27s operations.Findings illustrate parity as an immediate consequence of ES deployment. However, differences in rates of performance improvement following deployment eventually result in significant (albeit smaller than pre-deployment) performance differences. An additional consequence of deployment seems to be an increased synchronization of performance across the formerly independent regions

ERP PACKAGE EVALUATION, THE CASE OF SMEs KAVALA’s REGION

In this paper we want to examine how enterprise resource planning (ERP) systemseffects on small and medium-sized enterprises (SMEs) Kavala’s region. We consider several SMEsof our region, we use data from each SME and we form a questionnaire to secure more data fromthe enterprises. We weight up the factors that affect the choice of ERP. Also, we relate these factorswith basic characteristics of the specific SMEs of our region. Flexibility and functionality are themost important criteria of choosing an ERP system. Surprisingly, the cost is one of the lessimportant criteria. Also, minor effects have criteria such as brand, name and position of the vendor.Finally, we indicate issues for future research.ERP, SMEs, criteria evaluation

CRM packaged software: a study of organisational experiences

Customer Relationship Management (CRM) packaged software has become a key contributor to attempts at aligning business and IT strategies in recent years. Throughout the 1990s there was, in many organisations strategies, a shift from the need to manage transactions and toward relationship management. Where Enterprise Resource Planning packages dominated the management of transactions era, CRM packages lead in regard to relationships. At present, balanced views of CRM packages are scantly presented instead relying on vendor rhetoric. This paper uses case study research to analyse some of the issues associated with CRM packages. These issues include the limitations of CRM packages, the need for a relationship orientation and the problems of a dominant management perspective of CRM. It is suggested that these issues could be more readily accommodated by organisational detachment from beliefs in IT as utopia, consideration of prior IS theory and practice and a more informed approach to CRM package selection

Enterprise Systems Analysis and Modelling

In ES implementations, process modelling is a critical and often overlooked activity. This paper proposes a framework for process modelling of ES. The four steps method involves: Current Situation Analysis, Business Process Improvements and Requirements, Gap Analysis, and To-be process to develop. Outputs of the methodology are an interdependent set of organizational and system proposed changes, and feedback loops to the ES vendors and to the strategy of the firm. In-depth case studies and extensive literature review provides methodological support. For practitioners, this study provides useful insights into one of the reasons by which companies could be frustrated with ES implementation.E-business, ERP

Acceptance model of electronic medical record

This paper discusses acceptance issues of Electronic Medical Record System (EMR), particularly in Malaysia. A detailed overview of EMR and its benefits are firstly discussed. A number of acceptance models are scrutinized. Then factors affecting EMR acceptance are put forward. Finally, before proposing an EMR acceptance model, an instrument formed by adapting and then finding its factors loading is presented