Enterprise system software is a multibillion-dollar industry that produces components supporting a variety of business functions. IT investments have become the largest category of capital expenditure in United States-based businesses over the past[which?] decade. Though early ERP systems focused on large enterprises, smaller enterprises increasingly use ERP systems.
The ERP system integrates varied organizational systems and facilitates error-free transactions and production, thereby enhancing the organization's efficiency. However, developing an ERP system differs from traditional system development.
ERP systems run on a variety of computer hardware and network configurations, typically using a database as an information repository.
Not all ERP packages are developed from a manufacturing core; ERP vendors variously began assembling their packages with finance-and-accounting, maintenance, and human-resource components. By the mid-1990s ERP systems addressed all core enterprise functions. Governments and non-profit organizations also began to use ERP systems.
ERP systems experienced rapid growth in the 1990s. Because of the year 2000 problem and the introduction of the euro that disrupted legacy systems, many companies took the opportunity to replace their old systems with ERP.
"ERP II" was coined in 2000 in an article by Gartner Publications entitled ERP Is Dead--Long Live ERP II. It describes web-based software that provides real-time access to ERP systems to employees and partners (such as suppliers and customers). The ERP II role expands traditional ERP resource optimization and transaction processing. Rather than just manage buying, selling, etc.--ERP II leverages information in the resources under its management to help the enterprise collaborate with other enterprises.
ERP II is more flexible than the first generation ERP. Rather than confine ERP system capabilities within the organization, it goes beyond the corporate walls to interact with other systems. Enterprise application suite is an alternate name for such systems. ERP II systems are typically used to enable collaborative initiatives such as supply chain management (SCM), customer relationship management (CRM), and business intelligence (BI) among business partner organizations through the use of various e-business technologies.
Developers now make more effort to integrate mobile devices with the ERP system. ERP vendors are extending ERP to these devices, along with other business applications. Technical stakes of modern ERP concern integration--hardware, applications, networking, supply chains. ERP now covers more functions and roles--including decision making, stakeholders' relationships, standardization, transparency, globalization, etc.
ERP systems typically include the following characteristics:
An integrated system
Operates in (or near) real time
A common database that supports all the applications
A consistent look and feel across modules
Installation of the system with elaborate application/data integration by the Information Technology (IT) department, provided the implementation is not done in small steps
Customer relationship management (CRM): sales and marketing, commissions, service, customer contact, call center support – CRM systems are not always considered part of ERP systems but rather business support systems (BSS)
Data services : various "self-service" interfaces for customers, suppliers and/or employees
Government resource planning (GRP) is the equivalent of an ERP for the public sector and an integrated office automation system for government bodies. The software structure, modularization, core algorithms and main interfaces do not differ from other ERPs, and ERP software suppliers manage to adapt their systems to government agencies.
Both system implementations, in private and public organizations, are adopted to improve productivity and overall business performance in organizations, but comparisons (private vs. public) of implementations shows that the main factors influencing ERP implementation success in the public sector are cultural.
Most ERP systems incorporate best practices. This means the software reflects the vendor's interpretation of the most effective way to perform each business process. Systems vary in how conveniently the customer can modify these practices. In addition, best practices reduced risk by 71% compared to other software implementations.
Use of best practices eases compliance with requirements such as IFRS, Sarbanes-Oxley, or Basel II. They can also help comply with de facto industry standards, such as electronic funds transfer. This is because the procedure can be readily codified within the ERP software and replicated with confidence across multiple businesses who share that business requirement.
Connectivity to plant floor information
ERP systems connect to real-time data and transaction data in a variety of ways. These systems are typically configured by systems integrators, who bring unique knowledge on process, equipment, and vendor solutions.
Direct integration--ERP systems have connectivity (communications to plant floor equipment) as part of their product offering. This requires that the vendors offer specific support for the plant floor equipment their customers operate. ERP vendors must be experts in their own products and connectivity to other vendor products, including those of their competitors.
Database integration--ERP systems connect to plant floor data sources through staging tables in a database. Plant floor systems deposit the necessary information into the database. The ERP system reads the information in the table. The benefit of staging is that ERP vendors do not need to master the complexities of equipment integration. Connectivity becomes the responsibility of the systems integrator.
Enterprise appliance transaction modules (EATM)--These devices communicate directly with plant floor equipment and with the ERP system via methods supported by the ERP system. EATM can employ a staging table, web services, or system-specific program interfaces (APIs). An EATM offers the benefit of being an off-the-shelf solution.
Custom-integration solutions--Many system integrators offer custom solutions. These systems tend to have the highest level of initial integration cost, and can have a higher long term maintenance and reliability costs. Long term costs can be minimized through careful system testing and thorough documentation. Custom-integrated solutions typically run on workstation or server-class computers.
ERP's scope usually implies significant changes to staff work processes and practices. Generally, three types of services are available to help implement such changes--consulting, customization, and support. Implementation time depends on business size, number of modules, customization, the scope of process changes, and the readiness of the customer to take ownership for the project. Modular ERP systems can be implemented in stages. The typical project for a large enterprise takes about 14 months and requires around 150 consultants. Small projects can require months; multinational and other large implementations can take years.Customization can substantially increase implementation times.
Besides that, information processing influences various business functions e.g. some large corporations like Wal-Mart use a just in time inventory system. This reduces inventory storage and increases delivery efficiency, and requires up-to-date data. Before 2014, Walmart used a system called Inforem developed by IBM to manage replenishment.
Implementing ERP typically requires changes in existing business processes. Poor understanding of needed process changes prior to starting implementation is a main reason for project failure. The difficulties could be related to the system, business process, infrastructure, training, or lack of motivation.
It is therefore crucial that organizations thoroughly analyze business processes before they implement ERP software. Analysis can identify opportunities for process modernization. It also enables an assessment of the alignment of current processes with those provided by the ERP system. Research indicates that risk of business process mismatch is decreased by:
Linking current processes to the organization's strategy
ERP implementation is considerably more difficult (and politically charged) in decentralized organizations, because they often have different processes, business rules, data semantics, authorization hierarchies, and decision centers. This may require migrating some business units before others, delaying implementation to work through the necessary changes for each unit, possibly reducing integration (e.g., linking via Master data management) or customizing the system to meet specific needs.
A potential disadvantage is that adopting "standard" processes can lead to a loss of competitive advantage. While this has happened, losses in one area are often offset by gains in other areas, increasing overall competitive advantage.
Configuring an ERP system is largely a matter of balancing the way the organization wants the system to work with the way it was designed to work. ERP systems typically include many settings that modify system operations. For example, an organization can select the type of inventory accounting--FIFO or LIFO--to use; whether to recognize revenue by geographical unit, product line, or distribution channel; and whether to pay for shipping costs on customer returns.
Two tier enterprise resource planning
Two-tier ERP software and hardware lets companies run the equivalent of two ERP systems at once: one at the corporate level and one at the division or subsidiary level. For example, a manufacturing company could use an ERP system to manage across the organization using independent global or regional distribution, production or sales centers, and service providers to support the main company's customers. Each independent center (or) subsidiary may have its own business models, workflows, and business processes.
Given the realities of globalization, enterprises continuously evaluate how to optimize their regional, divisional, and product or manufacturing strategies to support strategic goals and reduce time-to-market while increasing profitability and delivering value. With two-tier ERP, the regional distribution, production, or sales centers and service providers continue operating under their own business model--separate from the main company, using their own ERP systems. Since these smaller companies' processes and workflows are not tied to main company's processes and workflows, they can respond to local business requirements in multiple locations.
Factors that affect enterprises' adoption of two-tier ERP systems include:
Manufacturing globalization, the economics of sourcing in emerging economies
Potential for quicker, less costly ERP implementations at subsidiaries, based on selecting software more suited to smaller companies
Extra effort, (often involving the use of Enterprise application integration) is required where data must pass between two ERP systems Two-tier ERP strategies give enterprises agility in responding to market demands and in aligning IT systems at a corporate level while inevitably resulting in more systems as compared to one ERP system used throughout the organization.
ERP systems are theoretically based on industry best practices, and their makers intend that organizations deploy them "as is". ERP vendors do offer customers configuration options that let organizations incorporate their own business rules, but gaps in features often remain even after configuration is complete.
ERP customers have several options to reconcile feature gaps, each with their own pros/cons. Technical solutions include rewriting part of the delivered software, writing a homegrown module to work within the ERP system, or interfacing to an external system. These three options constitute varying degrees of system customization--with the first being the most invasive and costly to maintain. Alternatively, there are non-technical options such as changing business practices or organizational policies to better match the delivered ERP feature set. Key differences between customization and configuration include:
Customization is always optional, whereas the software must always be configured before use (e.g., setting up cost/profit center structures, organizational trees, purchase approval rules, etc.).
The software is designed to handle various configurations, and behaves predictably in any allowed configuration.
The effect of configuration changes on system behavior and performance is predictable and is the responsibility of the ERP vendor. The effect of customization is less predictable. It is the customer's responsibility, and increases testing activities.
Configuration changes survive upgrades to new software versions. Some customizations (e.g., code that uses pre-defined "hooks" that are called before/after displaying data screens) survive upgrades, though they require retesting. Other customizations (e.g., those involving changes to fundamental data structures) are overwritten during upgrades and must be re-implemented.
Data migration is the process of moving, copying, and restructuring data from an existing system to the ERP system. Migration is critical to implementation success and requires significant planning. Unfortunately, since migration is one of the final activities before the production phase, it often receives insufficient attention. The following steps can structure migration planning:
Identify the data to be migrated.
Determine the migration timing.
Generate data migration templates for key data components
Freeze the toolset.
Decide on the migration-related setup of key business accounts.
Often, data migration is incomplete because some of the data in the existing system is either incompatible or not needed in the new system. As such, the existing system may need to be kept as an archived database to refer back to once the new ERP system is in place.
The most fundamental advantage of ERP is that the integration of a myriad of business processes saves time and expense. Management can make decisions faster and with fewer errors. Data becomes visible across the organization. Tasks that benefit from this integration include:
Provides a comprehensive enterprise view (no "islands of information"), making real-time information available to management anywhere, anytime to make proper decisions
Protects sensitive data by consolidating multiple security systems into a single structure
ERP creates a more agile company that adapts better to change. It also makes a company more flexible and less rigidly structured so organization components operate more cohesively, enhancing the business--internally and externally.
ERP can improve data security in a closed environment. A common control system, such as the kind offered by ERP systems, allows organizations the ability to more easily ensure key company data is not compromised. This changes, however, with a more open environment, requiring further scrutiny of ERP security features and internal company policies regarding security.
ERP provides increased opportunities for collaboration. Data takes many forms in the modern enterprise, including documents, files, forms, audio and video, and emails. Often, each data medium has its own mechanism for allowing collaboration. ERP provides a collaborative platform that lets employees spend more time collaborating on content rather than mastering the learning curve of communicating in various formats across distributed systems.
ERP offers many benefits such as standardization of common processes, one integrated system, standardized reporting, improved key performance indicators (KPI), and access to common data. One of the key benefits of ERP; the concept of integrated system, is often misinterpreted by the business. ERP is a centralized system that provides tight integration with all major enterprise functions be it HR, planning, procurement, sales, customer relations, finance or analyrics, as well to other connected application functions. In that sense ERP could be described as "Centralized Integrated Enterprise System (CIES)"
Customization can be problematic. Compared to the best-of-breed approach, ERP can be seen as meeting an organization's lowest common denominator needs, forcing the organization to find workarounds to meet unique demands.
ERP can cost more than less integrated or less comprehensive solutions.
High ERP switching costs can increase the ERP vendor's negotiating power, which can increase support, maintenance, and upgrade expenses.
Overcoming resistance to sharing sensitive information between departments can divert management attention.
Integration of truly independent businesses can create unnecessary dependencies.
Extensive training requirements take resources from daily operations.
Harmonization of ERP systems can be a mammoth task (especially for big companies) and requires a lot of time, planning, and money.
Critical challenges include disbanding the project team very quickly after implementation, interface issues, lack of proper testing, time zone limitations, stress, offshoring, people's resistance to change, a short hyper-care period, and data cleansing.
The term "postmodern ERP" was coined by Gartner in 2013, when it first appeared in the paper series "Predicts 2014". According to Gartner's definition of the postmodern ERP strategy, legacy, monolithic and highly customized ERP suites, in which all parts are heavily reliant on each other, should sooner or later be replaced by a mixture of both cloud-based and on-premises applications, which are more loosely coupled and can be easily exchanged if needed.
The basic idea is that there should still be a core ERP solution that would cover most important business functions, while other functions will be covered by specialist software solutions that merely extend the core ERP. This concept is similar to the so-called best-of-breed approach to software execution, but it shouldn't be confused with it. While in both cases, applications that make up the whole are relatively loosely connected and quite easily interchangeable, in the case of the latter there is no ERP solution whatsoever. Instead, every business function is covered by a separate software solution.
There is, however, no golden rule as to what business functions should be part of the core ERP, and what should be covered by supplementary solutions. According to Gartner, every company must define their own postmodern ERP strategy, based on company's internal and external needs, operations and processes. For example, a company may define that the core ERP solution should cover those business processes that must stay behind the firewall, and therefore, choose to leave their core ERP on-premises. At the same time, another company may decide to host the core ERP solution in the cloud and move only a few ERP modules as supplementary solutions to on-premises.
The main benefits that companies will gain from implementing postmodern ERP strategy are speed and flexibility when reacting to unexpected changes in business processes or on the organizational level. With the majority of applications having a relatively loose connection, it is fairly easy to replace or upgrade them whenever necessary. In addition to that, following the examples above, companies can select and combine cloud-based and on-premises solutions that are most suited for their ERP needs. The downside of postmodern ERP is that it will most likely lead to an increased number of software vendors that companies will have to manage, as well as pose additional integration challenges for the central IT.
^Almajali, Dmaithan (2016). "Antecedents of ERP systems implementation success: a study on Jordanian healthcare sector". Journal of Enterprise Information Management. 29 (4): 549-565. doi:10.1108/JEIM-03-2015-0024.
^Rubina Adam, Paula Kotze, Alta van der Merwe. 2011. Acceptance of enterprise resource planning systems by small manufacturing Enterprises. In: Proceedings of the 13th International Conference on Enterprise Information Systems, edited by Runtong Zhang, José Cordeiro, Xuewei Li, Zhenji Zhang and Juliang Zhang, SciTePress, p. 229 - 238
^Shaul, L.; Tauber, D. (2012). "CSFs along ERP life-cycle in SMEs: a field study". Industrial Management & Data Systems. 112 (3): 360-384. doi:10.1108/02635571211210031.
Khosrow-Puor, Mehdi. (2006). Emerging Trends and Challenges in Information Technology Management. Idea Group, Inc. p. 865.
^Charles Møller (August 1, 2005). "ERP II: a conceptual framework for next-generation enterprise systems?". Journal of Enterprise Information Management. 18 (4): 483-497. doi:10.1108/17410390510609626. ISSN1741-0398.
^Ruhi, Umar (July 1, 2016). "An experiential learning pedagogical framework for enterprise systems education in business schools". The International Journal of Management Education. 14 (2): 198-211. doi:10.1016/j.ijme.2016.04.006.
^Shaul, L.; Tauber, D. (2013). "Critical Success Factors in Enterprise Resource Planning Systems: Review of the Last Decade". ACM Computing Surveys. 45 (4): 1-39. doi:10.1145/2501654.2501669.
^Sheilds, Mureell G., E-Business and ERP: Rapid Implementation and Project Planning. (2001) John Wiley and Sons, Inc. p. 9-10.
Yunliang, Xiongtao, Qing, Jing and Ning (2010) "Design of E-Government Information Management Platform Based on SOA Framework", 2010 First International Conference on Networking and Distributed Computing, Hangzhou, doi:10.1109/ICNDC.2010.42.
^Allen, Kern and Havenhand (2000) "ERP Critical Success Factors: an exploration of the contextual factors in public sector institutions", Proceedings of the 35th Hawaii International Conference on System Sciences.
^Chang, Gable, Smythe and Timbrell (2000) "A Delphi examination of public sector ERP implementation issues" Proceedings of ICIS.
^Wingreen, Maryam and Hritik (2014) "An Investigation into Enterprise Resource Planning Implementation Success: Evidence from Private and Public Sector Organizations", PACIS 2014/339.
^Shafqat, Enhong and Faisal (2012), "Enterprise Resource Planning - 'real blessing' or 'a blessing in disguise': an exploration of the contextual factors in public sector"
^Coelho, Cunha; Meirelles (2015). The client-consultant relationship in the implementation of ERP in government: exploring the dynamic between power and knowledge. DGO. p. 140. doi:10.1145/2757401.2757405. ISBN9781450336000.
^Monk, Ellen and Wagner, Brett."Concepts in Enterprise Resource Planning" 3rd.ed.Course Technology Cengage Learning.Boston, Massachusetts.2009
^"Enhanced Project Success Through SAP Best Practices - International Benchmarking Study". ISBN1-59229-031-0.
^Turban et al. (2008). Information Technology for Management, Transforming Organizations in the Digital Economy. Massachusetts: John Wiley & Sons, Inc., pp. 300-343. ISBN978-0-471-78712-9
^Brown, C.; Vessey, I. (2003). "Managing the Next Wave of Enterprise Systems: Leveraging Lessons from ERP". MIS Quarterly Executive. 2 (1).
^King. W., "Ensuring ERP implementation success," Information Systems Management, Summer 2005.
^Yusuf, Y., A. Gunasekaran, and M. Abthorpe, "Enterprise Information Systems Project Implementation: A Case Study of ERP in Rolls-Royce," International Journal of Production Economics, 87(3), February 2004.
^Kraemmerand, P.; et al. (2003). "ERP implementation: an integrated process of radical change and continuous learning". Production Planning & Control. 14 (4): 228-248. doi:10.1080/0953728031000117959.
^Vilpola, Inka Heidi (2008). "A method for improving ERP implementation success by the principles and process of user-centred design". Enterprise Information Systems. 2 (1): 47-76. doi:10.1080/17517570701793848.
^ abFryling, Meg (2010). "Estimating the impact of enterprise resource planning project management decisions on post-implementation maintenance costs: a case study using simulation modelling". Enterprise Information Systems. 4 (4): 391-421. Bibcode:2010EntIS...4..391F. doi:10.1080/17517575.2010.519785.
^Yakovlev, I.V. (2002). "An ERP implementation and business process reengineering at a Small University". Educause Quarterly. 2: 52-57.
^Fryling, Meg (2010). Total Cost of Ownership, System Acceptance and Perceived Success of Enterprise Resource Planning Software: Simulating a Dynamic Feedback Perspective of ERP in the Higher Education Environment. ProQuest Dissertations and Theses database. p. 403. ISBN978-1-109-74428-6.
^O'Brien, James (2011). Management Information Systems(MIS). New York: McGraw-Hill, Irwin. p. 324.
^She, W.; Thuraisingham, B. (2007). "Security for Enterprise Resource Planning Systems". Information Systems Security. 16 (3): 152-163. doi:10.1080/10658980701401959.
^Menon, Sreekumar (July 2019). "Benefits and Process Improvements for ERP Implementation: Results from an Exploratory Case Study". International Business Research. 12(8): 124-132. doi:10.5539/ibr.v12n8p124 – via Canadian Center of Science and Education.
^Menon, S.A.; Muchnick, M.; Butler, C.; Pizur, T. (June 2019). "Critical Challenges in Enterprise Resource Planning (ERP) Implementation". International Journal of Business and Management. 14(7): 54-69. doi:10.5539/ijbm.v14n7p54 – via Canadian Center of Science and Education.
Grant, David; Richard Hall; Nick Wailes; Christopher Wright (March 2006). "The false promise of technological determinism: the case of enterprise resource planning systems". New Technology, Work & Employment. 21 (1): 2-15. doi:10.1111/j.1468-005X.2006.00159.x.
Head, Simon (2005). The New Ruthless Economy. Work and Power in the Digital Age. Oxford UP. ISBN978-0-19-517983-5.
Lequeux, Jean-Louis (2008). Manager avec les ERP, Architecture Orientée Services (SOA) (in French). Paris: Ed. d'Organisation. ISBN978-2-212-54094-9.
Loh, Tee Chiat; Lenny Koh Siau Ching (September 2004). "Critical elements for a successful ERP implementation in SMEs". International Journal of Production Research. 42 (17): 3433-3455. doi:10.1080/00207540410001671679.
Manage research, learning and skills at IT1me. Create an account using LinkedIn to manage and organize your IT knowledge. IT1me works like a shopping cart for information -- helping you to save, discuss and share.