Relevant bibliographies by topics / Legacy Systems VS ERP systems

Contents

  1. Journal articles
  2. Dissertations / Theses
  3. Book chapters
  4. Conference papers

Academic literature on the topic 'Legacy Systems VS ERP systems'

Author: Grafiati
Published: 4 June 2021
Last updated: 13 February 2022

Create a spot-on reference in APA, MLA, Chicago, Harvard, and other styles

Select a source type:

Consult the lists of relevant articles, books, theses, conference reports, and other scholarly sources on the topic 'Legacy Systems VS ERP systems.'

Next to every source in the list of references, there is an 'Add to bibliography' button. Press on it, and we will generate automatically the bibliographic reference to the chosen work in the citation style you need: APA, MLA, Harvard, Chicago, Vancouver, etc.

You can also download the full text of the academic publication as pdf and read online its abstract whenever available in the metadata.

Journal articles on the topic "Legacy Systems VS ERP systems"

1

الهادی, محمد. "Cloud vs. Legacy ERP Systems Tug of War Intensifies for SMBs." مجلة الجمعیة المصریة لنظم المعلومات وتکنولوجیا الحاسبات 22, no. 22 (January 1, 2019): 17. http://dx.doi.org/10.21608/jstc.2019.117225.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Zeng, Yajun, Yujie Lu, and Miroslaw Skibniewski. "Enterprise Resource Planning Systems for Project-Based Firms: Benefits, Costs & Implementation Challenges." Journal for the Advancement of Performance Information and Value 4, no. 1 (October 1, 2012): 85. http://dx.doi.org/10.37265/japiv.v4i1.100.

Full text
Abstract:
Enterprise Resource Planning (ERP) systems are configurable enterprise-wide information system packages that integrate information and information-based processes within and across functional areas in an organization. They have been widely adopted in many organizations and accepted as a de facto industry standard for the replacement of legacy systems. This paper analyzes and presents the costs and benefits of ERP systems for project-based industries, which have lagged behind other major industries in adopting ERP systems due to their project-centric nature and the high stakes involved in ERP implementation. The challenges during the process of ERP implementations are also identified as part of the effort to understand the implied costs of an ERP system. The evidence of the costs and benefits are drawn from previous studies and the analysis of the prevailing working practices in project-based firms. The classification of the costs and benefits constitutes a cost and benefit taxonomy which can be used to enable executives in project-based firms to make informed decisions on their ERP system investments.
APA, Harvard, Vancouver, ISO, and other styles
3

Mekawie, Shereen, and Ahmed Elragal. "ERP and SCM Integration." International Journal of Enterprise Information Systems 9, no. 2 (April 2013): 106–24. http://dx.doi.org/10.4018/jeis.2013040106.

Full text
Abstract:
Organizations rely on various types of information systems (IS) to manage day-to-day business and make decisions such as enterprise resource planning (ERP) and supply chain management (SCM) systems. Organizations rely on ERP systems to replace their legacy systems, integrate core business processes and to help adding value and increasing visibility. Additionally, SCM systems help organizations to enhance relationships with supply chain members. It is essential for organizations to measure their business performance by taking into consideration intra-organizational and inter-organizational indicators. Therefore, the integration between ERP and SCM systems is a key to enable more business performance; that were otherwise hidden. Accordingly, the motive for this paper is to study the influence of ERP-SCM integration on enabling more business performance measures. For this reason, a business performance measures framework was constructed and then tested on two organizations using multi-case study qualitative research approach. Analysis results indicated that integrating ERP and SCM systems would render more performance measures and hence enable better and wider-scope evaluation. Consequently, managers are more informed and accordingly are able to make high quality decisions.
APA, Harvard, Vancouver, ISO, and other styles
4

Alksnis, Gundars, Ērika Asņina, Mārīte Kirikova, and Egils Meiers. "Enabling Support of Collaborative Cross-enterprise Business Processes for Legacy ERP Systems." Complex Systems Informatics and Modeling Quarterly, no. 2 (April 29, 2015): 1–18. http://dx.doi.org/10.7250/csimq.2015-2.01.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Bamufleh, Dalal, Maram Abdulrahman Almalki, Randa Almohammadi, and Esraa Alharbi. "User Acceptance of Enterprise Resource Planning (ERP) Systems in Higher Education Institutions." International Journal of Enterprise Information Systems 17, no. 1 (January 2021): 144–63. http://dx.doi.org/10.4018/ijeis.20210101.oa1.

Full text
Abstract:
It has become common practice for higher education institutions (HEIs) to replace existing computer systems, called legacy administrative information systems, with new ones to cope with the continuously changing demands in the context of education. At the top of these systems is enterprise resource planning (ERP) systems that integrate HEIs' business processes, functions, and data to improve their overall productivity and effectiveness. However, many studies on ERP adoption have shown that organizations frequently face several barriers, and the failure rate is high. In addition, various research projects have concluded that, quite often, HEIs do not obtain the expected advantages from the adoption of the ERP system. This research aims to explore the factors that affect the behavioral adoption and acceptance of an ERP system in the context of HEIs. Based on works from literature and authors' observations of the PeopleSoft system (ERP system) implementation at Yanbu University College (YUC) in Yanbu City, Saudi Arabia (SA), a conceptual model of users' acceptance of ERP systems has been proposed. The framework is based on the unified theory of acceptance and use of technology (UTAUT) model and is extended with additional constructs. The present study offers a theoretical contribution by extending the UTAUT model to provide a richer understanding of users' adoption behavior of ERP systems in the HEI context. In addition, according to the authors' knowledge, this is the first paper that to address ERP users' adoption perspective in HEIs in SA.
APA, Harvard, Vancouver, ISO, and other styles
6

Fisher, Ingrid E., and Marianne Bradford. "New York State Agencies: A Case Study for Analyzing the Process of Legacy System Migration: Part II." Journal of Information Systems 20, no. 1 (March 1, 2006): 139–60. http://dx.doi.org/10.2308/jis.2006.20.1.139.

Full text
Abstract:
Part II of this case chronicles the actions and outcomes of the legacy system migrations of five New York State agencies. The case highlights the problems these agencies encountered in migrating from legacy systems to enterprise-wide systems built upon relational databases. The case also explores the additional complexities of legacy system migration under the unique legal and operational constraints of governmental entities. Investigated issues include business process management, technical and financial project feasibility, cost-benefit analyses, consultant management, and ERP implementations.
APA, Harvard, Vancouver, ISO, and other styles
7

Hunton, James E., Arnold M. Wright, and Sally Wright. "Are Financial Auditors Overconfident in Their Ability to Assess Risks Associated with Enterprise Resource Planning Systems? (Retracted)." Journal of Information Systems 18, no. 2 (September 1, 2004): 7–28. http://dx.doi.org/10.2308/jis.2004.18.2.7.

Full text
Abstract:
The first objective of the current study is to examine the extent to which financial auditors recognize heightened risks associated with an enterprise resource planning (ERP) system, as compared to a non-ERP (legacy) system, in the presence of a control weakness over access privileges. The second objective is to assess the propensity of financial auditors to consult with information technology (IT) audit specialists within their firm when assessing ERP and non-ERP system risks during the planning stage of an audit. One hundred sixty-five auditors participated in an experiment in which we manipulated system type (ERP versus non-ERP) and measured auditor type (IT audit specialists versus financial auditors). Both auditor types indicate significantly higher business interruption, process interdependency, and overall control risks with the ERP, as compared to the non-ERP, system. Additionally, while IT audit specialists assess significantly higher network, database, and application security risks with the ERP system, financial audits do not recognize higher security risks in these areas. Perceived risk differentials from the non-ERP to the ERP system across all risk categories are significantly greater for IT audit specialists than financial auditors. Finally, financial auditors do not indicate a greater need to consult with IT audit specialists when auditing an ERP versus a non-ERP system and they are equally highly confident in the ability of financial audit teams to assess risks in both computing environments. Overall, evidence from this study suggests that financial auditors may be overconfident in their ability to assess ERP system risks.
APA, Harvard, Vancouver, ISO, and other styles
8

Sherer, Susan A. "Enterprise Applications for Supply Chain Management." International Journal of Information Systems and Supply Chain Management 3, no. 3 (July 2010): 18–28. http://dx.doi.org/10.4018/jisscm.2010070102.

Full text
Abstract:
Although many companies have implemented ERP systems to track and share information among cross functional business processes, they often supplement these with legacy, custom, or best of breed applications to support supply chain execution and management. This article offers a framework for understanding all types of enterprise applications that support the supply chain. In this study, the author organizes these applications, define acronyms, and describe the various types of systems that make up an information infrastructure for supply chain management.
APA, Harvard, Vancouver, ISO, and other styles
9

Khand, Z. H., and M. R. Kalhoro. "Testing and Validating DeLone and MacLean IS Model: ERP System Success in Higher Education Institutions of Pakistan." Engineering, Technology & Applied Science Research 10, no. 5 (October 26, 2020): 6242–48. http://dx.doi.org/10.48084/etasr.3762.

Full text
Abstract:
The universities in Pakistan have recently started replacing their old legacy systems with ERP systems which are commonly used in business organizations to gain a competitive edge over competitors. The Higher Education Commission (HEC) has implemented ERPs systems at eight different Universities in Pakistan. HEC has invested a huge amount of money to facilitate the integration, customization, and implementation of ERP systems in these universities. Previous studies have mainly focused on Critical Success Factors (CSFs) and risk factors of ERP systems. This study intends to empirically measure the support of ERP systems in teaching processes. DeLone and McLean model of Information Systems (IS) success is one of the most commonly used models cited in IS literature. In this study, the DeLone and McLean model was applied at a University level analysis to access the impact of ERP in higher educational institutions and their support in the improvement of academic processes. Hypotheses were tested on the research model using empirical data collected from 230 respondents, including students and faculty at two selected universities, with the use of a questionnaire. The data were analyzed by structural equation modeling. The model was empirically tested and the findings showed that use and user satisfaction affected most net benefits. Information quality, system quality, and service quality accounted for 42.6% effect in use. Whereas, information quality, system quality, service quality, and use accounted for 46.5% variance in user satisfaction.
APA, Harvard, Vancouver, ISO, and other styles
10

Gupta, M. P., and Deepak Bhatia. "Reworking with a Legacy Financial Accounting System: Lessons from a Pharma Company." Vikalpa: The Journal for Decision Makers 30, no. 3 (July 2005): 79–92. http://dx.doi.org/10.1177/0256090920050307.

Full text
Abstract:
The issues of legacy systems become more pronounced at the time of a major IT upheaval such as implementation of ERP or business process reengineering (BPR) exercise. In this changing scenario, there is a need to update the systems and skills and integrate them with the emerging enterprisewide infrastructure. The main problems with a legacy system are that it remains insulated from the update attempt that largely follows market trend thus rendering it outdated and also that its documentation is poor. In this paper, the authors share the experiences of a project undertaken in one of India's leading multinational pharmaceutical companies (MPC) which was to rework on the existing legacy system and design a new application. The legacy system referred to here is the company's financial accounting system which was developed in 1993. Originally designed in COBOL, it was subsequently improved as and when the finance department put forth its requirements. The major downside of the system was that it had virtually no documentation and no one from the original team that developed the system was still working with the company. This made it all the more difficult to understand and document the system. Also, the system had a high response time thus leading to lower productivity of the data entry staff and other users. Further, it had a limited reporting capability and was basically used for storing financial data. When this project was undertaken for rework, the MPC was in the process of implementing an ERP package for its manufacturing and, therefore, it was necessary to bring all its applications to the same database structure. The most obvious question was whether to discard the legacy system and implement ERP's accounting module. The management, however, decided to retain and rework on the legacy system with the intention of integrating the new system with ERP. The driving point in favour of this decision was the realization that the legacy system was regarded as very critical for the accounting function and also that the users had become conversant with the system despite it being not very user-friendly. Also, there was no risk of failure. Incidentally, the review of the legacy system and ERP implementation coincided thereby easing out concerns of managing organizational changes as the company already had its strategy and preparedness in place for the scenario emerging out of ERP implementation. The computer-aided systems engineering (CASE) tool was chosen for designing the new system because of its inherent advantages in handling software projects which are as follows: The well-documented new system simplifies the maintenance jobs and, therefore, fewer people are required for its maintenance (this was the major problem with the previous system). It has removed the dependence of the management on a small set of people who specialized in the maintenance of an undocumented system. Financial reporting has become easier and better. The experience on this project made it amply clear that the top management support can make or mar a project. This is one of the most popular hypotheses in the information systems literature which has been found to be true in the case of the MPC.
APA, Harvard, Vancouver, ISO, and other styles
More sources

Dissertations / Theses on the topic "Legacy Systems VS ERP systems"

1

Chiawah, Tambei. "Relationship Between Enterprise Resource Planning System and Organizational Productivity in Local Government." ScholarWorks, 2019. https://scholarworks.waldenu.edu/dissertations/6409.

Full text
Abstract:
Organizations experience challenges despite efforts to increase productivity through implementing large-scale enterprise systems. Leaders of local government institutions do not understand how to achieve expected and desired benefits from the implementation of enterprise resource planning (ERP) systems. Lack of alignment between social and technical elements in ERP implementation depresses organizational productivity. The purpose of this quantitative correlational study was to examine whether social and technical elements increase use and productivity in ERP implementation. The research questions addressed the relationship between ERP and organizational efficiency, cross-functional communication, information sharing, ease of ERP use, and ERP usefulness. Sociotechnical systems theory provided the theoretical basis for the study. Data were collected from online surveys completed by 61 ERP users and analyzed using Wilcoxon matched pairs statistics and Spearman's correlation coefficient. Findings indicated a positive significant relationship between ERP and information sharing, a positive significant relationship between ERP system quality and ease of ERP use, and a positive significant relationship between ERP system quality and organizational productivity. Findings may be used by local government leaders, technology managers, and chief information officers to ensure ERP sustainability and increase productivity.
APA, Harvard, Vancouver, ISO, and other styles
2

IDOWU, HAKEEM ADEWALE. "Strategic Dilemma With ERP System Implementation : Enterprise vs Consultant Perspective." Thesis, Jönköping University, JIBS, Business Informatics, 2009. http://urn.kb.se/resolve?urn=urn:nbn:se:hj:diva-9614.

Full text
Abstract:

Over the past few years and up to date, many companies around the globe have implemented Enterprise Resource Planning (ERP) systems. Implementing ERP system in an organisation is considered as an irresistible challenge, with the typical ERP system implementation approach. In correspondent, management in an organisation are facing critical challenges' to make decision on a specific ERP system implementation strategy, however, any considered decision would influence development, testing and ultimately the success of the implementation. Therefore, this thesis aims to examine solution to how organisation can decide or choose the best ERP system implementation strategy and explore the one that could be highly recommended by considering enterprise and consultant perspectives.

 

In order to accomplish the purpose of this thesis, qualitative and quantitative method of collecting and analysing data were adopted. Quantitative and qualitative data were collected through the mean of questionnaire and structure interview. This is one of the reasons why this thesis can be viewed in an inductive and deductive approaches. To this end, exploratory and descriptive knowledge should be derived from this study.

Analysis of this thesis has discovered that, there are many influencing factors in which organisation needed to be considered when making choice of a particular ERP system implementation strategy. These factors include: (i) Size and Complexity of an organisation (ii) Degree of internationalisation (iii) Number of requirements (iv) Nature of integration and (v) Skills and Experience of people within an organisation.

In order to choose appropriate strategy for ERP system implementation, organisation should considered to implement a skeleton system in which other application can be added to the systems when it is in operation. Clarification of a business vision that would call for the legacy system replacement or re-modification, is also essential for an organisation to consider. Considering the above statements, organisation should be able to choose appropriate strategy that would fit their business processes.

Nevertheless, Phased strategy is considered as the best or appropriate implementation strategy in which organisation can rely upon. Exploring Phased strategy simply means that, the problem of making choice of a particular implementation strategy will be minimal. That is; organisations that are willing to implement ERP system can easily consider phased strategy as their best alternative in order to attain success implementation.

 

APA, Harvard, Vancouver, ISO, and other styles
3

Hedman, Surlien Peter. "Economic advantages of Blockchain technology VS Relational database : An study focusing on economic advantages with Blockchain technology and relational databases." Thesis, Blekinge Tekniska Högskola, Institutionen för industriell ekonomi, 2018. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-17366.

Full text
Abstract:
Many IT-systems are when created not designed to be flexible and dynamic resulting in old and complex systems hard to maintain. Systems usually build their functionality and capability on the data contained in their databases. The database underlines such system, and when data do not correspond between different and synchronizing systems, it is a troublesome debugging process. This is because systems are complex and the software architecture is not always easy to understand. Due to increasing complexity in systems over time, making systems harder to debug and understand, there is a need for a system that decreases debugging costs. Furthermore, result in better transaction costs. This study proposes a system based on blockchain technology to accomplish this.   An ERP system based on blockchain with encrypted transactions was constructed to determine if the proposed system can contribute in better transaction costs. A case study at multiple IT-companies and comparison to an existing ERP system module validated the system. A successful simulation showed that multiple parts could read and append data to an immutable storage system for one truth of data. By all counts, and with proven results, the constructed blockchain solution based on encrypted transactions for an ERP system can reduce debugging costs.   It is also shown that a centralized database structure where external and internal systems can get one truth of data, decreases transaction costs. However, it is the decision makers in companies that need to be convinced for the constructed system to be implemented. A problem is also when modifications to the object type, then historical transactions cannot be changed in an immutable storage solution. Blockchain is still a new technology, and the knowledge of the technology and the evolution of the system determines if the proposed software architecture will result in better transaction costs.
APA, Harvard, Vancouver, ISO, and other styles
4

Khatib, Samy. "COBOL-skills, Where art Thou? : An assessment of future COBOL needs at Handelsbanken." Thesis, KTH, Skolan för informations- och kommunikationsteknik (ICT), 2016. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-187480.

Full text
Abstract:
The impending mass retirement of baby-boomer COBOL developers, has companies that wish to maintain their COBOL systems fearing a skill shortage. Due to the dominance of COBOL within the financial sector, COBOL will be continually developed over at least the coming decade. This thesis consists of two parts. The first part consists of a literature study of COBOL; both as a programming language and the skills required as a COBOL developer. Interviews were conducted with key Handelsbanken staff, regarding the current state of COBOL and the future of COBOL in Handelsbanken. The second part consists of a quantitative forecast of future COBOL workforce state in Handelsbanken. The forecast uses data that was gathered by sending out a questionnaire to all COBOL staff. The continued lack of COBOL developers entering the labor market may create a skill-shortage. It is crucial to gather the knowledge of the skilled developers before they retire, as changes in old COBOL systems may have gone undocumented, making it very hard for new developers to understand how the systems work without guidance. To mitigate the skill shortage and enable modernization, an extraction of the business knowledge from the systems should be done. Doing this before the current COBOL workforce retires will ease the understanding of the extracted data. The forecasts of Handelsbanken’s COBOL workforce are based on developer experience and hiring, averaged over the last five years. The forecasts take into consideration the age developers are hired, the age the developers exit, and their cumulative growing experience while in the skills pool. The state of COBOL in 2015 is used as a baseline of COBOL needs to forecast until 2060. I.e. the rate at which COBOL systems are developed stay the same. The forecasts show that if no developers are hired, most of their experienced developers will have left by 2030. To keep their current COBOL experience level, Handelsbanken needs to keep hiring over the coming 45 years. Handelsbanken has to hire on average 8.2 developers per year until 2030, and 6.5 developers per year until 2060. I.e. Handelsbanken has been able to keep a high average of 7.6 people per year for the last five years.
Organisationer som underhåller COBOL system är oroliga inför den åldrande COBOL-arbetskraftens pensionering. COBOLs dominans inom den finansiella sektorn leder till att COBOL kod kommer att fortsätta utvecklas i minst tio år till. Den här uppsatsen är uppdelad i två delar. Första delen är en litteraturstudie om COBOL som programmeringsspråk, samt kunskapsbehovet som COBOL utvecklare. Intervjuer gjordes med nyckelpersoner inom Handelsbanken, kring det nuvarande tillståndet av COBOL och COBOLs framtid i Handelsbanken. Den andra delen består av en kvantitativ prognos kring Handelsbankens behov av COBOL utvecklare i framtiden. Prognosen bygger på data som samlats genom att skicka ut en enkät till alla COBOL utvecklare. Den fortsatta bristen på nya COBOL utvecklare på arbetsmarknaden kan skapa en kompetensbrist. Det är viktigt att samla kunskapen som de pensionerande utvecklarna bär på, eftersom ändringarna i systemen kan ha gått odokumenterade, vilket gör det väldigt svårt för nya utvecklare att förstå systemen utan vägledning. För att minska kompetensbehovet och möjliggöra modernisering av systemen, bör en extraktion av affärskunskap göras ur systemen. Att ta hjälp av utvecklarna av systemen kan avsevärt förenkla förståelsen av den extraherade informationen. Prognoserna av Handelsbankens COBOL arbetskraft baseras på data om utvecklarerfarenhet och anställning över de senaste fem åren. Prognoserna tar hänsyn till åldern när utvecklarna anställs, åldern när utvecklarna slutar, och tillväxten av deras sammanlagda erfarenhet under tiden de jobbar. Prognosen använder COBOL erfarenhetsbehovet i 2015 som en bas för prognosen. Prognosen beräknar behoven fram till år 2060. Prognoserna visar att om inga nya tillskott av utvecklare görs, så kommer de flesta av Handelsbankens erfarna utvecklare ha slutat vid år 2030. För att behålla deras nuvarande erfarenhetsnivå, så kommer Handelsbanken behöva kontinuerligt anställa utvecklare över kommande 45 åren. Handelsbanken kommer behöva anställa i genomsnitt 8,2 utvecklare per år fram till 2030, och därefter 6,5 utvecklare per år fram till 2060. Handelsbanken har lyckats ha en hög genomsnittlig anställningstakt de senaste fem åren, 7,6 personer per år.
APA, Harvard, Vancouver, ISO, and other styles

Book chapters on the topic "Legacy Systems VS ERP systems"

1

Ng, Martin M. T., and Michael T. K. Tan. "Symbolic Processes in ERP Versus Legacy System Usage." In Information Systems Research, 713–22. Boston, MA: Springer US, 2004. http://dx.doi.org/10.1007/1-4020-8095-6_49.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Sudzina, F., A. Pucihar, and G. Lenart. "Actual vs. Planned ERP System Implementation Costs in Slovak and Slovenian Companies." In Information Systems: People, Organizations, Institutions, and Technologies, 477–84. Heidelberg: Physica-Verlag HD, 2009. http://dx.doi.org/10.1007/978-3-7908-2148-2_55.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Laukaitis, Algirdas. "Code Transformation Pattern Alignments and Induction for ERP Legacy Systems Migration." In Lecture Notes in Business Information Processing, 228–40. Cham: Springer International Publishing, 2015. http://dx.doi.org/10.1007/978-3-319-21915-8_15.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Coppolino, Luigi, Salvatore D’Antonio, Carmine Massei, and Luigi Romano. "Efficient Supply Chain Management via Federation-Based Integration of Legacy ERP Systems." In Communications in Computer and Information Science, 378–87. Cham: Springer International Publishing, 2015. http://dx.doi.org/10.1007/978-3-319-22689-7_29.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Alksnis, Gundars, Erika Asnina, Anita Finke, and Marite Kirikova. "Lessons Learned from Experimental Prototype Development for KPI Acquisition and Modeling from Legacy ERP Systems." In Lecture Notes in Business Information Processing, 155–70. Cham: Springer International Publishing, 2015. http://dx.doi.org/10.1007/978-3-319-24626-0_12.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Albadri, Fayez. "ERP Upgrade vs. ERP Replacement." In Cases on Enterprise Information Systems and Implementation Stages, 84–109. IGI Global, 2013. http://dx.doi.org/10.4018/978-1-4666-2220-3.ch006.

Full text
Abstract:
ERP systems life cycle may extend in some business organizations up to fifteen years or more. Nevertheless, the time comes in the life of an ERP system when there is a need to evaluate and compare the value of continuing to use the existing ERP system version against the option to upgrade to a higher version of the same system or having it replaced all together by a different system. In many cases, this translates into a critical management-sponsored mission designating a dedicated team or task force to investigate the feasibility of the alternative options, and to report on the preferred option with a recommendation of the way forward and implementation approach. This case reflects the investigations of Gulf Telecom Company (GTC) in exploring the viability and feasibility of its ERP options to support and provide the grounds for a management decision to mark the next phase of the ERP in the organization. The case describes the approach that was adopted by Gulf Telecom and highlights the challenges to accomplish the mission successfully and any lessons learned from this experience.
APA, Harvard, Vancouver, ISO, and other styles
7

Rashid, Mohammad A. "Evolution of ERP Systems." In Encyclopedia of Information Science and Technology, First Edition, 1138–43. IGI Global, 2005. http://dx.doi.org/10.4018/978-1-59140-553-5.ch201.

Full text
Abstract:
The functional units of today’s complex business environment require more and more interfunctional data flow for decision making, timely and efficient procurement of product parts, management of inventory, accounting, human resources, and distribution of goods and services. Management of such organizations need efficient information systems to improve competitiveness by cost reduction and better logistics. Enterprise resource-planning systems (ERP), or enterprise systems (Brady, Monk, & Wagner, 2001; Grant, 2003; Hamilton, 2002; Hossain, Patrick, & Rashid, 2002; O’Leary, 2000), are such software systems for business management encompassing modules supporting functional areas such as planning, manufacturing, sales, marketing, distribution, accounting, finances, human resource management, project management, inventory management, service and maintenance, transportation, and e-business. The architecture of the software facilitates transparent integration of modules providing flow of information between all functions within the enterprise in a consistently visible manner. Corporate computing with ERPs allows companies to implement a single integrated system by replacing or reengineering their mostly incompatible legacy information systems.
APA, Harvard, Vancouver, ISO, and other styles
8

Hwang, Mark I. "Integrating Enterprise Systems." In Enterprise Information Systems, 1657–62. IGI Global, 2011. http://dx.doi.org/10.4018/978-1-61692-852-0.ch707.

Full text
Abstract:
In the last two decades many organizations installed enterprise resource planning (ERP) systems as a means to integrate their back-office operations. The need for integration, however, actually amplified with the advent of ERP. In addition to integrating ERP with legacy systems, consolidating multiple copies of ERP running in different business units posed major challenges. Moreover, recent strategic initiatives such as customer relationships management (CRM), supply chain management (SCM), business to consumer (B2C), and business to business (B2B) all require a free flow of information between ERP and other enterprise systems to be successful. It is, therefore, more critical than ever to plan for and implement integration projects involving ERP properly. Hwang (2005) describes the need for integrating enterprise systems in detail. He also discusses several success factors cited in practitioner journals. Since then a handful of empirical studies have been published in the scholarly literature. This article provides a review of those studies with a special focus on the success factors. A consolidated list of success factors is developed for practitioners. Promising research directions are discussed.
APA, Harvard, Vancouver, ISO, and other styles
9

Hwang, Mark I. "Integrating Enterprise Systems." In Information Resources Management, 463–69. IGI Global, 2010. http://dx.doi.org/10.4018/978-1-61520-965-1.ch218.

Full text
Abstract:
In the last two decades many organizations installed enterprise resource planning (ERP) systems as a means to integrate their back-office operations. The need for integration, however, actually amplified with the advent of ERP. In addition to integrating ERP with legacy systems, consolidating multiple copies of ERP running in different business units posed major challenges. Moreover, recent strategic initiatives such as customer relationships management (CRM), supply chain management (SCM), business to consumer (B2C), and business to business (B2B) all require a free flow of information between ERP and other enterprise systems to be successful. It is, therefore, more critical than ever to plan for and implement integration projects involving ERP properly. Hwang (2005) describes the need for integrating enterprise systems in detail. He also discusses several success factors cited in practitioner journals. Since then a handful of empirical studies have been published in the scholarly literature. This article provides a review of those studies with a special focus on the success factors. A consolidated list of success factors is developed for practitioners. Promising research directions are discussed.
APA, Harvard, Vancouver, ISO, and other styles
10

Framinan, Jose M., and Jose M. Molina. "An Overview of Enterprise Resource Planning for Intelligent Enterprises." In Business Information Systems, 60–68. IGI Global, 2010. http://dx.doi.org/10.4018/978-1-61520-969-9.ch005.

Full text
Abstract:
Enterprise resource planning systems can be defined as customizable, standard application software which includes integrated business solutions for the core processes and administrative functions (Chan & Rosemann, 2001). From an operative perspective, ERP systems provide a common technological platform unique for the entire corporation allowing the replacement of mainframes and legacy systems. This common platform serves to process automation as well as to simplify current process either by an explicit reengineering process or by the implicit adoption of the system “best practices” (Markus & Tanis, 2000). Finally, the common centralized platform allows the access to data that previously were physically or logically dispersed. The automation of the processes and the access to data allows the reduction of operating times (thus reducing operating costs) while the latter serves to a better support of business decisions (see e.g., Umble, Haft & Umble, 2003 for a detailed review of ERP benefits). ERP is considered to provide businesses with new opportunities to acquire knowledge (Srivardhana & Pawlowski, 2007), being the sources of knowledge the aforementioned best practices from the ERP, and the ERP software company’s staff during the implementation phase. At present, ERP systems are either used or implemented in a large number of enterprises. According to Genoulaz and Millet (2006), up to 74% of manufacturing companies and up to 59% of service companies use an ERP system. In addition, more than 70% of Fortune 1000 companies have implemented core ERP applications (Bingi, Sharma, Godla, 1999; Yen, Chou & Chang, 2002). The objectives for implementing an ERP system can be classified as operational, strategic, dual (operational plus strategic), or without objective (Law & Ngai, 2007). The adoption of an ERP system with operational objectives is aimed at improvement operating efficiency together with the reduction of costs, while companies implementing ERP with a strategic objective would experience a change in business processes, improving sales and market expansion. A widespread critique to ERP systems is their high total cost of ownership (Al-Mashari, Al-Mudimigh & Zairi, 2003) and hidden costs in implementation (Kwon & Lee, 2001). Besides, ERP systems impose their own logic on an organization’s strategy and culture (Davenport, 1998), so ERP adopters must adapt their business processes and organization to these models and rules. Consequently, organizations may face difficulties through this adaptation process which is usually carried out without widespread employee involvement. This may cause sore employees, sterile results due to the lack of critical information usually provided by the employees; and also late delivery, with reduced functionality, and/or with higher costs that expected (Kraemmeraard, Moeller & Boer, 2003). Additionally, some analysts have speculated that widespread adoption of the same ERP package in the same industry might lead to loss of competitive advantage due to the elimination of process innovation-based competitive advantage (Davenport, 1998). This has been observed, for instance, in the semiconductor manufacturers sector (Markus & Tanis, 2000). The early stage of ERP was carried out through Materials Requirement Planning (MRP) systems (Umble, Haft & Umble, 2003). The next generation of these systems, MRP II (Manufacturing Resources Planning), crossed the boundaries of the production functionality and started supporting not only manufacturing, but also finance and marketing decisions (Ptak & Schragenheim, 2000). Current ERP systems appeared in the beginning of the 1990’s as evolved MRP II, incorporating aspects from CIM (Computer Integrated Manufacturing) as well as from EDP (Electronic Data Processing). Therefore, ERP systems become enterprise-wide, multilevel decision support systems. ERP systems continue evolving, incorporating Manufacturing Execution Systems (MES), Supply Chain Management (SCM), Product Data Management (PDM), or Geographic Information Systems (GIS), among others (Kwon & Lee, 2001).
APA, Harvard, Vancouver, ISO, and other styles

Conference papers on the topic "Legacy Systems VS ERP systems"

1

Al-Ghofaili, Abdullah A., and Majed A. Al-Mashari. "ERP system adoption traditional ERP systems vs. cloud-based ERP systems." In 2014 Fourth International Conference on Innovative Computing Technology (INTECH). IEEE, 2014. http://dx.doi.org/10.1109/intech.2014.6927770.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Ma, Chuangtao, and Bálint Molnár. "A Legacy ERP System Integration Framework based on Ontology Learning." In 21st International Conference on Enterprise Information Systems. SCITEPRESS - Science and Technology Publications, 2019. http://dx.doi.org/10.5220/0007740602310237.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Rossi, Paola, Itai Sela, Adam Rizika, Diogenes Angelidis, Mark Duck, and Ron Morrison. "Cyberdefence of Offshore Deepwater Drilling Rigs." In Offshore Technology Conference. OTC, 2021. http://dx.doi.org/10.4043/31235-ms.

Full text
Abstract:
Abstract An alternative methodology using new preventative technology to manage cybersecurity exposure on deepwater drilling rig assets is presented. For the past two years Shell's Deepwater Wells business has been evaluating typical cyber defence approaches and undertaken cybersecurity risk assessments and penetration tests. These activities have demonstrated the challenges attaining cybersecure drilling rig environments. Whilst cyberattacks increase in frequency, adaptability, and become cheaper to launch, regulatory and liability insurance requirements are also evolving. To achieve the goal of cyber-resilience, a major Operator has collaborated with a cybersecurity firm to trial technology for rapidly and reliably protecting deepwater rigs. The paper presents aspects of the numerous challenges faced and offers a different approach using new technology applied to both supplement and accelerate the attainment of a cyber-resilient environment onboard deepwater drilling rigs. It shares the deep dive lessons learnt leading to a more comprehensive understanding of how to protect drilling rigs and their safety critical control systems. Aside from addressing technical attributes using risk vs. maturity based methods, the approach also caters to business demands of short term rig contracts, managing multi-vendor legacy systems and satisfying increasing digitalisation/remote access needs with associated reductions in overall cybersecurity CAPEX spend.
APA, Harvard, Vancouver, ISO, and other styles
4

Anthony, Richard J., John P. Clark, John M. Finnegan, and Dean Johnson. "Modifications and Upgrades to the AFRL Turbine Research Facility." In ASME Turbo Expo 2012: Turbine Technical Conference and Exposition. American Society of Mechanical Engineers, 2012. http://dx.doi.org/10.1115/gt2012-70084.

Full text
Abstract:
The Turbine Research Facility (TRF) at the Air Force Research Laboratory has undergone a two-year effort to enhance and modernize multiple systems for advanced study of unsteady turbine aerodynamics and heat transfer. This paper provides an overview of several concurrent projects to upgrade a number of facility hardware and software systems. A unique scalable high speed, high channel count data acquisition architecture is developed with modern hardware and software that expands capability while maintaining compatibility and synchronization with legacy hardware. The combination of both new and existing channels with custom Matlab-based data acquisition and processing code provides accurate and efficient signal processing and display for over 750 high speed data channels. Codes are integrated with a new Turbine Design and Analysis System that provides design CFD modeling, optimization, and post-test analysis. The paper describes a new 1+ 1/2 stage cooled high pressure research turbine that has been designed, instrumented, and tested. Initial cooled vs. uncooled data comparisons are given including fast response unsteady airfoil pressure and heat flux. This work further describes significant modification to the TRF rotordynamic drive system. Analysis and mechanical re-design have been completed to mitigate vibration effects. Facility monitoring and control upgrades are implemented to improve test situational awareness and safety. Updated cryogenic cooling hardware and software improve cooling flow delivery to HPT airfoils, platforms, and blade outer air seals. Future work includes continued research turbine testing, industry test rig collaboration, new instrumentation technology, and advanced modeling and simulation development.
APA, Harvard, Vancouver, ISO, and other styles
5

Alissa, Husam A., Kourosh Nemati, Bahgat Sammakia, Alfonso Ortega, David King, Mark Seymour, and Russell Tipton. "Steady State and Transient Comparison of Perimeter and Row-Based Cooling Employing Controlled Cooling Curves." In ASME 2015 International Technical Conference and Exhibition on Packaging and Integration of Electronic and Photonic Microsystems collocated with the ASME 2015 13th International Conference on Nanochannels, Microchannels, and Minichannels. American Society of Mechanical Engineers, 2015. http://dx.doi.org/10.1115/ipack2015-48237.

Full text
Abstract:
The perpetual increase of data processing has led to an ever increasing need for power and in turn to greater cooling challenges. High density (HD) IT loads have necessitated more aggressive and direct approaches of cooling as opposed to the legacy approach by the utilization of row-based cooling. In-row cooler systems are placed between the racks aligned with row orientation; they offer cool air to the IT equipment more directly and effectively. Following a horizontal airflow pattern and typically occupying 50% of a rack’s width; in-row cooling can be the main source of cooling in the data center or can work jointly with perimeter cooling. Another important development is the use of containment systems since they reduce mixing of hot and cold air in the facility. Both in-row technology and containment can be combined to form a very effective cooling solution for HD data centers. This current study numerically investigates the behavior of in-row coolers in cold aisle containment (CAC) vs. perimeter cooling scheme. Also, we address the steady state performance for both systems, this includes manufacturer’s specifications such as heat exchanger performance and cooling coil capacity. A brief failure scenario is then run, and duration of ride through time in the case of row-based cooling system failure is compared to raised floor perimeter cooling with containment. Non-raised floor cooling schemes will reduce the air volumetric storage of the whole facility (in this small data center cell it is about a 20% reduction). Also, the varying thermal inertia between the typical in-row and perimeter cooling units is of decisive importance. The CFD model is validated using a new data center laboratory at Binghamton University with perimeter cooling. This data center consists of one main Liebert cooling unit, 46 perforated tiles with 22% open area, 40 racks distributed on three main cold aisles C and D. A computational slice is taken of the data center to generalize results. Cold aisle C consists of 16 rack and 18 perforated tiles with containment installed. In-row coolers are then added to the CFD model. Fixed IT load is maintained throughout the simulation and steady state comparisons are built between the legacy and row-based cooling schemes. An empirically obtained flow curve method is used to capture the flow-pressure correlation for flow devices. Performance scenarios were parametrically analyzed for the following cases: (a) Perimeter cooling in CAC, (b) In-row cooling in CAC. Results showed that in-row coolers increased the efficiency of supply air flow utilization since the floor leakage was eliminated, and higher pressure build up in CAC were observed. This reduced the rack recirculation when compared to the perimeter cooled case. However, the heat exchanger size demonstrated the limitation of the in-row to maintain controlled set point at increased air flow conditions. For the pump failure scenario, experimental data provided by Emerson labs were used to capture the thermal inertia effect of the cooling coils for in-row and perimeter unit, perimeter cooled system proved to have longer ride through time.
APA, Harvard, Vancouver, ISO, and other styles
You might also be interested in the extended bibliographies on the topic 'Legacy Systems VS ERP systems' for particular source types:
Journal articles
We offer discounts on all premium plans for authors whose works are included in thematic literature selections. Contact us to get a unique promo code!

To the bibliography