183,396 research outputs found
Technical Risk Management on Enterprise Integration Projects
Enterprise Integration (EI) is essential to organisations wishing to fulfill broader business objectives related to e-business, customer relationship management (CRM), supply chain management (SCM) and business-to-business (B2B) commerce. This paper describes and presents the results of a study into practices for managing technical risk on EI projects. In the study, 21 managers participated in a facilitated workshop or interview sessions to identify areas of risk (RAs) associated with EI projects and risk management practices (RMP) for addressing those RAs. Risks were identified in four separate phases in the lifecycle of an EI project, namely the strategy, planning, implementation and rollout phases. Many of the risks identified were not specific to EI projects, but were applicable to large IT projects in general. The paper is primarily concerned with technical risk although some aspects of business and organizational risk are discussed briefly
Recommended from our members
Using ERP as a basis for Enterprise application integration
Architecting and implementing e-Business supply chain solutions across and within the modern day enterprise, is now becoming a necessity in order to maintain competitive and be adaptable to market needs. As such, the integration of information and processes is a vital step, using technologies such as using Enterprise Resource Planning (ERP), Supply Chain Management (SCM) and enterprise portal platforms. The effective sharing of resource planning and other enterprise related data across and within the enterprise is typically seen as a facet of a business to business (B2B) platform. However, such infrastructures typically involve a tight integration across intra and inter-organisational systems. This paper examines an Enterprise Application Integration (EAI) initiative taken by a global manufacturer of industrial automation products, which attempted to utilise ERP as an integration tool across its internal B2B infrastructure, to achieve such an aim. This paper discusses those integration considerations and complexities, experienced by the case company upon embarking on an EAI integration programme through the adoption of a core ERP as a catalyst for organizational change. In doing so the authors present an analysis of the inherent risks and limitations of this approach in terms of previously published literature in the field, relating to technology-driven organizational change and EAI impact and adoption frameworks
Surfacing ERP exploitation risks through a risk ontology
Purpose – The purpose of this paper is to develop a risk identification checklist for facilitating user companies to surface, organise and manage potential risks associated with the post-adoption of Enterprise Resource Planning (ERP) systems.
Design/methodology/approach – A desktop study, based on the process of a critical literature review, was conducted by the researchers. The critical review focused on IS and business research papers, books, case studies and theoretical articles, etc.
Findings – By systematically and critically analysing and synthesising the literature reviewed, the researchers identified and proposed a total of 40 ERP post-implementation risks related to diverse operational, analytical, organisation-wide and technical aspects. A risk ontology was subsequently established to highlight these ERP risks, as well as to present their potential causal relationships.
Research limitations/implications – For researchers, the established ERP risk ontology represents a starting point for further research, and provides early insights into a research field that will become increasingly important as more and more companies progress from implementation to exploitation of ERPs.
Practical implications – For practitioners, the risk ontology is an important tool and checklist to support risk identification, prevention, management and control, as well as to facilitate strategic planning and decision making.
Originality/value – There is a scarcity of studies focusing on ERP post-implementation in contrast with an over abundance of studies focusing on system implementation and project management aspects. This paper aims to fill this significant research gap by presenting a risk ontology of ERP post-adoption. It represents a first attempt in producing a comprehensive model in its area. No other such models could be found from the literature reviewed
Applied business analytics approach to IT projects – Methodological framework
The design and implementation of a big data project differs from a typical business intelligence project that might be presented concurrently within the same organization. A big data initiative typically triggers a large scale IT project that is expected to deliver the desired outcomes. The industry has identified two major methodologies for running a data centric project, in particular SEMMA (Sample, Explore, Modify, Model and Assess) and CRISP-DM (Cross Industry Standard Process for Data Mining). More general, the professional organizations PMI (Project Management Institute) and IIBA (International Institute of Business Analysis) have defined their methods for project management and business analysis based on the best current industry practices. However, big data projects place new challenges that are not considered by the existing methodologies. The building of end-to-end big data analytical solution for optimization of the supply chain, pricing and promotion, product launch, shop potential and customer value is facing both business and technical challenges. The most common business challenges are unclear and/or poorly defined business cases; irrelevant data; poor data quality; overlooked data granularity; improper contextualization of data; unprepared or bad prepared data; non-meaningful results; lack of skill set. Some of the technical challenges are related to lag of resources and technology limitations; availability of data sources; storage difficulties; security issues; performance problems; little flexibility; and ineffective DevOps. This paper discusses an applied business analytics approach to IT projects and addresses the above-described aspects. The authors present their work on research and development of new methodological framework and analytical instruments applicable in both business endeavors, and educational initiatives, targeting big data. The proposed framework is based on proprietary methodology and advanced analytics tools. It is focused on the development and the implementation of practical solutions for project managers, business analysts, IT practitioners and Business/Data Analytics students. Under discussion are also the necessary skills and knowledge for the successful big data business analyst, and some of the main organizational and operational aspects of the big data projects, including the continuous model deployment
Recommended from our members
Leveraging simulation practice in industry through use of desktop grid middleware
This chapter focuses on the collaborative use of computing resources to support decision making in industry. Through the use of middleware for desktop grid computing, the idle CPU cycles available on existing computing resources can be harvested and used for speeding-up the execution of applications that have “non-trivial” processing requirements. This chapter focuses on the desktop grid middleware BOINC and Condor, and discusses the integration of commercial simulation software together with free-to-download grid middleware so as to offer competitive advantage to organizations that opt for this technology. It is expected that the low-intervention integration approach presented in this chapter (meaning no changes to source code required) will appeal to both simulation practitioners (as simulations can be executed faster, which in turn would mean that more replications and optimization is possible in the same amount of time) and the management (as it can potentially increase the return on investment on existing resources)
Adaptation of domestic state governance to international governance models
The purpose of the article is to provide the evolving international trends of modern management models and authorial vision of model of state governance system in Ukraine, its subsystems, in particular, the system of provision of administrative services that is appropriate for the contemporary times. Methodology. On the basis of scientific and theoretical approaches to the definitions of terms “state governance” and “public governance”, there was an explanation of considerable difference between them and, taking into consideration, the mentality of Ukrainian society and peculiar weak side in self-organization, the authors offered to form authorial model of governance on the basis of historically traditional for Ukraine model of state governance and to add some elements of management concepts that proved their significance, efficiency and priority in practice. Results. The authors emphasized the following two prevailing modern management models in the international practice: “new state management” and “good governance”. The first concept offered for consideration served as a basis for the semantic content of state activity that reflects more the state of administrative reformation. Practical meaning. A practical introduction of management to the domestic model of governance creates the range of contradictions that do not allow implementing herein concept. Pursuant to authors, the second one allows in considerable measure to reform state governance, considering historically developed peculiarities of this model. Moreover, the involvement of concept herein into introduction of informational and communicational technologies in the process of governance eliminates the necessity of power decentralization, it allows to form real net structure and, at the same, to keep vertical power structure, to involve citizens for formation and taking of management decisions, to form electronic communicational channel of feedback, to provide citizens with electronic administrative services. All indicated advantages of the concept certify about the necessity to reform state governance exactly in this field. Meaning/ Distinction. This article raises a question about the significance of formation and sequence of state policy in Ukraine aimed at creating an information-oriented society, space, as well as informational and technological infrastructure
Attitudinal and behavioural determinants influencing decision makers when adopting integration technologies in local government
Over the last few years, the advent of innovative
or revolutionary integration technologies has
influenced pivotal decisions within top management
to strategically transform Local Government
Authorities (LGAs). These technologies may
represent a huge cost for adopting LGAs, but may
also offer the chance to achieve competitive
advantage through superior service delivery. With
the emergence of electronic Government (e-
Government), LGAs are turning to integration
technologies to fully automate and e-enable their
business processes and integrate their IT
infrastructures. While prior research on the adoption
of integration technologies in the private and public
domain has considered several determinants (e.g.
benefits, barriers, costs), little attention has been
given to investigate the attitudinal and behavioural
determinants influencing top management’s decision
making process for the adoption of integration
technologies in LGAs. Notwithstanding, the
implications of this research have yet to be assessed,
leaving scope for timeliness and novel research.
Therefore, it is of high importance to investigate this
area within LGAs and contribute to the area of
strategic decision making by examining attitudinal
and behavioural determinants of top management in
relation to integration technologies adoption
Recommended from our members
Designing a consulting services architecture model
textDuring my years of experience in the technology industry, it has become obvious that standard processes and methodologies within the engineering discipline are at a mature state. The realization though is that software engineering specifically lags behind. Most software engineering methodologies that I have studied focus on the mission of software development. It is this realization and the need for structure that led me to review existing methodologies used within my company's software services organization. The definition of what a successful software services methodology entails is rather limited. This report will provide a history of existing software engineering methodologies that I have studied, describe an initial services method that was being developed within my organization, develop a new model that addresses previous shortcomings and identify additional components required to further define a strong software services-oriented delivery methodology.Electrical and Computer Engineerin
- …