How Small and Medium-Sized Businesses Can Plan For ERP Implementation

Introduction: Proper Planning to Reduce Risks of ERP Failure

In the first article, we discussed how a well-structured system assessment scorecard can help Small and Medium-sized Enterprises (SMEs) mitigate enterprise resource planning (ERP)[1] implementation failure risks at the system acquisition stage.

In this article, we outline certain steps SMEs can take to mitigate ERP implementation failure risks in the subsequent phase of implementation: the planning phase.

Briefly defined, the planning phase is the stage during which the organization prepares to “ERP-ize” its business. An ERP project requires much more than the mere installation of an IT software system. It requires organizational restructuring.

Generally, SMEs have to restructure their operations to satisfy the business flow parameters defined by the ERP software. These days, most ERP software packages are pre-customized to sectors according to certain industry best-practices.

The extent of organizational restructuring that is required depends on the structure of existing business processes, and on the technical and functional requirements imposed by the ERP software.

As with any complex restructuring project, ERP implementation is accompanied by certain risks of project failure. For example, failure can result from a runaway implementation that causes the project to become uneconomical. It can also result from organizational rejection of the restructured environment where such rejection impedes the achievement of the projected efficiencies.

In the following sections, we elaborate on these particular risks of implementation failure and how effective implementation planning can mitigate these risks.

Failure Risk 1: Run-Away Implementation

If an SME is planning to implement ERP, its primary reason for doing so is probably to achieve cost efficiencies. According to 2009 research by the Aberdeen Group, the need to reduce operating and administrative costs continues to be the main driver of ERP acquisition in the SME segment [2].

Since financial reasons drive the decision to implement ERP, it is critical that the implementation be completed within budget. A failure to deliver an economical implementation will mean project failure.

Since this section deals with ERP-related finance, it is important to briefly discuss some of the underlying principles.

The cost side of an ERP budget is based on a total cost of ERP ownership (TCO) calculation. TCO is the sum of the present values of system, maintenance and service costs. System and maintenance costs are fixed and largely determinable in advance.

In contrast, service costs are usually highly variable and difficult to project with accuracy. Further, service costs are proportionately significant. In 2007, service costs accounted for 45% of TCO for SMEs. Put another way, for every $100 an SME spent on ERP software, it spent an additional $81 on service [3]. As you will have probably guessed, service costs mainly reflect implementation costs.

Poor scheduling, improper resource allocation, project delays and scope creep (i.e. unplanned increases to the project’s scope) are the usual culprits for runaway implementation costs. The first three are generally well understood. Scope creep deserves a bit more attention.

During implementation, there is a holy-grail temptation to “ERP-ize” certain business processes that were not included in the original project plan. The rationale supporting a scope increase is that incremental efficiencies will be gained by “ERP-izing” the additional tasks. Implementation seems like the perfect time to widen the scope: the project is underway, consultants are on site and the teams are dedicated.

These temptations must be resisted. Implementation is seldom the right time to widen the scope (except for dealing with unforeseen items that must be addressed).

The reason the temptation must be resisted is because the argument favouring unplanned scope changes only accounts for the benefits side of the financial equation. Incremental costs must also be considered. These costs include direct service costs as well as the opportunity costs of delay. With respect to the latter, every unplanned day that the SME is unable to operate under the new system is a day of lost efficiencies.

It is fair to assume that an ERP project scope is designed to maximize the net ERP benefits (net benefits = cost efficiencies – costs). This means that all components of the project that yield a positive net benefit are accepted. It also means that all components that yield a negative net benefit (where the incremental costs exceed the incremental efficiencies) are rejected. Unplanned scope increases are typically components that would yield negative net benefits, i.e. they would be unprofitable. Since they diminish the return on ERP investment, these components should be rejected.

The following graph (omitted) depicts the relationship between a project’s gross costs, gross efficiencies and net benefits (net benefits = gross efficiencies – gross costs). As seen by the Net Benefits line, the ideal project plan is at Point A. At this point, all profitable components are accepted and all unprofitable components are rejected. Any project plan that lies to the left of Point A would mean that the plan could be profitably expanded. Any project plan to the right of Point A would mean that unprofitable components are being accepted. Scope increases are generally components that lie to the right of Point A.

The above profitability analysis explains why incremental scope changes are both unnecessary and unbeneficial to the project. As time passes, these incremental changes will either be ignored or implemented as part of a profitable optimization plan.

In summary, a well-structured plan can mitigate the financial risks associated with overly broad scope definition and scope creep. Such a plan will help keep the ERP project within budget and on time.

However, even if financial risks are mitigated, other types of failure risk still threaten the project’s success. One such risk is that certain key people will reject the new ERP system and/or the restructured business processes.

Failure Risk 2: Improperly Managed Change

Restructuring is a necessary evil. It causes the SME to undergo significant and disruptive changes. For example, the SME’s organizational and reporting structures will likely change as departments are shifted. Its operations will likely change as business processes are re-engineered. Daily tasks will likely change as manual tasks are automated. All of these changes mean that employees, management and executives will have to unlearn old habits and learn new ways of doing business.

Some people will embrace the challenges and opportunities presented by the change. These people will help move the project forward. However, there will be those who fear the uncertainties associated with change. These people may resist the project and may risk undermining its success.

Change resistors are powerful forces. Even relatively innocuous-seeming resistance can thwart success. Consider, for example, the case of a sales person at a manufacturer who decides not to input an order into the new ERP system. Instead, the employee calls the order into production – the way he had always performed the task under the old system. Although the order is now in the process queue, it was not registered in the ERP planning system.

This one omission can have severe and far-reaching consequences. Automated production planning, shop floor scheduling and material movements planning become inaccurate and unreliable. These inaccuracies will prevent sales people from providing accurate lead time quotations. As a result, sales relationships will become strained and customers will be lost. The unplanned production backlog will also cause an increase in inventory-related costs. Further, real-time performance reporting will become less accurate since the reports fail to include certain transactions. Unreliable reports will negatively impact management’s ability to make important and timely decisions.

In summary, a failure to buy-in to the new system and processes can cause the organization to fail to reap the efficiency and informational benefits of ERP. The result: an uneconomical ERP investment.

The above is but one example of a change resistor. Generally, an organization faces different groups that resist change for different reasons. Common examples of resisting forces include:

· A union that objects because its members’ job functions would change as a result of process re-engineering and automation.

· Employees who object because they have performed the same manual assembly tasks for 20 years and are afraid of or don’t want to learn new processes.

· Managers who object to donating their “A-players” to the implementation team. The loss of key performers would almost certainly have a negative impact on departmental performance.

· Executives who object to short-term business interruptions caused by the restructuring project, notwithstanding the long-term benefits. This moral hazard is caused by an incentive system that rewards the executives for short-term performance. Interruptions may cause the SME to miss compensation targets.

Fortunately, many of the various human capital forces that can sabotage an ERP-driven restructuring can be mitigated at the planning stage.

Good Planning Lessens Failure Risks

A good implementation plan accomplishes two goals:

1. It presents a clearly marked and easy-to-follow roadmap to implement the process changes and ERP system; and

2. It prepares the organization and all potentially affected stakeholders to adapt to the changed environment.

A plan that achieves these twin goals will significantly help the implementation project’s prospects for success.

Although each plan should be customized to meet the SME’s particular needs, there are certain fundamental principles that can frame the design of every project plan. These principles relate to project championship, project plan design and team formation.

Project Championship

Top management is ultimately responsible for allocating time, resources and money to the project. Its collective attitude towards the project filters down and impacts organizational commitment to the project. Consequently, top management support can make the project while its absence of support can break the project.

Given the importance of executive commitment, the project requires a top-level manager to convert the non-believing managers. This person must be both fully committed to the project and capable of influencing others’ commitment. In his capacity as project champion, this person will be responsible for ensuring that the project remains a top priority and is allocated the resources that are required. In other words, the project champion acts as an advocate who drives change, encourages perseverance and manages resistance. Ultimately, it is this person who legitimizes the project and the accompanying organizational change.

Project Plan

The project plan is a formal document that is instrumental in preventing runaway implementations and change resistance.

If done properly, the project plan helps prevent runaway implementations by memorializing the project deliverables on a timeline and allocating a specific budget to each deliverable. Each deliverable should be broken down into manageable and measurable tasks. A well conceived roadmap prevents scope creep, cost overruns and project delays.

The details of the project plan should be (to the extent necessary) transparent throughout the entire organization. Communicating the project plan will diffuse a portion of the organizational anxiety by eliminating ambiguity about the project and the future state of the organization.

In terms of its components, the main project plan should, at a minimum, include the following:

Project Charter:

This is an articulation of the project’s mission and vision. It clearly and unambiguously states the business rationale for the project.

Scope Statement

This defines the parameters of the project. The scope is broken down into measurable success factors and strategic business accomplishments that drive the intended results.

Target Dates and Costs

This sets out individual milestones. Identifiable, manageable and measurable goals are established. Target completion dates are set. Each individual milestone is valued. This step articulates the breakdown of the project into discrete sub-projects.

Project Structure and Staff Requirements

This sets out the project’s reporting structure, and how that reporting structure fits into the larger organizational structure.

The main project plan should be supported by whatever subsidiary plans are necessary. Common examples of subsidiary plans include: IT infrastructure and procurement plan, risk plan, cost and schedule plan, scope management plan, resource management plan, and communications plan. For present purposes, these last three subsidiary plans deserve a bit more attention.

Scope Management Plan

This is a contingency plan that defines the process for identifying, classifying and integrating scope changes into the project.

Resource Management Plan

This sets out individual assignments, project roles, responsibilities and reporting relationships. It also sets out the criteria for back-filling positions and modifying project teams. Further, this plan details human capital development and training plans. Finally, where necessary, it sets out the reward system used to incentivise project performance.

Communications Plan

A communications strategy is critical to manage change resistance. This plan codifies the procedures and responsibilities relating to the periodic dissemination of project-related information to the project teams and throughout the organization. Examples of common channels include email newsletters, press releases and team meetings.

A good project plan is only effective if the project teams are capable of executing the recommendations. For this reason, team formation and training are critical parts of the planning phase.

Team Formation

Successful execution requires an enabling structure. Like many well-structured organizations, an ERP project structure should contain a steering committee that has executive-level strategic responsibilities; a core team that has managerial-level delegation authority; and functional teams that are responsible for implementing the changes.

To facilitate communication and decision-making, each hierarchy level should have a member who is represented on the level below. For example, the ERP project manager should sit on both the steering committee and the core team, and certain key users should sit on both the core team and a given functional team.

The Steering Committee

The project steering committee should be comprised of the chief executive officer, the CIO, executive level business managers, and the ERP project manager. The committee has strategic-level responsibility for reviewing and approving the project plan, making changes to the plan and evaluating project progress.

The Core Team

The core team is responsible for managing the implementation project. It should be comprised of the ERP project manager, functional leads, the outside consultants and certain key end-users.

Functional leads should be top-performers who are reassigned to the implementation project on a full-time basis. They should be experts in their respective departments, should understand other departments’ business processes and should be knowledgeable about industry best practices. In many cases, functional leads will have to be backfilled in their day-to-day jobs.

During the planning phase, the core team is trained on the fundamentals of ERP theory and on the particulars of the ERP software. The purpose of the training is to ensure that the core team is capable of managing the development of the new business processes.

Functional Teams

These teams are responsible for implementing the business process changes in their respective functional departments. Each functional team is comprised of a core team key end-user, select end-users that cover all of the functional unit’s business processes, and a functional consultant with an understanding of the ERP software.

Organizing committed and capable teams is critical to the project’s success. The project teams will be responsible for managing the implementation and helping the organization adapt to the new business environment.

Conclusion

ERP implementation is a complex project that involves significant operational restructuring. The restructuring is accompanied by certain risks of project failure, including runaway implementation and resistance to change.

Fortunately, an SME can mitigate many of the ERP failure risks by properly planning for the project. At a minimum, proper planning requires a project champion to secure executive buy-in, the preparation and communication of a project plan that breaks the project down into manageable sub-projects, and the assembly of strong teams capable of executing the project.

[1] Briefly, an ERP system is intended to electronically integrate an organization’s functional areas, administrative areas, processes and systems.

[2] Jutras, C. (2009). ERP in the Midmarket 2009: Managing the Complexities of a Distributed Environment. Boston: Aberdeen Group.

[3] Jutras, C. (2007). The Total Cost of ERP Ownership in Mid-Sized Companies. Boston: Aberdeen Group.

ERP (Enterprise Resource Planning)

The emergence of the Internet, evolving customer demands, pressure to accelerate business process, and the need to establish more collaborative relationships with key suppliers and business partners are all pushing organizations towards ERP solution. So, what is ERP?

Enterprise Resource Planning (ERP) is described as an “information system package that integrates information and information based processes within and across functional areas in an organization” [1].

Traditional stand-alone applications were designed for specific customers, with limited functionality, and isolated from other applications. On the contrary, ERP is a business tool that integrates all the applications required by an organization as a whole, and connects the organization to other enterprises in a network form. It is usually compromised of several modules such as: a financial module, a distribution module, or a production module. Today, ERP have added new functions such as supply chain management, product data management, electronic commerce and warehouse management. Thus, ERP opens a window of opportunity for businesses to compete globally, respond to competitive pressures, and increase revenue.

ERP Characteristics & Basic Operations:

ERP facilitates company-wide Integrated Information System covering all functional areas like Manufacturing, Selling and distribution, Payables, Receivables, Inventory, Accounts, Human resources, Purchases etc.

– ERP performs core business activities and increases customer service satisfaction.

– ERP facilitates information flow across different sections or departments of the organisation.

– ERP bridges the gap between business partners allowing ongoing collaboration.

– ERP is a good solution for better project management.

– ERP is built as open system architecture, meaning it allows automatic introduction of the latest technologies such as: Electronic Fund Transfer (EFT), Electronic Data Interchange (EDI), Internet, Intranet, Video conferencing, E-Commerce etc.

– ERP not only addresses the current requirements of the company but also provides the opportunity of continually improving and refining business processes.

– ERP provides business intelligence tools like Decision Support Systems (DSS), Executive Information System (EIS), Reporting, Data Mining and Early Warning Systems (Robots) for enabling people to make better decisions and thus improve their business processes.

– ERP tracks a wide range of events in an organisation, and plans for future activities based on these events.

ERP driving forces:

1. The need to increase supply chain efficiency.

2. The need to increase customer access to products or services.

3. The need to reduce operating costs.

4. The need to respond more rapidly and flexibly to a changing market place.

Global ERP Implementation:

Historically, most international companies have managed their systems on regional basis, because there was no single solution that was globally acceptable.

In today’s dynamic business environment there is a strong need for the organisations to become globally competitive. The key for success lies in customer satisfaction, through understanding customer needs, and providing quality goods and services in the shortest time possible. To support a global outlook, many firms implemented or are in the process of implementing Enterprise Resource Planning (ERP) Systems, in order to improve level of coordination among national entities of the same firm, and also with business partners. However, to achieve this level of coordination it is important to have a global market strategy, a common IT infrastructure, and business processes in place.

An analysis of past global ERP projects, highlight on the importance of aligning organisation structure with business process and business strategy with IT strategy in order to compete in the international market. ‘Threads’ is a good example of an international company that replaced its legacy system with ERP. ‘Threads’ had a national organisation structure that operates on country by country basis.

To obtain a global view ‘Threads’ decided that its time for change by transforming the company from a local to a global geographical perspective. Hence, making Europe as one market for their business operations, and also ensuring competitiveness through a focus on the quality, price, and customer service. The intended organization structure and supporting global ERP is shown in [2].

Enabling Technologies:Traditional ERP systems required sophisticated and expensive information technology infrastructure such as, mainframe computers. Nowadays, with the advancement of information technology and the cost reduction of computers it becomes possible for SME’s to think about ERP Systems. Moreover, the power of Three Tier Client Server architecture and scalable relational data base management has made it easier to deploy ERP Systems in multiple locations.

Implementation of ERP

Implementing an ERP project is a process consisted of many phases. Following, a step by step approach will simplify the process and is more likely to yield a better result. The normal steps involved in the implementation of an ERP are as below:

o Project Planning

o Business & Operational analysis including Gap analysis

o Business Process Reengineering

o Installation and configuration

o Project team training

o Business Requirement mapping

o Module configuration

o System interfaces

o Data conversion

o Custom Documentation

o End user training

o Acceptance testing

o Post implementation/Audit support

In short, implementing ERP can transform the way an organization conducts business. It helps the enterprise link its resources, utilise and allocate them in the best possible manner and control them on real time basis. For instance, in the case of ‘Threads’ the transformation from Legacy system to ERP system resulted in a reduction of data redundancy, reduction of overheads, an increase in customer responsiveness and customer service levels throughout the firm. This has been facilitated by implementing a common global ERP system throughout its European operation.

Critical factors for Success of ERP:

The successful implementation of an ERP project requires management to plan carefully, and have all needed human and financial resources in place. Below is a list of the main critical factors for the success of ERP:

1- Top Management Support:

Among the most important factors for the success of ERP project is the top management commitment and support. The role of top management includes, developing an understanding of the capabilities and limitation of the proposed system, setting goals, and communicating the corporate IT Strategy to all employees [3].

2- Project Management:

Another important factor for the success of ERP is managing the project life cycle from initiating to closing phase. The Project Manager (PM) has sole responsibility and authority for planning and controlling the project scope to meet the deliverables in the given time frame and budget.

3- Selection of the appropriate package:

Selecting the appropriate package is an important managerial decision. Analysing and evaluating the organisation needs and processes help in taking the right choice that best suits the business environment. A careful selection of the right package results in minimum modification and successful implementation and use. On the hand, selecting the wrong software may mean a commitment to architecture and application that do not fit the organizational strategic goal or business process [3].

4- User training and education:

A quality implementation can de derailed by poorly trained employees who do not know how to properly operate the ERP system. The knowledge transfer to employees is arguably more important than the quality of the system. For that reason, companies should use consultants to run training sessions on how the system works, and how they relate to the business process.

5- Business Process Re-engineering:

Business Process Reengineering is a pre-requisite for going ahead with implementing ERP system. An in depth BPR study has to be done before taking up ERP. Business Process Reengineering brings out deficiencies of the existing system and attempts to maximize productivity through restructuring and re-organizing the human resources as well as divisions and departments in the organisation

6- Dedicated Resources:

One of the main critical factors for ERP success is determining the human and financial resources needed to implement the system. This should be done at an early stage of the project. Failing to commit the required resources often result in schedule and cost overdue.

7- Project Team Competence:

Another key element of ERP success or failure is related to the knowledge, skills, abilities, and experience of the project manager and team members. The project team should work in a coordinated way to achieve one goal. Hence, it is vital for team members to have technical and business skills to complement their work.

8- Clear goals and objectives:

Setting clear goals and Identifying the Objectives of the ERP Project is the third most critical success factor. The initial phase of any project should begin with a conceptualization of the goals and possible ways to accomplish these goals. It is important to set the goals of the project before even seeking top management support [3].

9- Ongoing Vendor Support:

Ongoing vendor support represents an important factor with any software package. ERP systems require ongoing vendor support to keep them up to date with the latest modules and version. In addition to this, vendor support provides technical assistance, and maintenance.

10- Interdepartmental communication:

Good communication is a key component for the success of ERP. Hence, it is essential to communicate effectively between team members and the rest of the organization, in order to keep everything working properly.

To conclude, ERP implementation could become a complex and risky process, if not managed properly. Organizations need to identify the critical issues that affect the implementation process. Such as: selecting the appropriate software package, securing commitment and support from top management, cooperation from business partners, having adequate knowledge among team members, training employees and keeping them informed. All those issues and other more can minimize the failure of ERP project and maximizes the success of ERP implementation.

References:

[1] Kumar, K. and Van Hillegersberg, J. ERP Experiences and Evolution, Communication of the ACM, (43:4), pp. 23- 26, 2000.

[2] Holland C. and Light B. (1999) Global Enterprise Resource Planning Implementation Retrieved August, 27, 2005 from: http://csdl2.computer.org/comp/proceedings/hicss/1999/0001/07/00017016.PDF

[3] Somers T.M., and Nelson K. (2001), The Impact of Critical Success Factors across the Stages of Enterprise Resource Planning Implementations, published in 34th Hawaii International Conference on System Sciences 2001, Hawaii

[4] Holland C.P, and Light B. (1999), A Critical Success factor Model for ERP implementation, IEEE Software, May/June 1999, pp. 30-36

[5] Hammer M. and Champy J. (1994) Reengineering the Corporation, New York, Harper Business.

[6] Kerchevak M. (2005) Five Steps to an ERP Solution, Retrieved September 3, 2005 from: http://archives.tcm.ie/businesspost/2005/06/05/story5254.asp

[7] Robinson S. (2004) A Developer’s Overview of ERP, Retrieved September 1, 2005 from: http://www.developer.com/design/article.php/3446551

Benefits Of Enterprise Resource Planning (ERP) Systems

Business owners demand instant and low-cost solutions that are easy to upkeep and maximize return on their investment. Enterprise resource planning – ERP systems fit the bill perfectly and hence have become popular with many businesses, especially in implementing the the resource efficiency lessons learned during recent recessionary periods. In fact, now not only multi-million dollar businesses that deploy such systems, but also small-sized units and even start-ups.

So how will your business benefit from an Enterprise resource planning software system? Here are the lures that have prompted business owners to walk the ERP road:

Reduction in Operational Costs: Deploying an ERP software system holds benefits for all three process streams of an organization-strategic planning, production control, and management control. Such a system integrates varied business processes across the myriad of departments in an organization into a single and comprehensive information repository. This integration makes communication smooth in-between departments and this improved communication, in turn, imparts a degree of efficiency in the production, planning, and decision making processes. This efficiency is manifested in various ways-lower production costs, less marketing expenses incurred, and less need for securing help desk support.

Facilitating Inventory Management: Businesses these days are located in various geographical regions. Administrative units, warehouses, and back-end support offices are spread all over the world and this leads to complexities in managing the inventory in these locations. An Enterprise Resource Planning (ERP) software system lets you maintain detailed inventory records, keep a track of materials and lot, thus simplifying your inventory transactions. With an ERP system empowering you, you can keep inventory volumes at optimum levels.

Streamlining Day-to-Day Management: An Enterprise Resource Planning (ERP) system streamlines the process involved in carrying out the day-to-day tasks of managing a business. This is primarily because an ERP software system facilitates the creation of a backbone data warehousing system. This makes it easy for the employees of an organization to easily gain access to updated business-related data. This ready access to data eases the process of decision-making and exerting managerial control over key factors of production.

Support to Resource Planning: Resource planning forms an integral component of the strategic planning process that is carried out in an organization. Enterprise Resource Planning (ERP) systems are therefore designed to take on the tasks involved in planning resources effectively and efficiently, and over the years, this functionality has improved in leaps and bounds.

So where can you obtain an Enterprise Resource planning (ERP) software system that will provide you with all these strategic benefits? ABAS Software Partner has ERP software solutions that will take care of the varied resource planning needs of your business.

Exit mobile version