Managing An ERP Project: © Prentice Hall, 2005: Enterprise Resource Planning, 1 Edition by Mary Sumner
Managing An ERP Project: © Prentice Hall, 2005: Enterprise Resource Planning, 1 Edition by Mary Sumner
Managing An ERP Project: © Prentice Hall, 2005: Enterprise Resource Planning, 1 Edition by Mary Sumner
Chapter 8:
Managing an ERP Project
© Prentice Hall, 2005: Enterprise Resource Planning, 1 st Edition by Mary Sumner 8-1
Objectives
© Prentice Hall, 2005: Enterprise Resource Planning, 1 st Edition by Mary Sumner 8-2
Factors Influencing Information
Systems Project Success
• Number of modifications
• Effective communications
• Authority for project implementation
• Business management
• Ability to generate additional funds to
cover implementation
© Prentice Hall, 2005: Enterprise Resource Planning, 1 st Edition by Mary Sumner 8-3
Factors Causing Information
Systems Project Failures
• Poor technical methods
• Communication failures
• Poor leadership
• Initial evaluation of project
© Prentice Hall, 2005: Enterprise Resource Planning, 1 st Edition by Mary Sumner 8-4
© Prentice Hall, 2005: Enterprise Resource Planning, 1 st Edition by Mary Sumner 8-5
Risk Factors
• Organizational factors
– Changes in scope
– Sufficiency of resources
– Magnitude of potential loss
– Departmental conflicts
– User experience
• Management support
– Changing requirements and scope
– Lack of commitment
• Software design
– Developing wrong functions, wrong user interface
– Problems with outsourced components
© Prentice Hall, 2005: Enterprise Resource Planning, 1 st Edition by Mary Sumner 8-6
Risk Factors, continued
• User involvement
– Lack of commitment
– Ineffective communication
– Conflicts
– Inadequate familiarity with technologies
• Project management
– Size and structure
– Control functions
• Project escalation
– Societal norms
– Continue pouring resources into sinking ships
© Prentice Hall, 2005: Enterprise Resource Planning, 1 st Edition by Mary Sumner 8-7
Implementation Risks
• Technology
– Consistencies with current infrastructure
• Organizational
– Customization increases risks
– Redesign of business processes to fit
package decreases risk
• Human resource factors
– IT staff skills and expertise
• Project size
© Prentice Hall, 2005: Enterprise Resource Planning, 1 st Edition by Mary Sumner 8-8
Managing Large-Scale Projects
• MRP or ERP
– Package implementation differs from
custom implementation
• Vendor participation
• User skills and capabilities
– Management commitment
• Project champion
• Communication with stakeholders
– Training in MRP
– Good project management
© Prentice Hall, 2005: Enterprise Resource Planning, 1 st Edition by Mary Sumner 8-9
Managing ERP Projects
• Implementation factors
– Re-engineering business processes
– Changing corporate culture
– Project team
• Include business analysts on project team
– Management support
– Commitment to change
• Risk management
© Prentice Hall, 2005: Enterprise Resource Planning, 1 st Edition by Mary Sumner 8-10
© Prentice Hall, 2005: Enterprise Resource Planning, 1 st Edition by Mary Sumner 8-11
Factors in Successful ERP
Projects
• Customization
– Increases time and cost
– BPR advantage from “best practices” adoptions lost
• Use of external consultants
– Offer expertise in cross-functional business processes
– Problems arise when internal IT department not involved
• Supplier relationship management
– Need effective relationships to facilitate and monitor
contracts
• Change management
– People are resistant to change
– Organizational culture fostering open communications
• Business measures
– Create specific metrics at start of project
© Prentice Hall, 2005: Enterprise Resource Planning, 1 st Edition by Mary Sumner 8-12
Project-Related Factors
© Prentice Hall, 2005: Enterprise Resource Planning, 1 st Edition by Mary Sumner 8-13
Additional Factors in the Success
of a Project
• User training
– Focus on business, not just technical
– Critical
• Management reporting requirements
– May need to add query and reporting
tools
• Technological challenges
– Data conversion
– Interface development
© Prentice Hall, 2005: Enterprise Resource Planning, 1 st Edition by Mary Sumner 8-14
© Prentice Hall, 2005: Enterprise Resource Planning, 1 st Edition by Mary Sumner 8-15
FoxMeyer versus Dow Chemical
• FoxMeyer
– Project went over budget because of new client
– Implemented two new systems at same time
– Technical issues with the ERP software
– No open communications
– Unrealistic expectations on ROI
• Dow
– Had project implementation problems
– Dow had strong leadership and project champion
– Was able to adjust scope and maintain control
– Fostered open communications
© Prentice Hall, 2005: Enterprise Resource Planning, 1 st Edition by Mary Sumner 8-16
Featured Article: FoxMeyer’s Project Was
a Disaster. Was the Company Too
Aggressive or Was It Misled?
© Prentice Hall, 2005: Enterprise Resource Planning, 1 st Edition by Mary Sumner 8-17
Featured Article: FoxMeyer’s Project Was a
Disaster. Was the Company Too Aggressive or
Was It Misled?, continued
© Prentice Hall, 2005: Enterprise Resource Planning, 1 st Edition by Mary Sumner 8-18
Featured Article: FoxMeyer’s Project Was a
Disaster. Was the Company Too Aggressive or
Was It Misled?, continued
• Background
– FoxMeyer had orders for over 300,000 items per
day, anticipated much growth
• Processing hundreds of thousands of transactions each
day
– Old system was Unisys mainframe
– Wanted scalable client/server system
– Tested SAP’s software on both DEC and HP
against benchmarks
– Implementations scheduled by Andersen for 18
months
• Modules to be implemented in 2-3 months
– Unrealistic – could take up to 12 months
– All modules fast-tracked
© Prentice Hall, 2005: Enterprise Resource Planning, 1 st Edition by Mary Sumner 8-19
Featured Article: FoxMeyer’s Project Was a
Disaster. Was the Company Too Aggressive or
Was It Misled?, continued
• FoxMeyer strategies
– High volume
– Low price
– Anticipated savings from new computer
system
– Wanted to win market share by further
price-cutting
– Hoped new system would be more
efficient, but did not improve processes
© Prentice Hall, 2005: Enterprise Resource Planning, 1 st Edition by Mary Sumner 8-21
Featured Article: FoxMeyer’s Project Was a
Disaster. Was the Company Too Aggressive or
Was It Misled?, continued
© Prentice Hall, 2005: Enterprise Resource Planning, 1 st Edition by Mary Sumner 8-22
Summary
© Prentice Hall, 2005: Enterprise Resource Planning, 1 st Edition by Mary Sumner 8-23
Summary, continued
© Prentice Hall, 2005: Enterprise Resource Planning, 1 st Edition by Mary Sumner 8-24
© Prentice Hall, 2005: Enterprise Resource Planning, 1 st Edition by Mary Sumner 8-25
Enterprise Resource Planning, 1st
Edition by Mary Sumner
Chapter 9:
Supply Chain Management and the
eMarketplace
© Prentice Hall, 2005: Enterprise Resource Planning, 1 st Edition by Mary Sumner 9-26
Objectives
© Prentice Hall, 2005: Enterprise Resource Planning, 1 st Edition by Mary Sumner 9-28
Supply Chain Relationships
• VMI
– Responsibility of inventory management on
supplier
– Supplier monitors level and replenishes
inventories
– No risk of stockouts
– Quicker response time
– Retailer reduces inventory and administration
costs
– Supplier gets more business
– No expedited orders
– Returned goods to supplier drops
© Prentice Hall, 2005: Enterprise Resource Planning, 1 st Edition by Mary Sumner 9-32
SCM Evolution
© Prentice Hall, 2005: Enterprise Resource Planning, 1 st Edition by Mary Sumner 9-33
eBusiness Value Chain
© Prentice Hall, 2005: Enterprise Resource Planning, 1 st Edition by Mary Sumner 9-34
eProcurement
• eProcurement
– RFBs on web
– Bidding more competitive
• Free-market bidding levels playing field
– Increased choices
– Reduced transaction costs
© Prentice Hall, 2005: Enterprise Resource Planning, 1 st Edition by Mary Sumner 9-35
B2B Hubs
• B2B hubs
– Spot sourcing of operating inputs
– Systematic sourcing of inputs
– Bring suppliers of similar or
complementary products together at one
web site
• One-stop shopping
– Automate transactions and reduce costs
© Prentice Hall, 2005: Enterprise Resource Planning, 1 st Edition by Mary Sumner 9-36
eSupply Chain
© Prentice Hall, 2005: Enterprise Resource Planning, 1 st Edition by Mary Sumner 9-37
Business Intelligence with ERP
Data
• Data warehouse
– Repository for making management decisions
– Data integrity accomplished by cleaning
– Consistent formatting applied
• Data mart
– Data storage for specific set of users
• Special data analysis
• Data mining
– Analysis of data for trends, sales forecasting,
inventory management
• Identifies problem, develops research, collects and
analyzes data
© Prentice Hall, 2005: Enterprise Resource Planning, 1 st Edition by Mary Sumner 9-38
© Prentice Hall, 2005: Enterprise Resource Planning, 1 st Edition by Mary Sumner 9-39
Future of ERP
• Disitributor of presentation
technologies
• Wants to netsource back-office
functions
– Has no internal IT capability
– Wants and ERP vendor via hosting
arrangement
© Prentice Hall, 2005: Enterprise Resource Planning, 1 st Edition by Mary Sumner 9-42
Featured Article: Leveraging the ERP
Backbone?
© Prentice Hall, 2005: Enterprise Resource Planning, 1 st Edition by Mary Sumner 9-43
Summary
© Prentice Hall, 2005: Enterprise Resource Planning, 1 st Edition by Mary Sumner 9-44
Summary, continued