Adoption of information systems in organizations

Introduction

The achievement of a sustained competitive edge is a crucial consideration for the corporate
performance in today's globalized and competitive environment. In this newly developed market
horizon, competition and outsmarting of key actors without creating a scalable and efficient
supply chain management is quite difficult and even unlikely (Lambert and Cooper, 2000). As a
result, modern enterprises, for example enterprise resource planning (ERP), are making
substantial investments in advanced information technology to deal with the dynamic market
climate. A more comprehensive analysis of the ERP framework covers many central processes
like accounting, sourcing, supply and inventory control, systems engineering, construction
activities, organizational funding and final product and service distribution records (Reitsma &
Hilletofth, 2018). ERP systems combine multiple key business processes to allow data and
knowledge to flow among themselves (Awa et al, 2017). It eliminates fragmentation by
centralizing data from many sites, thus reducing replication and leakage of data (ORACLE,
2018). ERP vendors have offered personalized kit services to companies regardless of scale,
development and organizational divisions until recently (Everdingen et al, 2000).

The existing studies indicates quite clearly that the ERP increasing adoption has not really been
examined properly in developed countries. Just a small number of experiments have been
undertaken in developed countries to establish antecedents for ERP adoption (Rajan & Baral,
2015). In addition, organizations must sort out behavioral factors which complicate the adoption
and implementation of ERPs to ensure optimization of ERP adoption through efficient and
effective operational definition apart from technical specifications (Nandi & Vakkayil, 2018). In
essence, the behavioral variables that affect the successful acceptance and application of EPR in
the Bangladeshi context need to be discussed and analyzed. The goal of this research is
forevermore to explore the rates of ERP adoption as well as the factors that influence its
popularity in the various sectors of Bangladesh. We would analyze the relationship between a
variety of variables, including success expectation, effort expectations, societal impacts and
circumstances that promote the system, opposition to improvement, presumed reputation, and
real use with behavioral intent.
Purpose

The use of business structures by small businesses has been growing for some time. There are
several explanations for taking them with well-documented possible benefits. However, this
research explores a small organization's choice to implement smaller parts of information
systems to include a counter illustration of integrated approach literature. The case offers a
complex tale about a small company with the intention of implementing an entrepreneurial
framework at the outset, and how different influences influenced the purpose and culminated in
the assembly of information systems. The case suggests that, in addition to the frequently cited
variables, such as organization and The preparation, social values and attributes of a key person,
such as possession, play a significant role in the implementation of information systems and
demonstrate how these factors are relevant to each other. Through the acceptance of the
technological organization-environment structure and a single case study design.

Objective

The research study's goals are;

1. To explore the present position of ERP in industrial and business companies. Enterprise
Resource Planning.
2. To illustrate the introduction and deployment of information systems in SMEs

Methodology

In this text, a small organization's decision to implement smaller off-shelf ISs in conjunction
with its information system (IS) is discussed. By exploring what factors affect IS adoption in a
smaller company and how they communicate, this paper attempts to address the question of
study "How does a small organization adopt an IS? "For many reasons a small enterprise is
chosen for this study: although ERP literature started to include SMEs, there is often no
difference among small and medium-sized enterprises (Iskanius et al. 2009).

In concentrating on a small business alone, the research will contribute to the literature by
offering a viewpoint to complement the medium-sized enterprise view. The research will also
illustrate how SMEs in general—resource deficiency, short-term focus—play in IS adopted
sometimes taken for granted assumptions. The main goal of this research is, then, to add to the
literature on implementation of information systems by observing the IS application process of a
small business.

The research adopts the environment-technology paradigm (TOE). TOE gives a helpful lens for
examining a non-American or European environment by deliberately focusing on the
environment. The case offers an insight into interconnected IS decisions: when the firm was set
up, the director of the company had expertise and intended to use one of ERP systems. But for
four years, the organization has no ERP system in the pipeline, pending recent conversations
with the owner that it still has in mind the possibility of using an ERP system. Besides, the
organization has introduced smaller standard shelving structures to build IS. The adoption of IS
that allows the business to operate over these four years also has multiple stakeholders to serve
and to play different roles in the organization. The case was studied during this timeframe and a
longitudinal viewpoint close to Kietzmann (2008) allows examining the stages the company has
taken.

Framework

There are various reasons to describe how such an IS is embraced or why. Any of the theories –
like the TAM, coherent theory of technology acceptability and implementation (Venkatesh et al.
2003), diffused inventions (DOI) and TOE – are adopted in the paper. There are particular
theories that specifically answer the problem. This review. The TOE structure has been adopted
in this article. The TOE method is an empirically supported and commonly applied IS adoption
framework that is used in diverse decisions on IS adoption. It was believed to be a generalized IS
theory, which implies only separate sources of control without defining variables of each (Zhu &
Kraemer 2005). Decisions are affected by three contexts in the TOE system. Descriptive metrics
on organizational characteristics such as management support, scale, organizational readiness
and IT experts of employees are represented in the organizational sense.
Figure 1 – the adopted framework in this study

Research hypothesis

In this study, a small agency's decision to implement smaller off-shelf ISs in conjunction with its
information system (IS) is discussed. By exploring, what factors affect IS adoption in a smaller
company and how they communicate, this paper attempts to address the question of study "How
does a small company embrace an information system?”

Results

Kitchen Co. is a small company with less than 30 employees. The workshop is used mainly to
build kitchens – to form the cupboards, cut the top of the kitchen, etc., or even to mount these
kitchens on the ventures. Owing to the capital costs associated with automatic equipment, much
manual processing takes place. The employees are presented with designs which are planned by
the engineers' CAD tooles and produce the kitchen according to precise blueprint specifications.
After the parts are made, the list of specifications given in the blueprint is reviewed and re-
checked during implementation. The CAD will make a list of project specifications and the list
will be printed as an Excel file that is eventually stored in inventory management applications.
This function is normally performed automatically, but the administrative assistant must first
update the Excel file manually to verify if the requirements list and inventory list are the same
after the inventory system has been supplied with the file. Together with the developers, Hugo
has occasionally done this to ensure the lists are similar. Such direct communication with the
details helps Hugo and the engineers to get an understanding of how the organization tracks the
programs and people involved. Hugo has a small squad of engineers building and working as a
sales team in the kitchens. Hugo has an experience in industrial production and manufacturing
managerial, with technical experience and management experience in order to support the
regular operation of the company. He is an enthusiastic leader who spends time at the business
and at the workshop. His direct presence and the use of his network and his terms "to be there at
the right time" became the first project for the living they got.

Implications

Compatibility has also been demonstrated by the information systems that have been
implemented by Kitchen Co. While certain aspects of the working system need manual
assistance, the selected IS systems are mutually supplementary. The inventory management
system contains the real inventories of the warehouse while CAD is used for preparing the
kitchens' development. At the workshop, the blueprints developed by CAD are used for kitchen
development and inventory tracking. An office administrator – and even from time - to - time the
technicians and Hugo – manages the processes manually, passes the files to the accounting
program. This very simple set up helps Hugo to keep track of the business without the potentials
of ERP systems – automation, centralization.

Limitations

Although the analysis is a single case study and does not generalize the investing mechanism it
reveals, it indicates variables which may be relevant in other situations too, and that other cases
which expose other significant aspects. The comparisons of the earlier findings may be a
function of the use by proven methods of existing meanings, which involve a different use of
TOE than a strict collection of predefined and comprehensive factors.

Article studied in this paper

https://www.diva-portal.org/smash/get/diva2:1164004/FULLTEXT01.pdf
References

1. Lambert, D. M., & Cooper, M. C. (2000). Issues in supply chain management. Industrial
Marketing Management, 29(1), 65–83.
2. Reitsma, E., & Hilletofth, P. (2018). Critical success factors for ERP system
implementation: A user perspective. European Business Review, 30(3), 285–310.
3. ORACLE. (2018). What is ERP? Retrieved from
https://www.oracle.com/applications/erp/what-is-erp.html
4. Awa, H. O., Uko, J. P., & Ukoha, O. (2017). An empirical study of some critical adoption
factors of ERP software. International Journal of Human–Computer Interaction, 33(8),
609–622.
5. Everdingen, Y. V., Hillegersberg, J. V., & Waarts, E. (2000). Enterprise resource
planning: ERP adoption by European midsize companies. Communications of the ACM,
43(4), 27–31.
6. Rajan, C. A., & Baral, R. (2015). Adoption of ERP system: An empirical study of factors
influencing the usage of ERP and its impact on end user. IIMB Management Review,
27(2), 105–117.
7. Nandi, M. L., & Vakkayil, J. (2018). Absorptive capacity and ERP assimilation: The
influence of company ownership. Business Process Management Journal, 24(3), 695–
715.
8. Iskanius, P., Halonen, R. & Mottonen, M., 2009. Experiences of ERP use in small
enterprises. In 11th International Conference on Enterprise Information Systems, Milan,
Italy.
9. Kietzmann, J., 2008. Interactive innovation of technology for mobile work. European
Journal of Information Systems, 17:3, 305–320.
10. Venkatesh, V. et al., 2003. User Acceptance of Information Technology: Toward a
Unified View. MIS Qarterly, 27:3, 425–478.
11. Zhu, K. & Kraemer, K.L., 2005. Post-adoption variations in usage and value of e-
business by organizations: Cross-country evidence from the retail industry. Information
Systems Research, 16:1, 61–84.
12. Zammuto, R.F. et al., 2007. Information Technology and the Changing Fabric of
Organization. Organization Science, 18:5, 749–762.
13. Uwizeyemungu, S. & Raymond, L., 2012. Impact of an ERP system’s capabilities upon
the realization of its business value: A resource-based perspective. Information
Technology and Management, 13:2, 69–90.
14. The Economist, 2014. The Peter Pan syndrome. The Economist.