ENTERPRISE RESOURCE

PLANNING
SUBMITTED BY:
Anam Azmi(03)
Harsh Kumar(08)
Priyanka Vishnoi(15)
Shivangi(21)
What is ERP?
Enterprise Resource Planning (ERP) is a packaged
business software system that allows a company to
automate and integrate the majority of its business
processes, to share common data and practices across
the entire enterprise, and to produce and access
information in a real-time environment.
Source: http://www.datainstincts.com/glossary.htm
Benefits of ERP
What are the benefits of all the partners in this process
having access to each others information in real-time?
-Single point of data entry
-Accurate inventory management
-Available vendor information
-Pending purchasing information
-Automatic data transfer and reconciliation
-Accurate financial information
ERP automates and integrates many of the tedious, common
business practices.
Source: http://www91.homepage.villanova.edu/william.wagner/MBA8556/erplec1.ppt
In the Real World
-Legal Issues
-Resource
-Potential Market
-Suppliers
-Material Prices
-Material Availability
-Inventory Control
-Production
-Human Resource
-Advertising
-Pricing
-Target Customer
-Customer Relationships
-Accounting
-Financial Reporting
Get
approval
from
parents
Buy
supplies
Make
lemonade
Find a good
location
Collect
cash
Source: http://www91.homepage.villanova.edu/william.wagner/MBA8556/erplec1.ppt
Advertise
Set-up
stand
History Of ERP
Mathematical
Programming
techniques
focused on
planning
MRP MRP II ERP ERP II
Inventory
and time
reduction
with new
production
planning
systems
Greater
reduction
due to
integration
with
accounting
and HR
systems
Focused
on clients.
Real time
trans-
actions.
Asset
managem
ent.
Optimizin
g the
whole
business
network;
including
suppliers
and
clients.
2000s 1990s 1960/70s 1920s 1980s
Source: http://www.e-innovation.org/presentations/kick-off/mrp-erp.ppt
History Of ERP
1. Manual Intensive
2. Not real-time
3. Non-Collaborative
4. Multiple
Application
Source: http://webprofesores.iese.edu/valor/Docs/EMBA/intro%20ERPS.pdf
History Of ERP
1. Automated
2. Real-time
3. Collaborate
4. Single Application
Source: http://webprofesores.iese.edu/valor/Docs/EMBA/intro%20ERPS.pdf
Case Study 1:
Successful Implementation of ERP at
Oregon Health and Sciences University
Case Study
Oregon Health & Sciences University

Academic, health and research university
3500 student enrollment
187,000 patients annually
Introduced 650 new medical technologies since 1985

Headquartered in Portland, Oregon

11,000 employees

Generates $2.35B annually in regional economic
activity
Source: http://www.ohsu.edu/about/facts/simply_ohsu.pdf
Problem
The traditional hospitals are
facing the low efficient
management in different
departments, therefore a new
tool as ERP in hospital to solve
this issue is needed.

ERP Fully Integrated
Integrates all the systems within the
hospital allowing the physician to
have instant access to his patients'
medical data from other physician's
offices, emergency rooms and
hospitals.
An Enterprise Resource Planning
(ERP) system replaces the need for
different interfaces between two or
more applications within hospital. It
provides an integrated database to
store various parts of a hospital and
increases standardization and
reporting capacities.
ERP Hospital is a solution that
helps hospital to manage all kind
of operations and a available
resources in there facilities.
Case Study
Oregon Health & Sciences University

Installed Oracle ERP

Separated from the Oregon State System of Higher
Education
Needed independent financial system

10 year phased installation
1994 2004

Cost - ???
Features
Web-based applications.
Friendly GUI(Graphical User Interface).
Compatible with HL7 international.
Based in modules.
Integrated Design.
Multi-lingual.
Highly secure, remote access with alternative
devices(laptops, tablets).

Case Study
Oregon Health & Sciences University

Phased implementation
1994 Integrated administrative applications
G/L, A/P, Purchasing
1998 Implemented additional applications
Cash management, HR, payroll, fixed assets, and grants
software
Recent Installed browser-based front ends
Integration of affiliate healthcare providers
Profmax ERP module in Hospital
Case Study
Oregon Health & Sciences University

Success
Estimated annual savings of $2M
Automated ordering and receiving
Volume based purchase ordering
2004 We feel like we are finally through the pain of
transition and to the point where were getting a lot of
value from the ERP system Bridget Haggerty Senior
Manager

Risk averse approach
No major application glitches
System operated as required
Advantages
Able to integrate all hospital departments into a single,
cohesive platform.
Clearer overview of it functioning and quicker
performance.
Enable hospital to have greater control over daily
planning, surgical and nursing care etc.
Help hospitals strengthen management capacity,
improve coordination and collaboration between
organizations, to strengthen capital equipment
management, medical supplies, etc.
Improve management capabilities to enhance
performance, so as to improve patient satisfaction.

6/15/2014
Case Study 2
Failed Implementation of ERP at
Raskas Foods, Inc.
19
About Raskas
One of the 150 Largest Privately held companies in
St. Louis.
Purchased by Schreiber Foods in October, 2002.
Founded in 1888.
Nations first private label manufacturer of cream
cheese for retail grocery distribution.
Sales of over $280 million in 2002.
3 Manufacturing Plants.


The ERP Package


21

Approved in early 1999.
Adage ERP package.
SCT consultants.
Budgeted $2.2 million.
Anticipated 6 months to 1 year to complete.
Waited until after the Y2K problem to implement.
Completed the Blueprint of Business Processes.
Training for IS.


Project Personnel



22

Mike Doyle (Finance), Project Manager.
Cliff Thomason (Finance), Project Facilitator.
John Lazare (IT), Project Lead.
Wayne Dixon, Director - IT, was left out.



Problems
23


Implementation started in April of 2000.
Employees found that the ERP system didnt do
things the same way they did things.
Changes approved to keep Operations involved.
Stopped for fall Busy Season September 2000.






Startup-January, 2001


24

No momentum restarting.
Had to upgrade the software to the latest release.
Budget increases to $3.3 million.






Large Sales Increase



25


The number two private label Cream Cheese
manufacturer develops quality and delivery problems.
Spring 2001, Operations gets approval for a new
plant.
Operations pulls key people from ERP for new plant
startup.







More Problems



26
Work on the ERP implementation stopped for fall
busy season again.
By February, something was wrong.
March 2002, lack of Upper Level Management
interest in ERP.
April 2002, a successful ERP implementation was no
longer necessary.









Lessons learned
27
The budget will increase when changes are made.
Senior level personnel have to stay involved.
Everyone involved in the project has to be 100%
dedicated to the project.
The people involved in the ERP project have to be
key employees.
ERP has to be the number one priority.













THANK YOU