Upgrade strategy - Lenoir

Download Report

Transcript Upgrade strategy - Lenoir

Critical considerations for timing,
sizing and scoping your SAP BW
upgrade
Dr. Bjarne Berg
Lenoir-Rhyne
College
Philippe Tanguy
IBM Global Services
© 2004 Wellesley Information Services. All rights reserved.
What We’ll Cover …
•Why upgrade?
What is new?
Why should I care?
In te g ra te d A n a ly tic s
•Planning the upgrade
The business case
Staffing, duration and scope
•Creating an upgrade strategy for the future
Content upgrades
Technical upgrades
B
s
u
i
n
e
s
s
T e c h n o lo g y
In te g ra tio n
Leveraging new features
The bigger picture –NetWeaver
and Portals
M
a
r
k
e
t
p
l
a
c
e
S ys te m s
•Questions and Answers
2
What is New?
One of the major reasons for upgrading your BW environment
is the availability of new content and features in the next
release.
Let us take a look at what is new in version 3.5:






Business Planning and Simulation
Information Broadcaster
Data warehousing and Business Intelligence
Universal Data Integration
Unicode Support
BeX Portfolio in Enterprise Portals
We will now take a
quick look at these
features
3
What is New - Business Planning and Simulation
You need no installation of SEM add-ons to use the planning
functionality with BW 3.5, and you only one software installation.
You can also plan towards totals (i.e. total costs, total revenue)
through pre-defined totals in rows or columns.
You can now remove outliers from the plan (unusual data points).
We can handle incomplete time-series with improved BPS
functionality
BPS increases the functionality and
statistical features
4
What is New - Information Broadcaster
In version 3.5 you can schedule delivery of reports
through a variety of methods.
a) Users can schedule reports to be delivered to them through email, portal
roles, web based reports (browser & handhelds), and zip files.
b) Reports can be mailed as pre-run or to allow people to execute ondemand.
c) We can trigger the reports to run at:
Certain times
When data is loaded to the system
Or we can mail it to the users ad-hoc
when we want to do it…
BW 3.5 can “push” data to the users, instead
of forcing them to “pull” the data
5
What is New - Information Broadcaster
What to you need?

SAP NetWeaver Knowledge Manager to do content ratings,
searches, feedback, subscriptions and discussions.

Java Repository Manger for pre-calculated KM services,
templates and queries, as well as metadata.

Enterprise Portal 6.0
Broadcaster with NetWeaver can create a truly collaborative
work environment with more data transparently
6
What is New - DW & Business Intelligence
The Web Application Designer has more features:
 The navigational state can be stored in XML format
 JavaScript can be used to customize web navigation
 Corporate web templates can be reused
N o te
New truly advanced chart designer with cool charts and a
development wizard (and you can actually read these cool
charts!!)
7
What is New - DW & Business Intelligence
New BeX features
 Better search features in hierarchies
 Improved masterdata display (long text and keys)
 Better Analysis Process Designer for classifications,
stratification and pre-processing for data mining
 Multiple currency types support (i.e. bids middle-rate)
Process chains can call 3rd party load tools and vendors
may be certified for open-hub compliance
8
What is New - Universal Data Integration
BW becomes truly an open solution..
Custom
Applications
BW
3. Java
1. Universal
Data Connect
2. Java
connecttors
BI Java SDK
Universal Data Connect
SAP Query
SAP
JDBC
ODBO
XML-A
Non-SAP
9
Universal Data Connect
UD Connect is based on BI Java connectors
OLAP
1. BI OLE connector a
Microsoft standard
RELATIONAL DATABASES
1. Over 190 JDBC drivers
for database connectivity
2. BI SAP Query connector
for R/3, SAP CRM ad-hoc
connectivity
BW 3.5
WAS 6.4
2. BI XMLA connector
for web based OLAP
sources
Java 2 Enterprise Edition 6.4
Universal Data Connect
SAP Query
JDBC
RFC, BAPI, API
JDBC Driver
R/3
RDBMS
ODBO
ODBO provider
BW
XML-A
URL/HTTP
3rd Party
10
What is New - Unicode Support
Unicode support for SAP DB, Oracle 9.2, IBM DB2 AS400
UDB, and SQL Server:
BW
3.5 Supports multiple languages through a unicode enabled
server (back-end) and a unicode enabled web front-end
For Microsoft
based components the “log-on language” is
supported
‫ﻲﻶﻺﻕﻒﻏﻎ‬
‫תשרחפא‬
11
What is New – BeX Portfolio in Enterprise Portal
Business Explorer (BeX) can be used to publish queries to the
Portal Content Catalog.
The BeX Portfolio consists of applications that include
collaborative information such as:
Technical
metadata (run times, descriptions, priority etc)
Subscriptions of a report
Feedback of a report (i.e. comments)
Rating of report (by users)
Report details such as descriptions and use information
Mailing of a report to others
The Portfolio is the entry point for BW reports
BeX Portfolio on Enterprise Portal (v.6.0) creates a
collaborate way to distribute and work with information
12
What is New – BW content in Enterprise Portal
We can publish a BW application in
to the SAP Enterprise Portal as:

A Knowledge management
object to a collaboration room

A Knowledge management (KM)
object to a KM folder

An iView to the Portal Role

An iView to the Portal Content
Directory
Source: SAP AG
You don’t have to upload iView files anymore!!!
13
End of support dates and upgrade paths
SAP BW
End of standard
maintenance
Can be upgraded to
2.0B
Feb. 2004
2.1C, 3.0B, 3.1C, 3.50/3.51
2.1C
Feb. 2004
3.0B, 3.1C, 3.50/3.51
3.0A
Sep. 2002
3.0B, 3.1C, 3.50/3.51
3.0B
May 2005
3.1C, 3.50/3.51
3.1C
May 2005
3.2 and 3.3 must be applied before 3.5
3.2
?
3.3 and 3.5
3.3
?
3.5
3.5
?
4.0
A direct release upgrade from 2.0B, 2.1C and 3.0B
to 3.5 is possible. However an upgrade from 3.1C
needs to apply 3.2 and 3.3 content add-ons before
upgrading to 3.5
Source: SAP & intelligence
14
What We’ll Cover …
• Why upgrade?


what is new?
why should I care?
• Planning the upgrade


The business case
Staffing, duration and scope
In te g ra te d A n a ly tic s
B
s
u
i
n
e
s
s
T e c h n o lo g y
In te g ra tio n
M
a
r
k
e
t
p
l
a
c
e
S ys te m s
• Creating an upgrade strategy for the future



Content upgrades
Technical upgrades
The bigger picture –NetWeaver and Portals
• Questions and Answers
15
Planning Your Upgrade
• Determine the business case
Understand the content/features provided in the BI
Pack or Technical Release
Cross reference content/features with your
organization’s “pain points” or needs
&*#@!
Not again!
Month Close
16
Planning Your Upgrade
• Determine the business case
Examples:
o Performance issues?
o System Admin/Support issues?
o End of standard support?
o
o
T ip
Planning new content roll outs?
Planning new MySAP product roll outs?
Conduct user surveys or focus groups as needed
17
Planning Your Upgrade
• Determine the business case
“Quantify” and Qualify the benefits of upgrading –
what’s the value (productivity/satisfaction/key
measures/etc.)?
Example:
D e ve lo p m e n t tim e O D S
D e ve lo p m e n t tim e in fo c u b e s
D e ve lo p m e n t tim e w e b re p o rts
M a in te n a n c e tim e (yr)
R e tire m e n t o f o ld a rc h ite c tu re
C o s t o f n e w a rc h ite c tu re
Show me the money!
Now
N ew
N um ber of
C ost per
N et C hange
(h rs )
re le a s e
o b je c ts
hour
($ )
35
55
120
1
1
1
105
105
105
55
230
270
40
3200
160
190
15
1800
$
$
$
$
$
$
2 5 7 ,2 5 0
4 6 2 ,0 0 0
3 1 5 ,0 0 0
7 7 ,0 0 0
1 9 0 ,0 0 0
(1 5 0 ,0 0 0 )
…
$
-
…
$
-
…
$
-
$
-
…
N e t b e n e fits o f u p g ra d e
$ 1 ,1 5 1 ,2 5 0
18
Planning Your Upgrade
Examples:
o
o
o
o
o
o
T ip
Reduced support – IT Labor cost $avings?
Eliminate redundant work (Cost avoidance)?
Data availability – Time saved closing books/responding to
information requests?
Information “on demand” – Only spend time looking
at/analyzing problem areas (Reporting Agent/Alerts)?
New BI content – Legacy reporting systems consolidations
opportunity/transition expensive R/3 ABAP reports to
BW/Implementation time to value?
Operational necessity?
Quantify any improvements in business
metrics that are important in your company/industry
19
Planning Your Upgrade
• Determine the business case
Balance the technical requirement and associated
implementation cost with the derived business benefit
Upgrade
$$
Can you do more with a new
release? (I.e. mobile)
Is the upgrade justified?
20
Planning Your Upgrade
• Scope the project
Based on Business Case, determine and prioritize the
content of your upgrade project(s)
o BI Pack
o Technical Release
o Leveraging new features
21
Planning Your Upgrade
• Scope the project
Determine your upgrade “readiness” & path
o Conduct a technical review of your existing
landscape - Factors to consider…



Number of R/3 & BW Systems – Check Plug in and Support
Pack Level requirements for your release of R/3 – multiple
R/3s on different releases will drive pre-upgrade effort
MySAP apps – Compatibility/Content – Does an upgrade in
one force an upgrade in the other? (e.g. BW 3.1C -> SEM
3.2, BW 3.0B -> CRM 3.0/3.1)
Non SAP Apps – Will custom interfaces/extracts need to be
updated? (Benefits of moving to DB Connect?)
22
Planning Your Upgrade
• Scope the project
Determine your upgrade “readiness” & path
o Conduct a technical review of your existing
landscape - Factors to consider…




SAP GUI – New GUI roll out, Patches? (e.g. BW 3.0B/3.1C > 6.20 BUT… BW 3.5 -> 6.20/6.40 – unless Unicode
required)
PC Requirements – Need upgrade to take advantage of
new features? BW 2.0/2.1/3.0 - Same PC requirements – but
the devil is in the details (see OSS 161993, 66971)
DB/OS – Are they supported on the new release? Take the
opportunity to apply patches as needed.
IGS – If need rendering of charts and graphs in BW 3.x
Web Applications you need IGS…BUT only runs under NT
and W2K. (BW 3.5 will support UNIX until IGS 6.40)
23
Planning your upgrade
•Scope the project
Determining the requirements for resizing your
Hardware/Infrastructure:
o ODS -> Parallel Load = more memory, ODS Layer =
more space
o Crystal Reports -> new hardware
o IGS -> may require new hardware
o Archiving -> may reduce need for space
o New content -> more users -> more app servers?
Rerun the SAP Quicksizer – work with HW provider
T ip
24
Planning Your Upgrade
Example
Production
12 CPU
96GB RAM
AppServer
4 CPUs
32GB RAM
Development
Test
4 CPUs
32GB RAM
4 CPUs
32GB RAM
This company reallocated their
Sun-6800 box and planned for
gigabit connectivity to the
AppServer….
More memory allowed them to
take better advantage of the
parallel load feature of 3.x
25
Planning Your Upgrade
• Scope the project
Estimate your upgrade effort
o
Determine your testing strategy
o
Don’t forget about end-user training requirements!
o
Review level of effort with Basis, Security,
Infrastructure, Functional teams, etc.

Example: Basis tasks: allocation of memory, back ups,
application of kernal patches, etc.
New licensing requirements/costs? (e.g. Open Hub, Crystal)
26
Planning Your Upgrade
•Scope the project
 Sample Timeline for a complete landscape with a large BW implementation
W1
W2
W3
W4
W5
W6
W7
W8
W9
W 10 W 11 W 12
P ro je c t s ta rtu p a n d T e a m tra in in g
P re p a ra tio n fo r u p g ra d e o f S a n d b o x s ys te m
a n d ro ll o u t o f S A P G u i
U p g ra d e S a n d b o x s ys te m
Note: The duration is
driven also by:
T e s t fu n c tio n a lity a n d d e c id e w h a t to
im p le m e n t in u p g ra d e (W h a t h a s th e b e s t R O I)
P la n u p g ra d e o f p ro d u c tio n la n d s c a p e
1. the number of BW systems
in your landscape.
A n d ro ll o u t o f n e w fu n c tio n a lity to u s e rs
U p g ra d e d e ve lo p m e n t s ys te m
2. The new functionality your
are rolling out
T e s t a n d va lid a te u p g ra d e
3. The support technology
needed (I.e. app servers, GUI
etc).
U p g ra d e T e s t s ys te m
Im p le m e n t n e w fu n c tio n a lity
(C o p y o f p ro d u c tio n if p o s s ib le )
T e s t a n d va lid a te T e s t s ys te m a n d u s e r tra in in g
& ro ll o u t o f S A P G u i
U p g ra d e P ro d u c tio n s ys te m
T e s t a n d va lid a te P ro d u c tio n s ys te m
The more content you have the longer the upgrade
(the more you have to test)
27
Planning Your Upgrade
• Staff the project
Resource requirements vary based on scope & approach
Typical upgrade roles & responsibilities includes:
o 1 Project Sponsor (10%)
o 1 Project Manager (50-100%)
 Budgets/resources/timelines
o 1 BW Architect (50-100%)
 Determining strategies/impact analysis/features
to be leveraged
o 1-2 BW Analysts (100%)
 Implementing new features
 Regression testing
One person may perform more than one role
28
Planning Your Upgrade
•Staff the project
Typical upgrade roles & responsibilities includes:
o 1 Training/Change Management Resource (50%)
 Updating/Creating Training Material
 Communications
o 1 SAP Basis (75%)
 Basis/DBA/OS/Security
o Other R/3 or MySAP Functional (25%)
 Regression testing
o 1+ Business Analysts (50-100%)
 Implementing new features
Ensure assigned resources are trained on new release
N o te
29
Planning Your Upgrade
• Sell the Upgrade Project Internally!
Compile detailed business case, work plans, budgets
Drum up interest in your business case with the
business/end users
Leverage SAP Service Marketplace for canned demos
of new features/”point of view” on benefits
W h e re
to
www001.sap-ag.de/
F IN D it
30
Planning Your Upgrade
• Sell the Upgrade Project Internally!
“Use and abuse” SAP BW consultants to support your
internal sale (demos, prototypes, expert sessions etc).
T ip
31
What We’ll Cover …
• Why upgrade?


what is new?
why should I care?
• Planning the upgrade


The business case
Staffing, duration and scope
In te g ra te d A n a ly tic s
B
s
u
i
n
e
s
s
T e c h n o lo g y
In te g ra tio n
M
a
r
k
e
t
p
l
a
c
e
S ys te m s
• Creating an upgrade strategy for the future



Content upgrades
Technical upgrades
The bigger picture –NetWeaver and Portals
• Questions and Answers
32
Types of Upgrades – BW add-ons
The new upgrade strategy from SAP is to provide BW releases and
BI content add-ons,
Content releases such as 3.2, 3.3 and 3.51 contains more business
content and can be applied via delta upgrade.
The content upgrade can occur in as little as 1-2 hours (per
system) and are shipped on supplement CDs.
You do not need to perform a technical upgrade to update the
business content
Apply content when you need it to the release you are running!!
Source: SAP & intelligence
33
Types of Upgrades – BW add-ons
The content delivered in add-on 3.5.1 is the same as the content in
Release 3.1 with version 3.3. content.
D o n 't
F o rg e t
Source: SAP & intelligence
Future upgrade strategies needs to include both content
as well as release upgrade plans for BW
34
Types of Upgrades – BW Releases
The Technical upgrades are called BW releases.
This include changes and/or additions to technical capabilities
such as improved ODSs (ver 2.x) and Process Chains (ver 3.x).
The release 3.5 is a technical release with initial 3.5.1 add-on
(business content).
3 .5 .1
Additional add-ons include:
W a rn in g
Source: SAP & intelligence
Plan a periodic review
of new content before
you build custom
solutions
3 .5 .3
R a m p up
3.5.2
2 nd w e ek
TBD
of Jun e
35
An Upgrade Strategy - Example
2004
Sept Oct Nov Dec
BW
Au g
3 .5
C on ten t
P ortal
E xch an g e
3 .5 .1 3 .5 .2
6 .0
3 .0
W AS
Ja n
Feb M ar
Ap r
2005
M a y Ju n Ju l Au g S e p O c t N o v D e c
4 .0
3 .5 .3
S e rvic e P a c k s a s a va ila b le
6 .4
4 .0 .1
xxx
xxx
Think bigger than BW..
T ip
Apply content as soon as feasible. Especially if you have
on-going development work. This way you can avoid
many “work-arounds”.
You should also coordinate the patches in the interim
periods (i.e. every 3 months or when needed for
integration purposes).
36
The Bigger Picture
Stop looking at infrastructure
and technology…
Start looking at the big
picture…
How are you going to make it
all work together?
And,.. how will you plan your
upgrades to make sure it
does so in the future?
Source: SAP, Léo Apotheker
37
The Bigger Picture – Why NetWeaver
Role-based
User Interfaces
Composite
Business
Scenarios
Service request
Price
ATP
Delivery delay
Focused
Operational
"Nodes"
Source: SAP AG
Enterprises has realized that they cannot create the same “stove-pipe”
solutions for their decision support systems as existed for transactions
systems prior to the ERP revolution.
They have also realized that business is not data driven, but event driven
The question has been… “How do I integrate it all to my job role?”
38
The Bigger Picture – NetWeaver ??
NetWeaver consolidates
the integration of
processes, information
and people.
NetWeaver is a set of
solution components
that provides a
comprehensive
architecture that actually
works together!!!
Source: SAP AG
39
The Bigger Picture – How Do you get Access?
• Ramp-up is SAP’s way to bring new products to
market (all SAP products).
• Ramp-up is really a “controlled release” of a new
product. Once no longer restricted, a product can be
acquired by anyone.
• You can apply to the ramp-up program through:
W h e re
 SAP Service Marketplace alias /nw04
 SAPnet alias /nw-ramp-up
to
F IN D it
40
The Bigger Picture – Ramp-up
• BW 3.5 is part of the NetWeaver 04 Ramp-up
• 3.5 unrestricted access is scheduled for 3rd quarter04.
What is included in NetWeaver-04 ramp-up?





BW 3.5
Portal 6.0 Service Pack 3
Exchange Infrastructure 3.0
MI 2.5
Web Application Server 6.4
Companies in Ramp-up can go-live with the product!!
41
Resources
Getting access:
SAP Service Marketplace alias /nw04
SAPnet alias /nw-ramp-up
G
o
o
d
T
h
i
n
g
Demos of new content
www001.sap-ag.de/
Collaboration room
http://sap.ittoolbox.com
42
7 Key Points to Take Home
• Look at new features and functionality. Is it cheaper to upgrade
to new content or risk reinventing the wheel?
• A BW architecture is part of a larger decision support
landscape
• An upgrade strategy must contain more then single NetWeaver
components
• You upgrade strategy should include both release upgrades as
well as content upgrades
• Cross reference new features & functionality with your
organization’s pain points…and ensure the implementation
costs do not exceed the business benefits
•
Include any needed hardware/infrastructure upgrade costs in
your estimates
• Your upgrade time is largely a function of scope, your
regression test strategy and the amount of content in your BW
43
Your Turn!
How to Contact Us:
Dr. Bjarne Berg
Philippe Tanguy
[email protected]
[email protected]
44