Beruflich Dokumente
Kultur Dokumente
Company Background
Manufacturing industrial process
equipment used in the production of
rubber and latex
Founded in Minnesota during World
War II
Grew through acquisition
Plant treated as revenue centers
High degree of independence
Heterogeneous IT Infrastructure
1
Company Background
Growing competition in mid 1980s
Restructuring
Lean production
Resizing the company
Return to profitability in mid 1990s
Identification of short comings
Higher priority to manufacturing and order
fulfillment
Requires integrated systems and processes
2
Existing Informations Systems
Challenges:
Scheduling: Required manual effort
Forecasting: Monthly planning vs. weekly
customer orders
Ordering: Manual handling
Delays & Losses
HR: Incompatibality Redundancy
Problems with Confidentiality
FI & Accounting: Lack of Integration
3
SAP R/3
Why SAP?
Client/Server Technology
Graphical User Interface – Ease of Use
Scalability
Modularity, functionality & integration
Modules share and transfer information
Single database
Interconnectivity to other applications
4
Implementation Strategy
Clean Sheet
All four dimensions of change are explored
without constraints (strategy, process, people,
technology)
Technology-enabled Change
Technology is selected, which influences the
other three dimensions
Vandelay already chose their technology
(SAP) technology-enabled change
5
Team Structure
Focus on:
Project Management
Change leadership talent
Steering Committee – 8 people
Business Strategy – monthly meetings
Project Team – 20 people
Implementation specifics – full time
Change Management
Project Team Members Selection
Selection based on skills and
characteristics of employees
Optimal skill set for Project Team
vs.
One representative from each of
Vandelay’s implementation
Project champion at each location
6
Change Management
Centralization vs. autonomy
“Input by many, design by few” ?
Tightly defined processes vs.
encouraging innovation and autonomy
Resistance to externally defined ‘best
practices’
Change agents
Overcome resentments
Encourage enthusiasm for new system
Problems
Engineers are enthusiastic
Eager to “play” with the new system
Need to accept that new centralized
system introduces new constraints
Resentments
Heterogeneous software and business
processes
7
Possible Solutions
Change business processes to match
software capabilities
+:easy maintenance, “best practices”
–: employee resistance
Interface R/3 to other software solutions
+:more flexibility, use of legacy system
–: cost, loss of BPR benefits
Extend/modify R/3 to match requirements
+:compatibility with Vandelay’s processes
–: no SAP support, maintenance,
reducedintegration
Recommendations
BPR: Change the business process to fully
utilize the R/3 SAP software
Keep engineers in the loop to avoid
resentments
Project Champions
Banner and Online Campaign
Reasons:
“Best practices” – maximize benefits
Standardization throughout company
Maintenance and upgrades – industry-wide
8
Thank you
Q&
QUESTIONS
ANSWERS