21 |
Value Creation from IT Systems Integration : A Benefits, Openness and Price Model PerspectiveBrege, Harald, Hampusson, Petter January 2014 (has links)
This thesis is aimed at finding out how integration of IT systems creates value for companies and is conducted as a qualitative case study, where six companies are interviewed about their integration solutions. The interviewees were five CIOs and one Managing Director. Four of the companies interviewed have genuine Application Integration solutions, where a middleware platform is the hub of the integration system, while the remaining two used solutions based around a system of point-to-point integrations. The value of an integration solution will be considered a combination of the benefits an integration solution provides, openness aspects, and the price models used to pay for the system. Value is defined as what the company gains, in monetary terms, in exchange for what it pays for an offering (Anderson, Kumar, & Narus, 2007). This definition further defines the attractiveness of an offering as the value minus the price. When discussing the value of an IT system, it is important to consider the difference between the potential value, which is the maximum the system can deliver with an ideal environment and usage, and the realised value, which is some fraction of the potential value that a company actually gains, of the system (Davern & Kauffman, 2000; Smith & Nagle, 2005). Affecting the realisation of potential value are certain factors, called conversion contingencies, which are things like preparation of implementation projects or efforts at using all aspects of a system. Benefits are analysed according to a framework that divides IT systems benefits into five categories: operational, managerial, strategic, IT infrastructure, and organisational benefits (Shang & Seddon, 2000). These categories are focused around, respectively, productivity gains, enhanced planning capabilities, new strategic capabilities, better IT administration, and process improvements. We conclude that most companies gain several large benefits in the operational and managerial types, while the other three types have fewer reported benefits. We conclude that there seems to be quite a lot of unrealised potential value in the integration solutions, if the view of the potential of integration from the technological side is used. We also conclude that companies in certain environments and with more complex organisational structures seem to have a larger value potential than others, meaning they have more to potentially gain from an integration solution. For openness, five aspects of open source software are studied: lock-in, cost, security, flexibility/modifiability, and community. These aspects are mainly derived from literature on open source. The first conclusion we make regarding openness is that most of the CIOs seems not to be fully aware of what the term truly entails. Companies’ opinions regarding open source can be seen on a range between two extremes: those who want to modify or develop software and those who only want to use standard systems. The former category has more to gain from the aspects of cost and modifiability than the latter, but both categories can gain from the lock-in, security, and community aspects. The combination of factors that creates the price of an offering can be described as a price model. To study the value of price models of integration solutions, the SBIFT model (Iveroth, et al., 2013) is used, where the price model is divided into five dimensions, scope, base, influence, formula and temporal rights. None of the interviewed companies were satisfied with the alternatives for price models currently on the market. It was concluded that the dissatisfaction mostly stemmed from the facts that the companies had little opportunity to affect the price model, meaning they could not adapt it to better fit their internal conditions, the complexity of the license agreements, and that it was hard to get vendors to cite a price for a system. Price models that would be more attractive are e.g. models with a larger variable part, like transaction-based ones, or models that affect the time scale of the contract, even though no single model seemed more attractive to all companies.
|
22 |
Design of a service-oriented dashboardSundar, Gayathri. January 2007 (has links) (PDF)
Thesis (M.S.)--University of Alabama at Birmingham, 2007. / Additional advisors: David G. Green, Gary J. Grimes, John L. Hartman IV. Description based on contents viewed Feb. 5, 2008; title from title screen. Includes bibliographical references (p. 110-120).
|
23 |
Management accounting and integrated information systems : how to exploit the potential for management accounting of information technology /Rom, Anders. January 2008 (has links) (PDF)
Business School, Diss.--Copenhagen, 2008.
|
24 |
Enterprise resource planning implementation in higher educationGraham, James F. Hutchinson, Sandy January 2009 (has links)
Title from PDF of title page (University of Missouri--Columbia, viewed on Feb 15, 2010). The entire thesis text is included in the research.pdf file; the official abstract appears in the short.pdf file; a non-technical public abstract appears in the public.pdf file. Dissertation advisor: Dr. Sandy Hutchinson Vita. Includes bibliographical references.
|
25 |
Enabling scalable self-management for enterprise-scale systemsKumar, Vibhore. January 2008 (has links)
Thesis (Ph.D.)--Computing, Georgia Institute of Technology, 2008. / Committee Chair: Schwan, Karsten; Committee Member: Cooper, Brian F.; Committee Member: Feamster, Nick; Committee Member: Liu, Ling; Committee Member: Sahai, Akhil.
|
26 |
Assessing operational impact in enterprise systems with dependency discovery and usage miningMoss, Mark Bomi. January 2009 (has links)
Thesis (Ph.D)--Computing, Georgia Institute of Technology, 2010. / Committee Chair: Pu, Calton; Committee Member: Ahamad, Mustaque; Committee Member: Liu, Ling; Committee Member: Mark, Leo; Committee Member: Owen, Henry. Part of the SMARTech Electronic Thesis and Dissertation Collection.
|
27 |
An ontology-based approach for semantic level information exchange and integration in applications for product lifecycle managementZhan, Pei, January 2007 (has links) (PDF)
Thesis (Ph. D.)--Washington State University, August 2007. / Includes bibliographical references (p. 121-125).
|
28 |
Towards an extended enterprise through e-Business integrationMostert, Nicolette January 2004 (has links)
The focus of this project will be on introducing the concept of an extended enterprise to business leaders, subsequently presenting e- Business Integration and the supporting role that it can play in the establishment of an extended enterprise. Various literature sources will be consolidated to describe the integration approaches and supporting integration technologies and standards that can be employed in establishing integrated communication between the members of the extended enterprise. Finally, a phased approach will be proposed that can be employed in supporting the establishment of an extended enterprise through e-Business Integration.
|
29 |
Inter-organisational Application Integration : Developing Guidelines Using Multi Grounded TheorySkild, Fredrik, Thai, Men, Älverdal, Johan January 2005 (has links)
Background: Information technology (IT) has drastically changed the traditional way to do business. In theory, coordinating information sharing among organisational partners offers notable advantages through cost savings, productivity, improved decision making, and better customer service. Supported by modern information technology, business processes can change and be developed into new more effective forms, both internally and externally. However, as IT facilitates new business opportunities, it requires a steady flow of information and information exchange, both within intra- and inter-organisational contexts where a consensus on terms and definitions coordinating the uniform communication is vital. Purpose: With the focal point on inter-organisational information exchange, the purpose of the thesis is to define a set of guidelines for AI that can be used and adjusted according to the needs of a specific situation or context. Method: The thesis was carried out with a Multi Grounded Theory approach. Interviews were conducted at a local IT-company and with an associate professor of Informatics at Jönköping International Business School. Results: Five categories were discovered which impact AI: integration governance, project management, context, integration content, and testing. The result also implied the importance to distinguish between an operational and strategic level when working with Application Integration.
|
30 |
Inter-organisational Application Integration : Developing Guidelines Using Multi Grounded TheoryÄlverdal, Johan, Skild, Fredrik, Thai, Men January 2005 (has links)
Background: Information technology (IT) has drastically changed the traditional way to do business. In theory, coordinating information sharing among organisational partners offers notable advantages through cost savings, productivity, improved decision making, and better customer service. Supported by modern information technology, business processes can change and be developed into new more effective forms, both internally and externally. However, as IT facilitates new business opportunities, it requires a steady flow of information and information exchange, both within intra- and inter-organisational contexts where a consensus on terms and definitions coordinating the uniform communication is vital. Purpose: With the focal point on inter-organisational information exchange, the purpose of the thesis is to define a set of guidelines for AI that can be used and adjusted according to the needs of a specific situation or context. Method: The thesis was carried out with a Multi Grounded Theory approach. Interviews were conducted at a local IT-company and with an associate professor of Informatics at Jönköping International Business School. Results: Five categories were discovered which impact AI: integration governance, project management, context, integration content, and testing. The result also implied the importance to distinguish between an operational and strategic level when working with Application Integration.
|
Page generated in 0.1577 seconds