Contents
www.sap-press.com 1
Contents
Sizing projects are carried out at very different stages of sizing). Moreover, we are using several custom develop-
an SAP project. They represent an iterative process that ments. How should we carry out a sizing project?”
depends closely on the amount of information that is This question refers to a specific component in
available to you at a certain point in time to make reliable accounting and is therefore more detailed. Perhaps
statements on the actual hardware requirements. this customer has already carried out sizing projects
Accordingly, in each sizing project, you will often face for other SAP applications and wants to perform
new situations that you must react to with different meth- another one for this particular application. In addi-
ods and, consequently, using different tools. This chapter tion, the customer wants to know how sizing can be
focuses on these different methods. done for proprietary developments.
왘 “We are planning to consolidate our seven data centers
into one. Can we simply add up existing sizings?”
2.1 Phases of Sizing Projects
This question (which comes from an existing SAP
SAP regularly receives information requests like the fol- customer) refers to a system consolidation process
lowing: in which additional hardware requirements must be
왘 “We are a large customer in the consumer goods indus- taken into account if the different existing systems
try with 30,000 business partners and 60,000 sales are combined. System consolidation and single-
orders containing 50 line items per month. How much instance concepts, which are used to check whether
hardware do we need for our SAP application?” all systems can be globally integrated with one data-
This is a rather general question. The customer needs base, are currently red-hot issues with our customers.
information about hardware for a first estimate. The 왘 “We are currently running Release SAP R/3 4.6C and
question itself does not indicate why this is a large want to upgrade to SAP ERP 6.0. What are the upgrade
customer. Perhaps the customer is only looking for a factors?”
partial solution since the volumes mentioned indicate This customer uses a specific release that he wants
that this customer is a large medium-sized company. to upgrade across multiple releases in one step and
The business partners represent master data and are therefore wants to know if new hardware needs to be
not yet relevant to sizing because they do not gener- purchased for that.
ate any load during live operation. In contrast, the
sales orders and sales order items are much more By further analyzing these kinds of requests, we ulti-
critical to CPU sizing since they represent transac- mately get to the different phases in which you can per-
tion data. In terms of revenue, an average of 2,000 form sizing projects (see Table 2.1). The informational
sales orders per day is quite considerable; however, value of the sizing project can vary, depending on the
from the point of view of software, this is not a high different phases. In addition, you should note that not
throughput volume. SAP has several customers who all the phases described in Table 2.1 have to occur in an
process more than a million sales order items per day. SAP project.
왘 “We can’t find any guidelines for the FIN-FSCM-TRN Thus, if the system GoLive is still way down the road
component in your sizing area (http://service.sap.com/ and you — as a customer — are not yet very familiar with
www.sap-press.com 7
2 Sizing Methods
Orientation phase 18 to 12 months You familiarize yourself with the software functionality and want to know what the range
(Phase A) prior to GoLive of expenses is for the new hardware. Accordingly, you will certainly know which processes
you want to map using the software, and you also know the approximate amount of data
that is supposed to be processed. However, you are not familiar with the SAP jargon, nor
are you interested in specific releases.
Blueprint phase (Phase B) 12 to 6 months The first business blueprints have been created, and now you need reliable information on
prior to GoLive the scope of hardware you have to order because you must make sure you meet all your
deadlines. You know how to implement the relevant processes, have become more familiar
with SAP products and SAP terminology, and know which release you want to use.
Implementation phase 6 to 0 months You have ordered the hardware or are just about to do so, and you want to be absolutely
(Phase C) prior to GoLive sure that sizing is correct. For example, you are able to measure core processes using the
performance monitors.
Consolidation phase System is The system is operational and is supposed to be consolidated. Region 1, for instance, has
(Phase D) operational gone live with a specific software, and Region 2 is now supposed to go live on the same
system.
Extension phase System is The system is operational and you want to add new functions. For example, your live sys-
(Phase E) operational tem runs the SAP ERP applications, and you want to add CRM applications now.
Upgrade phase System is The system is operational and you want to perform an upgrade. For example, the system
(Phase F) operational runs on SAP R/3 Enterprise and you want to upgrade it to SAP ERP 6.0.
the software, you will probably have only basic informa- ings in phases B and C, resizings in phase D, delta sizings
tion on how you are going to use it so that you can at in phase E, and upgrade sizings in phase F.
least make a rough estimate of the costs involved. During
the course of the implementation project, you can refine
2.2 Methods for Initial Sizings
your initial assumptions by using standard sizing rules in
order to take a closer look at the critical issues. Initial sizings are sizings that refer to new installations,
If an installation’s complexity differs too much from that is, installations in which you use SAP software for
the standard, you can, for instance, measure customer the first time. That is also the case if, for instance, you
processes in order to create customer-specific sizings. want to use SAP SRM for the first time while SAP ERP
All these different phases require different sizing meth- is already running in your company’s production system
ods. In this context, we generally distinguish between ini- — at least the sizing for SAP SRM will be considered as
tial and production sizings. Figure 2.1 provides an over- being initial.
view of the available sizing methods, with initial sizings Depending on the project phases, we differentiate ini-
being shown in the upper section and production siz- tial sizings into hardware budget sizings (budget sizings
ings in the lower one. Expert sizing is marked as a hybrid for short), advanced sizings, and expert sizings. Usually,
because under certain circumstances, some processes can budget sizings and advanced sizings are based on tools,
be mapped using standard methods while, at the same whereas expert sizings are a mixture of tools and addi-
time, customer-specific data can be analyzed. tional rules or measurements.
The following sections describe the characteristics of
these different sizings in greater detail. At this point it is Hardware Budget Sizings
important to know that sizings can be performed within The main characteristic of budget sizings is that they
several phases of a project: Sizing is an iterative process. don’t require much information from the customer and
Budget sizing, for example, could be done in phases A they contain many assumptions (i.e., values provided by
and B, advanced sizings in phases A through C, expert siz- SAP based on experience). For example, if the only infor-
Go-
Hardware Budget Sizing Advanced Sizing Expert Sizing Live
Initial Sizings
mation you have is that 100 users will use SAP CRM, but Budget Sizings Help in Estimating the Entire Size
you don’t know the other applications they will use and Let’s suppose a budget sizing determines 4,000 SAPS
what will be their average activity, you can certainly per- (SAP Application Performance Standard1). Currently,
form the sizing, but in the long run, the informational 4,000 SAPS correspond more or less to a dual-core
value provided by the result of the sizing process will be machine (server) with two processors, which has a list
too restricted. price of $15,000. Now you can make up your mind
For this reason, budget sizings are usually performed whether it makes sense to tackle a rather intensive siz-
way ahead of the GoLive phase (most of the time in ing process or whether you want to take one of the
Phase A) if the goal is to estimate the approximate scope following two risks:
of hardware. 왘 Result Is Too High
For budget sizings, you can use the user-based sizing This means the server will not be fully utilized dur-
function in SAP’s Quick Sizer (see Chapter 5, Quick Sizer). ing live operations. A result that is too high often
Alternatively, you can use T-shirt sizings (see Section 4.2, occurs because the initial estimates are usually too
T-shirt Sizing), which have the advantage of requiring you conservative.
to answer only a few questions. Of course, the disadvan- 왘 Result Is Too Low
tage is that the rough categorization into S through XL This means that you must buy additional hard-
provides only limited informational value. Occasionally, ware. In this case, the question is whether you can
such sizings can be sufficient, depending on the specific afford to use the wrong assumptions. Let’s sup-
situation. pose your initial estimate is wrong by 100%. You
For this reason, it makes a lot of sense to compare the
time and effort you want to invest into a sizing project 1 See Section 9.2, SAP Application Performance Standard, for a
with the potential hardware costs. more detailed description of SAPS.
www.sap-press.com 9
2 Sizing Methods
www.sap-press.com 11
2 Sizing Methods
왘 Load Test All these situations can affect the hardware and require
Load tests are occasionally used in the context of a more or less comprehensive sizing project. The major
expert sizings and make sense when a single-user advantage of sizings that are based on a production sys-
analysis does not provide sufficient information about tem is that you can use your own data and settings as a
the locking procedure or memory requirements. basis. In other words, you do not need to rely on assump-
In the sizing environment, load tests have a hybrid tions made by SAP.
nature: On the one hand, you can use them as a siz- Regarding production sizings, we distinguish between
ing tool. On the other hand, you can use them to the following three methods, which pursue different
verify sizing results. Because customers usually use goals:
them to verify sizing results, you can find detailed 왘 Resizing
information on them in Section 7.1, Load Tests. In a resizing project, the throughput or user volume
changes, but not the processes (or customizing or it can also be projects or calls. Alternatively, you can also
parameter settings, and so on). use the number of activities or sales orders, depending,
왘 Delta Sizing on the one hand, on which unit is best suited to reflect
In a delta sizing project, you add new functionality. the respective business activity, but also, on the other, on
왘 Upgrade Sizing how easily it can be determined.
An upgrade sizing involves a change of the SAP
release. Sample Analysis of a Production System
The following example forms the basis for the descrip-
Common to all these sizing methods is that you must first tion of individual sizing methods. A customer uses
analyze the status of the existing system before you can strategic procurement in the SRM environment. The
plan the new hardware requirements. analysis of the current utilization provides the follow-
ing result:
Production System Sizings Versus Quick Sizer 왘 CPU
The unbeatable advantage of sizing on the basis of pro- Utilization of the database server is 34%; that of
duction data is that you can take your own data, pro- the two application servers is 56%.
cesses, and settings into account. Quick Sizer has been 왘 Database
designed for new installations and contains assump- 213GB out of 512GB are occupied with a monthly
tions about the productive operation. For this reason, growth of 7GB.
we recommend Quick Sizer for initial sizings only. 왘 Memory
26GB out of 32GB are being consumed.
Basic Analysis for All Production Sizings By using a system monitor, the customer has found
For all production sizings, you must first identify the uti- out that approximately 1,254 named users out of a
lization of the sizing-relevant components in the exist- total of 1,567 have been active during the period ana-
ing system. Using the appropriate monitors, which are lyzed. Based on this information, you can now deter-
described in detail in Chapter 6, you can determine the mine whether the existing hardware is sufficient or
following information: whether it must be extended.
왘 CPU Utilization
What is the actual utilization of the CPU? Can the Resizing
existing hardware compensate for the future load? A basic prerequisite for resizing is that only the through-
Here, you must distinguish between the utilization of put and user volumes can change, but not the function-
the application server and that in the database. ality. Based on the current load situation and the new
왘 Memory Consumption information, you can easily determine future require-
How much room for maneuver do you have regard- ments using a rule of three.
ing the memory requirement: Will it increase or stay Typical resizings occur in system consolidations or in
the same? what is referred to as phased rollouts, in which customers
왘 Database Space install new software in different phases in their business
Take a look at the 30 biggest tables and indexes, and units or international subsidiaries.
make a note: How quickly did they grow during the
last several months? Resizing a Production System
Based on the above example (see previous box, Sam-
Once you have determined the current utilization or the ple Analysis of a Production System), a resizing could
database growth and the increasing memory require- look as follows: You want to add another 200 named
ments using the various vendor-specific monitors or the users to the 1,567 existing ones. We assume that the
SAP monitors, you should relate this information to a ratio between named users and active users is identical
simple business key figure. Usually this is the users, but
www.sap-press.com 13
2 Sizing Methods
www.sap-press.com 15
2 Sizing Methods
The sizing method used essentially depends on the initial certain limitations. These limitations primarily depend on
position you’re in. Basically, there are different methods the way in which business processes and the associated
for an initial sizing, which can be mapped via standard application software interact with each other. For this
tools, and for a production sizing, which uses production reason, the following chapter, Sizing Approaches (Chap-
data as a basis for forecasting. ter 3), describes how you can convert user-based and
In this chapter, we have mentioned several times that throughput-based sizings into algorithms, and discusses
although sizing tools are very useful, they are subject to the pros and cons of different sizing approaches.
www.sap-press.com 107
Index
www.sap-press.com 109