BW Security Upgrade

Nov 28th, 2011

Gate 1 Presentation

Agenda
Executive Summary Project Timeline Project Organization Project Goals and Objectives Project Scope Management Project Risks Assumptions and Dependencies Work Breakdown Communication Plan Questions

Printed Date: 2/17/2012

1 Confidential Do Not Distribute

Executive Summary
Our current SAP BW system is in version BW 7.0 and the technical upgrade was done in 2010. Security project was not part of the SAP technical upgrade project, so currently all the SAP systems (BWD, BWQ and BWP) are using old security concepts. SAP has stopped supporting the old security model and requires a mandatory upgrade to BI 7.0 Analysis Authorizations. This is also a pre-requisite for future upgrade like SAP BW upgrade to 7.3 Upgrading to SAP BI 7.0 Analysis Authorizations will be a strong step forward toward building the technical framework for future capabilities. SAP has introduced new features with the BI 7.0 Analysis Authorizations including improvements to the previous issues and gaps. yThe new features contain major improvements for security analysts/administrators. This upgrade is a purely security technical upgrade. Nevertheless, current security is not structured and therefore the upgrade needs input from the business.

Printed Date: 2/17/2012

2 Confidential Do Not Distribute

BW Security Upgrade :- Proposed Implementation Timeline

FY2012 Jan
Prep & Planning Blueprint

Feb

Mar

Apr

May

Jun

Jul

Aug

Realization
Go Live 10th June 2012

Testing Final Prep Go-Live / Support

Phase Preparation & Planning Business Blueprint Realization Testing Implementation/Go-Live

Duration 6 Weeks 5 Weeks 3 Weeks 8 Weeks 1 Week

Start Date 4th Jan 2012 16th Feb 2012 22nd March 2012 11th April 2012 5th June 2012

Completion Date 15th Feb 2012 21st March 2012 10th April 2012 4th June 2012 10th June 2012

Printed Date: 2/17/2012

3 Confidential Do Not Distribute

BW Security Upgrade Organization Chart

Project Steering Committee Program Support
OCM Lead Srini Muddala Finance Lead Amy Dammann Project Sponsor's)/Chairman: Mark Sims Members: Tom Czajkowski, Dave Judson, Tom Van Atta, John Rockwood

Project Advisory Team

Mark Sims, Dave Judson, Mark Adams, John Rockwood

Project Change Control Team Project Management

Project Managers Business Project Manager: Mark Adams GBIS Project Manager: Venu Mareddy Consulting Project Manager: Jeevan Pulapa Dave Judson Mark Sims Srini Muddala Mark Adams

Architecture Review Board

Tom Van Atta, Preston Marshall, John Rockwood, , Dave Judson, Tariq Mahmood, Satish Jain, Alan Darcy, Mark Sims, Tom Czajkowski

Organizational Change Management

Mark Adams Christine Ellenberger Brian Hughes Ryan Moore Melinda Rogers

Business / Functional
Mark Adams POS/Shipments Christine Ellenberger - WCO Brian Hughes Supply Chain Ryan Moore Finance Melinda Rogers HR / TPS

Technical
Technical Manager Srini Muddala Technical Lead Venu Mareddy Security Consultant Jeevan Pulapa BW Consultant - TBD Sr Analyst, Security Jim Warrington ACS Project Manager Russ Leadbetter ACS Security Consultant Wally Bettes

Printed Date: 2/17/2012

4 Confidential Do Not Distribute

Project Goals and Objectives

    Upgrade the current SAP Business Warehouse security from BW 3.5 to BI 7.0. Achieve compliance for SAP BW security solution with SAP support levels. Simplify the current security model and remove/delete the obsolete roles, users and authorization objects. Upgrade to a release of BW that will be supported well into the future. It will provide the BW System with a foundation to continue Business Development without the obstacle of an obsolete system. Position the BW solution at Scotts to be upgraded from the current 7.0.1 to 7.3. Redefine approval process which mandates business ownership

 

Manager Approval

Role Owner Approval

Security Approval

Access Granted

Printed Date: 2/17/2012

5 Confidential Do Not Distribute

Project Scope Management

Functional & Business Scope Scope Inclusions

The scope of this project will be to upgrade the current security from BW 3.5 to BI 7.0  BW Security Upgrade: Security upgrade from BW 3.5 to BI 7.0 Analysis Authorizations  Analysis of current security model Review current security model. Delete obsolete/unused users, roles and authorizations.  Access points: Portal, Business Objects (BOE) and any other BW access points are taken into account.

Scope Exclusions

SAP BW Front End tool upgrade and BW 7.3 upgrade

Project Success Criteria

 Since this is a technical upgrade, it will be critical that the business retains uninterrupted access of regular and ongoing business functions outside of BW, during and after the upgrade  Grant appropriate access to all the users and ensure system and data security  New Process which involves approvals from business process owners  Fewer number of authorization profiles for easy ongoing maintenance
6 Confidential Do Not Distribute

Printed Date: 2/17/2012

Project Scope Management

Facilities in Scope
Applications in Scope

All Scotts locations using SAP BW (onsite and remote)

SAP BW 3.5, 7.0 and the Testing of systems like BOE and Garden.  Migrating the existing roles, users and authorization objects will be in scope for the Upgrade. The Base Upgrade is Strictly Technical.  All the custom authorization objects will be replaced by the analysis authorizations  All the roles will adhere to current naming standards at Scotts  Usage of SPM on BWP will be taken into account; the security model will comply with SPM needs

Migration Activities in Scope

Printed Date: 2/17/2012

7 Confidential Do Not Distribute

Project Risk
Resources:  As in any project, resource availability can have negative impact on the progress of the project. Therefore, it is critical that we have business and GBIS commitment.  User acceptance testing will require business representatives to dedicate time to testing scenarios in the upgraded environment. Hardware Availability:  ACS in the Relationship with The Scott s Company will be able to provide the hardware in a timely manner to meet the schedules. Execution: Business Expectations must be managed to minimize changes to the current BW security during the Upgrade project.

Printed Date: 2/17/2012

8 Confidential Do Not Distribute

Assumptions and Dependencies

Assumptions
No new functionality will be introduced; therefore, user processes and transactions should not be impacted. This is purely a security upgrade from 3.5 to 7.0. No BW upgrade will take place. Business Users will be available to thoroughly test the applications after the BWQ and BWP conversions. Business Objects testing will be performed by the current Scotts staff that supports the tool today. GUI upgrade is not part of the project scope and not a requirement identified at this time.

Dependencies
All SAP interfaces must be successfully tested (where applicable) prior to going live.

Printed Date: 2/17/2012

9 Confidential Do Not Distribute

Work Breakdown
What goes into upgrading BW 3.5 to BW 7.01 SP6
 A BW Sandbox is created. Each SAP BW Environment (Sandbox, BWD, BWQ, BWP) will be upgraded. Testing will take place in each environment to confirm a successful upgrade. Unit Testing Integration Testing User Acceptance Testing

Printed Date: 2/17/2012

10 Confidential Do Not Distribute

Communication Plan
Project Management: Project Team Daily status meetings for planning, progress, and issue resolution Weekly status reports posted Weekly meetings with GBIS & ACS Security teams Additional meetings as required Testing: Project Team and Business Representatives Daily status meetings for progress and issue resolution User Community: Daily communication beginning one week prior to cutover through the first week of transition. All the users in the BWQ system will be notified about the freeze during the simultaneous unit testing by BI Team and UAT by Super Users. All users will be asked to test their access in BWQ after the freeze is lifted. This will be the access they would get in production after going live. All the users will be notified about the go-live date. Contact information will also be provided in case the user should run into any issue. Help desk will be notified about the go-live date as well.

Printed Date: 2/17/2012

11 Confidential Do Not Distribute

Milestones
Phase Preparation & Planning Business Blueprint Realization Testing Implementation/Go-Live Duration 6 Weeks 5 Weeks 3 Weeks 8 Weeks 1 Week Start Date 4th Jan 2012 16th Feb 2012 22nd March 2012 11th April 2012 5th June 2012 Completion Date 15th Feb 2012 21st March 2012 10th April 2012 4th June 2012 10th June 2012

Upgrade of Sandbox, BWD, BWQ, and BWP Unit Testing Integration Testing User Acceptance Testing Go-Live within 96 hours

Printed Date: 2/17/2012

12 Confidential Do Not Distribute