Reference Book: "Enterprise Systems For Management": Implementation Strategies

CHAPTER 5
IMPLEMENTATION STRATEGIES
Reference Book:
“Enterprise Systems for Management”
1
Learning Objectives
• Acquire a greater knowledge base of
– ERP components and how they work together to support business.
• Learn why third party products are needed

– to operationally round out ERP system functionality and the issues involved in
using them.
• Appreciate the impact of an ERP implementation on platform components

– such as data security, system reliability, and sustainability.
• Understand …
– implementation approaches,
– the differences between vanilla and chocolate implementations, and
– the short and long term impacts on the system and company.
2
Preview
• A start-up process involves assessing the business environment, culture, and skills of
the staff and “readiness” of the company.
• Early in the project, open and honest assessments are critical to project planning.
• It is often said that
– the ERP software is the inexpensive component of an implementation
– other surrounding systems components and resources cost more.
• With any ERP implementation strategy, all the implementation components need to be
identified and planned.
3
ERP Components
• Hardware
– An ERP system will require a powerful set of servers for development, testing, and
production environments.
– Key Resources
• Servers. High-end multiprocessor systems, several gigabytes of main memory and
several terabytes of secondary storage
• Clients. People accessing ERP systems (e.g., end-users, IT support staff, and
developers)
• Peripherals. Print servers, printers, back-up power supply equipment, and

networking hardware
4
ERP Components (Cont’d)
• Software
– A set of operating instructions and logic called programs that control and direct the
computer hardware to perform its functions.
– Key Components
• System Software. Operating system platform (e.g., Microsoft Windows Server,
Linux, and Sun Solaris)
• Database Management System (DBMS). (SAP/R3 works with IBM-DB2, Oracle,
Microsoft SQL)
• Application Software. These are programs or software utilities that help in the
development, monitoring, and integration of ERP software. Many ERP
implementations will require project management software, development software,
remote access software, and automated software for monitoring system traffic, virus
protection, etc.
5
Figure 5-1 Typical ERP Architecture
6
Table 5-1 Software Components with Oracle/PeopleSoft ERP
7
ERP Components (Cont’d)
• People Resources
– End-users. Employees, clients, vendors, and others who will ultimately use the system.
– IT specialists. Database administrators, IT operations support, developers, change

management, trainers, and others in IT.
– The project manager. Puts together a harmonious team, works with top management
in getting support and resources for the project, and champion the system and its
benefits to the end-users.
• ERP implementation team includes various sub-teams from…

– business or functional areas,
– change management,
– development,
– data migration, and system support. 8
Third Party Products
• Add-on software components either
– to make the system operational or
– to add missing functionality.
• Integration with ERP

– Integration defined as the sharing of data and data elements directly with the ERP
system without data redundancy.
• Strategic Partners
– Assist in addressing integration and interface issues with third party products
• Middleware
– Assists with the development of reporting databases that use Extract Translate and
Load tools (ETL)
• Support- Third party product support 9

Database Requirements
• For an ERP system to perform up to expectations, the update or transactional
component and the reporting component must respond in a timely fashion.
• All ERP systems are initially set up to provide

– as rapid as possible a response time for single transactions as possible;
– However, this works in contrast to strategic reporting, which generally requires
• retrieval of large amounts of data for summarization or
• large-volume output.
– These two components, transactional and report generation,
• do not work well with a single database instance and
• lead to the development of data marts, data warehouses, and ETL middleware.
10
Database Requirements
• Large ERP system implementations require
– a robust relational database system (Oracle, DB2, Sybase, Microsoft SQL).
• Selecting a relational database

– Availability of software applications using the relational database
– Availability of skilled, trained technical staff to implement and maintain the database
environment
– Overall functionality of the database itself
• Staffing and database Administration

– Options include the use of full time staff and consultants.
ERP Approaches
• Governance
– Governance should outline and define committees and workgroups that are responsible for
the different components of the implementation, their interaction and decision making.
– Components
• Technical development,
• Hardware and software installation
• Functional components
• Communications and reporting
• Change management
• Project management
• Project owners and sponsors
• Budget management
• Issue escalation process 12
ERP Approaches
• A well-defined governance structure, with a clearly understood organization in place,
helps …
– to create a comfort level for all involved as to
• how the project decisions and priorities will be addressed
Vanilla Implementation
• A vanilla implementation is when the company chooses
– not to modify or customize the system,
– but instead to change business practices to fit the system.
• Reasons to consider Vanilla Implementation.

– Businesses with relatively straightforward business practices that are not unique
– Businesses that are not skilled or experienced at building or changing systems
– E.g., For a company using a purchased ERP system where the financial component
is critical for reporting
• All of a company’s branches are running the same system in a single instance, and
entering and retrieving data in a similar fashion
• For a competitive advantage, it is important to know the ability of what and where
things are around the world with the business.
21
Modifying an ERP (Chocolate Implementation)
• Businesses that have highly skilled IT developers and a proven process for
managing modifications can choose to change the system to match their
processes
• Benefits
– A single-system instance is easier to maintain and support.
– Assessing organizational change along with modifying the system to meet the
needs of the business will help to minimize risk.
• Drawbacks
– If a system is modified, each modification will need to be analyzed in light of the
upgrade to see if it needs to be incorporated in the upgrade or removed.
– An upgrade can sometimes turn into a re-implementation, which requires more
resources and time.
22
Platform Issues
• Servers
– Servers that make up the infrastructure will need to grow as the system grows and expands
with enough storage to ensure data is quickly retrievable.
• Network
– Businesses need a reliable and secure network in place.
• Security
– Several components must be installed and implemented to ensure that the ERP system is
secure from unauthorized access.
• Disaster Recovery and Business Continuity

– Planning for a disaster and providing business continuity is a part of every ERP
implementation.
23
Implications for Management
• An implemented ERP system
– can create opportunities for a business to grow and change for the better.
• Decisions around the hardware, software, governance, methodology, and level of
modifications need to be based on the goals set out for the purchase of the ERP system.
– Two initial management decisions
1. Use of an implementation methodology
2. Whether or not to modify the system
– Management must decide on whether or not to customize
» prior to the start of the implementation process and
» it must be communicated to all on the project.
24
Summary
• Many components make up an ERP system.
– The software, as well as the surrounding operational software and third party
software are needed to ensure that the business can accomplish its goals.
• ERPs are all about change,
– both to business flows and, more importantly, to employees making it very high risk.
• Managing the risk throughout the project with a proven implementation methodology
is key to being successful.
• One key decision to make before the implementation is
– whether or not to modify the system,
– change business processes, or
– use some combination of modification and business change.
25
Summary (Cont’d)
Hardware Software
•Application servers •Operating system
•Database servers •Database management system
•Web servers •ERP system
•Personal computers •Software development
•Storage devices •System performance
•Printers •Virus protection
•Networking equipment •Report distribution
•Uninterruptible power supply •Batch run control
•Software version control
26

Reference Book: "Enterprise Systems For Management": Implementation Strategies

Uploaded by

Copyright:

Available Formats

Reference Book: "Enterprise Systems For Management": Implementation Strategies

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Reference Book: "Enterprise Systems For Management": Implementation Strategies

Uploaded by

Copyright:

Available Formats

CHAPTER 5

• Learn why third party products are needed

• Appreciate the impact of an ERP implementation on platform components

• It is often said that

– the ERP software is the inexpensive component of an implementation

– other surrounding systems components and resources cost more.

• Peripherals. Print servers, printers, back-up power supply equipment, and

– IT specialists. Database administrators, IT operations support, developers, change

• ERP implementation team includes various sub-teams from…

• Integration with ERP

• Support- Third party product support 9

• All ERP systems are initially set up to provide

• Selecting a relational database

• Staffing and database Administration

• Reasons to consider Vanilla Implementation.

• Disaster Recovery and Business Continuity

You might also like