3-EY - RFP Response - State of The Art SAP ERP For Pipavav - 18 Aug

EY Response -RFP Response
State of the Art SAP ERP for Pipavav
Technical Proposal - August 2015

Table of Contents
1. Introduction .......................... 2
2. Key Project Objectives........... 3
3. Scope ................................... 4
3.1 Legal Entities in scope .......................................................................................................... 4
3.2 Track 1 - SAP ECC Enablement .............................................................................................. 5
3.3 Track 2 - SAP PLM Enablement ........................................................................................... 10
3.4 Track 3 - SAP SRM Enablement ........................................................................................... 12
3.5 Track 4 - SAP MDM Enablement ........................................................................................... 16
3.6 Track 5 - SAP HCM Enablement ........................................................................................... 17
3.7 Track 6 - SAP BI – BO ......................................................................................................... 26
3.8 Track 7 - SAP Productivity Pak by ANCILE / KNOA ............................................................... 27
3.9 Scope of Customizations / RICEFW ...................................................................................... 31
4. High Level Overall Project Roles & Responsibilities 32
5. Approach and Methodology .. 33
6. Expectations from client ...... 40
7. Pre-requisites ..................... 43
8. Assumptions ....................... 45
9. Technical Delivery ............... 56
9.1. Propose IT system architecture and Infrastructure required .................................................. 56
9.2. Server and Storage Sizing ................................................................................................... 56
9.3. Recommend the security infrastructure & setup ................................................................... 57
10. Detailed Project Plan with Key Milestones 59
11. Key Milestones & Deliverables60
11.1. Milestone: Project Preparation ........................................................................................ 60
11.2. Milestone: Business Blueprint .......................................................................................... 61
11.3. Milestone: Realization phase (Build and Test).................................................................... 61
11.4. Milestone: Final Preparation (Deploy) ............................................................................... 61
11.5. Milestone: GO LIVE & Support.......................................................................................... 62
12. Detailed Project - Roles & Responsibilities 63
13. Profile of all Project Resources68
14. Escalation Matrix................. 69
15. Payment Terms ................... 70
16. Vendor Details .................... 71
17. EY Contact Details.............. 75
1
1. Introduction
Reliance Infrastructure (RInfra) Team is working closely with Pipavav Defence and
Offshore Engineering Company Limited (PDOECL) team to identify the
requirements for SAP ERP implementation. The scope of work defined below is
based on the study conducted by RInfra Team, SAP ECC EHP7 product overview,
various discussions with PDOECL team and sessions by various consulting partners.
PDOECL currently uses IMMS Application including modules for Procurement,

Inventory, Quality, Finance, Budgeting, and Fixed Assets, which would be replaced
with integrated SAP Application
2
2. Key Project Objectives
As described in RFP, below is the project objective:
► Extensive automation of manual process

► Robust planning and budget control process
► Dynamic Analytics and reporting system
► Optimum utilization resources, enhanced efficiency and productivity
► Corporate Governance using access and process controls
Above shall be achieved by –

► Implementing SAP ERP System with all allied solutions
► Use of SAP Best Practices & SAP Standard functionalities relevant to PDOECL
► SAP interfaces with specialized system such as Design Software, RFID and Bar
Code
► Mobile enablement/Kiosks for specific required business processes
► Use of SAP BI/BO for analytics and reporting
► Minimizing customization of SAP Solutions
3
3. Scope
The scope of the project may be divided into the following main categories:
3.1 Legal Entities in scope
Abb. Companies Location

Pipavav Defense and Offshore Engineering Company Limited
Units Location
EOU/SCS Export Oriented Unit/Shipyard Site Pipavav
SEZ/BCS Special Economic Zone/Block Making Site Pipavav
HO Head Office Mumbai
Other Legal Entities in scope - Subsidiaries

PTSPL Pipavav Technical Services Private Limited Pipavav
PBMPL Pipavav Business Management Private Limited Pipavav
GBMPL Guardian Business Management Private Limited Mumbai
ECPL E Complex Private Limited Mumbai
ECPL E Complex Private Limited Pipavav
Location of the Project:

► PDOECL (Pipavav Defense and Offshore Engineering Company Limited) -
Head Office at Mumbai and Works (Shipyard) at Pipavav
► EY Offices
SAP has several features and functionalities which will help the organization to
undertake various activities through their digital mechanism of using its ERP
modules. All the relevant functionalities and features should be implemented using
SAP Best Practices and re-engineered feasible processes
If there are gaps in any of the processes needed and to be automated, then the
same may be bridged through customized or add-on applications.
Any SAP Module/functionality which is not specifically mentioned in detailed scope

document but is required for the processes followed in the company then the same
4
can be considered subject to approval from steering committee, EY will present the
impact analysis of scope, effort and timelines.
3.2 Track 1 - SAP ECC Enablement
Modules in scope
► Finance
► Controlling
► Funds Management
► Invest Management
► Materials Management
► Sales and Distribution
► Production Planning
► Plant Maintenance
► Project Systems
► Quality Management
► Warehouse Management
► Treasury and Risk Management
► Fiori – 10 for approval
Functionalities in scope
Main Process Process SAP Solutions

Customer Inquiry/Quotation SAP ECC - SD, BI BO
Sales Order Processing
Customer Contracts
Customer Complaints
Billing Processing
Marketing /
Business Revenue Recognition
Development
Down Payments Processing
Credit and Risk Management
Outbound Delivery Process
CIN related to Sales Process
Reports and Analyses
Cost Planning SAP ECC –Project

Project
Systems
Planning and Budget management for projects
5
Control Availability Control
Revenue planning
Resource-Related Billing
Project Cash management
Advance Procurement
Bill of Material Transfer
Delivery from Projects
Monitoring Dates
Assembly Processing in the Project System
Project-Oriented Procurement (ProMan)
Project Progress
Claim Management
Milestones
Interfaces to the Project System
Project Information System
Consumption Based Planning (MRP) SAP ECC - MM, SRM

Purchase Requisitions
RFQ and Quotation Processing
Purchase Order Processing
Down Payment Processing to Vendors
Logistics Invoice Verification
Integration of SAP MDM Catalogs in Purchasing
Procurement &
External Services Management
Inventory
Management Inventory Management and Physical Inventory
Material Valuation
Vendor Evaluation
CIN related to Material Management
Subcontracting Management
Self-Service Procurement in SAP ERP
Warehouse Management Control with Radio
Frequency Connection
6
Bill of Materials (BOM)

Master Planning SAP ECC - PP
Demand Management
Production Capacity Planning

Planning Material Requirement Planning
Production orders
Production Resource and Tools (PRT)
Assembly to Order
Quality Planning SAP ECC - QM
Quality Inspection
Quality Control
Inspection and Quality Certificates

Quality Control Quality Notifications
Test Equipment Management
QM Cockpit for Evaluations
Failure Mode and Effects Analysis (FMEA)
FI General Ledger SAP ECC - FI

FI Accounts Payable
Accounts Receivable
Indirect Taxation
Bank Accounting
Financial
Asset Accounting
Accounting
New General Ledger
Bank Guarantee
Letter of Credit
FM Master Data SAP ECC - FM

Budget Control System
Budget Control
BCS Planning
BCS Budgeting
7
BCS Availability Control
Budget Text and Budget Memos
Budget Reporting
Cost Element Accounting SAP ECC - CO

Cost Centre Accounting
Internal Orders
Controlling
Activity-Based Costing
Product Cost Controlling
Profitability Analysis
Transaction Manager SAP TRM
Treasury Accounting & Country India Specific Process

Management Cash Management
Loans Management
Equipment and Technical Object SAP ECC - PM

Refurbishment Orders in the MRO Process
Subcontracting for MRO Processes
Warranty Claim Processing
Preventive Maintenance
Plant
Maintenance Order Management
Maintenance
Breakdown Maintenance
Work Clearance Management
Mobile and Workflow Scenarios
Cross Application Time Sheet (CATS)
Web User Interface for SAP Plant Maintenance
Learning & SAP Productivity Pak by ANCILE SPP by ANCILE and

Training SAP UEM by Knoa
SAP User Experience by Knoa
8
Exclusions – SAP ECC
# Functionality
Material Management
1 Returnable Packaging Logistics
2 Logistics, Commodity Pricing Engine
3 Empties Management in Material Management
4 MM, Ariba Network Spot Buy in Purchasing
5 Transport Management System (TMS)-ERP: Invoice Integration
6 External Release for Purchase Requisition
Quality Management
1 Stability Study
2 Inspection Data Interface (QM-IDI)
3 Statistical Data Interface (QM-STI)
Warehouse Management
1 Value-Added Services (LE-WM-VAS)
2 LE, Extended Warehouse Management Integration
1 Multiple Valuation Approaches/Transfer Prices
2 Parallel Valuations in the Application Components
3 Accounts Payable Dunning Process
4 Paying by Payment Card
5 Schedule Manager (CA)
6 Withholding Tax - Classic Withholding Tax
7 Plants Abroad
8 Synchronization of Customer/Vendor Master Data (FI)
9 Business Partner Master Data
Controlling
1 Reconciliation Ledger
2 Functional Areas
3 Periodic Tasks
4 Schedule Manager
Project System
1 Multiple Valuation Approaches in Overhead Cost Controlling
2 Access Control List
3 Collaborative Engineering & Project Management (CEP)
Sales and Distribution
Special sales order
1 Cash sales
Rush order
2 Variant Settings for Archiving (SD-SLS)
9
3 SD CRM Condition Integration
4 Contract-to-Cash for Commodities
5 SD/FI-CA Integration with Distributed Systems
6 Empties Management
Production Planning (PP)
1 Line Design
2 Sales & Operations Planning
3 Capacity Planning in Repetitive Manufacturing
4 Forecast-Based Planning
5 BOM Explosion for Variant Configuration
6 BOM Explosion with Phantom Assemblies
7 PP Kanban
8 Repetitive Manufacturing
Make-to-Order Repetitive Manufacturing (Non-Valuated
9
Stock
10 Production Lot Planning
11 Production Planning - Process Industries
12 PP - PI-PCS Interface: Linking of Process Control Systems
13 SAP-OPC Data Access
14 ERP-MES Integration
Plant Maintenance (PM)
1 Linear Asset Management
2 Compatible Unit Management
3 Archive Management
Treasury and Risk Management
1 Credit Management
2 Portfolio Analyzer
3 Financial Risk Management for Commodities
4 Liquidity Planners
5 Commodity Risk Management
Extended Warehouse Management – module not in scope
SAP HANA not considered in scope
3.3 Track 2 - SAP PLM Enablement
Modules in scope
Main Solution
Process
Process
Product Life Document Management System SAP PLM, EHS,
10
Cycle Engineering Workbench ECC
Management
PLM Product Data Replication - SAP also
(PLM)
offers tool for EBOM to MBOM conversion,
which can be considered
Environment, Health and Safety – separate
solution
Service Part Management – separate tool
Product Structure and Assembly Management
Engineering Change Managements
CFolders
Interface of Design software to SAP SAP PLM, ECC
Organization & Maintenance of design drawing

Design Creation of Bill of Material
Revision Control of design documents
Design Document collaboration
Processes in scope
► Document Management System
· Document Control
· Document Distribution
· Document Search on the Internet
· Conversion of Original Application Files
· Document Approval
· Messages
· Data Transfer
· Redlining and Tracking
► Engineering Workbench
· Edit Working Areas
· Edit Layouts for Printing with MS Word
· Define Field Selection for the Engineering Workbench
► PLM Product Data Replication (Master Data) PLM to ECC

· Configuration Management
· Application Link Enabling (ALE)
· Workflow
► Environment, Health and Safety (EHS)

· Product Safety
11
· Hazardous Substance Management
· Dangerous Goods Management
· Waste Management
► Service Part Management (PM+MM)

· Complaints and Returns
· Quality Management
· Transfer and Inventory Management
► Product Structure and Assembly Management (iPPE)

· Define Descriptions for Node Types
· Define Descriptions for Variant Types
· Map Node Type to Generic Object
· Map Variant Type to Generic Object
► Engineering Change Management

· Release Key
· Change Master Records
· Revision Levels
· Profile Maintenance
· Authorization Management
► Collaboration Folders (cFolders)
· Setup collaboration structure for New Development

· Assign partners and provide specifications
· Subscribe to folder with design proposal
· Receive change subscription and send notification
· Release document for further editing
Exclusions - PLM
Exclusions
Recipe Management
Configuration Management
SAP HANA Search and Navigation for PLM
Visual Manufacturing Planner
Display change to ACL
PLM Product Modelling Environment in Variant Configuration
3.4 Track 3 - SAP SRM Enablement
12
Modules in scope
Main Process Process Solution
Central Contract Management SAP SRM
Shopping Cart
Sourcing
Quota Arrangements
RFx & Bidding
Live Auctions
Business Workflow
Supplier Qualification
Supplier
Supplier Self-Services
Relationship
Management Supplier Collaboration
Integration with Collaboration Projects
(cProjects)
SRM-MDM Catalog
Procurement for Public Sector (PPS)
Digital Signatures
Analytics
Strategic Procurement and Sourcing
Operational Procurement
Process in scope
Sub Modules Processes Functionalities

Strategic Procurement Demand Aggregation Collective Processing of
and Sourcing Purchase Requisitions
Shopping Carts
Plan Driven Requirements
External Requirements
13
RFx/Tenders Single Envelope Bid
Processing
(Public /Restricted Bidding)
Two Envelop Bid Processing
(Public /Restricted Bidding)
Offline Bidding Processing
Bidder Response Management
Bid Analysis and Award Note
Processing
Tender Fee Processing/EMD
Processing
Integration with cFolders
Live Auctions (Bidding Reverse Auction
Engine)
Forward Auction
Proxy Bidding
Saving Calculations Analysis
Multi-Currency Bidding
Others Digital Signatures
Functionalities
Centralized Contract Global Outline Agreements
Management
Interface from RFx/Auctions
Interface to ERP System
Operational Catalogue Internally Hosted Catalogues

Procurement
Internal Catalogues (Stock
Material)
Requisition Shopping Carts (Direct and
Indirect Purchases)
Purchase Requisitions
Confirmation Goods Receipts
Service Entry Sheets
Invoice Acceptance
14
Supplier Collaboration Registration of Supplier Registration
Supplier
Supplier Pre-Selection
Supplier Qualification
Portfolio Assignment
Collaboration PO Acknowledgement
Advanced Shipping
Notification Processing
Service Entry Sheet
Processing
Invoice Submission and
Processing
Credit/Debit Memo Processing
Reports/Workflows/ Workflows/Notification Workflows to approve
documents
Notifications/Interfaces
► Shopping Carts
/Roles
► RFx Documents
► Goods Receipts
► SES Confirmations
► Invoice Acceptance
Email Notifications
Reports Vendor Evaluation
All Standard SRM Reports
Interfaces SAP Enterprise Portal (Buyer
Side)
SAP Self Service Portal (Seller
Side)
SAP Business Warehouse
SAP cFolders
SAP ECC
SAP MDM
Roles User Roles and Authorizations
15
Exclusions - SRM
Exclusions
Vendor Managed Catalogues
Procurement for Public Sector (PPS)
Tax Enablement in SRM
Interface to any Non SAP Systems
Mobility
SRM, Country Specific Localization
3.5 Track 4 - SAP MDM Enablement
Modules in scope
Main Process Process Solution

Taxonomy and Attributes SAP MDM
Master Data Duplication/Matching Rule Set

Management User Role and Security definition
– Material
Master / Consolidation and Harmonization
Vendor Workflows
Master
Interfaces – SAP ECC / PLM / nonSAP
applications / SAP PI
Exclusions
Exclusions
MDM functionalities other than Material Master has been considered out of scope
Activities like Data Cleansing, Designing and Enrichment are kept out of scope
16
3.6 Track 5 - SAP HCM Enablement
Following SAP HCM Modules are in project scope.

These modules will be implemented in SAP ECC 6.0 with Enhancement package 7
(EHP7).
Personnel Management Personnel Time Management
► Personnel & Organization ► Positive Time Management

► Personnel Administration
► Personnel Development
► Organizational Management
► Personnel Cost Planning and Simulation
► Management of Global employees Payroll
► Budget Management
► Position Budgeting and Control
► HR Funds and Position
Management
► Payroll India (PY – IN)
► Travel Management
Talent Management Training and Event Management

► E-Recruiting ► Training and Event
► Objective Setting and Appraisals
Management
► Talent Management and Talent
Development
► Enterprise Compensation Management
Shared Services Mobility

► Employee Self-Service (HR Renewal)
► Manager Self-Service (HR Renewal)
► E-Separation
► Claim Settlement (Claims & Re- Apps relevant for approvals if
imbursements) any
► HR Administrative Services
Integrations
► HCM to E-Recruitment 17
► Time Attendance systems to SAP HCM using custom interfaces
► All SAP HCM Internal Integrations (to NW Gateway and Enterprise Portal in SAP)
► HCM to BI/BO (via BW)
Processes in scope
Module in Sub Process
Scope
Personnel & Personnel & Organization module supports HR Professional role
Organization which is used to manage employee data and organizational
data.
► Manage employee master data
► Manage organizational data from the landing page
Personnel Personnel Administration module helps in maintaining employee

Administration information (employee master data) in a systematic form.
► Personnel Actions will be configured based on the
requirement of business (Hire to Retire).
► The employee information will be maintained in the SAP
standard infotypes.
► Standard reports available in SAP
Personnel Personnel development module allows to maintain qualification

Development catalog, perform profile matchups, perform career and
succession planning scenarios and manage development plans
► Maintain Qualification catalogue
► Perform profile matchups (person for position)
► Execute career and succession planning scenarios
► Manage Development plans
Organization Organization Management is a module which is used to

Management represent the organization structure.
► Creation of organizational objects like organization unit,
position, jobs
► Creation of relationships between objects
► Additional characteristics of an object
18
Personnel cost Personnel cost planning and simulation module helps to execute
planning and operational personnel cost planning and simulate compensation
simulation models and analyze their effects.
► Maintain Payment relevant data
► Data collection
► Execute cost planning scenarios
Management Management of Global employees module helps global

of Global companies to streamline their expatriation and repatriation
employees processes.
► Relocation preparation
► Assignment activation
► Global assignment
► Repatriation or move to new assignment
Budget Budget management module enables organization to finance

Management employees efficiently in accordance with budget or legal
requirements.
► Position Budgeting and Control
► Personnel Budget Planning
► Assigning Persons or Positions to Budget Plan
► Check personnel expenditure
Travel Travel Management module enables integrated management of

Management all processes involved in a business trip and travel expenses
incurred.
► Request trip
► Plan and book trip
► Check trip
► Settle trip
► Posting to Finance and controlling
Personnel Time management helps to track the employee daily shift

Time timings, absence quota balances, absences, attendance swipe
Management in/out and evaluation of time data.
► Maintain Public holiday calendar
► Generate and assign Work schedules
► Generate Absence quotas of employees
► Maintain employee absences
► Capture employee clock in/out from attendance systems
via custom interfaces in Time events infotype.
19
► Evaluation of Employee time data
► Time Integration with Payroll
Payroll India Payroll India module enables running of payroll for all
employees in line with India legal and business requirements.
► Maintain Employee’s Basic Pay, Recurring payment or
deductions and Adhoc payments or deductions
► Maintain statutory details for India employees in India
specific infotypes. This is for details like Labour welfare,
Provident fund, Professional tax, Investment
declarations etc.
► Simulation and Live Payroll runs
► Simulation and Live Payroll Posting
► Standard reports available in SAP for statutory forms
like form 16, form 24Q, Challan mapping, etc
Training and Training and event management enables organization to plan

event and manage all business events in a simple and efficient
management manner.
► Business event preparation
► Create Business event catalogue
► Day to day activities ( Book, Prebook, Replace, Rebook,
Cancel)
► Recurring Activities (Follow up activities like Appraisals,
billing and cost transfer activity)
E-recruiting E-recruiting module enables to manage recruitment process to

acquire right talent and fill up vacant or new positions in an
organization.
► Create /Manage Requisitions
► Internal/External Job Posting
► Candidate registration and application
► Screening and Selection process
► Release job Offer
Objective Objective setting and appraisal module helps to manage

Setting and employee objectives in line with organizations objectives and
Appraisals evaluate performance of employees to the set goals.
► Preparation of appraisal documents
► Planning - Goal setting process
► Employee evaluation process (Self- evaluation,
evaluation by appraisers)
► Rationalization
► Release Final appraisal rating
20
► Integration with Enterprise compensation management
module
Talent Talent management and talent development module enables

Management organization to assess employees, create talent groups, assign
and Talent employees to talent groups and view talent profile.
Development
► Talent review meeting/Assessment of employees
► Create Talent Group
► View Talent profile
Enterprise Enterprise compensation management module helps to plan

Compensation remuneration policies effectively, handle job pricing, create and
Management allocate budgets and keep costs under control.
► Job Pricing
► Budgeting
► Compensation Administration (Perform Compensation
reviews and activate reviews)
Employee Self- Employee Self-service enables employees to create, display and

Service change their own data on enterprise portal.
Following SAP Standard Ui5 based applications will be
enabled:
► Landing Page
► Lane Overview
► Work feeds
► My Information
► Search lane
► My Services
► My Timesheet
► Personnel Information
► Employee Profile
► Working Time
► Record working times
► Create Leave request
► Team Calendar
► Benefits and Payments
► Salary Statement
► Workforce viewer for Employee
Following SAP Standard Web dynpro based applications will be

enabled:
► Working time
► Leave overview
► View Time account balances
► Clock in/out corrections
21
► Time Sheet
► Time statement
► Public holiday calendar
► Benefits and Payments
► Form 16
► Advanced Claims (Claims and Reimbursement )
► Leave encashment for India
► Income Tax declaration
► Work Events
► E-Separation Counselling
► E-Separation Approvals
► E-Separation Tasks
► E-Separation Request
► Travel and Expenses
► Create Travel Request
► Delete Travel Request
► Create Expense Report
► Delete Expense Report
► Career and Development

► Appraisal documents
► Overview of appraisal documents
► View/Edit Appraisal document
► Talent profile
► My Career Cockpit
► Job Search
► My Candidate Profile
► Team Information
► Team Calendar
► Birthdays and Anniversaries
Manager Self- Manager Self-service gives managers centralized access to

Service applications they need to perform their tasks and provides them
with all the important data and information for their particular
area of responsibility.
Following SAP Standard Ui5 based applications will be
enabled.
► Lane overview
► Work Feeds
► Approvals
► My Team
► My Team Services
► Substitution
► Team Calendar
► Leave Approval
22
► Employee Profile
► Working time approval
Following SAP Standard HCM Webdynpro applications will be

enabled:
► Team view
► Birthdays and Anniversaries
► Competency Matchup
► Time Recording status of My Team
► Deadline Monitor
► Work Overview Page
► Edit Work Item
► Approve Time sheet
► Time statement
► Approve Leave Request
► Approve Clock In/Out Corrections
► Work Overview Page ( UWL )
► Travel Approval Work center
► Time Approval and Task Reminder
► Employee Information
► Recruiting
► Requisition Monitor
► Questionnaire
► Candidate Assessment
► Data Overview
► Overview of Requisition Requests
► Create Requisition Request
► Talent Management
► Talent Management Page
► Competency Matchup
► Performance Management (Appraisal
documents)
► Compensation Management
► Compensation Planning
► Compensation Approval
► Planning Overview
► Compensation Information
► Compensation Comparison
► Compensation Profile
► Organization
► Organizational Information
► Organization Profile
► Organizational Services
► Reports
► Substitution
► Manage Substitution rules
23
► Substitution overview
► Reminder of dates
► Salary history
HR HR Administrative Services module helps to execute HR

Administrative activities within Portal in both centralized and decentralized
Service manner by involving managers and employees in the process
flow.
► Ten (10) Standard forms will be configured based on
client requirement.
E-Separation The E-Separation module allows to automate processes involved

when an employee leaves or resigns from the organization.
► Initiation
► Counselling
► Approvals
► Due clearance
► Exit Interview
Claims Claims and Re-imbursement functionality in SAP enables

Settlement employee to create, edit and display requests like Claim,
Advance, Advance Repayment, Claim against Advance and
(Advanced
Encashment. This will be part of ESS/MSS.
Claims and Re-
imbursement) ► SAP Standard Apply Claim request
► SAP Standard Approve or reject request
► SAP Standard Post approved requests to Infotypes for
payment via Payroll India
Fiori Standard SAP HR Fiori Apps will be enabled (with no

Applications enhancements):
► People Profile
► Employee Look-up including organizational view
► My Team Calendar
► My Leave Requests (Version 2)
► My Timesheet (Version 2)
► My Paystubs (Version 2)
► My Benefits (Version 2)
► Approve Leave Requests (Version 2)
► Approve Timesheets (Version 2)
► My Time Events
► My Travel and Expenses
► My Travel Requests
► Approve Travel Requests
► Approve Travel Expenses
24
Exclusions - HCM
Exclusions Remarks
Benefits Administration (PA- This module is not in Project scope.

BN)
Concurrent Employment This module is not in Project scope.
Manager’s Desktop Obsolete Functionality. This module is not in

Project scope.
Manager Self Service which is the latest
functionality is covered in the scope
Payroll India (PY-IN) - Mid Year Applicable only for initial Go Live.
Go live functionality
Payroll for countries other than Only Payroll India is in scope. Payroll for other
India than India geography is not in scope.
SAP Learning Solution This module is not in Project scope.
SAP Enterprise Learning This module is not in Project scope.
SAP Employee Interaction This module is not in Project scope.

Center (EIC)
SAP HCM Integration with BPC SAP BPC is not in project scope.
Anything not specifically included in the relevant sections above is excluded from scope.
25
3.7 Track 6 - SAP BI – BO
Following SAP BI BO is in project scope.
SAP BO Dashboards SAP BW
► Dashboards- 5 (across Finance,

► No. of data flows – 15
Procurement, Projects, HR)
► Module Scope – SAP Modules
► 4-5 KPIs in each of these
(Finance, Controlling, SD, MM,
dashboards (maximum) in one
QM, PP, SRM)
single tab
► Source systems for SAP BW –
► Following Dimensions would be
SAP ECC, SAP SRM
covered and would be common to
► 25 BW reports
all function areas
► BW would be enabled to meet the
► Entity
data requirements of 25 BW
► Geography
reports, BO dashboards only
► Product
► KPIs and reports/dashboard
► Customer/segment
finalized by the business users as
► Vendor
per the timeline provided by EY
► Plant
► We have considered following
objects per BW reports:
► Maximum 5 key-figures
(includes calculated,
restricted key figures)
► Maximum 5
characteristics per BW
reports
BI, BO includes dashboards, BW reports
as specified in the scope and hence the
26
3.8 Track 7 - SAP Productivity Pak by ANCILE / KNOA
Modules in scope
► SAP User Experience Management (SAP UEM @ KNOA) and
► SAP Productivity Pak (SPP)
27
28
Source: Information received from SAP India
The details of the functional and technical scope, assumptions, pre-requisites,

etc. are mentioned in
Annexure 2 - EnY_KNOA_SPP_Contract_Draft.pdf enclosed. Responsibilities to
E&Y to be read as Client as this is a back to back sub-contracting with SAP India.
Functional Scope Exclusions

► Implementation of KNOA and SPP covering non SAP GUI and any non-SAP
applications
► Integrating SAP Productivity Pak to Solution Manager
► Implementation of SAP Productivity Pak covering any non-SAP applications
► Anything else, that is not explicitly specified as part of scope
Technical Scope – Exclusions

The technical scope of the implementation excludes the following activities:
► Implementation of any application other than KNOA
► Procurement and installation of infrastructure, hardware and networking
► Procurement and installation of servers and other system requirements
► Installation of Operating Systems (OS) and Database (DB)
► System Volume and Stress Test, Benchmarking tests pertaining to hardware
► System administration and performance tuning at OS/DB and network levels
► Network design (WAN, LAN) and related infrastructure for connectivity
► Anything else, that is not explicitly specified as part of scope
29
Source: Information received from SAP India
30
3.9 Scope of Customizations / RICEFW
Reports & Forms: Pipavav core team will identify the reporting and forms
requirements. EY will suggest standard report provided by SAP which can be used
to address reporting requirements. EY will also provide assistance in identifying
whether ABAP development would be required to address these reporting
requirements or Business Intelligence can be used to address these MIS
requirements. Post this EY would perform the ABAP/ BW report development
Interface: Along with Pipavav Core team, EY will jointly identify interface
development which needs to be done with other applications and SAP. Based on the
business requirements provided by Pipavav, functional specification and technical
documents would be prepared by EY team. EY will suggest leading practices used
during interface development. Further interfaces to and from the SAP with other
product side will require inputs from Pipavav / and its interface vendors.
Developments: 200 ABAP Objects in scope will include(25 ECC reports + 15

Approval workflows and other objects) In order to deliver the above, along with
Pipavav Core team, EY will jointly identify the above developments as per the
attached table to be done in SAP and on the basis of business requirements.
Note: The above is indicative and may vary / increase based on specific reporting /
localization requirements for a given country. If the number increases beyond 200,
additional requirements will be delivered in slabs of 50 ABAP Objects pro-rated as
per the above table.
Additional request – at the rates mentioned in the commercial proposal.
31
4. High Level Overall Project Roles & Responsibilities
Sr. Activity Owner Participate

No.
1 Project Office Setup Reliance Vendor
2 Hardware and Bandwidth Sizing Vendor Reliance
3 Hardware/ Software Procurement Reliance Vendor
4 Infra Setup, Server Installation & Reliance Vendor
Landscape management
5 Project Governance Reliance Vendor
6 Project Management Reliance Vendor
7 Solution Design Vendor Reliance
8 Training / Knowledge Transfer Vendor Reliance
9 Training Adoption Vendor Reliance
10 Configuration, Development & System Vendor Reliance
Integration Testing
11 User Acceptance Testing Reliance Vendor
12 Data Preparation Reliance Vendor
13 Data Migration Vendor Reliance
14 Data Validation Reliance Vendor
15 Project Documentation Vendor Reliance
32
5. Approach and Methodology
EY's Identify, Diagnose, Design, Deliver and Sustain ("IDDDS") framework forms the
foundation of our methodology and will guide our overall approach. This Section
describes the phases in which the Software will be implemented, as well as the
Parties’ respective responsibilities and EY’s deliverables.
Phase 1: Identify (Project Preparation)

Purpose:
► Initial planning and preparation for the Software implementation
► Define the Project goals, scope, timelines and resource requirements
► Identify, on-board and train team members
In this phase, we will work with you to agree ways of working and clarify roles and
responsibilities across EY and PIPAVAV. During this phase, we will validate the
Client’s requirements and perform engagement-specific planning.
The purpose of this phase is to plan and prepare for SAP revamp. During this phase
EY will:
► Assist PIPAVAV team in defining project governance structure comprising
Steering Committee and project escalation matrix. EY will also assist PIPAVAV
team in defining project execution structure comprising Project managers,
business process team, SAP in-house team and EY team;
► Conduct workshop with PIPAVAV senior management team to understand
management expectation from SAP implementation. The goal of this workshop
is to develop vision and action plans that will help in designing future solution;
► Co-develop Project charter and define detailed project plan with phases,
activities and milestones with deliverables for each phases;
► Define detailed process scope, functionality scope, organizational scope and
scope of interfaces with other applications;
► Conduct team orientation workshop and project kick off meeting will be carried
out;
► Check if PIPAVAV IT team has set up a fully operational IDES/Test SAP
environment of SAP which can be used by Project team;
► Check if PIPAVAV has set up a fully equipped Project site infrastructure and
facilities for the Project team;
► Conduct business process owner/Core team training.
Key activities:
► Assist in the development of detailed Project Plan, clearly defining the Project’s
goals, scope, timelines and resource requirements in order to establish
necessary controls for the delivery of the Project
33
► Review the terms on the definition and agreement on project status reporting
and escalation protocols and procedures
► Validate deliverable templates
► Assist in on-boarding of team members will brief them on the business case and
goals of the programme as well as clarifying their roles and responsibilities.
Deliverable(s):
► Project charter
► Project Plan
Phase 2: Diagnose
Purpose:
We will review your current processes against Industry leading / SAP practices. This
is in order to drive alignment of your processes with respect to these reference
models and to develop the consolidated Process Inventory list.
Key activities:
► Develop the BPML (Business Process Master List) covering all the business
processes in the organisation in scope.
► Conduct interviews, working sessions and design sessions with functional and
business unit stakeholders to understand the current state and detailed
requirements.
► Study the current organisation structure, roles and responsibilities along with
the process inventory.
► Validate our understanding of the current state with the client and assist in
updatation of current state documentation as required, along with identified
requirements / improvement opportunities.
Deliverables:
► BPML
► GAP Document for Key processes
Phase 3: Design
Purpose:
This phase is where the end-to-end processes are designed in detail and is therefore
the most effort intensive in our approach. We will work with you to design the
processes within and across each functions / departments.
Key activities:
Build System Design
The purpose of this phase is to prepare detailed ‘Business Blueprint Document’
which is a design document explaining how the Client would run its business
34
processes within SAP. This document will be prepared based on EY’s interaction
with business process owners, and leveraging the inputs for Gaps with respect to
leading Practices conducted in the previous phase.
During this phase EY will -
► Explore opportunities to incorporate leading Shipping and Defense practices
while defining TO-BE business process documentation;
► Conduct SAP discussion/workshop with business process owners/Core team to
discuss new SAP functionalities;
► Advise on SAP Enterprise structure considering scalability and key operating
and reporting requirements of PIPAVAV. Conduct meetings with process
owners and senior management team to validate and approve the proposed
structure;
► Document ‘SAP Business Blueprint Document’ highlighting how business
processes would be executed in SAP
► Conduct meetings with Core team to discuss;
► process and functional gaps i.e. business requirements that cannot be mapped
in SAP directly;
► workaround solutions or developments for the identified gaps;
► EY will conduct business process workshops validating business processes to be
executed in SAP with business process owners and respective functional heads;
► Set up the SAP development server environment.
Build MIS and Interface - during this phase EY will:

The purpose of this phase is to finalize ‘SAP Business Blueprint Document’ with
incorporation of group/local MIS, interfaces, conversions, layouts and enhancement
requirements. Finalize the Business Blueprint document based on inputs provided
by Core team to include statutory and compliance requirements.
During this phase EY will –

► Update the BBP with inputs provided by Core team members on statutory and
compliance requirements;
► Discuss group/local MIS requirements and identify ABAP developments for
reports which can’t be addressed through standard SAP functionalities and
identify development requirements for interfaces with other applications;
► With help of Core team members EY would identify layouts/forms requirements
eg. Purchase Order, Sales Invoice, and Check Printing etc. Existing ABAP
developments will also be explored to be used while development of this
layouts;
► Master data conversion and cut over data conversion requirements would be
identified by EY. EY will share draft listing of key field for master data
requirement so that PIPAVAV IT and Core team can initiate master data
compilation and cleansing activities;
35
► EY would finalize ‘SAP Business Blueprint Document’ with listing for key reports,
interfaces, layout and enhancement requirements;
► EY and PIPAVAV Core team will make a joint presentation to process owners for
BBB sign-off.
Deliverable(s):
► Business Blueprint Document (BBP)
► Listing of developments for reports/ interfaces/ enhancements
Phase 4: Deliver
Purpose:
The purpose of this phase is technology enablement and testing the business
process as documented in future state process design.
Key activities:
During this phase we will do following
SAP Configuration
The purpose of this phase is to enable/configure business process as documented in
‘Business Blueprint Document’ during BBP phase configure system as per ‘SAP
Business Blueprint Document’ in following two stages;
► Baseline Configuration – This sub-stage focuses on delivering a standard system
to business process owners/Core team to ensure that unit testing can be
performed;
► Final Configuration – This sub-stage focuses on delivering a complete end-to-end
cycle including all ABAP developments for full operations. The Core team would
test complete end-to end cycle.
Testing
The purpose of this phase is to perform functional testing so as to assess whether it
has been defined as per business requirement. EY will;
► Prepare Testing Strategy along with PIPAVAV team;
► Co-develop unit and integration test plan and test scripts;
► Provide inputs on unit and integration test scenarios prepare by the Core team;
► Review comprehensiveness of test scripts prepared by PIPAVAV Core team;
► Monitor the user acceptance testing and integration testing performed by
PIPAVAV Core team;
► Set up the production environment;
► Monitor adherence of testing to test plan and test scripts defined earlier;
36
► Provide template to PIPAVAV Core team for capturing user authorization and
profile requirements;
Data conversion
The purpose of this phase is to check system and people readiness comprising
master data, transaction readiness and training to end users. EY will monitoring
master data and cut over migration activities. Following activities would be carried
out as part of this phase:
► Monitor PIPAVAV Core team activities related to perform data collection,
extraction from legacy/SAP system, cleansing and testing of data;
► Co-develop training curriculum. Monitor the activity of the role based product
training conducted by PIPAVAV Core team to end users;
► Define production support plan during and after Go-Live;
► Check the activity of PIPAVAV team uploading master data and cut over data in
production server;
Deliverable(s):
► Testing Strategy
► Data Migration Strategy
► End User Manual
Phase 5: Sustain
Purpose:
The purpose of this phase is to
► Move to production environment for live operation. To ensure system is
stabilized with minimum business disruption. As part of this phase, EY will
prepare ‘SAP Governance structure post Go-live’ document. This document is
prepared before Go-Live in order to have smooth Go-live and support
environment.
► Provide two months onsite support- EY will depute its team onsite for two
months
Governance Approach
37
Post Go-Live Support:
► During the enablement phase EY shall come up with the Post Go-Live Strategy
which would be split into onsite and offsite process. The strategy document
shall be discussed with the Pipavav team to ensure smooth operations during
the Post go –live phase.
► Onsite – The current scope includes 2 month onsite support for each track
separately after go-live of the respective track. This will cover post go-live
support of all processes/ reports delivered till go-live of respective phases. Post
go-live, for all new processes and/ or additional ABAP Objects additional amount
will be charged as part of change request
Governance model will be based on the guidelines as illustrated below:
38
Helpdesk: This is the first line of request where all calls/emails etc. are logged and
reviewed, routed by Pipavav Helpdesk Manager;
► Level 1: The initial routing of the issues for in house resolution by the Help
Desk Manager as per the pre- defined guidelines
► Level 2/Level 3 : The next level of routing of the issue where the Level 1
resource cannot resolve the issue
► Level 4 : All product related issues shall be logged with SAP and EY shall
coordinate for the same.
The above model shall be worked on a minimum fixed number of hours required per
month at an agreed per hour/day rate.
39
6. Expectations from client
Track 1 - SAP ECC Enablement

► PIPAVAV will ensure that all stakeholders have been identified and that they are able to
devote adequate time to this engagement. PIPAVAV has clarity on the process design
that needs to be enabled in the system.
► If the client follows a change governance mechanism, it is the client’s responsibility to
ensure that such process is followed during the project. It is also the client’s
responsibility that project documentation is cleared by the Change Control Board in the
shortest possible time, but no longer than 5 working days after it is presented for
clearance.
► All logistical arrangements during the period when EY consultants are in the PIPAVAV
facility, will be the responsibility of the client SPOC.
► Where a requirement can be met through standard functionality, EY and PIPAVAV will
both work towards using standard functionality. This is in line with the project objectives
outlined at the start of the document.
► The project might require raising OSS tickets for technical issue resolutions. Since
Reliance is the primary customer, the onus of raising and following up on these issues
remains with the customer.
► All technical issues that are related to system setup, are to be owned and resolved by
Reliance technical team. In case OSS suggests any action / resolution related to
PIPAVAV solution then EY team will evaluate the same for further action. All technical
issues related to developments are owned by EY, to the extent that they do not need
SAP OSS Support.
► For the purpose of UAT, we will only test adherence to the blueprinted requirements.
Any new requirements at the UAT Stage, if they do not already exist in the blueprint,
cannot be taken up. UAT sign off cannot be withheld due to any reason other than “Non
Adherence to blueprint.”
► If the customer does not complete sign offs , UAT and other milestone activities within 5
working days, these will be deemed completed and the project will continue as if these
activities had been completed by the customer. The sign off will be deemed given and
the UATs will be deemed approved. The review will be deemed approved.
► Knowledge Transfer is the responsibility of Reliance Infra/ Pipavav stakeholders. During
the Design, Build and Test phases, the team is encouraged to actively participate in the
process. EY will conduct formal KT sessions at the following stages only:
► Final Preparation – To the core team.
► End of post go live support - To the Support Team of the client.
► A program as ambitious as this requires active Organisation Change Management to be
started on Day 1 of the technical implementation project. PIPAVAV will be responsible
for ensuring that such a OCM program exists and runs parallel to ensure the success of
the implementation projects.
► PIPAVAV will ensure that the following stakeholders are identified for each module on
the day of Kick Off.
Role Responsibility
Process Responsible for providing the process that needs to be enabled using
Owner the system.
SPOC The single point of contact who will ensure that all relevant approvals,
40
process adherence and stakeholder meetings are ensured.
Sign Off Responsible for providing the following sign offs: A. Blueprint B. User
Acceptance Testing C. Go Live
Project The Project Manager from Reliance.
Manager
Track 2 - SAP PLM Enablement

► Sanitized data in SAP compatible format
► Relevant information of legacy system interfacing with PLM is to be provided
► Establish regular communications to address any issues as they arise
Track 3 - SAP SRM Enablement

► Well Documented Business Processes
► Digital Signatures
► Templates like Forms/Reports and other business documents
Track 4 - SAP MDM Enablement

► Clean master data from Legacy system
Track 5 - SAP HCM Enablement

► All functional processes are documented. They are well established and all employees
are aware of the processes.
► We assume a 20-30% deviation in process from one site to another. The BBP effort has
been estimated with the assumption that 70% of the configuration and design is
reusable across sites.
► Authorisations Blueprint will be created by EY. The Basis work related to the creation of
roles, user Ids and authorisations is in scope for the BASIS team. The EY functional
team will then do functional testing of roles in Dev client. The Client team will do
functional testing of roles in the Quality client.
► All modules that are starting from Month 2 are starting to allow the customer to do
internal work in process documentation and inputs consolidation. This is recommended.
► Data Migration and Upload is necessary to use any reports.
Track 6 - SAP BIBO

► Availability of dedicated core team for following modules in scope
► Availability of module champions during SAP BW requirement gathering
► Reconciliation with source system and testing would be done by Client business users.
Client would provide the test result for each report and dashboard. EY would perform
the unit testing based on the expected results shared by Client for each BW report and
dashboard.
► Implementation of any third party software or interfaces (other than identified in
technical scope) with SAP is excluded from the scope of this assignment.
► It is assumed that EY will outsource specific area of project (for example Technical). EY
will however ensure robust quality assurance process to achieve quality standards for
outsourced area.
► Client will negotiate directly and procure the hardware, software/ licenses required for
the project
41
42
7. Pre-requisites
Track 1 - SAP ECC Enablement / general

► EY would require S User id, access to configurations and all necessary access to existing
production or confirmation of replica of quality
► Name & Contact details of Project Co-ordinator
► Identification of Core team members and their full time availability for the project
► Access to As Is processes
► Availability of hardware / IT team to support installation activities

► ECC 6.0 EHP 5 or above
► Clean data set for existing masters

► SAP ECC 6.0 with Minimum Eh5 Level
► Clean data set for existing masters
► Separate instance for LAC and Portal

► Clean data set for existing Material masters
► SAP PI Instance

EY assumes that the following pre-requisites to be in place and project commencement
would start after this:
► Adequate authorisation to the customer development and quality systems to be
provided on day of Kick off to EY
► The client to share all report / documentation format with EY and all final
documentation format would be co-developed and agreed
► The technical setup of the system is in scope for the client. The systems, when provided
to EY, will be ready for configuration/ development. This technical set up will be
complete for the Dev client on the day of Kick off.
► For Budget Management, if Position Budgeting Process has never been done in the
organisation, there has to be significant end user training of all managers who are
expected to use fixed budgets for manpower next year. This has to start roughly in the
first month and has to be outside the system. This is a prerequisite for the successful
adoption of the program.
Track 6 - SAP BIBO

43
► Meta data/ hierarchy for each dimension is defined and documented by RINFRA
► Changes to the “Project Scope” will be processed in accordance with the “Request for
Change” procedure. The investigation and the implementation of scope changes may
result in modifications to the Estimated Schedule, Charges, and other terms of these
services to be provided by EY.
► Changes to Client organization (e.g. new entities, acquisitions, reorganizations) may
cause changes in the project scope if the company requests that they be included as
part of the project and the same shall be processed in accordance with the “Request for
Change” procedure.
► Procurement of hardware infrastructure or negotiations with related suppliers is outside
the scope of this assignment and is the responsibility of Client
► Data flows developed in SAP BW will be used for populating SAP BO dashboards & BW
reports only.
► Client will be responsible for providing cleansed data to EY.
► The management of client shall make all management decisions in respect of design,
policy and transformation of business processes at various stages in the entire study.
44
8. Assumptions
Scope Limitations & Assumptions: SAP Software

► Enablement of "off-the-shelf" accounting or financial information reporting software
that was developed by SAP with the standard functionalities available in the package
► EY will not be responsible for resolution of any product related bugs/ issues. EY will
handle aspects related to the issues, if any, by raising the requisite Technical Assistance
Requests through OSS requests to SAP with the help of PIPAVAV.’s administrator. EY
will not be held responsible for resolution of the same. However, EY will be responsible
for all issues relating to custom ABAP objects within scope and developed / deployed by
EY for the duration of the project
► All relevant SAP tools for maintenance shall be provided by PIPAVAV.
Scope Limitations & Assumptions: Scope

► Functionality provided within Standard SAP ERP will be implemented for all the modules
considered in the proposed scope. All modules other than those identified in the scope
of work above are excluded from the scope of the project
► EY will not make any changes to the source code for the current Enablement
► EY will provide PIPAVAV with the leading global repository of controls. It is up to the
PIPAVAV management to pick and choose which controls would be best suited for their
business processes. EY will accordingly configure the same in the system.
► It is assumed that the customization required to meet the client’s needs are not
significant. For the purpose of defining the boundary of the scope there are 200 nos (25
ABAP reports and 15 approval workflows and others). custom development ABAP
objects considered for the various phases of the project (this is applicable to core SAP
ECC6.0 modules as indicated in the scope section) of this SAP enablement. Any
additional development will have to go through the “Request for Change” procedure.
► PIPAVAV will use common chart of accounts for all entities.
► Any changes in the GaaP, localization requirements during the project will be evaluated
for its impact on project time lines and efforts.
► PIPAVAV to provide a detailed roadmap for other non-SAP applications along with the
expected deployment dates for their various functionalities before initiating the SAP
project. SAP deployment solution will heavily depend on the readiness of other non-SAP
applications. Any delays on deployment of non-SAP applications may impact efforts and
timelines of SAP track, which will be evaluated by EY and presented to steering
committee.
► SAP ECC will have opening balances as on go-live date. Historical data / financial
numbers is not considered in scope.
► All group companies identified for the enablement of SAP are to be configured on single
SAP instance.
► Changes to the “Project Scope” will be processed in accordance with the “Request for
Change” procedure. The investigation and the Enablement of scope changes may result
in modifications to the Estimated Schedule, Charges, and other terms of these services
to be provided by EY.
► Changes to PIPAVAV organization (e.g. new entities, acquisitions, reorganizations) may
cause changes in the project scope if the company requests that they be included as
part of the project and the same shall be processed in accordance with the “Request for
Change” procedure.
45
► Data upload programs, integration with current legacy systems and banks will be
considered part of the RICEF list.
► Certification against any standard / law etc. is excluded from the scope of work.
► We assume that there won’t be any changes to legal entity structure, holding structure
for existing entities in the scope. In case of changes, EY will assess its impact on scope
and timelines and present it to steering committee
Scope Limitations & Assumptions: Approach

► All the activities of the Project will be executed from PIPAVAV Mumbai office and EY
offices
outsourced area.
► EY will use train the trainer approach for training which implies that training will be done
to a set of super users/process owners who in turn will provide training to ‘End Users’.
EY may use appropriate tools at its discretion, for this activity. Further it has been
assumed that trainings across various tracks will be conducted simultaneously and not
sequentially. Training across zones should be carried out by PIPAVAV team. All the
trainings will be imparted in English Language only. Training manuals would be prepared
in English language only.
► EY will assist PIPAVAV in the preparation of the test scenarios / scripts
► EY assumes that all activities like Integration Testing , User Acceptance Testing , Master
upload shall happen centrally
► Post go-live support for two month has been included
► PIPAVAV would complete the review and approval of all the project deliverables/
documents within a maximum of 5 continuous working days from the date of
submission. Documents subject to review and approval would be deemed to be accepted
if reviews / approvals are not completed within the stipulated time, unless extensions
have been previously agreed to.
► Processes are common and standardized across all the business lines
► User community is IT mature
► Integration testing with SAP & Legacy systems will be validated by the PIPAVAV
business process owners from the Legacy systems side
Scope Limitations & Assumptions: People & Governance

► PIPAVAV shall nominate and name senior management personnel to oversee the
project.
► PIPAVAV senior management and/or process owners will give time for meeting and
discussions as requested by EY. Intimation for the same will be given for the same in
advance by EY.
► EY understands that PIPAVAV has a competent Core team with good knowledge of
PIPAVAV’s business processes and who will be available and dedicated full time to the
Project. EY also assumes that core team members from all locations would be available
at single location
policy & transformation of business processes at various stages of enablement.
Scope Limitations & Assumptions: Data
46
► PIPAVAV will be responsible for providing cleansed & validated master data and cutover
data to EY for migrating to SAP system.
► Stabilization of SAP ECC for data integration with BW
► Business process needs to be configured and stable in back end transaction system
► Source systems for BW would be SAP ECC only.
Scope Limitations & Assumptions: Infrastructure and Project Office

► We have considered three system land scape in ECC server installation. Installation of
OS is not part of the current scope
► Procurement of hardware infrastructure or negotiations and installation with related
suppliers is outside the scope of this assignment and is PIPAVAV’s responsibility.
► PIPAVAV shall provide necessary connectivity to EY office
► Maintenance, patch updates, software life, integration between the current legacy
systems will be managed by PIPAVAV.
► Enablement of any third party software or interfaces (other than identified in technical
scope) with SAP is excluded from the scope of this assignment.
► PIPAVAV will provide access to all the required documentation, applications, and
servers as necessary for execution of this project.
► PIPAVAV will negotiate directly and procure the hardware, software/ licenses required
for the project
► Seating Hall: Hall with cubicles for consultants & CTMs with sufficient seating capacity.
Preferably, 2 Power Points and 2 network LAN points at each cubicle – with intercom
telephone
► Cabins: Two cabins, one each for EY and PIPAVAV Project Manager – with telephone
and STD and ISD calling facility
► Meeting rooms: Two meeting rooms, one with a seating capacity of 10 people (smaller
meetings), another with a seating capacity of 25 people (large meetings). Each meeting
room to have: One large whiteboard for meeting discussions, projector with screen,
telephone with intercom facility, LAN points (4 in small meeting room, 10 in large
meeting room).
► Printers: 2 Network Printers – Laser. PCs for core team members and consultants and
access to PIPAVAV mail system on outlook and Microsoft Office . SAP GUI loaded on all
front ends
► Access to the internet, consumable like stationery, A4 size sheets, Compact Discs,
writing pens, white board markers etc. as and when needed for the Project. Initial stock
to be maintained on start
► Consultants (travelling from outstation) will be entitled to stay in air conditioned hotel
rooms or guesthouses on single occupancy basis with attached bathrooms. An internet
connection and VPN access is also desired in order to give consultants the flexibility to
work from home as required. Food is expected to be arranged as part of the guesthouse
arrangement.
► EY Consultants will carry company laptops at client site. For EY team 4-6 desktops with
latest system configuration is expected to be arranged.
► Similar arrangement is expected in case consultants are required to travel out of project
base location.
► All consultant (travelling from outside location) will be entitled for monthly project fly
back as per EY travel policy
47
► Local conveyance, local travel, food, lodging at project locations will be borne by
PIPAVAV.
► Project will be based out of Pipavav Mumbai office and EY offices. In case of
international travel / out of Mumbai travel (if any), client would arrange for visa issue,
expense, travel, insurance, accommodation, and other related expenses.
► All terms and conditions to be finalized while singing of the EL.
Assumptions – Infrastructure and Hardware

► All the disk storage should be on RAID 5 of SAN, for Production systems it should be
RAID 1+0
► ECC Production will be on High availability cluster.
► SAP router would need one Public IP as well as one Private IP address.
► Storage should be expandable.
► HW procurement should be on the basis of SAPS.
► RAM shown in the sizing part is only approximate figure.
► CPU Cores depends on the type of hardware.

► SAP ECC has been considered as leading system with classic scenario
► The above mentioned scope has been based on standard fitment only and any
requirement which requires custom development will be considered separately
► Mobile integration has not been considered for PLM. Mobile platform will be Fiori
Standard Apps.
► The total custom object has been capped to 20 Nos. Any requirement beyond 20Nos
shall require separate commercials

► SAP ECC 6.0 has been considered as leading system with classic scenario.
► Vendor Managed Catalogues has not been considered in this scope
► The above mentioned scope has been based on standard fitment only and any
requirement which requires custom development will be considered separately
► Workflows with Approve/Reject features up to maximum 5 approval steps has been
considered
► No direct/automated interface for EMD/Bank portal has been considered
► No third part integration has been considered for SRM
► Mobile integration has not been considered for SRM
► Client has to provide requisite digital signatures required for business transactions
► Multiple digital signatures applicability on single document has not considered for this
48
scope
► Where custom applications are being developed completely as part of this project like
Forward Auctions, this platform would be SAP Netweaver Platform. Non SAP
technology platform will not be used.
► The total custom object has been capped to 42 Nos. Any requirement beyond 42 Nos
49
► SAP PLM has been considered as leading for material master information flow and will
serves are data hub for replication to other SAP applications and Non SAP applications
► MDM Functionalities for Material Master shall only be considered for this scope
► Data Management for Non data structures eg, PDF/FLAT Files are not been considered
for this scope
► Workflows with Approve/Reject features up to maximum 5 approval steps has been
considered
► Mobile integration has not been considered for MDM
► All interfaces for MDM has been considered as synchronous mode via SAP Process
Integration
► Interface to Non SAP System has been kept as 2 NOs
► The total custom object has been capped to 13 Nos. Any requirement beyond 13 Nos

► All functional processes are documented. They are well established and all employees are
aware of the process.
► We assume a 20-30% deviation in process from one site to another. The BBP effort has been
estimated with the assumption that 70% of the config and design is reusable across sites.
► Data Migration and Upload is necessary to use any reports .
► Position Budgeting and Control cannot be started until Funds Management Module has been
implemented in FI.
► EY would require S User id, access to configurations and all necessary acess to existing
production or confirmation of replica of quality.
► Adequate authorisation to the customer development and quality systems to be provided on
day of kickoff to EY.
► The client to share all report / documentation format with EY and all final documentation
format would be co-developed and agreed.
► The technical setup of the system is in scope for the client. The systems, when provided to
EY, will be ready for configuration/ development. This technical set up will be complete for
the Dev client on the day of Kick off.
► Authorisations Blueprint will be created by EY. The Basis work related to the creation of
roles, user Ids and authorisations is in scope for the BASIS team. The EY functional team will
then do functional testing of roles in Dev client. The Client team will do functional testing of
roles in the Quality client.
► The scope is limited to the company codes mentioned in the RFP (Page 5) .
► No integrations with non SAP systems have been included in scope. The integrations taken
into consideration are mentioned below:
► HCM to E-Recruitment
► Time Attendance systems to SAP HCM using custom interface/s
► All SAP HCM Internal Integrations (to NW Gateway and Enterprise Portal in SAP)
► HCM to BI/BO (via BW)
► SAP TREX Engine will be deployed for text search.

► At this time, it is assumed that E Rec will be on a separate server.
50
► All modules that are starting from Month 2 are starting to allow the customer to do internal
work in process documentation and inputs consolidation. This is recommended.
► For Budget Management, if Position Budgeting Process has never been done in the
organisation, there has to be significant end user trng of all managers who are expected to
use fixed budgets for manpower next year. This has to start roughly in the first month and
has to be outside the system. This is a prerequisite for the successful adoption of the
program.
► SAP ANCILE will be used for training material for the new modules being implemented by
EY. No other hard/soft copy manuals or training material needs to be prepared.
► EY has assumed a maximum of 10 screens in UI5 to be delivered.
► All time that is lost because of unavailability of client stakeholders / pending decision from
client or delay response/ sign off beyond three days will be charged extra to the client.
Since this is a fixed bid project, all such time outside the reasonable decision window (3 days
max) is additional cost borne by customer. Impact of such delays would be discussed every
month as change request mode.
► EY will play an Advisory role in the following requirements. The onus of this implementation,
and any risk that arises from non implementation of this is entirely borne by Reliance.
► Assessment of the current system landscape
► Propose the To Be system architecture
► Server and Storage Sizing based on the scope of implementation
► Recommend the security requirements for the To Be landscape
► With help of KNOA we can do the analysis of system performance, however the execution of
this is dependent to variuos factors (like, desktop, network, etc.) which are explicitly out of
scope. For any screen related to HR screens / end user portal (ESS and MSS) EY can advise
on the functional area to client on where all we can optimise.
► 60 days post go live support is scoped at this time.
► Only India geography (India Localisation and India based company codes) are in scope for
the project.
► The customer will ensure that all stakeholders have been identified and that they are able to
devote adequate time to this engagement.
► Post Go Live Support is limited to the following:
► End user Queries
► Any performance issues in the current system. (technical bugs only)
► Post Go Live specifically excludes the following:
► Any new technical requirements.
► Anything other than the two items mentioned above.
► For the purpose of this project, the following terms are defined as under:
► UAT(User Acceptance Test) : The system conforms to the specifications as laid out
in the blueprint.
► Blueprint: The document that mentions the configuration required for the system,
and the functional specification documents for all developments.
► Go Live: When all configuration and development has been moved to the production
client.
► Solution Manager will be used for Project Management in the project and will be the central
repository of documents and process maps.
► For the duration of this project, the EY team will have access to the relevant systems. Any
risk arising out of such access rests entirely with the client. EY does not, at any time, solicit
or accept access to the production systems. No request will be made by the client to the EY
team to check the production client.
51
► In Training/Knowledge Transfer, the Knowledge Transfer to client core team will be done by
EY. End User Training will be planned and conducted by Pipavav for its stakeholders. The
end user training content will be created by EY using ANCILE.
► EY Consultants will have access to reasonable work environment. This includes, but is not
limited to, access to a laptop/desktop connected to the internet, a seating area and desk,
and access to a desk phone connected to the client's internal telephone network, allowing us
to reach stakeholders quickly.
► The client has qualified professionals who will be able to understand SAP Blueprints and
Functional Specification Documents and provide informed sign offs within reasonable time
► There is no integration with any legacy system in scope.
► There is no legacy data migration in scope.
► EY will not do any development that requires the use of an Access Key from SAP (no change
to core code).
► Anything not specifically included in the relevant sections above is excluded from scope –
even if the exclusions section does not specifically list it as an exclusion.
► No post go live support is separately scoped for OM and PA. This will be provided by existing
consultants’ available onsite.
► If the client follows a change governance mechanism, it is the client’s responsibility to
ensure that such process is followed during the project. It is also the client’s responsibility
that project documentation is cleared by the Change Control Board in the shortest possible
time, but no longer than 5 working days after it is presented for clearance.
► All logistical arrangements during the period when EY consultants are in the client facility
will be the responsibility of the client SPOC.
► EY can decide to do some part of the work offshore to hasten delivery. EY has complete
discretion over such delivery.
► The client will nominate one SPOC who will be responsible for all liaison, internal information
gathering, and logistical support to the EY Team at the client location. No logistical support
will be provided to EY team NOT at the client location.
► It is the client's responsibility to ensure that the team that participates in Requirement
Gathering Workshops is aware and empowered to provide final requirements on behalf of
the client. If internal sign off is required, the module SPOC will be responsible for getting it
within ONE day of the Requirement Gathering Workshop.
► For each module, the client will nominate a SPOC who will devote at least 40% of their time
to the said module during the blueprinting stage and 100% of their time during the UAT
Stage. Where the same SPOC is allotted to more than one module, the project plan will be
adjusted to ensure that the SPOC is never booked for more than 100% of their time. The
blueprinting stage of these modules will then be shifted to ensure that the SPOC is able to
participate. Any delay to the overall project plan as a result of same SPOC on multiple
modules, will be attributed to the client, without prejudice to EY.
► The project might require raising OSS tickets for technical issue resolutions. Since Pipavav
is the primary customer of SAP, the onus of raising and following up on these issues
remains with the customer.
► If the customer does not complete sign offs , UAT and other milestone activities within
THREE working days, these will be deemed completed and the project will continue as if
these activities had been completed by the customer. The sign off will be deemed given and
the UATs will be deemed approved.
► Knowledge Transfer is the responsibility of client stakeholders. During the Design, Build and
Test phases, the team is encouraged to actively participate in the process. EY will conduct
formal KT sessions at the following stages only:
► Final Preparation – To the core team.
► End of post go live support - To the Support Team of the client.
52
► The client will ensure that the following stakeholders are identified for each module on the
day of Kick Off.
► Process Owner: Responsible for providing the process that needs to be enabled
using the system.
► SPOC: The single point of contact who will ensure that all relevant approvals,
process adherence and stakeholder meetings are ensured.
► Sign Off: Responsible for providing the following sign offs: A. Blueprint B. User
Acceptance Testing C. Go Live
► The Project Manager from the customer.
► The project plan will be shared with the client within 2 weeks of kick off. Progress against
the project plan will be reviewed once a month. If the baseline has to be changed, a Root
Cause Analysis will be done by both project managers before approving baseline change.
► The client commits to a deep and well thought out organisation change management
program that runs parallel to the delivery program. This OCM program will be designed and
owned by the client. It is very necessary to ensure adoption of the SAP rollout program.
► The project plan will be prepared by the EY project manager and monitored jointly by EY
and Client PM on a day to day basis. The PMO will be setup with equal participation from EY
and the client.
► The methodology that will be followed for delivery is the EY proprietary MPT delivery
methodology. EY will run a familiarisation workshop to ensure that the client is aware of the
methodology, that their queries have been satisfactorily answered and that the client
understands the delivery pattern.
► For development/ stroke, EY will discuss with Reliance team and identify and prioritise items
to be delivered before go live. The balance will be delivered post go live.
► SAP Fiori
a. All FIORI component and NW components are installed in system.
b. Required WF customization should be activated from BASIS side.
c. Trusted RFC config done from BASIS side.
d. HR Config Along with Release strategy in line.
e. Credentials to Access Reliance network.
f. Accessing authorization of FIORI Launchpad.
g. Business Suit Client for FIORI Apps config.
h. Development will be done in Sandbox/development only.
i. Following activities are 0ut of scope of SAP Fiori:
i. Customisation of FIORI apps. (Not in scope)
ii. Customisation of Launchpad. (Not in Scope)
Track 6 – SAP BIBO

► EY assumes that all activities like Integration Testing , User Acceptance Testing , Master
upload shall happen centrally
► Post unit testing EY will release the report/ dashboard for UAT to Client business users.
All reports and dashboards will be deemed validated if no UAT response in received in 3
working days.
► Dashboards will be designed after the report finalization & will be based on the
data/Parameters finalized in the report
53
► Sign off from top management on dashboard mock-ups
► Data flows developed in SAP BW will be used for populating SAP BO dashboards & BW
reports only.
► Implementation of any third party software or interfaces (other than identified in
technical scope) with SAP is excluded from the scope of this assignment.
outsourced area.
► Client will be responsible for providing cleansed data to EY.
policy and transformation of business processes at various stages in the entire study.
Track 7 - SAP Productivity Pak by ANCILE / KNOA (Satyam)

Functional Scope Assumptions
► Implementation of KNOA and SPP will be in English language only
► Implementation of KNOA will be with version 7.1 (available SP level at the time of
implementation)
► Implementation of SPP will be with version 5.2 (or whichever is the latest available
version with licensee at the time of implementation)
► Implementation of SPP and KNOA will be for one instance of SAP only. Any additional
implementation will be managed by Client in house team
► It is assumed that client team will verify and clear created content within one working
day. In the absence of a feedback within this period, output shared will be deemed
accepted
► SAP Consultant will assist Client with the installation and post-installation testing of the
SPP server software in one environment and on one set of servers. Client will be
responsible for the installation and post-installation testing of the SPP server software in
additional environments and/or on additional sets of servers.
► SAP Consultant may provide guidance to Client to set up online context-sensitive help.
However, Client will be responsible for executing the necessary steps to set up online
context-sensitive help
► Content development beyond handholding for 2 sample documents as part of Author
training
► Conversion of non-SCORM compliant content to SCORM compliant content
► Translation of content in any language
► Creation of content using SAP Productivity Pak covering non SAP applications
► Context sensitive help configuration other than standard SAP GUI
54
55
9. Technical Delivery
9.1. Propose IT system architecture and Infrastructure required
The landscape will consist of the following SAP environments:

► SAP ECC
► SAP SRM
► SAP BI
► SAP BO
► SAP EP
► SAP cFolders
► SAP Solution Manager
All the above environments (except solution manager) will be implemented with
three system architecture namely: Development, Quality and Production.
9.2. Server and Storage Sizing
Server Type Size (SAPS) Approx. Memory Hard Disk
ECC Development 2000 16 GB 400 GB
ECC Quality 3000 24 GB 600 GB
ECC Production DB 10000 64 GB 600 GB
ECC Production CI + ASCS 10000 64 GB 100 GB
ECC App1 5000 32 GB 100 GB
ECC App 2 5000 32 GB 100 GB
SRM Development 2000 16 GB 200 GB
SRM Quality 2000 16 GB 400 GB
SRM Production 4000 32 GB 400 GB
BI Development 2000 16 GB 200 GB
BI Quality 2000 16 GB 400 GB
BI Production 4000 32 GB 400 GB
EP Development 2000 16 GB 150 GB
56
EP Quality 2000 16 GB 150 GB
EP Production 6000 48 GB 200 GB
cFolders Development 1000 8 GB 150 GB
cFolders Quality 1000 8 GB 150 GB
cFolders Production 3000 24 GB 200 GB
Solution Manager + SAP 2000 16 GB 300 GB

Router
9.3. Recommend the security infrastructure & setup
57
58
10. Detailed Project Plan with Key Milestones
Resource M1 M2 M3 M4 M5 M6 M7 M8
SAP ECC all modules, PLM, SRM
PP / BBP BBP BBP / R R R FP PGLS PGLS
MDM
BBP R R FP PGLS PGLS
HCM
FP / BBP BBP R FP PGLS PGLS
BI + BO
BBP BBP / R R / FP PGLS PGLS
► PP – Project Preparation
► BBP – Business Blueprint
► R – Realization
► FP – Final Preparation
► PGLS – Post golive support
59
11. Key Milestones & Deliverables
Following are the Key Milestones & Deliverables for the project.
11.1. Milestone: Project Preparation
Deliverables Time Line

KEY activities - overall
· Finalize Project Team · Project Team Structure Organization
Organization Chart
· Format : MS Word , PDF .
· Finalize Project Team

· Project Team Training Schedule
Training Plan
· Format : MS Excel , MS Word
· Define Team Facilities · Project Team Seating Chart (including

Requirements required equipment)
· Format : MS Excel
· Resource plan
· Develop Project Plans · Format : MS Excel , MS Word
· Implementation strategy , End user

training strategy , Testing strategy 0.5 month
· Develop project strategy
and scope · Format : MS Word , PDF
· Post implementation approach

· Define post
implementation approach · Format : MS Word , MS EXCEL
· Size initial hardware, Approve sizing

results,
· Procure hardware
· Format : MS Word
· System landscape strategy
· Define landscape strategy

· Format : MS PPT
· Kick Off meeting

· Prepare for Kick Off
60
11.2. Milestone: Business Blueprint
Key activities Deliverables Time Line -

overall
· Prepare for Business · Blueprint workshop schedule ► 2.5

workshops · Format : MS Excel months
· Conduct business · Business process flows , Gaps identified
workshops ·
· Format : PDF , MS Word
· Finalize project scope and · Finalise scope document and BBP signed
BBP off
·
· Format : PDF , MS Word
· Finalize development · Reporting Interfaces , Enhancements
scope ·
· Format : MS Word , PDF
11.3. Milestone: Realization phase (Build and Test)

overall
· Define master data · Master data definitions 2.5 months
· Format : MS Word , MS Excel

· Baseline configuration · Baseline configuration
· Final configuration · Configured relevant modules
· Develop technical and · Prepare the documentation and approve

Functional Specifications
· Format : MS Word
· All Developments · All enhancements in the SAP System
Developed
· Execute cycle testing · Cycle testing completed
· Integration testing · Testing completed interrelated to other
modules
11.4. Milestone: Final Preparation (Deploy)

overall
· Perform system test · Processes tested 1 month
· Format : MS Excel , MS Word
· Cutover plan Uploading · Cutover work plan and data uploaded
61
overall
·
· End user documents · End user manuals prepared
preparation ·
· Format : MS Word
· Deliver end user training · Trained End user
·
· Format : MS Word
· User acceptance testing · Unit test scripts prepared
·
· User acceptance Sign Off · MS Outlook , PDF , MS word
· Final preparation sign off · Signed off for GO Live to be Held
11.5. Milestone: GO LIVE & Support
Key Activities Deliverables Time Line -

overall
· Provide production · Support provided 2 months

support
· Validate system process · Business process results
results
· Post implementation · Post implementation findings report
review
62
12. Detailed Project - Roles & Responsibilities
Sr. Activity Responsibility

No.
1
· Chairs the Steering Committee
Sponsor Executive
· Establishes the project organisation, roles and
reporting structure
· Ensures that the business need is valid and correctly (Vice Admiral Malhi,
prioritised and launch the project successfully CEO)
· Drives organization change management, takes key

decisions, approves all key project deliverables
· Provides guidance on overall project risk mitigation
and intervention to key deviations
2. Project manager
· Act as the link between the project, the business
community and most importantly, management
decision making groups (Arun Mattaparthi)
· Resource scheduling and monitoring work progression
· Ensures attendance at training courses, chases
subject matter experts when needed
· Ensures that the business is ready for the new system
and to endure the impacts on the business of the
system are appropriately managed and communicated
· Ensure availability, accessibility, quality and security
of all stakeholders, resources, infrastructure including
various product vendors, services providers, internal
stakeholders etc. for various activities and tasks
involved during the project tenure
3. Business Process
· Explain key business processes to implementation
Owners
team
· Explain the key control integration into the processes
1.Sh. Nikhil Jain –
· Agree on the gap analysis on current processes and
Finance
align on the recommendations
· Validate and agree on “To-Be” business processes
(BBP) 2. Sh. Devi Prasad
Satpathy- Supply
· Identify risks and approve risks for monitoring
Chain Management
· Providing test data for Training and Testing
63
· End User Training 3. Sh. Alphesh Darji –
Projects
· Approve user role assignments and communicate
access assignments or role changes to users
· Testing of changed business processes/systems owing 4. Sh. Somnath
to ERP controls Ganjuli – Production
(BCS)
· User Acceptance Testing of the configured solution
· Integration testing by verifying all Interfaces
developed across systems 5.Sh. Noushad –
Production (Blasting &
· Validate and verify migrated data
Painting)
· Providing data for configurations
· Providing assistance in end-user support as well as
6.Sh. Malay
roll-outs
Choudhary –
Production (Piping)
7. Sh.Snehal Singla –
Production (System
Integration)
8.Sh. Pradeep C -
Designing
4. IT and Hardware
· Providing the knowledge and understanding of the
support - Pipavav
current infrastructure and internal controls processes
· Work in tandem with the implementation team during
installations and execution of the trainings, testing
· Provide inputs on development of Interfaces across
systems
· Attending all relevant trainings to gain expertise on
ERP modules
· Participation in the development of reports and other
technical components
· QA based testing on ERP application from IT
deployment perspective (security, configurations etc.)
Eventual support ownership for ERP application
modules
5
· Ownership of the Change Management Plan
Sh. Debashis Bir, COO
· Execution of the Change Management Plan
· Report Status of Change Management to the Senior
Management
· Provide inputs while the Change Management
64
Strategy and Communications plan are being built
· Facilitate the identification of stakeholders and
meetings with them
· Facilitate the roll-out of Change Readiness Survey
· Implement the Change Impact Action Tracker Plan
· Ownership of the Communication Plan
· Execution of the Communication Plan
· Drive the Change Champion Network
6 Vendor Partner /
· Provide business value to client and act as trusted
Director
advisors effectively maintaining close working
relationships with senior client engagement and
sponsorship team
· Monitor project progress and participate in steering
committee, review meetings, as required
· An ultimate escalation point on vendor side in case of
issues
· Ensure proper team deployment and own overall
scheduling and commercials for the engagement
· Manage client expectations regularly and ensure
delivery of highest quality service to customers
7 Vendor Engagement
· Develops and manages the project team work
Leader
schedule and aligns with the client expectations
· Coordinates with the project stakeholders, project
team and reviews risks, schedule and conflicts
· Provides knowledge and expertise on common
practice internal controls processes
· Tracks quality control measures and timely
deliverables meeting project milestones
· Periodic schedule tracking and team oversight
· Collates and produces Status reporting at agreed
interval
· Aid in overall change management and communication
8 Functional team
· Understand the current business processes
· Finalise functional design document along with Client
Business process owners
· Provide work around and recommendations for
product gaps
65
· Finalise the design and direction of data flow for
interfaces between SAP and non-SAP Applications
(Project management software / design software)
· Configuration of the system and assist during UAT
sessions
· Provide training to Business Process Owners
9 Technical team
· Technical solution design
· Development of objects
· Development of conversion programs/control check
scripts
· Technical documentation
· Testing of technical objects
· Support and technical troubleshooting
10 Data base
· Instance Management
Administrator
· Database and system administration
· Overseeing applications and database hardening
requirements and procedures
66
67
13. Profile of all Project Resources
Attached Annexure 1
68
14. Escalation Matrix
Level - I: Immediate
Level - II: Crossing defined response and resolution time
Level - III: Exceeding defined response and resolution time by 6 hours
Level - III: Exceeding defined response and resolution time by 12 hours
Level – IV: Management Escalation for very critical Issues.
Escalation Level Name Designation Contact Number Email I’d
To be decided
Level I after contract Module Lead
signing
To be decided
Level II after contract Project Lead
signing
Haresh
Level III Practice Head
Culcuttawala
Partner – SAP
Level IV Mazhar Khan +91 22 61920002 Mazhar.khan@in.ey.com
IT Advisory
69
15. Payment Terms
EY shall bill the Client for its fees, expenses and applicable taxes, if any, as they are
incurred, in accordance with the below/attached schedule.
► On signing of the engagement letter - 20 % of total fees

► On Enterprise Structure finalization - 10 % of total fess
► On submission of Business Blueprint - 20 % of total fess
► On completion of Integration testing - 15 % of total fees
► On completion of User Acceptance Test - 15 % of total fees
► On Go-Live of the project - 15 % of total fees
During support phase of 2 month of post go live - the balance amount of 5 % of total fees
would be invoiced at the end of each month.
For Annexure 4- GCC

EY response: EY response to GCC has been submitted to CPG team.
The terms and conditions with respect to Services performed by EY shall be governed by
the Engagement Letter (to be signed while finalizing of the project) including the,
statement of work and General Terms and Conditions (shared separately with the
commercial team (CPG)).
Annexure 3 SCC is with EY comments and inputs is shared with CPG team
70
16. Vendor Details
Please find below details from EY as per the RFQ format.

Company background India Presence Client References
(including global presence, turnover, key (offices, staffing, Indian
executives, global clients) projects – both
commissioned and
won/in-process)
Global headquarters: London The offices information Provided in the tables

is provided in the last below
Global Chairman and CEO: Mark
page of this document.
Weinberger.
India Regional Managing Partner and and
Chair of Global Emerging Markets
Committee: Rajiv Memani
Number of people globally: 190,000 (as
of 30 June 2014). Read about our
commitment to our people.
Global revenues: US$27.4 billion
(Financial Year '14, ending 30 June
2014).
Geographic Areas: Americas; Europe,
Middle East, India and Africa; Far East;
Japan; Oceania.
Offices: 709 in 150 countries. See our
office locator.
Service lines: Assurance and Advisory
Business Services, Tax, Transaction
Advisory Services. Read more about our
Services.
Founded:1989 through the merger of
Ernst & Whinney and Arthur Young & Co.
Oldest component from 1849. Learn
more about our history.
SAP Implementation Experience (Client Names & High Level Scope of Work highlighting EHP7 implementation)
S.
No Client Name High Level Scope of work EHP7 (Yes/No)
NA
1 Global Cloud Xchnage SAP BPC Manpower Planning
SAP EHP 7 Implementation across all SAP HCM Yes
2 LT Foods Modules
71
3 Mayur Uniquoters Modules
4 Lotus Greens Modules
Industry Experience (SAP projects in Shipping Industry / Functional templates)

S. Functional Templates
No Client Name High Level Scope of work Used (Yes/No)
1. Cochin Shipyard (case study enclosed) Yes
Ministry of Defence IT Advisory for ERP Project- As-is, FRS, Data NA
2. (Navy) Migration, PMO
IT Advisory for ERP Project- in areas of Finance, NA
IHQ of Ministry of
procurement, HR, Eng. & QA, Contract
Defence (Army)
3. Management, Asset/ Plant Maintenance
72
Program Management Capabilities (Project Team Sizes managed)
No Client Name Project Team Size Team Composition
IPG India (Inter Public To be shared later To be shared later
Group)
NHPC To be shared later To be shared later

Dialog Telecom To be shared later To be shared later
(Srilanka)
GSPC To be shared later To be shared later

Nirma To be shared later To be shared later
HMEL To be shared later To be shared later
Delhi Airport To be shared later To be shared later
Reliance Group Experience
Name of Reliance Group Entities Engagement Name Service Name

PMS Advisory, project details attached in
Reliance Group PMS Appendix
Reliance Globalcom Limited (Global SAP Enablement of - (ECC, HCM, BPC, BI, Controls
Cloud Xchange (GCX)) Transformation Manual, Accounting Manual)
Due Diligence
Reliance Communications Limited Review Domestic Taxation - Compliance
Business valuation Share-Business Valuation
Business Valuation Share-Business Valuation
Reliance Power Limited DDR assignment Indirect Tax Advisory
IT Due Diligence IT Transformation
Project Om M&A
Project OM Due Diligence - Others
Project OM Corporate Deal Advisory - Domestic
Project OM HR Transaction Advice
CDM Advisory
Reliance Infrastructure Limited Services CCS-CDM Advisory
EDDR EDD - EDDR
Messaging system Information security
review assesment/design/development
Project Opal M&A
73
Regulatory Analysis
for entry Business Tax Advisory
WBGA - Ind. Veri -
Slum Dwell Internal Audit
Reliance Life Insurance Company
Limited FBT Consulting - Personal tax
Retainer May 04-
April 05 Domestic Taxation - Consulting
Review of the TP
Document Transfer Pricing
Service tax SCN &
Rep Indirect Taxation - Consulting
Transfer Pricing
Review Transfer Pricing
ITSPP review and
update ITRM-IS Audits
Valuation of
Reliance Securities Limited Potential Target Share-Business Valuation
Memo- Tax
Reliance Infratel Limited provisioning Business Tax Compliance - Single Country
Memo-Tax
Provision for FY '09 Business Tax Compliance - Single Country
Reliance Infratel
March 2010 FAAS support-advice-training-other
Stat Audit yr end
Mar 31,2009 Statutory Audit
Stat Audit- Sep 07 Statutory Audit
Tax Provisioning TARAS
Val Rev of RCL
tangible assets Valuation Review
Val Review of RTIL SAS 73 - Valuation Review
74
17. EY Contact Details
Please find below the contact details of single point of contact with contact details.
Name: Satyam Jha

Ernst & Young LLP
Block No B2, 5th Floor, NKP , Goregaon - East, , Mumbai , , Maharashtra 400063, India
Office: +91 22 61923349 | Mobile: +91 9819904272 | satyam.jha@in.ey.com
Website: http://www.ey.com
75
Our offices
Ahmedabad Kolkata
2nd floor, Shivalik Ishaan 22, Camac Street
Near. C.N Vidhyalaya 3rd Floor, Block C”
Ambawadi, Kolkata – 700 016
Ahmedabad – 380 015 Tel: + 91 33 6615 3400
Tel: + 91 79 6608 3800 Fax: + 91 33 2281 7750
Fax: + 91 79 6608 3900
Mumbai
Bengaluru 14th Floor, The Ruby
12th & 13th floor 29 Senapati Bapat Marg
“U B City” Canberra Block Dadar (west)
No.24, Vittal Mallya Road Mumbai – 400 028
Bengaluru – 560 001 Tel + 91 22 6192 0000
Tel: + 91 80 4027 5000 Fax + 91 22 6192 1000
+ 91 80 6727 5000
Fax: + 91 80 2210 6000 (12th floor)
Fax: + 91 80 2224 0695 (13th floor) 5th Floor Block B-2,
Nirlon Knowledge Park
1st Floor, Prestige Emerald Off. Western Express Highway
No.4, Madras Bank Road Goregaon (E)
Lavelle Road Junction Mumbai – 400 063
Bengaluru-560 001 India Tel: + 91 22 6192 0000
Tel: +91 80 6727 5000 Fax: + 91 22 6192 3000
Fax: +91 80 2222 4112
6th floor NCR

“U B City”Canberra Block Golf View Corporate
No.24,Vittal Mallya Road Tower – B
Bangaluru-560 001 Near DLF Golf Course,
Tel: + 91 80 4027 5000 Sector 42
Tel: + 91 80 6727 5000 Gurgaon – 122 002
Fax: + 91 80 2210 6000 Tel: + 91 124 464 4000
+ 91 80 2224 0695 Fax: + 91 124 464 4050
Chandigarh 6th floor, HT House

1st Floor 18-20 Kasturba Gandhi Marg
SCO: 166-167 New Delhi – 110 001
Sector 9-C, Madhya Marg Tel: + 91 11 4363 3000
Chandigarh – 160 009 Fax: + 91 11 4363 3200
Tel: + 91 172 671 7800
Fax: + 91 172 671 7888
4th & 5th Floor, Plot No 2B,
Tower 2, Sector 126,
Chennai
Noida – 201 304
Tidel Park,
Gautam Budh Nagar, U.P. India
6th & 7th Floor
Tel: + 91 120 671 7000
A Block (Module 601,701-702)
Fax: + 91 120 671 7171
No.4, Rajiv Gandhi Salai
Taramani
Chennai – 600 113 Pune
Tel: + 91 44 6654 8100 C—401, 4th floor
Fax: + 91 44 2254 0120 Panchshil Tech Park
Yerwada (Near Don Bosco School)
Hyderabad Pune – 411 006
Oval Office Tel: + 91 20 6603 6000
18, iLabs Centre, Fax: + 91 20 6601 5900
Hitech City, Madhapur,
Hyderabad – 500 081
Tel: + 91 40 6736 2000
Fax: + 91 40 6736 2200
Kochi 76
9th Floor “ABAD Nucleus”
NH-49, Maradu PO,
Kochi – 682 304
Tel: + 91 484 304 4000
Fax: + 91 484 270 5393
Ernst & Young LLP
EY | Assurance | Tax | Transactions | Advisory
About EY
EY is a global leader in assurance, tax,
transaction and advisory services. The insights
and quality services we deliver help build trust
and confidence in the capital markets and in
economies the world over. We develop
outstanding leaders who team to deliver on our
promises to all of our stakeholders. In so doing,
we play a critical role in building a better working
world for our people, for our clients and for
our communities.
EY refers to the global organization, and may
refer to one or more, of the member firms of
Ernst & Young Global Limited, each of which is a
separate legal entity. Ernst & Young Global
Limited, a UK company limited by guarantee,
does not provide services to clients. For more
information about our organization, please visit
ey.com.
Ernst & Young LLP is one of the Indian client serving member
firms of EYGM Limited. For more information about our
organization, please visit www.ey.com/in.
Ernst & Young LLP is a Limited Liability Partnership, registered
under the Limited Liability Partnership Act, 2008 in India, having
its registered office at 22 Camac Street, 3rd Floor, Block C,
Kolkata - 700016
© 2015 Ernst & Young LLP. Published in India.
All Rights Reserved.
ED None
This publication contains information in summary form and is

therefore intended for general guidance only. It is not intended to
be a substitute for detailed research or the exercise of
professional judgment. Neither Ernst & Young LLP nor any other
member of the global Ernst & Young organization can accept any
responsibility for loss occasioned to any person acting or
refraining from action as a result of any material in this
publication. On any specific matter, reference should be made to
the appropriate advisor.
77

3-EY - RFP Response - State of The Art SAP ERP For Pipavav - 18 Aug

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

3-EY - RFP Response - State of The Art SAP ERP For Pipavav - 18 Aug

Transféré par

Droits d'auteur :

Formats disponibles

EY Response -RFP Response

State of the Art SAP ERP for Pipavav

Technical Proposal - August 2015

PDOECL currently uses IMMS Application including modules for Procurement,

As described in RFP, below is the project objective:

► Extensive automation of manual process

Above shall be achieved by –

3.1 Legal Entities in scope

Abb. Companies Location

Other Legal Entities in scope - Subsidiaries

Location of the Project:

Any SAP Module/functionality which is not specifically mentioned in detailed scope

3.2 Track 1 - SAP ECC Enablement

Main Process Process SAP Solutions

Cost Planning SAP ECC –Project

Consumption Based Planning (MRP) SAP ECC - MM, SRM

Bill of Materials (BOM)

Production Capacity Planning

Inspection and Quality Certificates

FI General Ledger SAP ECC - FI

FM Master Data SAP ECC - FM

Cost Element Accounting SAP ECC - CO

Transaction Manager SAP TRM

Treasury Accounting & Country India Specific Process

Equipment and Technical Object SAP ECC - PM

Learning & SAP Productivity Pak by ANCILE SPP by ANCILE and

3.3 Track 2 - SAP PLM Enablement

Product Life Document Management System SAP PLM, EHS,

Organization & Maintenance of design drawing

► PLM Product Data Replication (Master Data) PLM to ECC

► Environment, Health and Safety (EHS)

► Service Part Management (PM+MM)

► Product Structure and Assembly Management (iPPE)

► Engineering Change Management

► Collaboration Folders (cFolders)

· Setup collaboration structure for New Development

3.4 Track 3 - SAP SRM Enablement

Sub Modules Processes Functionalities

Operational Catalogue Internally Hosted Catalogues

3.5 Track 4 - SAP MDM Enablement

Main Process Process Solution

Master Data Duplication/Matching Rule Set

Following SAP HCM Modules are in project scope.

Personnel Management Personnel Time Management

► Personnel & Organization ► Positive Time Management

Talent Management Training and Event Management

Shared Services Mobility

Personnel Personnel Administration module helps in maintaining employee

Personnel Personnel development module allows to maintain qualification

Organization Organization Management is a module which is used to

Management Management of Global employees module helps global

Budget Budget management module enables organization to finance

Travel Travel Management module enables integrated management of

Personnel Time management helps to track the employee daily shift

Training and Training and event management enables organization to plan

E-recruiting E-recruiting module enables to manage recruitment process to

Objective Objective setting and appraisal module helps to manage

Talent Talent management and talent development module enables

Enterprise Enterprise compensation management module helps to plan

Employee Self- Employee Self-service enables employees to create, display and

Following SAP Standard Web dynpro based applications will be

► Career and Development

Manager Self- Manager Self-service gives managers centralized access to