Enterprise resource planning (ERP) is business management software—typically a suite of integrated applications—that a company can use to collect, store, manage and interpret data from many business activities, including:
Enterprise system software is a multi-billion dollar industry that produces components that support a variety of business functions. IT investments have become the largest category of capital expenditure in United States-based businesses over the past decade. Though early ERP systems focused on large enterprises, smaller enterprises increasingly use ERP systems.
The ERP system is considered a vital organizational tool because it integrates varied organizational systems and facilitates error-free transactions and production. However, ERP system development is different 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 developed from a manufacturing core; ERP vendors variously began assembling their packages with accounting, maintenance, and human-resource components. By the mid-1990s ERP systems addressed all core enterprise functions. Governments and non–profit organizations also began[when?] to use ERP systems.
ERP systems experienced rapid growth in the 1990s. Because of the year 2000 problem and introduction of the euro 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.
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.
Customer relationship management: 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
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. Companies that implemented industry best practices reduced time–consuming project tasks such as configuration, documentation, testing, and training. 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.
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 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[who?] uses an ERP system to manage across the organization. This company uses 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 often feature gaps 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:
The fundamental advantage of ERP is that integrated myriad businesses 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:
ERP can improve quality and efficiency of the business. By keeping a company's internal business processes running smoothly, ERP can lead to better outputs that may benefit the company, such as in customer service and manufacturing.
ERP supports upper level management by providing information for decision making.
ERP creates a more agile company that adapts better to change. ERP 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. 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.
ERP provides increased opportunities for collaboration. Data takes many forms in the modern enterprise. Documents, files, forms, audio and video, 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.
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.
Harmonization of ERP systems can be a mammoth task (especially for big companies) and requires a lot of time, planning, and money.
Recognized ERP limitations have sparked new trends in ERP application development. Development is taking place in four significant areas: more flexible ERP, Web-enabled ERP, inter-enterprise ERP, and e-business suites.
^Bidgoli, Hossein, (2004). The Internet Encyclopedia, Volume 1, John Wiley & Sons, Inc. p. 707.
^Rubina Adam, Paula Kotze, Alta van der Merwe. 2011. Acceptance of enterprise resource planning systems by small manufacturing Enterprises. In: In: Proceedings of the 1tth 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. and Tauber, D. 2012. CSFs along ERP life-cycle in SMEs: a field study. Industrial Management & Data Systems, 112(3), 360-384.
^Khosrow–Puor, Mehdi. (2006). Emerging Trends and Challenges in Information Technology Management. Idea Group, Inc. p. 865.
^Turban et al. (2008). Information Technology for Management, Transforming Organizations in the Digital Economy. Massachusetts: John Wiley & Sons, Inc., pp. 300–343. ISBN 978-0-471-78712-9
^Brown, C., and I. Vessey, "Managing the Next Wave of Enterprise Systems: Leveraging Lessons from ERP," MIS Quarterly Executive, 2(1), 2003.
^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.
^Kovacs, G. L., & Paganelli, P. (2003). "A planning and management infrastructure for large, complex, distributed projects — beyond ERP and SCM." Computers in Industry, 51(2), 165-165.
^Kraemmerand, P. et al. (2003). "ERP implementation: an integrated process of radical change and continuous learning". Production Planning & Control14 (4): 228–248.
^Vilpola, Inka Heidi (2008). "A method for improving ERP implementation success by the principles and process of user-centred design". Enterprise Information Systems2 (1): 47–76.
^ 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 Systems4 (4): 391–421.
^Yakovlev, I.V. (2002). "An ERP implementation and business process reengineering at a Small University". Educause Quarterly2: 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.
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 & Employment21 (1): 2–15. doi:10.1111/j.1468-005X.2006.00159.x.
Loh, Tee Chiat; Lenny Koh Siau Ching (September 2004). "Critical elements for a successful ERP implementation in SMEs". International Journal of Production Research42 (17): 3433–3455. doi:10.1080/00207540410001671679.