1_RAIN_SOW_High Level Scope of Work_V1.0.pdf

SCOPE OF WORK

Submitted to

RAIN

By

Wipro Ltd. July 2008 Version 1.0

High Level Scope of Work

Wipro Limited of 50 © Wipro Limited, 2008, All Rights Reserved.

This document is proprietary to Wipro Infotech, a division of Wipro Limited.

You may not modify, copy, reproduce, republish, upload, post, transmit or distribute any material from this document, in any form or by any means, nor may you modify or create derivative works based on the text of any file, or any part

thereof for public, private or commercial use, without prior written permission from Wipro Limited.

DOCUMENT INFORMATION Project Name

Document Name Document Location

RAIN SCOPE OF WORK

Document Server

DOCUMENT HISTORY Version Document

Name Date Author Reviewed

BY Change Control

1.0 SCOPE OF WORK

30.07.2008 Anish kumar Draft Version






TABLE OF CONTENTS

1. STATEMENT OF WORK ............................................................ 5

2. PROJECT SCOPE ..................................................................... 6

2.1. High Level Scope of Engagement .................................................................................... 6

2.2. Functional Scope ....................................................................................................................... 6

2.3. Not in Scope ................................................................................................................................. 8

2.4. Organizational Scope .............................................................................................................. 9

2.5. Geographical Scope ................................................................................................................. 9

2.5.1. Geographical - Scope Exclusions .............................................................................. 10

2.6. Technical Infrastructure Scope ....................................................................................... 10

2.7. Development Scope ............................................................................................................... 11

2.8. Interface and Enhancement Scope ............................................................................... 11

2.9. Data Conversion Scope ....................................................................................................... 12

2.10. Reports and Forms Scope .............................................................................................. 15

2.11. SYSTEM TESTING ............................................................ 16

2.11.1. Testing Objectives .......................................................................................................... 16

3. PROJECT TIMELINES ............................................................ 23

4. PROJECT ORGANIZATION & TEAM STRUCTURE .................... 25

4.1. Wipro Project Team Composition ................................................................................... 25

4.2. RAIN Project Team Composition .................................................................................... 26

4.3. Roles & Responsibilities ....................................................................................................... 27

4.3.1. RAIN’s Roles and Responsibilities ...................................................... 27

4.3.2. Wipro's Roles and Responsibilities ..................................................... 29

5. PROJECT MANAGEMENT ....................................................... 34

6. PROJECT DELIVERABLES ...................................................... 39

6.1. Project Deliverables ............................................................................................................... 39

7. TRAINING PLAN ................................................................... 44






7.1. Training Objectives and Goals ......................................................................................... 44

7.2. Training Calendar .................................................................................................................... 44

7.3. Training Scope .......................................................................................................................... 44

7.4. Training Approach................................................................................................................... 46

8. QUALITY STRATEGY ............................................................. 50






1. Statement of Work This statement of work describes the work to be undertaken by WIPRO, the tasks to be performed and the Deliverable Materials to be delivered and the Estimated Schedule. In addition the responsibilities of RAIN are listed. Changes to this Statement of Work will be processed in accordance with the procedure described in Appendix B – Project Change control Procedure. The investigation and the implementation of changes may result in modification to the Estimated Schedule, Charges and other terms of this Statement of Work and/or Agreement. The following are enclosed with this Statement of Work: Appendix A – Deliverable Material Guidelines Appendix B – Project Change Control Procedure Appendix C – Deliverable Materials Acceptance Procedure Appendix D – Escalation Procedure In the event of any contradiction, inconsistency or ambiguity between the terms of this Statement of work and the Agreement, this Statement of Work will govern. This Statement of Work, its Appendices and the Agreement represents the entire agreement between the parties regarding the subject matter and replace any prior oral or written communications.






2. Project Scope

2.1. High Level Scope of Engagement

From the RFP document and discussion with RAIN , we have identified the during the engagement, Wipro will provide the following services to RAIN

• Program and Project Management Services • Implementation services for ERP solution as defined in detail in the scope

of work • Development of project artifacts described in detail in “Deliverables”

section of this proposal document • BASIS Administration and Implementation of Solution Manager • Assistance in development of Training Strategy, Plan and use of “Train the

Trainer” approach.

2.2. Functional Scope

The following components of SAP will be implemented during the engagement:

• mySAP ERP ECC 6.0. • SAP BI 7.0.

Wipro proposes to have a Big Bang approach towards the implementation of the above components. The following modules shall be implemented for RAIN. SAP ECC 6.0 SAP ERP Functional Module Sub-Module

Financial Accounting

• General Ledger • Accounts Payable • Accounts Receivable • Fixed Asset Accounting • Bank Accounting • Cash Journal Accounting • Tax Accounting • Financial Statement Versions. • Inventory Accounting.

Management Accounting (Controlling)

• Profit Center Accounting • Cost Center Accounting • Product Costing






SAP ERP Functional Module Sub-Module

• Profitability Analysis Sales and Distribution

• Sales Order Processing • Order Related Billing • Inter Company Billing • Credit Check • Invoicing • Sales Returns Processing • Scrap Sales Accounting

Materials Management

• Purchasing including Purchase Requisitioning and Purchase Order Processing

• Inventory Management • Batch Management • Vendor Invoice Verification • External Services Management • Service Entry Sheet and Acceptance • Storage and Physical Inventory • Lean Warehouse Management

Quality Management • Incoming material Inspection • In-process inspection • Out bound inspection

Production Planning • Sales and Operations Planning • Materials Requirement Planning • Shop floor Control • Made to Order / Made to Stock Scenarios

Plant Maintenance • Planned & Breakdown Maintenance. • Equipment Master Maintenance.

Country Specific Taxation

• Standard Content as available in mySAP ECC 6.0 both for US & Indian Operations.

Workflow • Standard Workflow Objects in SAP and develop 10 Z Workflows to cater the requirements of Business.

SAP Business Intelligence Sub-Module

Standard Content

Standard BI Content for the following ERP modules: • Financial Accounting • Controlling • Sales and Distribution






• Materials Management • Production Planning • Additional Z Developments to an

extent of 10 Infocubes and 70 reports there from.

Any changes to either assumptions above will have the effect of nullifying this document. If RAIN so desires, WIPRO will be pleased to provide another SOW considering the changed circumstances.

2.3. Not in Scope

1. CRM. 2. SRM. 3. SEM. 4. SCM / APO. 5. XI. 6. Entreprise Portal. 7. HCM & Payroll, ESS & MSS. 8. EHS. 9. TREASURY & FUNDS MANAGEMENT (FSCM), Travel Management. 10.WMS & Logistics Execution. 11.CS. 12.Project Systems. 13.DMS & KM 14.Governance, Risk & Compliance. 15.And any other Module not mentioned explicitly in the scope.






2.4. Organizational Scope

The following legal Entities will be covered as part of the implementation:

♦ Rain Commodities Limited (RCOL) ♦ Rain CII Carbon India Limited ♦ CII Carbon , USA

No Other organizational Unit will be covered as a part of the scope of Work.

2.5. Geographical Scope

The scope of the ERP project will include the following RAIN sites:

ENTITY RCOL RAIN CII Corporate Office

Hyderabad, India Hyderabad, India

Houston, TX. U.S.A

Manufacturing Plants

1. Nalgonda, A.P

2. Kurnool, A.P

1. Vizag 1. Chalmette, Louisiana (USA)

2. Gramercy, Louisiana (USA)

3. Lake Charles, Louisiana (USA)

4. Narco, Louisiana (USA)

5. Moundsville, Virginia (USA)

6. Purvis, Mississippi (USA)

7. Robinson, Illinois (USA)

Sales Offices 60 - - Depots 150 Depots None None Exports No Yes Yes






2.5.1. Geographical - Scope Exclusions

♦ Operations at the subcontractors ♦ Other Location of the company or its subsidiaries, sister companies or

organizations will be excluded from the scope of implementation ♦ Implementation at any other Business entity will be scoped and estimated

separately.

2.6. Technical Infrastructure Scope

WIPRO will make recommendation in the areas of :-

♦ Sizing of hardware and network required for RAIN ♦ Suitability of different platforms for the SAP Application

These recommendations will be made in a ‘non binding’ manner to RAIN. The recommendations may be made if required on the basis of transaction volume and user population expected by RAIN. In the different areas of operation, RAIN is free to request for third party opinion on the same and implement the same recommendation. WIPRO will play a supporting role to RAIN in obtaining the adequate performance from the hardware and network components of the solution. During the implementation, the scope of the activities performed by the technical stream can be broken into two broad areas :-

♦ System Administration

WIPRO will provide system administration support for the setup of the hardware infrastructure through the implementation of the project. The activities that will be covered during the implementation are :-

o Set up of the different SAP Environments - Development, Quality, Production as per the timelines requirements of the project

o Set up of the authorizations relevant in the different environment o Ensuring that the requisite level of patches and hot fixes are

downloaded and applied on the system as required o Backup of the different SAP Environment o SAP Transport Management o Basis Training to the RAIN personnel.

Regular infrastructure maintenance activities related to the existing Local Area Networks, Desktops, GUI, operating systems , applications, printers and backup resources will be managed by RAIN. Taking periodic Backups and planning and






executing disaster recovery will be sole responsibility of RAIN, Application of software patches and service packs will be responsibility of WIPRO.

2.7. Development Scope

The development team is responsible for design, coding and testing of identified reports/layouts/forms/enhancements, user exits , interface and data conversion programs. In addition the team will perform the following tasks :-

♦ Technical evaluation of Gaps ♦ Production of Technical Specification from Functional Specification for in

scope developments ♦ To provide Technical Inputs to the functional Team.

The standard solution envisaged for RAIN provides large number of useful reports. It is highly recommended that RAIN makes the fullest use of these standard SAP Reports.

2.8. Interface and Enhancement Scope

After the implementation of the SAP R/3 solution, there will be minimal interfaces maintained with the legacy system. The following are the interfaces indicated in the documents at the RFP Stage Application In SAP/

Outside SAP Interface (Into SAP)

Interface (From SAP)

Relevant Organizational Entity

Weighbridge Outside SAP Yes No RCOL,RCIL, CII

Distributed Control System

Outside SAP Yes No RCOL,RCIL,CII

LP System (Linear Programming Planning System)

Outside SAP Yes No CII,RCIL

Customized Sales Screen for Use of Data Entry

In SAP - - RCOL (Customized Development)

Payroll Interface

Outside SAP Yes No RCOL, RCIL, CII






=# In all these cases feasibility study needs to be carried for interface design, based on this some changes may be required to be carried out at the legacy system end in order to make it ‘Talk’ to SAP system. This needs to be carried out by a suitable third party identified by RAIN/RAIN. However the interfaces would be designed by WIPRO. Interfaces above will be evaluated during the Business Blueprint and the exact modules of interfaces will be decided at this point. The interfaces requirements associated with the above will be catered through batch data exchange process or information downloads in the form of text files or reports. Given this fundamental assumption, we propose that any other enhancements other than those detailed herein above to the SAP system be considered excluded. If there are any business critical requirements that are not handled by the standard software, these will be considered case to case basis and implementation will be initiated after going through the Project Change Control Procedure as outlined in Appendix B. Any other interfaces or Enhancements need to be analyzed and categorized according to the nature of the development during the initial stages of the project., and its impact on the overall timelines and effort of the project to be reviewed and addressed through Appendix B – Project Change control Procedure.

2.9. Data Conversion Scope

Data Migration is the process or set of processes whereby data from existing systems is moved to the new system. Data migration is also one of the critical elements associated with a successful system implementation. Unless valid accurate and complete data components are available in the new system, the new system cannot be useful regardless of the amount of effort exhausted during system development. To mitigate the risk of data migration, Wipro proposes that RAIN form a dedicated data migration team at the early stage of the project and work under the guidance of Wipro consultants along with the core team members of RAIN to achieve the necessary activities of data preparation and upload in time. It will be the responsibility of Wipro to develop and modify necessary BDCs for upload of master and cut over data to SAP system. Data Extraction and Validation will be the prime responsibility of Core Team Data Migration requires the following steps (As illustrated in the diagram):






• Formation of team for data extraction covering all locations and geographies during mid of project preparation phase

• If required build programs for data extraction from all locations and legacy systems

• Consolidation of data from all location for cleansing • Cleansing of data by functional team • Validation of cleansed data by identified data migration team • Conversion of cleansed and validated data into required formats provided

by Wipro consultants • Testing of upload programs and incorporation of changes as required • Upload of actual data

Wipro consultants will make available the format in which the data will be uploaded in the SAP system to the RAIN core team. The core team in turn is responsible for data cleansing, validate the data and providing the validated data in the required format to Wipro consultants for uploading into the SAP System. The following are the broad division of responsibilities for the data conversion effort in the implementation:

ACTIVITY RESPONSIBILITY Data conversion strategy definition and approach WIPRO Identification of conversion objects and data formats for SAP

WIPRO

Legacy system Migration workbench programs WIPRO Data collection, formatting as per the SAP Format, entry of missing information and data validations

RAIN

Upload of data into SAP WIPRO Data Validations/ Sign Off RAIN

Legacy Data

Extract

Data Cleansing Data Transformation/

Validation

SAP Data

Load

Legacy

1

Legacy

2

Legacy

n

Data Cleansing Data Validation/

Transformation

Data Stage

SAP

Business Connectors






The data Conversion scope by WIPRO will not include the following:-

♦ Manual Data collection, Data validation and ownership of data ♦ Any development work for data conversion on SAP or legacy system ♦ Translation and Transformation of data into SAP format , however

templates for data conversion as required by SAP system will be provided by Wipro.

♦ Collection and extraction of data from source system. The scope of data migration will be limited to specifications, cleansing and conversion of master data, opening balances and open items. No historical transactional data will be transferred to the live system. The following data objects are currently expected to require conversions:-

♦ Material Master ♦ Vendor Master ♦ Customer Master ♦ Bill of Materials ♦ Routing ♦ Stocks ♦ Open Production Orders ♦ Open Sales Orders ♦ Open Stock Transfer / purchase Orders ♦ Open Account Balances (Vendor and Debtors account)

The detailed data conversion scope will be worked out during the Business blueprint phase. Dependent on the volume of data to be uploaded, a decision will be taken by the Data conversion manager as to the best upload method. In some cases it may mean that data will be manually entered into SAP By Rain Resources. Where the records are more than 25, WIPRO would develop a program to facilitate upload so as not to upset the day to day operations.






2.10. Reports and Forms Scope

The standard SAP solution provides a large number of useful reports. We strongly recommend that RAIN makes the fullest use of these standard reports. There are certain reporting outputs like the Purchase Order Format, Invoice formats and cheque formats, which are available in the standard solution, but may not address the specific needs of the organization. These outputs will be designed and developed after understanding the specific requirements of each unit / country. WIPRO has planned for 50 FRCE (Forms/Reports/ Conversion/Enhancements) objects. In case there is a requirement to make more FRCE Objects to meet the business critical requirements, the processes as outlined in Appendix B - Project Change Control Procedure will be used for approvals. Once the approvals are in place WIPRO will undertake the development work.






2.11. System Testing

2.11.1. Testing Objectives

The overall objective of formal testing is to confirm that the SAP ERP system meets the “To-Be” business requirements as documented during the Blueprint Phase and configured during the Realization Phase. Another key objective of the integration testing strategy is to validate the data conversion approach, catch issues around data cleansing, and validation procedures. Additionally, testing is to verify that the production environment and its technical components are stable and prepared for operational use and to ensure system security proper controls are given based on actual job roles.

♦ To achieve the overall objectives, testing will typically focus on the following major areas:

♦ SAP Core Functionality – Validate that the business process teams have configured SAP ERP according to client business requirements and that on-line transactions work correctly and provide desired results.

♦ Enhancements – Validate enhancements to the system to resolve the identified gaps between SAP and client business requirements.

♦ Workflows – Validate that all workflows operate as expected in sending the correct notification to the right person in a timely manner.

♦ Reporting – Confirm that reports satisfy users’ requirements for layout and contain accurate data. Reports identified as Non GO LIVE Critical will be tested in the Go Live Environment.

♦ Data Conversions – Validate that all one-time conversions load data accurately and timely.

♦ Security – Verify that SAP security has been built to provide end users the necessary access to perform their job functions, while providing adequate segregation of duties and controls.

♦ Systems – Validate that the system’s components and procedures have been constructed to provide a stable and highly available and performing production environment for operational use.






Testing Assumptions:

This section covers overall assumptions and dependencies as they relate to the test strategy.

� Resources – A sufficient number of dedicated, trained resources will be available from client to support all testing requirements.

� Access – All individuals involved with testing will have access to SAP, Solution Manager Toolset, Shared Drive and all other standard software necessary to complete the testing processes.

� Unit Testing Required - All new or changed functionality will be fully documented and unit tested before advancing to the scenario test phase.

� Templates - All Test Scripts, Scenarios and Test Problem Reporting templates are developed within the test standards outlined in this document. All test scripts and scenarios must be completed and approved by client prior to the test phase for which they are required.

� Exit Criteria/Gate Reviews - All exit criteria/Gate Reviews for each test phase must be signed off and approved by client before the next testing phase can begin.

� SAP System Environments - The appropriate system environments must be established by client before the testing process begins.

� Freezes - To conduct valid Integration testing, the scope and configuration must be frozen prior to entering Integration testing.

� Data: Proper amount of cleansed data available for required interface and functional testing.

Methods and tools for Testing

Testing Life Cycle

The Testing process model typically contains the following phases:

• Test Requirements

• Planning

• Test Design

• Test Execution

• Release/Acceptance/Test cycle closure






Test Requirements

This phase involves the study of the system to be Tested and preparation of a Test requirement document.

Test requirements document typically captures the following:

Responsibility Key Steps RAIN Wipro Test environment √ Test cycle specific risks √ Acceptance criteria √ √ Functionality (Regression, Feature conformance, Performance, reliability, interoperability of the product/ release/ system to be tested)

√

Compatibility (interoperability) requirements- Circumstance under which testing can be suspended and when will it be resumed

√ √

Test limitations and assumptions √ √ Test approach and test logging mechanism √






Test Planning

This phase involves activity related to preparation of a Project plan. Project plan typically captures the following:

� Resource requirement for the project � Project overview and Project environment (target and testing) � Training Plan � Testing and quality process plan � Effort and Schedule of activities � Milestone and Project Progress Review � Defect Prevention and Reuse Plan � Tools and techniques to be used in the project

Test Design

This phase involves designing and developing the test cases for testing the system. The Test design document typically captures the following:

Responsibility Key Steps RAIN Wipro Features and functionalities to be tested √ √ Test suspension, resumption and Test completion criteria

√

Test cases (wherever applicable) √ Test Exit Criteria √ Features and functionalities not to be tested

√

Test approach √ √ Traceability matrix of test cases to test requirements

√ √

Assumptions while carrying out the Test √ √

Test Execution

This phase involves activities related to execution of test cases as given below:

� Test Floor set up as applicable. � Test cases to be executed as per the plan. � Identified test cases to be executed multiple times as planned. � Defects found in the test cases during test execution to be logged and the

customer to be updated on this while sending the report. � Test report should be prepared based on the observations made during Test

Execution.






� On completion of the Test execution QC/TL will conduct the Test Audit. Test Audit findings to be captured in the Test Audit Report.

Release/Acceptance/Test Cycle Closure

This phase involves activities related to release and acceptance/ closure of the Test Cycle. The end of Testing is decided based on:

Responsibility Key Steps RAIN Wipro Test Requirement √ √ Test exit criteria √ Test Audit Results √ Execution of Test Cases √ Test Report √ √

Roles and Responsibilities of Testing Phase

Activity Responsibility System Test Approach , standards, scope, procedure WIPRO Entry and Exit Criteria of Testing Phase WIPRO/RAIN Identification of Testing scenario/Cycles RAIN (WIPRO will

facilitate) Creation of Test Scripts RAIN (WIPRO will

Facilitate) Recording of Test Problem Report RAIN Resolution of Test Problem Report WIPRO Completion of Test Scripts RAIN

Personnel Involved

The following personnel will be involved during integration testing:

WIPRO Functional Test Leads: They will be responsible for coordinating the development of detailed test plan and schedule, which includes scripts to be tested, their sequences, planned dates and times, planned resources, planned location and/or terminals, etc. The test leads would be primarily responsible for managing the day-to-day test activities, monitor progress, record and track problems and issues and reporting to the Project Management Office on progress on a regular basis.






RAIN Functional Consultants & Leads: They will be responsible for developing end-to-end business cases (called test cycles) and detailed test scripts with proper dependencies. The Work-stream leads will be responsible for conducting integration test and recording issues. Expected results will be documented against these test scripts. The developed test scripts would need to be reviewed by the WIPRO Functional Team, before testing can begin.

RAIN Functional Team Members (including Super users): They will be responsible for carrying out the testing and ensuring that the data as per the test scripts is entered. They should also ensure that the environment remains controlled during testing. They will provide sign offs on completed test scripts as well as ensure that all problems are reported in a timely manner.

Project Management Team: They will be responsible for securing a separate test area during integration testing. Also, they will make the final decision on the criticality of any test issue and provide direction and guidance during the testing effort and help with resource issues.

WIPRO and RAIN Technical Development Team: They will provide support to the Functional Team during testing. This would involve bug-fixing, retesting and communicating to the functional team when a particular piece of code is ready.

Technical Infrastructure Team: The Technical Infrastructure team will be responsible for maintaining the proper instance support and patch application support. They would also be responsible for ensuring that all printers, email capabilities etc. are set up and working prior to testing. They will provide assistance to the testing team, based on ad-hoc backup and recovery needs. They will also be responsible for setting up the users and responsibilities required for testing.

External Support Groups: These are the groups that support external systems interacting with the ERP solution and are not part of the project team. They will be responsible for executing test steps as per the test plan, and communicate the results to the functional team. For e.g. The group maintaining the energy management system etc.

ENTRY CRITERIA

The entry criteria for integration testing are:

� Design Validation/Unit Testing is completed and signed off � No Critical issues are open from Design Validation/Unit Testing � Outstanding non critical issues from Design Validation/Unit Testing, will be

evaluated on a case-by-case basis, and cumulatively (several open non critical issues) may merit delay in Integration Testing.

� All configurations for RAIN have been completed. � Data for integration has been prepared. � Detailed Integration Test Plan is completed






� Integration Test Scripts have been completed � All approved patches have been moved to the Integration Test instance � All Go live critical developments have been migrated to the Integration Test

instance � Kick-off meeting on integration testing is conducted for all concerned users by the

Test Leads.

Exit Criteria

Severity Level

Description Incident Characteristics

1 Urgent (Critical)

Shall mean that a critical in-scope SAP application is affected or severely degraded causing severe impact on GO LIVE as defined. No alternative or bypass is available.

2 High shall mean (a) an SAP application is affected or severely degraded which may have an impact on the GO LIVE as defined.

Based on the following definition the exit criteria for Integration Testing are:

� All critical issues as defined have been closed (retested and verified during the Integration Testing cycle 1 ).

� Non Critical issues have been identified, addressed and if necessary, workarounds provided, demonstrated and accepted. For open non critical issues, an action plan is in place for resolution within an “acceptable” timeframe.

� The Unit Testing/Integration Testing signoff has been completed.






3. Project Timelines

The Cement LOB (RCOL) shall Go Live by the end of Six months, post which One Month of Support is given.

1 2 3 4 5 6 7 8 9 10 11 12 13 14

Proj. Org Setup (Acco/Project Plan/Change Mang. Plan etc), System Set up

Sap Organisation Structure Design, Business Process Design, FRICE, SAP Org Structure

System Configuration, Unit Testing/ Integration Testing, UAT. Developmen of FRICE Objects

Final Cut Over Support

M7M1 M2 M3 M4 M5 M6






The Calcining LOB (CII) in U.S.A and RCIL India shall Go Live by the end of Eight months, post which One Month of Support is given.

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18

Support

Country India Localisations and Verification of the BPD's created for CII

Proj. Org Setup (Acco/Project

Plan/Change Mang. Plan etc), System Set up in INDIA

Support

System Configuration, Unit Testing / Integration Testing, UAT

M8 M9

Sap Organisation Structure Design, Business Process Design, FRICE, SAP Org Structure

M3 M5M1 M2 M6M4 M7

FINAL PREPARATION

FINAL PREPARATION

System Configuration, Unit Testing/ Integration Testing, UAT

The Implementation of BI will be completed by the End of 8th Month.

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18

Testing of BW Reports

Testing of GRC Access Controls

Support

Support

M7 M8 M9M1 M2 M3 M4 M5 M6






4. Project Organization & Team Structure

4.1. Wipro Project Team Composition

The project staffing plan has been prepared keeping in mind the specific requirements outlined by RAIN. WIPRO will endeavor to provide a skilled team to ensure that the implementation is a success. Following would be the team structure from Wipro for SAP Implementation at RAIN.

W IP R O P ro je c t M a n a g e r

IM P L E M E N T A T IO N

T E A M

F o r R C O L


T E A M

F o r R C IL


T E A M

F o r C I I

W IP R O

T E C H N IC A L T E A M

W IP R O

B A S IS

W IP R O

P ro g r am M a n a g e r

W IP R O

Q u a li ty M a n a g e r

M M T E A M L E A D

S D (2 )

C O N S U L T A N T

C O T E A M L E A D

P P /Q M T E A M

L E A D

P M T E A M L E A D

P P / Q M T E A M

L E A D

R C O L T E A M

F I T E A M L E A D

M M

C O N S U L T A N T

S D

C O N S U L T A N T

C O

C O N S U L T A N T

P P / Q M (2 )

C O N S U L T A N T

A B A P L E A D

P M

C O N S U L T A N T

R C IL T E A M

F I

C O N S U L T A N T

M M T E A M L E A D

S D T E A M L E A D

P P T E A M L E A D

P M Q M T E A M

L E A D

C II T E A M

F IC O

T E A M L E A D

W O R K F L O W

C O N S U L T A N T

B I T E C H N IC A L

& F U N C T IO N A L

(2 )

R C O L /R C IL T E A M

A B A P T E A M

(4 )

B I T E A M L E A D

M o d u le L e a d

w ith th e P ro je c t

M a n a g e r

R e s p o n s ib i l i t y

C O M M O N

O B JE C T IV E

** Indicative figure depicting the peak team size during the implementation






4.2. RAIN Project Team Composition

Wipro would need the following team members of RAIN to be a part of the SAP implementation.


Wipro Limited of 50 © Wipro Limited, 2008, All Rights Reserved. This document is proprietary to Wipro Infotech, a division of Wipro Limited. You may not modify, copy, reproduce, republish, upload, post, transmit or distribute any material from this document, in any form or by any means, nor may you modify or create derivative works based on the text of any file, or any part thereof for public, private or commercial use, without prior written permission from Wipro Limited.

4.3. Roles & Responsibilities

4.3.1. RAIN’s Roles and Responsibilities

This section details the Roles and Responsibilities, which Wipro has assumed, will be performed by RAIN. Any deviation, which has a potential impact on Wipro responsibilities, will be subject to Change Control Procedure. RAIN shall allocate/ assign the required resources with the necessary skills and authority to execute the responsibilities given below.

Executive Sponsor/ Steering Committee

This committee is made up of senior executives from RAIN and the SAP implementation Project Managers from RAIN and Wipro. Its purpose is to review the progress of the project and resolve any management issues that may hinder the accomplishment of the project objectives. The committee chaired by the executive sponsor from RAIN will sit monthly and the Project Managers will review the status of the project with the committee.

Project Manager

RAIN shall designate a person, called Project Manager to whom all Wipro communications may be addressed and who will have the authority to act for RAIN in all aspects of the project. The specific roles and responsibilities of this person are:

• Setting up and managing the project team members from RAIN

• Update RAIN's management on the project status.

• Accept the deliverables or obtain the necessary acceptance sign-off from RAIN management, wherever so required.

• Initiate and approve Change Requests or obtain necessary sign-off and approval for the Change Requests from RAIN Management.

• Track accomplishments during the course of the implementation.

• Ensure that the project complies with RAIN's external and internal audit requirements.

• Ensure the availability of RAIN management and users whom Wipro may need to discuss with for the purpose of the project.



• Furnish all the necessary information required by Wipro.

• Ensure that project issues designated to RAIN's responsibility are resolved on a timely manner.

• Integration management

Organization Change Management Manager

The Organizational Change Management (OCM) Manager from RAIN will be primarily for providing strategic advice and direction for managing change arising from the project in the organization, identifies potential risks, creates plans to mitigate the risk and executes the plan. The OCM Manager will identify whether new teams/structure need to be set up as a result of implementing the new process and as well as how to communicate these changes and what training measures are necessary for the success of the project and the organization. The OCM Manager must have a broad knowledge of the industry in order to be effective.

Core Team Members

RAIN shall designate sufficient Core Team Members whose responsibilities include the following:

• Represent the business areas, business units from RAIN

• Make decisions on design or procedural issues affecting their area of jurisdiction

• Provide information on business operations and final requirements of the division or business areas represented

• Participate in the discussions/ meetings and confirmation of requirements with the Wipro Consultants

• Participate in discussion and contribute ideas on the design of new system/processes and identify implications on RAIN’s policies, procedures and resources

• Participate in evolving report/interface specifications



• Review, confirm and accept the design of the SAP system and interfaces, if any

• Prepare test conditions and test data, participate in all testing, verify and endorse test results

• Conduct User Acceptance Testing

• Train subsequent end-users that are not initially involved in the implementation

• Conduct Data Conversion (clean-up old systems, prepare data for conversion to new system, and execute data conversion)

4.3.2. Wipro's Roles and Responsibilities

This section details responsibilities of various roles, which will be performed by Wipro personnel on the project. Any deviation, which has a potential impact on the project, will be subject to Change Control Procedure. Wipro shall allocate/assign the required resources with the necessary skills and authority to execute the responsibilities given below.

Project Managers

RAIN's SAP implementation project shall constitute of two Project Managers for each of the LOB.

• Project Manager from Wipro (One for Cement & One for Calcining).

• Project Manager from RAIN (One for Cement & One for Calcining).

• To Co-ordinate with the US team from India, The Senior FI Consultant in India will double up the responsibility.

The Project Managers are responsible for the day-to-day running of the SAP implementation project.



The key responsibilities of the project manager are

• Visualizing and conceptualizing the entire project at the company level

• Defining the entire IS organization structure for the SAP implementation project and post implementation phase from RAIN side as well as Wipro side.

• Assist in the first production period closure and reconciliation (Preferably year end closing, otherwise, quarter end closing, depending on implementation schedule)

• Ensuring and auditing the quality, clarity and comprehensiveness of documentation of all KPI’s, business processes, functional requirements, technical requirements, configuration setups, data migration scripts, roles and responsibilities, access rules etc.

• Participating in the following activities and ensuring the deliverables are met during the various phases of the project

� Project Initiation / Defining Project Charter

� Project management including resource allocation and schedule management

� Defining communication plan; and its implementation

� Project Status Reporting

� Ensuring Quality of Implementation and deliverables

� Risk Management

� Scope management / Delivery of project

� Problem / Issue analysis, classification, prioritization and resolution

• Develop and maintain the master implementation plan and set project standards

• Develop detailed plans to micro-manage major phases

• Manage and mitigate project risks

• Perform project management coaching to project team members

• Provide leadership and give guidance to the project team

• Report to the steering committee and program management

• Control project performance



• Manage Wipro resources allocation and utilization

• Conduct regular meetings and/or updates with other project members

• Escalate major project issues and problems to RAIN's Steering Committee

• Assist RAIN Project Manager and Change Manager to implement Organizational Change Management (OCM) plan.

• Review work products produced by project members

• Ensure system fully-tested prior to cut-over to production

• Ensure Wipro's obligations on the project are completed on time

Project Team Members The Project Team Members are allocated to the project according to the resource requirements. These participants should possess the necessary skills within their areas of competence, whether in terms of knowledge of the business processes and Organization, or of existing systems and information technology skills. It is very important that they are able to work as a team across the project. The team will comprise of participants who are experienced business users, data processing personnel, and Wipro SAP Application (module) consultants. To provide training and supervision of the development team at RAIN, ABAP programmers will aid and assist the functional module team members. A Basis Consultant from Wipro will also be part of the team to take care of training, application tuning, security management and other technical aspects. Quality Coordinator The Quality Coordinator would provide a ‘Customer Centric Quality Approach’ with responsibilities as follows: • Ensure that the team is trained on Quality processes and procedures • Ensure that all ‘Quality’ related forms are available to the project team • Ensure that all deliverables are subject to required reviews: • Attend all project related meetings with the customer



Functional Consultants The Functional Consultant's responsibilities are as follows: • Assist Wipro project manager in overall program management

• Provide expert advice on SAP functionality

• Suggest solutions to customer based on SAP best business practices

• Assist in Organization Change Management (OCM) in their individual functional areas

• Conduct implementation & training workshops for process owners

• Conduct unit tests based on customer defined scenarios

• Provide guidance on end user documentation

• Provide guidance on test plan

• Responsible for the smooth cut over of the system

• Provide expert advice on SAP functionality

• Collate customer requirements on the following subjects:

� Determine customization and interface requirements

� Business processes and parameters

� Assist in data transfer mapping

• Ensure continual transfer of SAP configuration and system design to the RAIN SAP team – basic knowledge transfer during the project duration and detailed transfer during the support phase in order to adhere to tight schedules

• Suggest solutions to RAIN based on SAP best business practices

• Configure the system based on RAIN’s requirements

• Conduct system and solution testing based on customer defined scenarios

• Conduct implementation & training workshops for business process owners and key users.

• Provide guidance on end user documentation

• Provide guidance on test plan



• Be responsible for the smooth cut over of the system

Basis Consultant

The Basis Consultant's responsibilities will include:

• Ownership of hardware and operating system configuration, system maintenance, installation of SAP system, guidance to RAIN team for installation of GUI, network, system administration and BASIS configuration

• Responsible for backups, data security and physical security of machines • Correction and transportation of SAP repository objects (transfer of

customization objects from the development to the production system) • Upload and download (manual or through programs) of data as per the

requirements • Creation of all user profiles, authorizations and menus • Handling all enhancements and interface issues as and when required

(ABAP programs for FRICE) • Involvement in testing the SAP solution • Assistance in preparation of documentation on systems and procedures

for RAIN IT team • Ensure knowledge transfer and training of RAIN IT Team on all Basis

activities

ABAP Consultant

Responsibilities of an ABAP consultant include:

• Development of data conversion and interface programs

• Development of printed forms using SAP script / Smart forms

• Development of ABAP reports

• Development of enhancements for workaround solutions



5. Project Management

The success of the project lies in not just a very qualified team but also backed by a strong program governance framework. Wipro has over the years evolved a strong program governance model that ensures transparency, flexibility, simplicity and clear communication while remaining focused on the overall objectives of the project.

In this section we shall talk about the program governance created for RAIN which will highlight the communication between the teams at various levels during the course of the project. This would bring about greater cohesiveness in the activities between Wipro and RAIN team members to achieve the overall objectives.

The governance communication and reporting structure will be as per the following diagram given below:



Steering Committee The steering committee functions as the highest decision-making authority for the project. As such, it represents business management ownership of the project, and is responsible for ensuring that the project delivers its goals and benefits. The steering committee should be constituted as follows: • Representatives from the top management of RAIN • Wipro Program Manager • RAIN Project Manager • Wipro Project Manager. The chairman of the steering committee will be a senior manager from RAIN, with overall responsibility for the project's success. Wipro Program Manager Wipro will also have a program manager who will work on the project with an overall view of the project. Apart from the SAP implementation project he will also have responsibility of the entire project from support, infrastructure perspective also. The Wipro Project managers will report onto the Program Manger. Project Managers RAIN's SAP implementation project shall constitute of two Project Managers. • Project Manager from Wipro • Project Manager from RAIN

The Project Managers are responsible for the day-to-day running of the SAP implementation Project.



Communication Plan

The following project meetings will be held for proper co-ordination in successful execution of the project.

• Steering Committee Meeting – The meeting with the Steering Committee (SC) will be held once a month or as decided in the Project Charter. The Project Manager will report the progress of the project to the Steering Committee.

• Project Team Meeting – The Project Team Meeting will be held every week. This meeting would include the Wipro Project Manager, Wipro Project Team, RAIN Project Manger and Core Team Members. In case of the Wipro Team is not site, this meeting will happen thru a Telephonic Con-Call.

• Extraordinary Steering Committee Meeting - Wipro Project Manager may convene such a meeting if some unresolved issues in the project need immediate escalation.

• During these team meetings the following will be tracked:

a. Action points of previous team meetings

b. Technical issues

c. Project schedule

d. Changes in project resource requirements

e. Changes in project commitments

f. Critical dependencies within the project and with the support groups

g. Progress of the project with respect to the effort, size, productivity and other commitments

h. Project risks

i. Any configuration management related issues like pending Change Requests, changes to baseline library, etc.

• The minutes of each meeting along with the action points, date and responsibility of closure will be recorded and circulated at the end of each meeting. The problems identified during these meetings will be escalated, if required.



Status Reporting

Weekly report will be sent on every week during the entire duration of the project. In addition to the weekly status reporting Wipro also, conduct Milestone reviews involving appropriate stake holder’s personnel. Some of the reporting activities are mentioned below:

Type of reporting

Schedule Details

Status Reporting (Weekly Status Report as explained in the Deliverables Matrix)

Weekly This will have a detailed Project report for the 15-day period (consisting of the Current Week and the next

Week). It will consist of the Project schedule, Milestones achieved, Activities performed for the

Week and planned for the next week, issues / concerns. The status report will be initiated by Wipro Project Manager by email and sent to Steering

Committee & Project Manager

Escalation reporting

Fortnightly This will be a report, which will highlight concern

areas with respect to technology, user, and project. It is expected that RAIN will act on this escalation

report with due diligence and address the issues within 5 days to avoid schedule overruns

Phase completion reporting

Phase wise This report will be made on completion of each phase of the development lifecycle. Overruns &

dependencies will also be listed in this report. The report will also address review issues with respect to various deliverables

Conference Calls

Fortnightly Fortnightly conference call will be initiated by Wipro from the station where the Project Manager is

situated. The conference call will be for 1 hour. All the team members from Wipro will be present in this

call & from RAIN the Project Sponsor is expected to participate.



Project Monitoring

This project would be tracked and monitored for the following:

• Schedule

• Effort

• Project activities

• Risks – Identification, prioritization and tracking through out the project lifecycle

• Critical path, identified in the schedule

• Identification of potential overruns and under runs and appropriate corrective action

6. Project Deliverables

6.1. Project Deliverables

The specific deliverables, the dependencies and the parties responsible for the same for the work tasks to be performed as per the project scope is detailed in the table below.

Primary responsibility indicates that the entity is responsible for successful conclusion of the overall activity. Secondary responsibilities indicate that there are dependent subtasks, which this entity is responsible.

1 Project Management

Weekly status reports as per agreed upon formats

None Baseline Project Schedule in place

Wipro RAIN None

Project Preparation Phase

2 Project kick off/ initialization

Minutes of Project kick off meeting

Concur with minutes

Attendance of top management of RAIN and key users

Wipro RAIN Sign off on Minutes within 2 days of submission

3 Developing Project Charter & Establishing Project Infrastructure

� Project Mission Statement

Agree with project charter

Team Mobilization/orientation

Wipro RAIN Sign off

� Project Team Structure

within 2 days

� Project Risk and Critical Success Factor

� Operating Procedures

� Specific strategies for data conversions, interfaces, reports and forms, SAP enhancements.

4 Current state process Modeling for the module in scope

Document of current state Business Process model

Document represents current process

Active participation of RAIN users.

RAIN Wipro To be submitted by RAIN within the time frame



accurately

set by Wipro

Business Blueprint Phase

5 Future state process model for all modules

Document of future state process model

Model should fulfill stated business needs

Active participation of RAIN users and acceptance of future Business model

Wipro RAIN Inspection and sign off by RAIN within 3 days of submission of document

6 Workshop on change management

Change management issues and change management plan

Agreement on issues and plan

RAIN Change Manager in place

RAIN Wipro Inspection and sign off by RAIN within 3 days of submission of document

7 Training of Core Team as per functional scope.

Core Team Training

Completion of training as per schedule

Availability of suitably skilled participants

Wipro for training

RAIN for training facilities and deputizing skilled participants

8 Establishing Test

Sandbox client (test client to enable testing of configuration)

Client configuration complete and ready for testing

IT infrastructure and SAP installation in functional condition.

RAIN for sand box client

RAIN for IT Infrastructure and SAP installation.

Inspection and sign off of documents by RAIN within the time frame set by Wipro

environment

9 Choice of Functionality – As per SAP standard business practices

Document on functions suitable to RAIN (Baseline Configuration)

Functionality should meet defined business needs

Acceptance of To-be business model

Wipro RAIN Inspection and sign off of documents by RAIN within 3 days of delivery



10

SAP Fit / Gap analysis

Document of SAP Fit / Gap

Accept fit with SAP

Acceptance of To-be business model

Wipro RAIN Inspection and sign off of documents by RAIN within 3 days of delivery

Realization Phase

11 Baseline configuration and identification of interfaces to SAP

1st cut configuration of the proposed SAP

Configuration to have top level reflection of desired functionality as per fit/gap analysis document

Acceptance of SAP fit/ gap analysis document

Wipro RAIN Inspection of configured system and sign off on completion report within 3 days by RAIN - DELIVERY BY WIPRO

12 Final configuration

� Basic SAP system with the recommended modules configured

Desired functionality as per fit/gap analysis document is reflected in each module

Acceptance of Prototype configuration document

Wipro RAIN Inspection of configured system and sign off on completion report as well as acceptance report of the configuration document within 3 days of submission

� IMG Notes on configuration on the system.

� Configuration document

13 Develop BDCs for Data migration, Interfaces and Enhancements as per functional scope.

� BDCs Test results as defined

Signed specifications

Wipro RAIN to provide signed specifications

Inspection; sign off on test result completion document within 3 days of delivery

� Test result completion document



14 Integration testing and User acceptance

Integration and User acceptance test plan, documentation of test results completion

Test results as defined

Acceptance of results

RAIN to prepare test cases with expected results, execute and document the results

Wipro Inspection; sign off on test result completion document within 3 days of delivery

Final Preparation Phase

15 Establish production environment

� A productive SAP system with modules configured and with user live data

Functional SAP System

User acceptance of integration test result document

Wipro RAIN to provide system management operations and Authorization concepts

Sign off on completion report within 3 days of delivery

� Completion report

Trained Basis resource from RAIN

16 Data Migration

Migrated data Valid Data in the SAP system

RAIN to provide accurate and validated data as per Wipro format.

RAIN Wipro for assistance

As per schedule given by Wipro

17 End User Training

Conducting training and 1 copy of End user Documentation

Conclusion of training, End user documentation to reflect navigation paths

Final Configuration accepted

RAIN Wipro to assist in End-User Documentation and Hands-on training of the RAIN Trainers.

Sign-off on the End user documentation within 3 days

Go-Live and Support

18 Going live � Check list for going live, and a productive SAP System ready for use.

Availability of productive system

Acceptance of production environment

RAIN / Wipro

Sign off on check list and acceptance report within 3



� Acceptance report

days

19 Post implementation support

Production support

Conclusion as per schedule

RAIN Helpdesk operational and End-users trained

Wipro RAIN to set up helpdesk.

20 Project review

Project review report indicating extent of fulfillment of project objectives

Agreement with contents

Wipro RAIN Sign off on review report within 3 days

The deliverables mentioned are generic. These are indicative and during the project preparation phase the exact deliverables in each phase of the methodology would be finalized jointly by Wipro and RAIN.

In addition to the above deliverables and dependencies, a detailed project plan containing implementation schedule, deliverables, dependencies and responsibilities shall be developed during the project planning stage of the Implementation project.



7. Training Plan

7.1. Training Objectives and Goals

The primary objective of the training strategy is to provide the overall focus and direction for the entire training design, development, and the delivery effort for SAP RAIN end-user training.

The basic objective is

1. Educate Key Users on the end-to-end business processes, which are applicable to their role

2. Ensure that employees display SAP competency in their areas of responsibility by meeting pre-defined performance & learning objectives

3. Educate employees on how to obtain additional process/procedure and system information, from an on-going role-based training support solution

7.2. Training Calendar

Wipro proposes to train the core team at RAIN as per the schedule below.

7.3. Training Scope

• Dedicated Configuration Training on following modules.

o Configuration of FI Module

o Configuration of CO Module

o Configuration of SD Module

o Configuration of MM Module



o Configuration of PP Module

o Configuration of QM Module

o Configuration of PM Module

o Configuration of Business Warehouse

• Training on ABAP Programming comprising

o Table Structures o Reports, Smart Forms, ALE.

o SAP Script, BDC's

o User Exists, BADI'S ( Business Add'in )

• Training on SAP Server Administration

o Client/Server Architecture in SAP R/3

o Managing SAP Server Instances / Database Server Instances

o Managing SAP Services including SAP Solution Manager

o Configuring SAP System Landscape

o Managing Transport Management System including Requests

o Managing Clients Administration including creating new Clients

o Managing R/3 Users and Authorizations

o Monitoring and Troubleshooting Updates

o Configuring Spool Work Processes, Output Devices Landscapes

o System Monitoring including managing and customizing Alert Monitors

• Orientation Training Program for Senior Management.

• Training to Process Owners and Key users across the project during implementation process.



• Assistance in Change Management strategies during implementation process.

• Assistance in Developing Training Plan as well Supervision for End Users

Adequate training materials will be provided by RAIN during the training sessions.

7.4. Training Approach

1. Wipro will follow Train the Trainer Approach for training.

2. Follow the standard ASAP Training Methodology

3. Conduct a detailed Training Needs Analysis (TNA)

4. Develop a process-based and competency based training curriculum specific to job roles taking into consideration of all business processes

5. Establish mandatory pre-requisite and SAP Basic Skills training

6. Deliver an on-line user documentation support system

7. Supplement training materials with e-learning

8. Combined team strength of estimated 30 + Resources

9. Training will be designed, developed and delivered to cater to users as per tender scope.

10.Estimated classroom size is approximately 15 per classroom for effective training

11.RAIN to take the ownership in hosting the website and for upload of training materials to website for future usage and references

Train the Trainer Approach

Wipro will deliver training through a Train the Trainer course. The training will be imparted to Group of RAIN members as per scope. This Group of Key Users will in turn train RAIN end user. Train the Trainer approach prepares the Key Users to train the end users.



Aims of the Train the Trainer course are for Trainers to:

• Understand in detail the role of the Trainer

• Be introduced to basic principles of presentation, training and learning

• Develop effective presentation skills

• Develop effective training skills

• Gain confidence in delivering courses • Confidently evaluate training material effectively • Assess the needs of participants in the class • Establish goals • Understand how to motivate and stimulate participants in the class • Enhance their communication skills

Trainers from RAIN, who have undergone the Train the Trainer course, will conduct the End User training courses. Trainers should be adequately supported during the training delivery, though access to Process Teams and IT / Basis personnel.

Training Material Design & Development: Training documentation focuses on the production of walkthrough training exercises and includes presentation material, course guide and assessment exercises. This range of material has been found to provide a sound foundation for providing real and effective learning for end-users of all abilities. Each training course will consist of:



• Course Guide • Course Exercises • Course Answers • Presentation Slides • Data Sheet

The following trainings will be conducted during the project.

Project Phase Training Duration Responsibility

Final Preparation Functional Training on configured system

3 Day Workshop per module (to be done in parallel)

RAIN

Post Go-Live Support

IT Team Workshop

3 Day IMG Workshop

Wipro

Key users would be trained as per the following schedule:

Level No. of Batches Duration (Hours) Responsibility

Level I 1 Batch per LOB 8 Wipro

Level II 1 Batch per Module per LOB

40 Wipro

Level III 1 Batch per Module per LOB

40 Wipro



• Level I - SAP Overview & SAP Navigation

• Level II - Function Training at Module level

• Level III - Business Transactions based on the relevant Business Process (based on day in the life app

Trainers, who have undergone the Train the Trainer course, will conduct the End User training courses. Trainers should be adequately supported during the training

delivery, though access to Process Teams and IT / Basis personnel.



8. Quality Strategy

Overall Quality Management Approach

Dedicated Wipro Quality team will carry out exclusive quality audit. This will make sure that the project team is adhering to the quality requirements mutually agreed by RAIN and Wipro. Wipro Quality Team will do the Quality Audit at the completion major milestone as depicted below:

• At the completion of Project Preparation phase • At the completion of Business Blueprint phase • At the completion of Realization Phase • At the completion of Final Preparation phase • AT the completion of support phase

A quality review by WIPRO will be carried out at the end of major milestone along with the representative of RAIN. This is essential to check the quality of project documentation, evaluate the real project status, evaluate the achievements of project objectives and benefits, and to provide advice on resolutions to major project issues and risks and facilitate to plan the mitigation strategy. At the completion of each phase, the project deliverables as detailed in Appendix A may be reviewed by the Wipro Quality Team. Also at the completion of each phase all the deliverables will be checked as per the project compliancy check list as per the Solution Manager and as mutually agreed upon with RAIN Project Manager and RAIN internal quality team. This will assure

• A comprehensive project health check at various milestones

• Greater awareness of potential implementation issues and risks

• Consistent reporting across all phases of the project

Increased confidence in project delivery by both the Wipro Project Team and RAIN Team.

1_RAIN_SOW_High Level Scope of Work_V1.0.pdf

Documents

Transcript of 1_RAIN_SOW_High Level Scope of Work_V1.0.pdf