Showing posts with label Day 3 Articles. Show all posts
Showing posts with label Day 3 Articles. Show all posts

Tuesday, June 24, 2008

Day 3 Articles (Serkan Kocak)

Configuring an ERP System: Introducing Best Practices or Hampering Flexibility?

The photographic supplies distribution company is trying to install J.D. Edwards ERP system.

- The core team composed of 8 members and its first duty was to analyze business, specifying all business requirements and research an appropriate ERP package/provider
- It is hard to customize existing system and also existing system was no longer supported those are some of the reasons of changing system.
- In order to keep the task manageable, the team worked one module at a time (to have successive starts before the previous modules went live).
- First three modules took 14 months and six months for 4th one Order Management.
- Because of the complex workflow in ordering and also fair degree of flexibility of JD Edwards, it is hard to implement order module.
- Tom thoughts that if just a conceptual model is needed for pricing than accounting people can do pricing no need for marketing but then he also states the importance of marketing to decide prices.
- Pricing matrix taken out from the meeting with marketing but it is not agreed that JDE is good enough to use it in a no disciplined and no controlled area.

**************************************************************************************

A Framework for Evaluating ERP Implementation Choices

- By appropriately modifying both the ERP system and business process can be result as good implementation of the system. Sometimes software some times process needed to be changed
- Successful ERP implementation requires fit between ERP system and business process.
- Adaptation of the organization to the ERP system is also very important to have a successful implementation. Associated organizational changes should be done because ERP systems change the ways of doing jobs.

When the system is customized to fit the process = Technical Customization

Technical Customization
- Module Selection: Companies choose modules to be used, provider adapts modules to the system
- Table Configuration: according to organizational needs the chosen table types adapted to the system
- Code Modification: In order to satisfy required functionalities the source code of ERO system is changed
Module to Code; risk, and cost increase, it is not guarantied that there would be improvements.

Process Customization
- No Change
- Incremental Change : improvements only in tasks and resources
- Radical Change: fundamental rethinking and resign of some parts of business process.


ERP Customization Choices
- No Customization
- Process Adaptation
- Process Conversion
- Fit System to Process
- Mutual Adaptation
- Fit Process to System
- System Conversion
- System Conversion and Process Adaptation
- System and Process Reengineering
o Table II Customization Choices (pg 326)

Technical Change Capability
- Overall ability to customize ERP
- Understanding of default ERP system
- Ability to develop and modify large-scale software in a networked database environment
- Organizations ability to manage large scale systems development projects
o Tech. Chan. Cap. Consists of scope and depth of its ability to understand ERP

Process Change Capability
- Ability to customize business process
- Ability to design new or changed business process
- Organizations must be capable of large scale business process changes

Overall Capability
- Combination of technical change capabilities and process change capabilities, so that the total of capabilities that are explained up to now.

Day 3 Articles

Introducing Best Practices or Hampering Flexibility

- The company sells 1000 different raw items and they are repackaged into over 12000 different end products each they 300 to 500 orders are shipped in the same day.

- The company’s pricing strategy is different. They apply different discount strategies for different users. They had an 10 year old ERP system that is highly customized and that system could not meet their requirements.

- They were implementing one module at a time and there was problem in Order management. While implementing order management they expect that ERP system will calculate the prices automatically for different customers.

- When billing their customers, the firm did not use objective approach. In the article it can be seen that there is no organizational standards applied, and they want to implement ERP to that company. In order to implement ERP into pricing module there should be some standards. If there is no control, no discipline, and no organizational standard it would not be beneficial to implement ERP.

A Framework for Evaluating ERP Implementation Choices

ERP sector is one of the fastest growing sectors. While implementing ERP, companies fail most of the time. Reasons of failure is spending more money then the company can afford, being incompatible with strategic partners, conflicting with its management partners, style and structure.

Any successful ERP implementation requires a fit between ERP system and organizational processes.

Customization in ERP Implementation:

a) Technical Customization
1. Module Selection: Companies use the modules using the default configuration set by ERP vendors.
2. Table Configuration:
3. Code Modification: Source code of the ERP is changed for organizational needs.

b) Process Customization
Fit can be achieved by changing the process. Process customization is the degree which business process is changed to fit the system.

It has 3 categories: No change, incremental change, radical change.

c) ERP Customization Choices
Mutual adaptation, process adaptation, System conversion, process adaptation



Capability Requirements for ERP Customization

a) Technical Change Capability
Technical change capability is an organization’s ability to customize ERP systems. Companies can develop and modify large-scale software in a networked database environment. Other thing is an organization’s ability to manage large-scale systems development projects.

b) Process Change Capability
Organization’s overall ability to customize business processes.

Day 3 Articles by Tolga YILDIRIM

A Framework for Evaluating ERP Implementation Choices & Configuring an ERP System: Introduction Best Practices or Hampering Flexibility?

An important argument topic regarding ERP systems is the issue of the alignment between an organization’s business processes and the ERP system. The ERP solutions, in general, come with ‘best practices’ and many times, an organization simply adapts its processes to the ERP system. Sometimes, however, some portions of the ERP system are customized to use the unique business processes of the organization. The question, then, is how to find an appropriate match between customizing the ERP system and changing the business processes in the organization. The fit between business processes and ERP systems and among business processes is believed to be critical to the success of ERP implementation.

In order to ensure the fit between business processes and the ERP system, an organization can either play with its processes, or with the system, or with both. We can call customization on the ERP system as technical customization, where we call customization of business processes as process customization.

There are three possible technical customization options, which are module customization, table customization and code customization. Code customization is the most technical and detailed customization among them. Similarly, there are three possible process customization options, which are no change, incremental change and radical change. An organization should first analyze its technical change and process change capabilities in order to choose an appropriate combination of customization options. An organization with high technical capabilities can go for even code customization, where one with low technical capabilities should definitely not.

It is highly difficult to implement in environments where there is resistance to change. It takes a lot of effort to establish a fit between business processes and the ERP system, if the business processes are unique, as in Photographic Supplies Distribution Company. Different parties’ differing and conflicting interests and awareness levels on specific problems incur problems that are hard to be addressed.

Day 3 Articles - OnurOzensoy

A Framework for Evaluating ERP Implementation Choices

-Although ERP systems usage are growing rapidly, for individual companies it is challenge to implement those systems. Most common failure reasons are exceeded budget, incompatibility between the company and the vendor/its software from cultural perspective, too comprehensive organizational change and necessity to improve and upgrade ERP and its infrastructure.
-Unlike traditional software, which is fitted upon any process, ERPs are more likely to urge the organization to change its processes in accordance.
-The crucial part is to determine a system customization vs. business adaptation /re-engineering point to decrease costs, time, applicability etc.
-ERP system "best practices", which are processes dictated by he software upon business processes, are not universal but country, culture, company specific. They are readily tailored for industry, though.
-Misfits between ERP capabilities, embedded "best practices" and company processes can be classified in three categories: data, process, output.
-Technical customization vs. process customization
-Technical customization may involve module selection. Since ERPs are modular softwares a specific company may select which modules to implement. This is, however, is not effective in fitting the system on business since it just provides a minimum number of alterations.
-It may involve table configuration. Without coding and leading to cease of vendor support, a company may determine what variables are for what and modify tables and hence table-driven ERP.
-Another option is code customization. This is done by changing the source code of software. The way a system communicates with others changes or a functionality may be augmented.
-Business process is a logical path that is performed to achieve a desired output by using company resources. These processes may also be customized to fit to ERP "best practices".
-If the process customization involves changes in tasks and/or resources, it is classified as "no change" and Little effort is necessary.
-In incremental change, relationships between tasks and/or between tasks and resources change but performance indicators or logic behind the process remain unchanged. TQM applications are examples.
-Radical changes, on the other hand, involve changes in the performance measures and/or logic.
-Capability to change processes is process change capability.
-First process change capability is about understanding current business processes and environments. Second is about designing and implementing new processes. Third is about managing and coordinating large-scale process changes.
-To find a optimum point in ERP implementation, the paper prepares a 3x3 ERP Customization matrix which combines process and software customizations.
-Technical Change capability is an organizations ability to modify the software.
-The first capability is about understanding the software and recognizing built-in options and modules. The second capability is about modifying an integrated large-scale software. The third capability is about the ability to manage large-scale software modification/development projects. i.e. matching and allocation necessary resources efficiently
-This combination of change choices and capabilities result in ERP Customer Evaluation Framework, which consists of another similar 3x3 matrix. This time indicating necessary human and IT(tangible and intangible) resources.
-The paper provides a case study which is an example of controversy to "conventional wisdom". Conventional wisdom states that firms should convert or re-engineer their processes to fit ERP best practices.
-Understanding ERP implementation as a series of projects.

Configuring an ERP System: Introducing Best Practices or Hampering Flexibility?

-Implementing ERP in non-systematic environment is very difficult. ERP implementation , ordering module in particular, will cut the flexibility and since flexibility in pricing is a strategic competency of PSDC, it should have been considered at the first place.
-In PSDC there was considerable resistance to change in sales department. It makes implementation even more difficult. We also see that key people from departments should be involved in the process to increase communication and define processes better.
-PSDC war team configured tables thoroughly to introduce some discount options that were normally not available but the process was difficult and it still did not satisfy sales people. But it showed that implementations can be a means of revising departmental strategies, procedures etc.

Day3 - Article Key Points by Basak Tektemur

A Framework for Evaluating ERP Implementation Choices by Wenhong Luo and Diane M. Strong

It is important to define a connection between ERP system and organization’s business processes for an organization. There must be a good supportive system for the ERP implementation decision-making process and this paper provides a framework for a relevant support system including customization choices and the capabilities required to accomplish these choices. ERP systems are packaged software solutions rather than customized systems with built-in assumptions and some best practices. However, mostly these assumptions and practices do not match with the company and therefore, appropriate customization up to some level is required and crucial. There are various customization possibilities in order to achieve a successful ERP implementation and various capabilities required for technical ERP customization options and process change capabilities needed for process customization.

Technical Customization:
Module selection
Table configuration
Code modification

Process Customization:

No change
Incremental change
Radical Change

ERP Customization Choices:

No Customization
Process Adaptation
Process Conversion
Fit System to Process
Mutual Adaptation
Fit Process to System
System Conversion
System Conversion and Process Adaptation
System and Process Reengineering

Technical Change Capability:

Understanding of default ERP system processes, configurations and built-in options
Ability to develop and modify large-scale software
Ability to manage large-scale systems development projects

Process Change Capability:

Ability to understand company’s own existing business processes and their business environment
Ability to design new or changed business processes
Ability to manage and coordinate large-scale business process changes

Overall Capability in implementing and customizing ERP systems:

Novice Organization => Low technical change capability, low process change capability
Technician Organization => High technical change capability, low process change capability
Organizer type of organization => Low technical change capability, high process change capability
Expert Organization => Low technical change capability, high process change capability

Configuring an ERP System: Introducing Best Practices or Hampering Flexibility? by Olga Volkoff

The case is an example of an ERP implementation which is similar with Welch Allyn’s ERP implementation project that we cover in day3. Therefore many issues are similar such as the project team, who are involved in team. The team of 8 worked on implementing the order management and set up a pricing module. In the end, Tom Brown, Director of Finance and Accounting, made the best point: it is not easy, if not impossible, to make work a system like JDE in an organizational environment where there is no control, no discipline, no desire for change or resistance to change. Here, it is possible to refer lecture learning where we discussed a lot about communication and importance of communication before, during and after ERP implementation in order to release stress and anxiety, and break the resistance against ERP systems.

Day 3 Articles

A Framework for Evaluating ERP Implementation Choices

  • The paper proposes the balance of degree of customization for ERP software and processes
  • A successful ERP implementation requires fit between software and business processes
  • ERP systems are packaged, which indicates they target the market, not individual companies. So, the work with assumptions of their clients. These create
  • Differences between ERP capabilities and Company requirements are company-industry-country specific, and can be categorized as in 3 groups, data, output and process.
  • ERP projects are more riskier than IT projects because they are Company wise
  • Module Selection, table configuration and code modification are the 3 steps of ERP customization.
  • Design, implementation, stabilization, continuous improvement, and transformation are 5 steps that companies experience with ERP.
  • Primary reason to customize ERP implementation is to fit processes that are supported with ERP to ERP system. Technical customization deals with that.
  • Fit can be achieved by changing processes other than the system. Process customization deals with that
  • Modules, tables and codes may have different degree of customization, ERP customization choices depends on the degree of fit between ERP system and the company’s requirements.
  • When the degree of change and the capabilities of the companies to handle that change are low, project team’s development level must be high.
  • The research helps companies understand the customization decisions given the company’s capabilities.

Configuring an ERP System: Introducing Best Practices or Hampering Flexibility

  • Large number of orders, quick response is needed, too many employees are included.
  • Implementation team is experts in their departments, external consulting is acquired but not in terms of customization
  • Team is handling 1 department out of 6 at one time.
  • Order management is complex because of difference of products and customers.
  • Order management module was too complex to handle with only customizing the ERP software
  • So the team decided to find a way between reengineer their customer dealings (business processes) and the software together.

Day 3 Key Points of the Articles

A Framework for Evaluating ERP Implementation Choices

ERP is a packaged software and is developed for a market not an individual customer, there is a time to market pressure on the developers ad usually the developers are not related to the customers.
Therefore the fit of an ERP system to an organization is difficult.

Traditional software is tailor made and developers are involved first hand.

Best practices are hardly universal, culture and country specific applications are present

Larger, global, more complex, associated with higher risk.. ERP is regarded as a standard

Adaptation involves customization, positive correlation between initial fit and implementation success. Different types of customization are;
Technical customization
Module selection
Table configuration
Code modification

Table configuration is difficult since there are many tables, and relations and they should be understood very well and also it is time consuming however if the system is tailored this way full vendor support and ease of future upgrades remain.
Code customization has greatest flexibility, highest risk highest cost; incompatibility with higher versions.

The decision on which customization to choose depends on the capabilities both of the software and the company.

Technical change capabilities
1) understanding of ERP systems
2) ability to make desired system changes
3) ability to develop system management projects

Process change capabilities
1) understand business processes
2) ability to design and change business processes
3) ability to manage large scale change projects

Configuring an ERP System: Introducing Best Practices or Hampering Flexibility?

When configuring a system people knowing the business processes must be involved. Also in order to be able to benefit form an ERP system and avoid resistance key people from departments who will be using ERP after going live should be convinced and participate in the process.

Day 3 Articles

A framework for Evaluating ERP implementation:
  • ERP systems are packaged softwares, a little bit customization required for both erp system and business processes.
  • There are process and technical customization options and also technical and process change capabilities.
  • ERP software is developed for all market, not for an individual company. ERP implementation requires data entry and integration
  • ERP best practices are generic solutions and are not universal.
  • ERP implementations are company wide and generally contains all company business processes.
  • ERP system customizations are module selection, table configuration, code modification, another defines this by bolt-ons, screen masks, extended reporting, workflow programming, user exits, ERP programming, interface development, package code modification.
  • ERP implementations goes into 5 stages, design, implementation, stabilization, continous improvement, transformation.
TECHNICAL CUSTOMIZATION
  • module selection
  • table configuration
  • code modofocations-- which is great flexibility bu backward compatibility injures.
PROCESS CUSTOMIZATION
  • no change
  • incremental-- relationships among tasks are customized
  • radical change
CAPABILITY TO CHANGE BUSINESS PROCESS
  • comprehensive understanding of ERP vendor reasons underlying
  • developing an enterprise software or networked database software
  • managing a large scale software project
  • wide rang of understanding business processes and the evaluation of the process
  • creative thinking for redesigning business processes
  • need for large scale organizational change management
EXAMPLE CASE
  • Framework let a company resides in appropriate cell and thus figures out effort needed
  • A variety of modules implemented using customization options mentioned in the article.
Configuring an ERP System: Introducing Best Practices or Hampering Flexibility

  • Case is about implementing order management module while other modules are already implemented.
  • they formed a war team that is appropriate for such project
  • the existing software would be changed without any business reengineering.
  • They thought they had enough expertise to implement ERP by themselves.
  • In JD Edwards order processing tables are totally different identified.
  • Grouping orders, customers is needed to manage discoutns or incentives.
  • But marketing people have totally different and not organized procedures.
  • Software system needed to make standardize pricing strategy of marketing.

Day 3 - Articles key points - Seçil Akdemir

Configuring on ERP System: Introducing Best Practices or Hampering Flexibility
The key personnel from the key departments related to the ERP module should be placed in the ERP implementation project team in order to assess the suitability of the ERP system to the process.

Employees, departments and end users of ERP systems should be convinced related to the benefits of ERP implementation before the implementation starts.

ERP projects could be beneficial in terms o f assessing and determining the main business strategy of the related departments since before the implementation every department should analyze and re-examine their processes in detail in order to match the process and the system.

Highly customization of ERP systems could be risky in terms of obtaining future help and upgrades. Moreover, excessive customization could be very costly for the company.

Systems used for core activities of the firms should be examined in more detail before the implementation since they are the strategic ones.

In order to integrate the activities, business process rules must be carefully specified and data must be defined in ways that make sense for different department users.

Key department should certainly be involved in order to sustain the future health of the ERP system because if they were not involved then, they would not know the essentials of the system. Therefore, they will create new stuff that does not fit with the system.

To conclude, implementing an ERP system in an environment with no control, no discipline and no desire to change would not work.

A Framework for Evaluating ERP Implementation Choices
The most important issue in ERP implementation is catching the match between the ERP system and the business processes of the firm.

In order to match these two things, companies should assess their technical and process change capabilities and the overall capabilities.

Traditionally, systems were developed and designed in order to fit with the current business processes of the firms but now many experts suggest that it is less costly and easier to change the business processes for the ERP systems.

ERP implementation is a very challenging task since it results in large-scale organizational changes.

Every ERP system has a generic best practice in mind but as discussed in the paper these best practices are not universal and there exist some cultural differences between companies.

Sunday, June 22, 2008

Day 3 Articles

Articles:
A Framework for evaluating ERP Implementation choices:
This paper is about how to find a way to match the ERP system and the organization's business process by appropriately customizing the ERP system or the business process. Reasons for failures are interesting:
  • spending more money on ERP than the company can afford
  • being incompatible with strategic partners
  • conflicting with management style and structure
  • being overwhelmed by the required organizational changes to fit the system
  • dealing with ever changing ERP technology and its infrastructure
It says that many researches show that molding the business processes instead of changing the software is easier and less costly. ERP projects are more risky than traditional projects, since ERP projects are bigger and includes many departments, business cycles and workflows. It is found that there is a positive correlation between the initial fit and the implementation success. ERP system customization tasks are configuration, bolt-ons, screen masks, extended reporting, workflow programming, user exits, ERP programming, interface development and package code modification.
Key decision in the early stages is whether to accept the assumptions about business processes built into the system. Software development life cycle methodology is a little bit different in ERP projects, since analysis and design phases should be merged in ERP implementations.
There are two types of customization: Technical and process. Technical one is making modifications one the ERP system. Moving from module customization to code customization increases the risk and cost but it may or may not increase the benefits that much.
Moreover, technical change capability and process change capability should be considered to define the customization's scope whether it is a technical modification or not.