Professional Documents
Culture Documents
BPCL Case
BPCL Case
Submitted By:
Submitted To:
Group Epsilon
WHY ERP?
Planned increase in Non-Fuel Revenues (VAS).
Need for IT initiatives in post-APM era.
IT INITIATIVES @ BPCL
Three-Pronged Strategy
1.
2.
3.
WHAT?
WHY?
HOW?
Creating Communication
Network
Microsoft Exchange
Server Intranet
Creating Basic
Information Network
Need to facilitate
information retrieval from
corporate databases
VSAT hub
THE SYSTEMS
Security for Online Business
Sun Ultra 5 Firewalls
Real Secure
Internet Scanner
Floodgate
PROJECT ENTRANS
ERP SYSTEM IMPLEMENTATION AT BPCL
A NECESSITY IN CHANGING
TIMES
1991 economic reforms
Partial deregulation of the sector
Imperative to remain competitive through improved customer
service and customer satisfaction and to transform the
company into a Learning Organization
IS PLAN
Massive restructuring undertaken at all levels of the organization;
CUSECS initiated.
Evolution of IS: replace the existing batch-process-oriented legacy
systems with a state-of-the-art ERP system.
Mapping of major processes;
Pre-selecting, validating and evaluation of ERP products
Training provided to employees
Involvement of all stakeholders including vendors; SAP R/3 software
selected
IMPLEMENTATION
A Project Steering Committee (PSC) was constituted with the
heads of all the SBUs, Finance, HR, and IS as its members.
Conceived in two phases:
I.
II.
IMPLEMENTATION
SAP's ASAP methodology for implementation consisted of five
distinct phases, viz., project preparation, business blueprint,
realization, final preparation, and go live and support.
However, in BPCL, the whole project was divided into a pilot phase
and a rollout phase.
All the SBUs went live at one or two locations and only after their
stabilization, the remaining locations were added.
PILOT PHASE
Three sites were selected: Refinery, Wadilub Lubricants Plant,
and a Lubs C&F Agency at Pune.
Criteria : business and IT-readiness, proximity to project team
(Juhu, Mumbai), salience of processes involved.
The SAP modules implemented during the pilot
implementation were FI, MM, QM, PP, SD, PM, IS oil, and CIN
PROBLEMS FACED
Tasks becoming tedious and time consuming
Formalization required
Configuration issues
BENEFIT
Discipline enforced
Data made available
The actual roll-out team will then go to the location and execute cut-over
to SAP R/3.
Support provided in the form of CCSE.
CHALLENGES AHEAD
The cost estimates of the project do not cover disaster recovery or networking.
Many of the estimated benefits could be attributed to networking of the locations and not to
ERP.
No process reengineering in BPCL's implementation.
The change in process and consequently in roles has been software-driven and not through
a radical business review.
Without process reengineering, ERP provides mere process automation and integration that
can lead certainly to downsizing of the workforce. BPCL's benefit list does not include any
man power reduction.
In order to provide for benefit measurement (project evaluation), there should be
benchmarks for the key parameters. In the absence of these benchmarks, benefit
measurement remains a big question mark.
Optimization
Impact on productivity and creativity of workforce.
Redefining of roles and expertise.
Flexibility
To streamline processes
Retain market position
INFRASTRUCTURE REQUIRED
Intranet
7 web servers
VSAT hub
Routers and switches
PRE- REQUISITE
Top-Management Involvement
Strong & Multi-talented Project Management
Active Risk Management
Project controls on schedule & scope
Capable Teams
Thank You