View
219
Download
2
Category
Preview:
Citation preview
OVERVIEW
WESTERN TELECOM REGION
ERP PROJECT OBJECTIVE
BSNL has decided to implement Enterprise
Resource Planning in BSNL. The objective of
ERP system is to improve the information
flow to facilitate better decision makingflow to facilitate better decision making
leading to overall improvement in the
performance of the organization by way of
improvements in productivity, cycle time,
financial performance and information
transparency.
• The project shall prepare BSNL to face new
challenges due to competition by providing
effective and efficient business processes
and improved operational efficiencies
besides aiding in better decision making.
ERP PROJECT OBJECTIVE
besides aiding in better decision making.
• HCL is the System Integrator (SI), who along
with E&Y as the Business Process Re-
engineering (BPR) partner & SAP as the
Software Solution Provider (SSP) will
implement this project.
• The project would be executed in two parts.
Firstly, as a proof of concept (POC) at 7
locations.
• The application would be rolled out in the
rest of BSNL units during the second part of
ERP PROJECT OBJECTIVE
rest of BSNL units during the second part of
the project.
• The application would be hosted on a
centralized server located at Hyderabad
Data Centre (DC) and Kolkata would be the
Disaster Recovery (DR) site for the project.
S.No Name of the Module Nodal Officer
1 Finance and management accounting (FICO) GM(TP&FC)
2 Material and inventory management including e-
procurement (MM)
GM(MM)
3 Plant/Equipment Maintenance (PM) PGM(NWO)
4 Human Capital Management (HCM) GM(Estt.)
5 Sales & Distribution (SD) GM(BPE)
6 Project Systems (PS) GM(CNP)
ERP PROJECT OVERVIEW
7 Real Estate & Telecom Infrastructure Management
(REM)
PGM(Civil)
8 Production Planning /Supply Chain Management
(PP/SCM)
GM(TF)
9 Business Information system / Business Intelligence
& Analytic (BI)
GM(Co-ordination)
10 Enterprise Strategy Management (SEM) PGM(CP & M)
11 Enterprise Portal (EP) CGM, ITPC, Pune
Quality Management (QM) DGM (QA)
POC LOCATIONS
S. No. POC Locations
1 BSNL CO, New Delhi
2 ALTTC Ghazaibad
3 Maharashtra Telecom Circle
4 Telecom Factory Mumbai4 Telecom Factory Mumbai
5 Karnataka Telecom Circle
6 Southern Telecom Region
7 Western Telecom Project
CIRCLES COVERED
ZONE CIRCLES
SOUTH Andhra Pradesh, Chennai District, Tamilnadu,
Karnataka, Kerala
EAST Kolkata Telecom District, West Bengal Circle,
Orissa, Jharkhand, Bihar, Assam, North East-I,
North East-II, Andaman & NichobarNorth East-II, Andaman & Nichobar
WEST Maharashtra, Gujarat, Madhya Pradesh,
Chattisgarh.
NORTH Punjab Circle, UP-East, UP-West, Haryana,
Rajasthan, Himachal Pradesh, Uttarakhand,
Jammu & Kashmir
ERP OVERVIEWConnectivity to ERP Server at Hyderabad
ERP SERVER : 10.197.216.213
NETWORK PLAN DOMAIN REMARKS
CDR FROM NEAREST CDR
ROUTER OR SWITCH
MPLS-VPN 2 MBPS GOLD
BBoVPN BUSINESS-700
BROADNET-512
BROADNET-256
ERPBSNL.IN
ERP OVERVIEWERP CONNECTIVITY : VPN OVER BROADBAND
ERP OVERVIEWGMM wise ERP Connectivity Status
WTR Circle Office, Mumbai :
Division/Unit Connected via
CDR/VPN/BBoVPN
Status Remarks
WTR Circle Office
Prabhadevi
VPN Completed
Telecom Building
Prabhadevi
VPN Completed
Fountain Telecom
Building-1
VPN Completed
Fountain Telecom
Building-2
VPN Completed
ERP OVERVIEWGMM wise ERP Connectivity Status
GMM, WTR Mumbai :
Division/Unit Connected via
CDR/VPN/BBoVPN
Status Remarks
MUMBAI VPN Completed
KALYAN VPN Completed
THANE (KOPRI) VPN Completed
THANE (DGMM OFFICE) VPN Completed
SATELLITE THANE VPN Completed
PANVEL CDR Completed
NASIK CDR Completed
DHULIA CDR Completed
RATNAGIRI CDR Completed
ERP OVERVIEWGMM wise ERP Connectivity Status
GMM, WTR Mumbai : continued…
Division/Unit Connected via
CDR/VPN/BBoVPN
Status Remarks
PUNE (MHS) CDR Completed
PUNE (MPLS) CDR Completed
AHMEDNAGAR CDR Completed
AURANGABAD CDR Completed
KOLHAPUR CDR Completed
LATUR CDR Completed
PANJIM CDR Completed
SATARA CDR Completed
SOLAPUR CDR Completed
ERP OVERVIEWGMM wise ERP Connectivity Status
GMM, WTR Mumbai : continued…
Division/Unit Connected via
CDR/VPN/BBoVPN
Status Remarks
NAGPUR VPN Completed
NAGPUR
(SAKKARDARA)
VPN Completed
(SAKKARDARA)
AKOLA CDR Completed
CHANDRAPUR CDR Completed
JALGAON CDR Completed
NANDED CDR Completed
YAVATMAL CDR Completed
ERP OVERVIEWGMM wise ERP Connectivity Status
GMM, WTR Bhopal :
Division/Unit Connected via
CDR/VPN/BBoVPN
Status Remarks
BHOPAL (CITY) CDR Completed
BHOPAL (ARERA) CDR Completed
GWALIOR CDR Completed
GUNA CDR Completed
INDORE BBoVPN Completed
ITARSI CDR Completed
MANDSAUR CDR Completed
RATLAM BBoVPN Completed
UJJAIN BBoVPN Completed
ERP OVERVIEWGMM wise ERP Connectivity Status
GMM, WTR Bhopal : continued…
Division/Unit Connected via
CDR/VPN/BBoVPN
Status Remarks
JABALPUR CDR Completed
CHATARPUR BBoVPN Completed
CHINDWARA BBoVPN CompletedCHINDWARA BBoVPN Completed
NARSINGHPUR CDR Completed
REWA BBoVPN Completed
SAGAR CDR Completed
RAIPUR CDR Completed
BILASPUR CDR Completed
DURG CDR Completed
AMBIKAPUR CDR Completed
JAGDALPUR CDR Completed
ERP OVERVIEWGMM wise ERP Connectivity Status
GMM, WTR Ahmedabad :
Division/Unit Connected via
CDR/VPN/BBoVPN
Status Remarks
AHMEDABAD VPN Completed
AHMEDABAD (BHADRA) CDR Completed
BARODA CDR CompletedBARODA CDR Completed
BHARUCH CDR Completed
BULSAD CDR Completed
GODHRA CDR Completed
HIMMATNAGAR CDR Completed
MEHSANA CDR Completed
PALANPUR CDR Completed
SURAT CDR Completed
ERP OVERVIEWGMM wise ERP Connectivity Status
GMM, WTR Ahmedabad : continued…
Division/Unit Connected via
CDR/VPN/BBoVPN
Status Remarks
RAJKOT CDR Completed
BHAVNAGAR CDR Completed
BHUJ CDR CompletedBHUJ CDR Completed
JAMNAGAR CDR Completed
JUNAGARH CDR Completed
SURENDRANAGAR CDR Completed
ERP REVIEWCommon mistakes/errors faced during GO-LIVE
# Issue / Risk Impact Resolution / Mitigation
1 Vendor Details not
available:
• Address
• Registration details
• Duplicate Vendors
• Unidentified Vendors
• Payment automation
hindered – NEFT / RTGS
• Distribute Data forms to collect
data at the point of vendor
interactions.
• Encourage Vendors to provide
data through BSNL Portal • Registration details
• Pan Card,
• Bank Details
• IFSC Code
• Tax Registrations
hindered – NEFT / RTGS
• Un-reconciled vendors
payables
• Audit Observation
data through BSNL Portal
• Make payments subject to
submission of data – on lines of
KYC of Banks
ERP REVIEWCommon mistakes/errors faced during GO-LIVE
# Issue / Risk Impact Resolution / Mitigation
2 Employee Details not
available:
• IFSC Code
• Bank account details not
• Credit of Salary
• Credit of
reimbursements
• Payment automation
• All employees to verify & update
their personal details in HRMS
• Data forms to collect data at the
point of retired employee
interactions / Unions• Bank account details not
updated
• Details for Retired
employees
• Communication details
• Payment automation
hindered – NEFT / RTGS
• Un-reconciled employee
advances / payables
• Higher tax rate (TDS for
not providing PAN).
• Audit Observation
interactions / Unions
• Encourage retired employees to
provide data through BSNL Portal
• Make payments subject to
submission of data – on lines of
KYC of Banks
ERP REVIEWCommon mistakes/errors faced during GO-LIVE
# Issue / Risk Impact Resolution / Mitigation
3 Schedule of Employee
Loan & Advances do not
reconcile with the Trial
Balance:
• Employee / Loan type
• Employee Loans and
advances data can not
be uploaded in SAP
• Automatic Loan
management is
• All employees to verify & update
their personal details in HRMS
• Data forms to collect data at the
point of retired employee
interactions / Unions• Employee / Loan type
break-up does not
match with G/L
• Balance Outstanding
does not have details /
identifier
management is
hampered
• Un-reconciled employee
Loans & Advances
• Audit Observation
• Extended Black out
interactions / Unions
• Encourage retired employees to
provide data through BSNL Portal
• Make payments subject to
submission of data – on lines of
KYC of Banks
ERP REVIEWCommon mistakes/errors faced during GO-LIVE
# Issue / Risk Impact Resolution / Mitigation
4 IT / Arrear data not updated
in HRMS correctly:
• Established processes in
HRMS not being
followed by units.
• Income Tax calculation
would not tally with SAP
• Wrong IT liability
calculated
• All employees to verify & update
their personal IT
• Standard process to be followed
across BSNL in HRMS.
followed by units.
• Wrong data pertaining to
IT/ Arrear / Perks /
Medical are fed in HRMS
• Salary calculation would
not reconcile
• Audit Observation
ERP REVIEWCommon mistakes/errors faced during GO-LIVE
# Issue / Risk Impact Resolution / Mitigation
5 EMD / SD details not
available (unidentified):
• EMD / SD outstanding
for more than three
years
• EMD / SD outstanding
data can not be uploaded
in SAP
• In future cannot be
refunded through SAP
• All EMD / SD details to be dug out
and matched against parties
• Write-off EMD / SD outstanding
for more than three years as per
BSNL policy (Treat as Misc Income)years
• EMD / SD outstanding
for less than three years
refunded through SAP
• Un-reconciled EMD /
SD
• May need to pay
penalty if payment
deadline will be missed
• Audit Observation
• Extended Black out
BSNL policy (Treat as Misc Income)
ERP REVIEWCommon mistakes/errors faced during GO-LIVE
# Issue / Risk Impact Resolution / Mitigation
6 Interface with banks for
electronic transactions not
standardized across
BSNL :
• Interface for electronic
• Automatic payment
process from SAP will be
delayed.
• Automatic BRS will not
be done.
• Unified bank for making payment
• Liaison with banks to get the
electronic transactions in place.
This should be completed for entire
BSNL well in advance.• Interface for electronic
upload of RTGS/NEFT
transfers not in place
with the banks BSNL is
operating with.
• Banks not geared up
with electronic bank
statements in standard
formats fir BRS
• Cheque printing formats
not standardized
be done.
• Manual effort will be
increased leading to
inherent mistakes.
• Manual Check writing to
continue
BSNL well in advance.
• Finalization of format required for
bank reconciliation by using
international formats (MT940 /
Multicash)
• Moving to a phase of single
banker for all employees for all
payroll / reimbursement related
payments.
ERP REVIEWCommon mistakes/errors faced during GO-LIVE
# Issue / Risk Impact Resolution / Mitigation
7 The Application
Landscape of BSNL is
not standardized across
BSNL. Automated
Electronic Interfaces with
SAP would not work :
• Automatic Interfaces
with SAP will not work.
• PM / SD / MM / FICO
processes in SAP would
get impacted.
• Unified Standard Application to be
implemented across BSNL – QMS,
HRMS, Sancharsoft etc.
• Sancharsoft to be configured with
mapping tables for entire BSNL (as SAP would not work :
• Interface with QMS for
fault data at NTR / ETR
/ WTR.
• Sancharsoft not being
used for sales
processes with
standardized processes
• HRMS not being used
in BSNL CO for payroll
/ HR processes
get impacted.
• Non standardized
interfaces / processes
would leave room for
errors / mischief.
• Manual effort would
increase
• Reconciliation problems
mapping tables for entire BSNL (as
done for KTK)
• Sales processes to be aligned
with KTK processes.
• Process standardization of entire
BSNL to be done inline with
processes frozen for POCs
ERP REVIEWCommon mistakes/errors faced during GO-LIVE
# Issue / Risk Impact Resolution / Mitigation
8 Un-reconciled Remittance
• Intra-circle remittances
not paired and having
balance.
• Data can not be
uploaded in SAP
• Un-reconciled data
• Audit Observation
• All intra-circle remittances should
be paired at circle level.
• After pairing remittances, requisite
heads of account will get the due
credit /debit and the balance should
• Balance will not be
matching at different
head of account
(exp/cash/bank/asset/in
ventory/payable/receiva
ble)
• Incorrect TB
• Audit Observation
• Extended Black out
credit /debit and the balance should
be matched with TB.
ERP REVIEWCommon mistakes/errors faced during GO-LIVE
# Issue / Risk Impact Resolution / Mitigation
9 Inappropriate budget at
node levels of IM
structure.
• Problem at the time of
booking CAPEX/OPEX
• Data can not be
uploaded in SAP
• Un-reconciled CWIP
balances
• Budgets should be allocated
appropriately to each node of an IM
structure to ensure that the
expenditure/budget available at
bottom level is always less than the
budget available in the upper node.booking CAPEX/OPEX
expenditure.
• Delay in defining
applicable IM structure
• Expense booking on
wrong Estimate / Project /
exceeding budget
allocation / closed projects
• Audit Observation
• Extended Black out
• Stops inventory
processing / period
closure
budget available in the upper node.
• Reverse mechanism or, bottom up
approach should be followed to
derive the appropriate budget at
each node of an IM structure.
• IM structure to be defined well in
advance
ERP REVIEWCommon mistakes/errors faced during GO-LIVE
# Issue / Risk Impact Resolution / Mitigation
10 CWIP Data not reconciled
with open projects /
estimates
• Data can not be
uploaded in SAP
• Un-reconciled CWIP
• Asset will get proper
• All Project / Estimate details to be
dug out and matched against CWIP
trial in advance
• Old estimates to be closed as per
BSNL norms• Asset will get proper
value if CWIP could not
be matched with open
projects
• Audit Observation
• Extended Black out
BSNL norms
• Reverse mechanism may be used
to get this data reconciled.
ERP REVIEWCommon mistakes/errors faced during GO-LIVE
# Issue / Risk Impact Resolution / Mitigation
11 Asset Data not reconciled
with GL codes:
• Non-assets included
• Assets line items not
• Data can not be
uploaded in SAP
• Un-reconciled Asset
Register
• All Asset to be dug out and
reconciled against trial – class,
component, GL wise in advance
• Retired / decommissioned assets
to be accounted for prior to cutover• Assets line items not
maintained with details
• Decommissioning not
taken care of
• Capitalization not
updated in register
• Wrong posting of
Depreciation
• Asset Class /
component not proper
• Wrong calculation of
depreciation
• Audit Observation
• Extended Black out
to be accounted for prior to cutover
• Capitalization of assets – squaring
of ATD / ATC to be completed prior
to cutover
ERP REVIEWCommon mistakes/errors faced during GO-LIVE
# Issue / Risk Impact Resolution / Mitigation
12 Un-reconciled Inventory
• Sancharsoft and other
inventory management
application inventory
does not tally with TB
• Data can not be
uploaded in SAP
• Un-reconciled data
• Audit Observation
• All Inventory to be dug out and
reconciled against trial – GL wise in
advance
• Requisite treatment should be
done for inventory scrapped and does not tally with TB
• Stock position is not
reconciled store wise
• Non-usable inventory
is not retired /
scrapped
• Audit Observation
• Extended Black out
done for inventory scrapped and
the scrapped inventory balance
should be matched with TB before
cut-over.
• Retired / decommissioned assets
to be taken into inventory (if the
same is inventorised and removed
from asset register) prior to cutover
• Physical inventory to be done and
updated with trial prior to cutover
ERP REVIEWCommon mistakes/errors faced during GO-LIVE
# Issue / Risk Impact Resolution / Mitigation
13 Re-structuring of Units /
Merger of Trial Balance :
• Merger of Civil and
Electrical Trial balance
with SSA - delay
• Delay in migration
• Reconciliation issues
across units post
migration
• Appropriate Notification on merger
/ restructuring to be issued to all
units well in advance
• Merger of Civil and Electrical Trial
Balance to be completed in the with SSA - delay
• Delay in finalization of
Treatment of CMTS
units.
• Formation of CSC /
CPC cells
• Impacts master data
and Roles &
Authorization matrix of
related functions
Balance to be completed in the
legacy system itself
• The merged TB to be migrated in
ERP
• Treatment of CMTS unit to be
finalized for all locations well in
advance.
• All Master data & R&A to be
prepared after the merger /
restructuring.
ERP REVIEWCommon mistakes/errors faced during GO-LIVE
# Issue / Risk Impact Resolution / Mitigation
14 Changes incorporated in
ERP solution during
Cutover:
• Location specific
changes incorporated
• Pan-BSNL
Standardization of
business process is lost
• Last moment changes
impacts the solution
• All changes to the solution to be
governed through a Change
Control Board
• Effective Corporate
communication / campaign on changes incorporated
in the solution
• Changes done to the
solution / process at
the last moment
• Solution Changes
released to PRD
during cutover
impacts the solution
stability and has
cascading impact on the
integrated solution
• Impacts master data
and Roles &
Authorization matrix of
related functions
• Poses reconciliation
problem / Post
Implementation issues
communication / campaign on
standardized processes across
BSNL to all Units
• All Releases of the Application to
be controlled by a Release
Management Cell
• Use of tools for requirement
gathering and effective monitoring
of change management process
(currently Mantis is used).
ERP REVIEWCommon mistakes/errors faced during GO-LIVE
# Issue / Risk Impact Resolution / Mitigation
15 Cut-over period is not
well defined: :
• Black-out period is too
extended
• Delay in reconciliation
of accounts
• Reconciliation issues
across units post
migration
• Ensure that all the master data is
complete and correct before
starting cut-over
• Ensure that all Schedules are
complete and tallied during last
• Business transactions
are carried out during
Black-out
migration
• Data inconsistencies
due to uncontrolled back
log data
• Lot of unnecessary
effort spent in bringing
the system to real time
• Checks & balances are
compromised making the
system vulnerable.
complete and tallied during last
closure of accounts prior to go-live.
• Cut-over should not exceed 3-4
days
• Business Transactions to be
stopped to near complete level
during the entire Blackout period.
ERP REVIEWGO-LIVE Schedule for WTR
Item Scheduled
Date
Remarks
BLACK OUT
START DATE
30-09-2014
START DATE
FINALISATION OF
TRIAL BALANCE
10-10-2014
GO-LIVE TO ERP 14-10-2014
Recommended