Implementation Of Standard Software Research Articles

A fuzzy multi-objective multi-period network DEA model for efficiency measurement in oil refineries

We define a fuzzy multi-objective multi-period network DEA model customized to evaluate the dynamic performance of oil refineries in the presence of undesirable outputs. In particular, we use a standard fuzzy operator to define the efficiency levels so as to integrate multiple objectives and periods of time within a unique maximization framework. Managers and decision makers are provided with a model characterized by its operational simplicity that allows for the straightforward implementation of standard spreadsheet software. The model is applied to a real-life case study, where the capacity of refineries to optimize their performance through the refining process is analyzed together with the introduction of value-added products that preserve and enhance the environmental dimensions of the refining process. The inclusion of a real-life case study aims at illustrating the efficacy and applicability of the proposed method relative to those of more conventional models. Moreover, the range of the time period covered allows us to analyze the evolution of efficiency beyond the standard two-period Malmquist framework generally considered in the literature dealing with the behavior of refineries.

Managing user acceptance: an empirical investigation in the context of business intelligence standard software

This study suggests and tests a model for the systematic evaluation of management activities in company-wide standard software implementations using the example of a business intelligence (BI) software package. The proposed model builds on an extended technology acceptance model (TAM), previous research on IT implementation success factors and reviews of relevant change management variables. Using structural equation modelling, several hypotheses are tested. The investigated management variables demonstrate significant influences on the psychological acceptance factors included in the model. Seven out of ten hypotheses are confirmed. In addition, the model explains a substantial amount of variance in actual user behaviour measured with a system-based indicator. Practical implications for the implementation of company-wide standard software in organisations are discussed.

Implementation governance across complex solution landscapes

This paper describes a concept for a strategic enterprise architecture team, e.g. Strategies, Architectures, and Standards Group (SASG) and associated infrastructure, tools, and mechanisms for providing project monitoring and oversight. This concept is critical for establishing governance, from an enterprise perspective, across complex technology and system landscapes. This paper is unique in that it addresses the implementation of commercial standard software from a solution architecture perspective, but without focusing on the implementation methodology of any particular solution provider. This paper should be of interest to executives who are responsible for coordinating many technology implementation initiatives in large and complex enterprises.

Contracting for implementation of standard software

PurposeTraditional contract vehicles do not align well with enterprise resource planning (ERP) implementation methodologies. The purpose of this paper is to identify different contract vehicles and how they map to ERP implementation methodologies. Traditional contract vehicles are more process‐oriented than outcome‐focused. Successful standard software implementations are dependent on the outcome. The misalignment of process‐oriented contract vehicles and results‐oriented implementation methodologies leads to many implementation problems with respect to scope creep and ill‐defined interfaces.Design/methodology/approachThe study is based on research from public and private sector contracting documents, interviews and a review of case studies to show that there is a misalignment between contract vehicles, implementation methods and the eventual project plan.FindingsThe research concluded that phased or life‐cycle contracting is the best approach when implementing standard (off the shelf) software in an ERP solution. This approach mimics the recognized life‐cycle approach to product/project management where a large project is broken up into several smaller stages.Research limitations/implicationsThe data analyzed are from primary and secondary sources such as direct interviews, case study and contract reviews. The primary focus is based on US Federal Agency acquisition and planning policies.Originality/valueIdentifies different contract vehicles and how they map to ERP implementation methodologies.