business solutions

IBM and SAP

IBM Sizing and Planning Questionnaire

for SAP Solutions

© Copyright IBM Corp. April-2008

For more information about IBM SAP solutions go to http://www.ibm-sap.com

For online entry of data from this questionnaire go to http://service.sap.com/sizing
For access to the most recent version of this questionnaire go to http://www.ibm.com/erp/sizing

Send completed questionnaire and SAP sizing questions to either your local IBM contact or:

Region IBM Contact by E-mail / Fax

North and South America IBM Americas Techline Solutions Sizing eSizings@us.ibm.com / +1 845-491-2372
IBMers raise a Techline Request
through http://w3.ibm.com/support/emea/techline

through
For both :
in case of attachment
Europe, Middle East, and Africa problems, send file to EMEA_ERP_TL@de.ibm.com
 IBM ASEAN/SA Techline(Singapore,
Malaysia, Thailand, Philippines,
Indonesia, Vietnam, India and Sri Lanka) techline@my.ibm.com
GCG(China) techline@cn.ibm.com
Hong Kong chankyk@hk1.ibm.com
Taiwan techline@tw.ibm.com
South Korea techline@kr.ibm.com
Japan r3sizing@jp.ibm.com
Asia, Pacific Australia and New Zealand HelpERP@au1.ibm.com
Competence Center, ISICC,
Others Walldorf isicc@de.ibm.com

The questionnaire was designed so that you can answer it without detailed knowledge of SAP solutions. IBM has established the Techlines
Solutions Sizing team to provide assistance to your queries and help to size and configure your SAP solution . These have been
established on geographical basis to address them locally. The following terms are trademarks or registered trademarks of the IBM
Corporation in the United States or other countries or both: AIX, DB2, DB2 Universal Database, IBM, System x, System p, System I,
System z. R/3, mySAP, SAP (Logo), SAP (Word), are trademarks or registered trademarks of SAP AG. Informix is a trademark of
Informix Corporation. Linux is a registered trademark of Linus Torvalds. Microsoft, Windows, Windows NT, Windows 2000, are
trademarks of Microsoft Corporation in the United States, other countries, or both. Oracle and Oracle 8 are trademarks or registered
trademarks of Oracle Corporation. UNIX is a registered trademark in the United States and other countries licensed exclusively through
X/Open Company Limited. Other company, product and service names may be trademarks or service marks of others.

Instructions for Completing the Questionnaire

Before completing the questionnaire, read the introduction on this page. Then follow the steps below:
1.      Complete the general sizing questions, providing special notes or comments about your SAP project.
2.      Complete the sizing questions for the SAP components/applications selected. Some of these components are supported
directly by the SAP QuickSizer. Other components in this questionnaire are estimated in this questionnaire tool by derivation from
white papers provided by SAP. Links to these white papers are provided within this questionnaire tool. You will need an OSS User
ID and an SAP customer number which you can get from your local SAP representative.
3. Return the questionnaire to IBM, or, enter the data directly into the SAP QuickSizer at web address: http://service.sap.com. You
will need an OSS User ID and an SAP customer number which you can get from your local SAP representative. Request sizing from
IBM via SAP Quicksizer to IBM link or sending Quicksizer project name and customer number to your IBM Contact after setting
 Quicksizer project status to final.

What has to be Sized?

SAP architectures have evolved from a client-server model to a Web-enabled front-end environment. The front-end device and network
elements are shared across IT applications and a dedicated server infrastructure for SAP application and database server is required.
The server infrastructure includes a hardware server plus operating system platform, a relational database and the application itself.
To obtain satisfactory end-user response times for any application, the technical specification for the client device, network and the server
infrastructure must be sized and specified.

The purpose of this questionnaire is to collect information that will be used to estimate the IBM hardware resources required to run the
SAP application suite on IBM eServers including System z, System i, System p, System x or mixed environments. The sizing estimate
results will include recommendations for CPU(s), memory, and disk for the server infrastructure. In addition, information from the sizing
questionnaire may be used by an IBM sales representative or business partner to develop an IBM infrastructure proposal including
additional hardware and software e.g. for systems management to support the SAP applications.

A sizing estimate is an approximation of the hardware resources required to support an SAP solution or component implementation. It is
a pre-sales effort based on information available at a point in time, providing an entry into understanding the customer’s hardware
requirements. Customers’ actual experiences will vary from the sizing estimate for many reasons, including batch and reporting workloads,
and custom code. The degree of variability can range from small to very significant. Sizing the hardware requirements for each
customer’s SAP implementation is an iterative process, which may be refined and repeated a number of times. We recommend checking
the sizing input data and estimations during the implementation project. It is important to understand that the sizing estimate is a
pre-installation effort mainly based on standard assumptions and benchmark performance data; it can not replace capacity planning for
installed systems. The IBM/SAP sizing methodology is continually reviewed and revised to provide the best possible estimate of the IBM
hardware resources required to run SAP. Guidelines for sizing SAP solutions come from a number of sources, including SAP, SAP
benchmarks, and customer feedback. Based on this information and your completed sizing questionnaire, we will analyze your
requirements and recommend an IBM hardware configuration.
Sizing Assumptions
This sizing will estimate the resources required to support your SAP activity with default values for CPU utilization, batch, spool, and
reporting. The default values have been determined as a result of our experience with many SAP projects and sizings.
This sizing estimation includes a workload from a provider other than IBM. IBM is not responsible for the accuracy of the data contained
in such a workload. Any reliance by you on the third party workload is at your sole risk and will not create any liability or obligation for
IBM. If you have any questions or are unsatisfied with the third party workload information, you should contact the third party provider.
The system resources quoted to you in any sizing related communications are sufficient only for the workload(s) estimated. Other factors
may require additional resources (e.g. additional non-estimated workloads, minimum configurations for RAID, allowance for growth,
workspace, etc).
The information provided to you in any sizing related communications are provided by International Business Machines Corporation (IBM)
as a service to you and may be used for informational purposes only. Use of any sizing related communications is restricted to the
purpose of helping you predict a possible IBM eServer model processor, memory and disk resources for a given workload. All
representations of processor utilization, throughput, response time, memory, disk, and other performance data in the sizing
communications are estimates and averages based on certain assumptions and conditions. No representation is made that these
throughputs and their corresponding response times or other performance data will be accurate or achieved in any given IBM eServer
installation environment. They are based on specific configurations and run time environments. Customer results will vary. Any
configuration recommended by the sizing information communicated should be tested and verified. By accepting this information or using
the sizing details you agree to the terms and conditions contained herein. If you do not agree with such terms and conditions, please do
not review or use the provided materials and return the materials to IBM.
Customer results may vary, and IBM assumes no liability for actual results that differ from the sizing estimate.
© Copyright IBM Corp. April-2008
Contact Information
Please fill in the information on the following contact points. If unknown or not applicable, leave blank.

Opportunity Number-
REQUIRED

QuickSizer customer number

QuickSizer project name

Company Name SAP Contact

Street Address Phone Number
City, State/Province e-mail address
Zip/Postal Code, Country

Customer Contact Business Partner or SAP Value Added Reseller

Title Contact
Phone Number Phone Number
e-mail address e-mail address

IBM Contact
Phone Number
e-mail address
© Copyright IBM Corp. April-2008
General Sizing Questions for Initial Sizings – New Installation or new workloads

In this section, we would like to know about your hardware and software requirements. Some of the subsections require responses; others are
optional.
This section is intended for new SAP implementations. If you already have installed SAP components and you want to expand your
installation by adding new modules or additional users or new components or solutions, you should select ‘Upgrade Sizing’ when generating
this questionnaire.

Industry Solution
Please specify if you plan to implement a specific industry solution or want to give any other additional information:

Planned Hardware Platform

Which IBM eServer would you like to consider for this sizing estimate? Specify a database server and one of its application server options. If
you want to consider more than one application server option, please describe each scenario in the comments section below. Smaller system
requirements can be configuration in which one server provides both the database and application server functions. Some application platform
components do have restricted sizing proposal will take your preferences into account wherever possible.

Database Application Server(s)

Server
System z System z System p System x
System p System p System x
System x System x
System i System i System x
Comments:

Preferred Disk Technology Sizing

Disk Technology Questions Answer Options
Please indicate your preferred disk technology? Default DS4300

Storage Sizing
Storage Capacity Questions Answer Options
What RAID Technology will you use? Default-RAID5
At what capacity do you run your storage subsystem? Default-80%
What storage growth factor over how many years would you like us to use? Default-0%, 0 years
What storage compression factor would you like us to use? Default-0%
Will you be backing up data directly to tape? Full backup to disk? Incremental backup to disk? Default-to tape

Scalability Sizing
Scalability Questions Answer Options
How important is scalability in your hardware configuration? Default-not important

High Availability Sizing

IBM servers offer a wide range of features to address high availability. Some features come as standard, others are optional. In order for us to
better determine which high availability options should be included in the recommended configuration, please indicate your preferences for
high availability.

High Availability Questions Answer Options

Is high availability technology, such as clustering or HACMP, on the database server required? Default-no
If yes, where will failover be? App Server? Test Server? Idle Server? Other? Default-App

Backup/Restore Sizing
Backup/Restore Question Answer Options
Do you want a backup device included in the proposed configuration? Default-no

UNICODE Sizing
UNICODE is an international character set standard which allows you to process and store virtually all the languages and scripts in the world.
UNICODE Question Answer Options
Will you be using UNICODE? Default-yes

Length of your business year Sizing

Length of your business year Question Answer Options
How many working days are in your business year? Default-250

Project Phases and Growth

By default, this sizing estimate will estimate the resources required to support the SAP activity you describe in the solution sections of this
questionnaire. If desired, you can use this section to request sizing estimates for specific project phases. A project phase may be the
implementation of one or more SAP business applications, growth in terms of additional users, or growth in business volumes.
If you plan to implement in different phases, please copy the respective tabs of the questionnaire and submit together.

Type of Sizing
Type of Sizing Question Answer Options
© Copyright IBM Corp. April-2008
QUICKSIZER SIZING FOR ERP

What release of ERP are you implementing 6

What time does the AVERAGE workday start 9:00
What time does the AVERAGE workday end 18:00
What time does the PEAK load start 12:00
What time does the PEAK load end 13:00

NON-PRODUCTION SYSTEMS
System Landscape (required)
A system landscape consists of the systems and clients that are needed for non-production. Once the system landscape has been
defined, you may then create an implementation strategy for the setup and maintenance of the systems and clients within this landscape.
IBM and SAP strongly recommend having at least a three-system landscape. A three-system landscape is comprised of a development
system, a quality assurance system and a production system. This configuration ensures the proper management and testing of changes to
the system before applying them to the live production environment. If nothing is specified we will assume a Dev and Test system.

Type Default Size Storage Default

First non-production system Dev 100GB's
Second non-production system QA =prod
Third non-production system, if needed None None
Fourth non-production system, if needed None None
Fifth non-production system, if needed None None

Please specify any other additional information to help in sizing

Enter total CONCURRENT users during the PEAK hour--A user must NOT be counted twice
He is either one type of user or another--NOT both at the same time during the PEAK hour
USER BASED SIZING
LOW MEDIUM HIGH
CO-Users in Controlling-PEAK PER HOUR
FI-Users in Financial Transactions-PEAK PER HOUR
PA-Users in Personnel Administration-PEAK PER HOUR
PD-Users in Personnel Development-PEAK PER HOUR
LE-Users in Logistics Execution-PEAK PER HOUR
ALM/PM-Users in Asset Lifecycle Management-PEAK PER HOUR
MM-Users in Materials Management-PEAK PER HOUR
PP-Users in Production Planning-PEAK PER HOUR
PS-Users in Project Management-PEAK PER HOUR
QM-Users in Quality Management-PEAK PER HOUR
CS-Users in Customer Service-PEAK PER HOUR
SD-Users in Sales & Distribution-PEAK PER HOUR
BC-Users in Basis transactions-PEAK PER HOUR
TOTAL CONCURRENT PEAK users -PEAK PER HOUR 0 0 0 0 users
Approximate SAPS 0 SAPS 0 init SAPS
Approximate Storage 0 GB's
If AFS is implemented add this uplift 0 SAPS Click for sizing white paper

THRUPUT SIZING FOR FINANCIALS--If you complete this section, you must resolve all "ERROR" messages. 0
OBJECTS ITEMS % CHG % DISP MONTHS ST TIME END TIME
CO-PA-BIL-AVERAGE Billing docs posted to CO per YEAR 0 0 NA NA
CO-PA-BIL-PEAK Billing docs posted to CO per PEAK TIME 0 NA 12:00 13:00
CO-PA-FI-AVERAGE Financial docs posted to CO per YEAR 0 0 NA NA
CO-PA-FI-PEAK Financial docs posted to CO per PEAK TIME 0 NA 12:00 12:00
CO-PA-SLS-AVERAGE Sales orders posted to CO per YEAR 0 0 NA NA
CO-PA-SLS-PEAK Sales orders posted to CO per PEAK TIME 0 NA 12:00 12:00
CO-AVERAGE Controlling docs or postings per YEAR 0 0 NA NA
CO-PEAK Controlling docs or postings per PEAK TIME 0 NA 12:00 12:00
EC-PCA-AVERAGE Profit center charged off docs per YEAR 0 0 NA NA
EC-PCA-PEAK Profit center charged off docs per PEAK TIME 0 NA 12:00 12:00
FIN-BAC-AVERAGE Business Accounting docs per YEAR 0 0 NA NA
FIN-BAC-PEAK Business Accounting docs per PEAK TIME 0 NA 12:00 12:00

OBJECTS ST TIME END TIME

CO-OM-PEAK Sender-receiver relations for all cycles NA NA NA NA 0 0
CO-OM-RAT-PEAK Orders/period with overhead rate NA NA NA NA 0 0
CO-OM-SET-PEAK Orders allocated/period NA NA NA NA 0 0

Contract Accounting--If you complete this section, you must resolve all "ERROR" messages.
OBJECTS ITEMS EDRs/bd ST TIME END TIME
EDR-BILL-PEAK Event Detail Record 0 0 NA NA 0 0

OBJECTS ITEMS ST TIME END TIME

LOAD-BILL-PEAK Load Billing 0 NA NA NA 0 0
LOAD-INV-PEAK Load Invoicing 0 NA NA NA 0 0
CONV-INV-PEAK Convergent Invoicing 0 NA NA NA 0 0
DUNNING-PEAK Dunning 0 NA NA NA 0 0

OBJECTS ST TIME END TIME

EDR-UPL-PEAK EDR Upload NA NA NA NA 0 0
PAY-RUN-PEAK Payment Run NA NA NA NA 0 0
CD-PL-PEAK Payment Lots NA NA NA NA 0 0
CORR-PRINT-PEAK Correspondence Print NA NA NA NA 0 0
DEF-POST-PEAK Deferred Postings NA NA NA NA 0 0

EDRs AddFld MONTHS ST TIME END TIME

EDR-UPL-AVERAGE Event Detail Record Upload NA NA 0 NA NA

OBJECTS MONTHS ST TIME END TIME

PAY-RUN-AVERAGE Payment Run NA NA NA 0 NA NA
CD-PL-AVERAGE Payment Lots NA NA NA 0 NA NA
CORR-PRINT-AVERAGE Correspondent Print NA NA NA 0 NA NA
DEF-POST-AVERAGE Deferred Postings NA NA NA 0 NA NA

OBJECTS ITEMS MONTHS ST TIME END TIME

EDR-BILL-AVERAGE Event Detail Record Billing 0 NA NA 0 NA NA
LOAD-BILL-AVERAGE Load Billing 0 NA NA 0 NA NA
CONV-INV-AVERAGE Convergent Invoicing 0 NA NA 0 NA NA
DUNNING-AVERAGE Dunning 0 NA NA 0 NA NA

Postings BP itm GL itm Payments P itm % credit MONTHS ST TIME END TIME
SUBLEDGER-AVERAGE Subledger Documents 0 0 0 0 0 NA NA

THRUPUT SIZING FOR HUMAN CAPITAL MANAGEMENT-- If you complete this section, you must resolve all "ERROR" messages.
ESS/MSS workload Scenarios Steps ST TIME END TIME
ESS-LEAVE 7 NA NA NA 0 0
ESS-CATS 9 NA NA NA 0 0
ESS-TRAVEL 18 NA NA NA 0 0
MSS_COST 9 NA NA NA 0 0
MSS-PERS 13 NA NA NA 0 0

OBJECTS ST TIME END TIME

HCM-PT-PEAK Processed Time Pairs per PEAK TIME NA NA NA NA 0 0
HCM-PY-PEAK Payroll periods incl retro calculations NA NA NA NA 0 0

THRUPUT SIZING FOR LOGISTICS EXECUTION-- If you complete this section, you must resolve all "ERROR" messages.
 OBJECTS ITEMS % CHG % DISP MONTHS ST TIME END TIME
LE-WM-AVERAGE Transfer Orders per YEAR 0 0 NA NA
LE-WM-PEAK Transfer Orders per PEAK TIME 0 NA 0 0
LE-SHP-AVERAGE Delivery notes and goods issue per YEAR 0 0 NA NA
LE-SHP-PEAK Delivery notes and goods issue per PEAK TIME 0 NA 0 0

THRUPUT SIZING FOR PRODUCT DEV AND EXECUTION-- If you complete this section, you must resolve all "ERROR" messages.
OBJECTS ITEMS % CHG % DISP MONTHS ST TIME END TIME
ALM-PM-AVERAGE Maintenance Orders per YEAR 0 0 NA NA
ALM-PM-PEAK Maintenance Orders per PEAK TIME 0 NA 0 0
MM-IM-AVERAGE Material Movements per YEAR 0 0 NA NA
MM-IM-PEAK Material Movements per PEAK TIME 0 NA 0 0
MM-PUR-AVERAGE Purchase Orders per YEAR 0 0 NA NA
MM-PUR-PEAK Purchase Orders per PEAK TIME 0 NA 0 0
PP-CONF-AVERAGE Order Confirmations per YEAR 0 0 NA NA
PP-CONF-PEAK Order Confirmations per PEAK TIME 0 NA 0 0
PP-REM-AVERAGE Planned Orders per YEAR 0 0 NA NA
PP-REM-PEAK Planned Orders per PEAK TIME 0 NA 0 0
PP-SFC-AVERAGE Production Orders per YEAR 0 0 NA NA
PP-SFC-PEAK Production Orders per PEAK TIME 0 NA 0 0
QM-IM-AVERAGE Inspections in Quality Mgmt per YEAR 0 0 NA NA
QM-IM-PEAK Inspections in Quality Mgmt per PEAK TIME 0 NA 0 0

OBJECTS WBS NETW Act/Net % CHG % DISP MONTHS ST TIME END TIME
PS-AVERAGE Projects per YEAR 0 0 NA NA
PS-PEAK Projects per PEAK TIME 0 NA 0 0

PLAN OR COMP REORD Non-REORHORIZON % CHG % DISP % LTS ST TIME END TIME
MRP RUN 0 0 0 0

THRUPUT SIZING FOR SALES AND SERVICE--If you complete this section, you must resolve all "ERROR" messages.
OBJECTS ITEMS % CHG % DISP MONTHS ST TIME END TIME
CS-AG-AVERAGE Customer Service objects per YEAR 0 0 NA NA
CS-AG-PEAK Customer Service objects per PEAK TIME 0 NA 0 0
SD-CUST-AVERAGE Customer Contacts per YEAR 0 0 NA NA
SD-CUST-PEAK Customer Contacts per PEAK TIME 0 NA 0 0
SD-BIL-AVERAGE Billing Documents per YEAR 0 0 NA NA
SD-BIL-PEAK Billing Documents per PEAK TIME 0 NA 0 0
SD-POS-AVERAGE Point of Sales objects for Retail per YEAR 0 0 NA NA
SD-POS-PEAK Point of Sales objects for Retail per PEAK TIME 0 NA 0 0
SD-SLS-AVERAGE Sales Orders per YEAR 0 0 NA NA
SD-SLS-PEAK Sales Orders per PEAK TIME 0 NA 0 0

COM CAS REMC MONTHS ST TIME END TIME

ICM-CASE-AVERAGE Customer Service cases per YEAR 0 NA NA 0 NA NA
ICM-CASE-PEAK Customer Service cases per PEAK TIME 0 NA NA NA 0 0

DOCU REMD MONTHS ST TIME END TIME

ICM-DOC-AVERAGE Commission documents posted per YEAR 0 NA NA 0 NA NA
ICM-DOC-PEAK Commission documents posted per PEAK TIME 0 NA NA NA 0 0

ITEMS COM CON ST TIME END TIME

ICM-SET-AVERAGE Settlement items per YEAR 0 NA NA NA NA NA
ICM-SET-PEAK Settlement items PEAK TIME 0 NA NA NA 0 0

THRUPUT SIZING FOR CORPORATE SERVICES--If you complete this section, you must resolve all "ERROR" messages.
OBJECTS ITEMS % CHG % DISP MONTHS ST TIME END TIME
TV-RECEIPT-AVERAGE Travel Receipts per YEAR 0 0 NA NA
TV-RECEIPT-PEAK Travel Receipts per PEAK TIME 0 NA 0 0

THRUPUT SIZING FOR APPLICATION SERVER SERVICES-- If you complete this section, you must resolve all "ERROR" messages.
OBJECTS % CHG % DISP MONTHS ST TIME END TIME
BC-PRINT-AVERAGE Print Pages per YEAR NA 0 NA NA
BC-PRINT-PEAK Print Pages per PEAK TIME NA NA 0 0
© Copyright IBM Corp. April-2008
QUICKSIZER SIZING FOR CRM

What release of CRM are you implementing 2007

What time does the AVERAGE workday start 9:00
What time does the AVERAGE workday end 18:00
What time does the PEAK load start 12:00
What time does the PEAK load end 13:00

NON-PRODUCTION SYSTEMS
System Landscape (required)
A system landscape consists of the systems and clients that are needed for non-production. Once the system landscape has been
defined, you may then create an implementation strategy for the setup and maintenance of the systems and clients within this landscape.
IBM and SAP strongly recommend having at least a three-system landscape. A three-system landscape is comprised of a development
system, a quality assurance system and a production system. This configuration ensures the proper management and testing of changes to
the system before applying them to the live production environment. If nothing is specified we will assume a Dev and Test system.

Type Default Size Storage Default

First non-production system Dev 100GB's
Second non-production system QA =prod
Third non-production system, if needed None None
Fourth non-production system, if needed None None
Fifth non-production system, if needed None None

Please specify any other additional information to help in sizing

Enter total CONCURRENT users during the peak hour--A user must NOT be counted twice
He is either one type of user or another--NOT both at the same time during the PEAK hour

USER-BASED SIZING FOR CRM MASTER DATA

 LOW MEDIUM HIGH ext SAPS GB-Storage
ACC-USER-CRM Account Management-PEAK PER HOUR 0 0

THRUPUT SIZING FOR CRM Acc for BP's--If you complete this section, you must resolve all "ERROR" messages.
New Acct Chg Acct Dis Acct Tot Acct ST TIME END TIME
CRM-CORACC-AVERAGE Corp Accounts per YEAR NA 0 NA NA
CRM-CORACC-PEAK Corp Accounts per PEAK TIME NA NA 0 0
CRM-INDACC-AVERAGE Individual Accounts per YEAR NA 0 NA NA
CRM-INDACC-PEAK Individual Accounts per PEAK TIME NA NA 0 0

USER-BASED SIZING FOR CRM SALES

LOW MEDIUM HIGH ext SAPS GB-Storage
Users doing CRM Activity Management-PEAK PER HOUR 0 0
Users doing CRM Opportunity Management-PEAK PER HOUR 0 0
Users doing CRM Sales Transactions-PEAK PER HOUR 0 0
TOTAL CRM Sales-PEAK PER HOUR 0 0 0 0 0

THRUPUT SIZING FOR CRM SALES--If you complete this section, you must resolve all "ERROR" messages.
OBJECTS ITEMS % CHG % DISP MONTHS ST TIME END TIME
CRM-SLSQC-AVERAGE sales quotations per YEAR 0 0 NA NA
CRM-SLSQC-PEAK sales quotations per PEAK TIME 0 NA 0 0
CRM-SLS-AVERAGE sales orders per YEAR 0 0 NA NA
CRM-SLS-PEAK sales orders per PEAK TIME 0 NA 0 0
CRM-SLSCO-AVERAGE sales contracts per YEAR 0 0 NA NA
CRM-SLSCO-PEAK sales contracts per PEAK TIME 0 NA 0 0

OBJECTS % CHG % DISP MONTHS ST TIME END TIME

CRM-LEAD-AVERAGE sales leads per YEAR NA 0 NA NA
CRM-LEAD-PEAK sales leads per PEAK TIME NA NA 0 0
CRM-ACT-AVERAGE sales activities per YEAR NA 0 NA NA
CRM-ACT-PEAK sales activities per PEAK TIME NA NA 0 0
CRM-APP-AVERAGE sales appointments per YEAR NA 0 NA NA
CRM-APP-PEAK sales appointments per PEAK TIME NA NA 0 0
CRM-OPP-AVERAGE sales opportunities per YEAR NA 0 NA NA
CRM-OPP-PEAK sales opportunities per PEAK TIME NA NA 0 0

USER-BASED SIZING FOR CRM SERVICE

LOW MEDIUM HIGH ext SAPS GB-Storage
Users doing CRM Service Transactions-PEAK PER HOUR 0 0

THRUPUT SIZING FOR CRM SERVICE--If you complete this section, you must resolve all "ERROR" messages.
OBJECTS ITEMS % CHG % DISP MONTHS ST TIME END TIME
CRM-SRVQC-AVERAGE service order quotes per YEAR 0 0 NA NA
CRM-SRVQC-PEAK service order quotes per PEAK TIME 0 NA 0 0
CRM-SRV-AVERAGE service orders per YEAR 0 0 NA NA
CRM-SRV-PEAK service orders per PEAK TIME 0 NA 0 0
CRM-SRVCC-AVERAGE service contracts/quotes per YEAR 0 0 NA NA
CRM-SRVCC-PEAK service contracts/quotes per PEAK TIME 0 NA 0 0
CRM-CPLT-AVERAGE compliants/returns/repairs per YEAR 0 0 NA NA
CRM-CPLT-PEAK complaints/returns/repairs per PEAK TIME 0 NA 0 0
CRM-WCL-AVERAGE warranty claims per YEAR 0 0 NA NA
CRM-WCL-PEAK warranty claims per PEAK TIME 0 NA 0 0

OBJECTS % CHG % DISP MONTHS ST TIME END TIME

CRM-SRVAC-AVERAGE service activities per YEAR 0 NA NA
CRM-SRVAC-PEAK service activities per PEAK TIME NA 0 0
CRM-CONF-AVERAGE service confirmations per YEAR 0 NA NA
CRM-CONF-PEAK service confirmations per PEAK TIME NA 0 0

THRUPUT SIZING FOR CRM E-COMMERCE--If you complete this section, you must resolve all "ERROR" messages.
VISITS % ORD ITEMS MONTHS ST TIME END TIME
AVERAGE Internet sales orders and visits per YEAR NA 0 0 0 NA NA
PEAK Internet sales orders and visits per PEAK TIME NA 0 0 NA 0 0

USER-BASED SIZING FOR CRM INTERACTION CENTER

LOW MEDIUM HIGH ext SAPS GB-Storage
Total users in the Call Center(CIC)-PEAK PER HOUR 0 0
THRUPUT SIZING FOR CRM IC--If you complete this section, you must resolve all "ERROR" messages.
OBJECTS % CHG % DISP MONTHS ST TIME END TIME
AVERAGE calls/emails in customer center per YEAR NA 0 NA NA
PEAK calls/emails in customer center per PEAK TIME NA NA 0 0

USER-BASED SIZING FOR CRM MOBILE

LOGONS ext SAPS GB-Storage
MSA-USER--Users synchronizing laptops-PEAK PER HOUR 0 0

THRUPUT SIZING FOR CRM MOBILE--If you complete this section, you must resolve all "ERROR" messages.
OBJECTS ITEMS % CHG % DISP MONTHS ST TIME END TIME
AVERAGE orders thru Mobile Sales and Service per YEAR 0 0 NA NA
PEAK orders thru Mobile Sales and Service per PEAK TIME 0 NA 0 0

Campaign Execution sizing Guidance Click for sizing white paper

Bus Part Activities Int Objects e-mails to BW ST TIME END TIME ext SAPS
Profile for Campaign number one 0
Profile for Campaign number two 0
Profile for Campaign number three 0
Profile for Campaign number four 0
Profile for Campaign number five 0

TPM-Trade Promotions Management

Promotions Products Periods Keyfigures Plng Cells Partners PR_REB Rec CDET Rec

CRM ABAP SAPS DB SAPS GB's-Memory

Core TPM process(adding products) 0 0
Generation of price/rebate condition records process 0 0
Generation of campaign determination condition records process 0 0
Rendering the planning layout 0 0
Re-synchronizing with SAP NW BW(Saving the promotion) 0 0
Total for CRM 0 0 0

SEM/BI ABAP SAPS DB SAPS GB's-Memory GB Storage

Rendering the planning layout 0 0
Re-synchronizing with SAP NW BW(Saving the promotion) 0 0
Total for SEM/BI 0 0 0 0
© Copyright IBM Corp. April-2008
QUICKSIZER SIZING FOR BI & SEM

What release of BI/SEM are you implementing 7

What time does the AVERAGE workday start 9:00
What time does the AVERAGE workday end 18:00
What time does the PEAK load start 12:00
What time does the PEAK load end 13:00

NON-PRODUCTION SYSTEMS
System Landscape (required)
A system landscape consists of the systems and clients that are needed for non-production. Once the system landscape has been
defined, you may then create an implementation strategy for the setup and maintenance of the systems and clients within this landscape.
IBM and SAP strongly recommend having at least a three-system landscape. A three-system landscape is comprised of a development
system, a quality assurance system and a production system. This configuration ensures the proper management and testing of changes to
the system before applying them to the live production environment. If nothing is specified we will assume a Dev and Test system.

Type Default Size Storage Default

First non-production system Dev 100GB's
Second non-production system QA =prod
Third non-production system, if needed None None
Fourth non-production system, if needed None None
Fifth non-production system, if needed None None

Please specify any other additional information to help in sizing

Enter total CONCURRENT users during the peak hour--A user must NOT be counted twice
He is either one type of user or another--NOT both at the same time during the peak hour
SEM Business Planning
SEM Users STEPS ChngRec Data/Step Data/User ST TIME END TIME
Business Planning and Simulations Group 1-PEAK 6 30000 60000 200000 12:00 13:00
Business Planning and Simulations Group 2-PEAK 12 15000 30000 100000 12:00 13:00
Business Planning and Simulations Group 3-PEAK 30 5000 10000 25000 12:00 13:00
0

BI(fill in the number of concurrently active BI users)

BI Users % Report % OLAP % Explore Web IP BIA B.P ST TIME END TIME
BI-INFO-typically 71% of all BI users 80 20 0 yes no no 1 NA NA
BI-BUSIN-typically 26% of all BI users 50 50 0 yes no no 1 NA NA
BI-EXPERT-typically 3% of all BI users 0 0 100 yes no no 1 NA NA
0

RECORDS ST TIME END TIME

Data record uploads NA NA NA NA 0 0

INFOCUBES
DIMEN KEY FIG INITIAL PERIODIC PERIODS BIA % MD D Values % DVL % DV1
INFOCUBE-DISK-Duplicate as needed 0 no 10

DATASTORE OBJECTS
NUMFLD TXTFLD INITIAL PERIODIC PERIODS
DS OBJECTS-DISK-Duplicate as needed 0
© Copyright IBM Corp. April-2008
QUICKSIZER SIZING FOR PORTAL

What release of Enterprise Portal are you implementing 7

NON-PRODUCTION SYSTEMS
System Landscape (required)
A system landscape consists of the systems and clients that are needed for non-production. Once the system landscape has been
defined, you may then create an implementation strategy for the setup and maintenance of the systems and clients within this landscape.
IBM and SAP strongly recommend having at least a three-system landscape. A three-system landscape is comprised of a development
system, a quality assurance system and a production system. This configuration ensures the proper management and testing of changes to
the system before applying them to the live production environment. If nothing is specified we will assume a Dev and Test system.

Type Default Size Storage Default

First non-production system Dev 100GB's
Second non-production system QA =prod
Third non-production system, if needed None None
Fourth non-production system, if needed None None
Fifth non-production system, if needed None None

Please specify any other additional information to help in sizing

Enter total CONCURRENT users during the peak hour--A user must NOT be counted twice
He is either one type of user or another--NOT both at the same time during the peak hour
Enterprise Portal
USERS Think time Java iViews URL iViews
NW-EP-URL-PEAK 600 0 1
NW-EP-INT-PEAK 211 3 0
NW-EP-PCC-PEAK 180 3 0
NW-EP-PRT-PEAK 0 0 0
Total Users 0

LOGONS
Maximum number of logons per PEAK hour

NetWeaver Portal Knowledge Management and Collaboration

Acc Docs New Docs Size Rooms MONTHS ST TIME END TIME
NW-KMC-Documents per TIME Period 0 700 4000 0 NA NA
NW-KMC-PEAK Documents per PEAK TIME 0 NA NA NA 0 0
© Copyright IBM Corp. April-2008
QUICKSIZER SIZING FOR PROCESS INTEGRATION

What release of PI are you implementing 7

What time does the PEAK load start 12:00
What time does the PEAK load end 13:00

NON-PRODUCTION SYSTEMS
System Landscape (required)
A system landscape consists of the systems and clients that are needed for non-production. Once the system landscape has been
defined, you may then create an implementation strategy for the setup and maintenance of the systems and clients within this landscape.
IBM and SAP strongly recommend having at least a three-system landscape. A three-system landscape is comprised of a development
system, a quality assurance system and a production system. This configuration ensures the proper management and testing of changes to
the system before applying them to the live production environment. If nothing is specified we will assume a Dev and Test system.

Type Default Size Storage Default

First non-production system Dev 100GB's
Second non-production system QA =prod
Third non-production system, if needed None None
Fourth non-production system, if needed None None
Fifth non-production system, if needed None None

Please specify any other additional information to help in sizing

PI ADVANCED SIZING FOR INTEGRATION SERVER

XML SIZE KB Messages Sync/Async Inbd adap Outb adap Int.S. BPM Pat ST TIME END TIME
PI-INT-SRV-ADVANCED-PEAK per PEAK TIME 0 Asynchronous XI (Proxy) XI (Proxy) no None 0 0

PI NON-CENTRAL ADAPTER ENGINE

XML SIZE KB Messages Sync/Async Inbd adap Outb adap Int.S. ST TIME END TIME
PI-ADAPTER-PEAK per PEAK TIME 0 Asynchronous None None no 0 0
© Copyright IBM Corp. April-2008
QUICKSIZER SIZING FOR TREX

What release of TREX are you implementing 7

What time does the PEAK load start 12:00
What time does the PEAK load end 13:00

NON-PRODUCTION SYSTEMS
System Landscape (required)
A system landscape consists of the systems and clients that are needed for non-production. Once the system landscape has been
defined, you may then create an implementation strategy for the setup and maintenance of the systems and clients within this landscape.
IBM and SAP strongly recommend having at least a three-system landscape. A three-system landscape is comprised of a development
system, a quality assurance system and a production system. This configuration ensures the proper management and testing of changes to
the system before applying them to the live production environment. If nothing is specified we will assume a Dev and Test system.

Type Default Size Storage Default

First non-production system Dev 100GB's
Second non-production system QA =prod
Third non-production system, if needed None None
Fourth non-production system, if needed None None
Fifth non-production system, if needed None None

Please specify any other additional information to help in sizing

THRUPUT SIZING FOR TREX

Searches Indexed data Delta Index NA NA ST TIME END TIME
TREX-SRCH-PEAK TREX Searches per PEAK TIME NA NA 0 0
© Copyright IBM Corp. April-2008
QUICKSIZER SIZING FOR SCM

What release of SCM are you implementing 5

What time does the AVERAGE workday start 9:00
What time does the AVERAGE workday end 18:00
What time does the PEAK load start 12:00
What time does the PEAK load end 13:00

NON-PRODUCTION SYSTEMS
System Landscape (required)
A system landscape consists of the systems and clients that are needed for non-production. Once the system landscape has been
defined, you may then create an implementation strategy for the setup and maintenance of the systems and clients within this landscape.
IBM and SAP strongly recommend having at least a three-system landscape. A three-system landscape is comprised of a development
system, a quality assurance system and a production system. This configuration ensures the proper management and testing of changes to
the system before applying them to the live production environment. If nothing is specified we will assume a Dev and Test system.

Type Default Size Storage Default

First non-production system Dev 100GB's
Second non-production system QA =prod
Third non-production system, if needed None None
Fourth non-production system, if needed None None
Fifth non-production system, if needed None None

Please specify any other additional information to help in sizing

QuickSizer customer number

QuickSizer project name

THRUPUT SIZING FOR DEMAND PLANNING

CharCom KeyFig Periods Com Index Times Time Buck Pl Vers
TIMESERIES-Planning Area Sizing for LiveCache memory 0 0 0 0

CharCom Time Buck ST TIME END TIME

DP-RUN-Planning Run Sizing for CPU NA NA NA 0 0 0

APO Users ST TIME END TIME

DP-USER-Additional Users for CPU NA NA NA NA 0 0

THRUPUT SIZING FOR SUPPLY & PRODUCTION PLANNING

LOC PROD Resources
MASTERDAT-Master data Sizing for LiveCache memory

SCM OBJ
STOCK-Warehouse Stocks Sizing for LiveCache memory

SCM OBJ Components OPER ACT/OP ALT/RES ParCap

PLANNEDORD-Planned orders Sizing for LiveCache memory 0 0 0

SCM OBJ SUB OBJ

FORECAST-Forecast orders Sizing for LiveCache memory 0
PURCHORD-Purchase orders Sizing for LiveCache memory 0
SALES-Sales orders Sizing for LiveCache memory 0
TRANSFER-Transfer orders Sizing for LiveCache memory 0

SKUs Time Buck ST TIME END TIME

SNP-RUN-Heuristic plan Sizing for CPU--PEAK NA NA NA 0 0 0

APO User ST TIME END TIME

PP USER-Planning Board User Sizing for CPU--PEAK NA NA NA NA 0 0
SNP USER-SNP User Sizing for CPU--PEAK NA NA NA NA 0 0

THRUPUT SIZING FOR ORDER FULFILLMENT

Loc prod
ATP-MD-ATP Masterdata Sizing for LiveCache memory

Requests ST TIME END TIME

ATP-SIMPLE-ATP simple checks Sizing for CPU--PEAK NA NA NA NA 0 0
ATP-RULE-ATP rules based checks Sizing for CPU--PEAK NA NA NA NA 0 0
ATP-CTP-ATP Capable to promise checks Sizing for CPU--PEAK NA NA NA NA 0 0

THRUPUT SIZING FOR SERVICE PARTS PLANNING

 SKUs ST TIME END TIME
SPP-STK-Stocking and DeStocking--PEAK NA NA NA NA 0 0
SPP-EOQ-Economic order quantity--PEAK NA NA NA NA 0 0
SPP-DPLY-Deployment--PEAK NA NA NA NA 0 0

SKUs Time Buck ST TIME END TIME

SPP-FCST-Forecasting--PEAK NA NA NA 0 0 0
SPP-DRP-Distribution requirements processing--PEAK NA NA NA 0 0 0

SNC-Purchase Order Collaboration

Profile SAPS Storage
Initial Sizing--See whitepaper on the QuickSizer website 0 0

SNC-Release Processing
Profile SAPS Storage
Initial Sizing--See whitepaper on the QuickSizer website 0 0

Messages Products Periods MONTHS ST TIME END TIME

ICH-DS-AVERAGE Delivery Schedule messages per YEAR 0 0 NA 0 NA NA
ICH-DS-PEAK Delivery Schedule messages per PEAK TIME 0 0 NA NA 0 0
ICH-PROACT-AVERAGE Product Activity messages per YEAR 0 0 NA 0 NA NA
ICH-PROACT-PEAK Product Activity messages per PEAK TIME 0 0 NA NA 0 0

Messages Products MONTHS ST TIME END TIME

ICH-ASN-AVERAGE Advanced Scheduling messages per YEAR 0 NA NA 0 NA NA
ICH-ASN-PEAK Advanced Scheduling messages per PEAK TIME 0 NA NA NA 0 0
ICH-GR-AVERAGE Goods Receipt messages per YEAR 0 NA NA 0 NA NA
ICH-GR-PEAK Goods Receipt messages per PEAK TIME 0 NA NA NA 0 0

THRUPUT SIZING FOR INTEGRATION TO ECC

SCM objects Items ST TIME END TIME
PI-PROD-PEAK Manufacturing Orders per PEAK TIME 0 NA NA NA 0 0
PI-SALES-PEAK Sales Orders per PEAK TIME 0 NA NA NA 0 0
PI-PURCH-PEAK Purchase Orders per PEAK TIME 0 NA NA NA 0 0
PI-STOCKL-PEAK Stock movements per PEAK TIME 1 NA NA NA 0 0

THRUPUT SIZING FOR EWM INBOUND

OBJECTS ITEMS % CHG % DISP MONTHS ST TIME END TIME
IEWM-DLV-AVERAGE Inbound delivery documents per YEAR 0 0 NA NA
IEWM-DLV-PEAK Inbound delivery documents per PEAK TIME 0 NA 0 0

Ware tasks % DISP MONTHS ST TIME END TIME

IEWM-UNTSK-AVERAGE creation of unloading tasks per YEAR NA NA 0 NA NA
IEWM-UNTSK-PEAK creation of unloading tasks per PEAK TIME NA NA NA 0 0
IEWM-CONF-AVERAGE confirm of unloading tasks per YEAR NA NA 0 NA NA
IEWM-CONF-PEAK confirm of unloading tasks per PEAK TIME NA NA NA 0 0

Ware tasks % DISP MONTHS ST TIME END TIME

IEWM-PATSK-AVERAGE creation of putaway tasks per YEAR NA NA 0 NA NA
IEWM-PATSK-PEAK creation of putaway tasks per PEAK TIME NA NA NA 0 0

Ware tasks % RF % DISP MONTHS ST TIME END TIME

IEWM-PACON-AVERAGE confirm of putaway tasks per YEAR NA 0 NA NA
IEWM-PACON-PEAK confirm of putaway tasks per PEAK TIME NA NA 0 0

Ware tasks RsChg % DISP MONTHS ST TIME END TIME

IEWM-RESPA-AVERAGE chg/resource of putaway tasks per YEAR NA 0 NA NA
IEWM-RESPA-PEAK chg/resource of putaway tasks per PEAK TIME NA NA 0 0

HU's Put. It. Unpk Items % DISP ST TIME END TIME

IEWM-DECON-AVERAGE unpacking of putaway tasks per YEAR 0 NA NA NA
IEWM-DECON-PEAK unpacking of putaway tasks per PEAK TIME 0 NA 0 0

Ware tasks % DISP MONTHS ST TIME END TIME

IEWM-MOVE-AVERAGE move warehouse tasks per YEAR NA NA 0 NA NA
IEWM-MOVE-PEAK move warehouse tasks per PEAK TIME NA NA NA 0 0

Ware tasks RsChg % DISP MONTHS ST TIME END TIME

IEWM-RESFI-AVERAGE chg/resource of packing tasks per YEAR 0 NA 0 NA NA
IEWM-RESFI-PEAK chg/resource of packing tasks per PEAK TIME 0 NA NA 0 0

THRUPUT SIZING FOR EWM OUTBOUND

OBJECTS ITEMS % CHG % DISP MONTHS ST TIME END TIME
OEWM-DLV-AVERAGE Outbound delivery documents per YEAR 0 0 NA NA
OEWM-DLV-PEAK Outbound delivery documents per PEAK TIME 0 NA 0 0
 Ware tasks % DISP MONTHS ST TIME END TIME
OEWM-PICK-AVERAGE creation of picking tasks per YEAR NA NA 0 NA NA
OEWM-PICK-PEAK creation of picking tasks per PEAK TIME NA NA NA 0 0

Ware tasks % RF % DISP MONTHS ST TIME END TIME

OEWM-CONF-AVERAGE confirmation of picking tasks per YEAR NA 0 NA NA
OEWM-CONF-PEAK confirmation of picking tasks per PEAK TIME NA NA 0 0

Ware tasks % DISP MONTHS ST TIME END TIME

OEWM-DEST-AVERAGE move warehouse tasks per YEAR NA NA 0 NA NA
OEWM-DEST-PEAK move warehouse tasks per PEAK TIME NA NA NA 0 0

Ware tasks RsChg % DISP MONTHS ST TIME END TIME

OEWM-RESPI-AVERAGE chg/resource of picking tasks per YEAR 0 NA 0 NA NA
OEWM-RESPI-PEAK chg/resource of picking tasks per PEAK TIME 0 NA NA 0 0

HU's Put. It. % DISP ST TIME END TIME

OEWM-PACK-AVERAGE packing tasks per YEAR 0 NA NA NA NA
OEWM-PACK-PEAK packing tasks per PEAK TIME 0 NA NA 0 0

Ware tasks % DISP MONTHS ST TIME END TIME

OEWM-STAGE-AVERAGE move warehouse tasks per YEAR NA NA 0 NA NA
OEWM-STAGE-PEAK move warehouse tasks per PEAK TIME NA NA NA 0 0

Ware tasks RsChg % DISP MONTHS ST TIME END TIME

OEWM-RESST-AVERAGE chg/resource tasks per YEAR 0 NA 0 NA NA
OEWM-RESST-PEAK chg/resource tasks per PEAK TIME 0 NA NA 0 0

Ware tasks % DISP MONTHS ST TIME END TIME

OEWM-LOAD-AVERAGE warehouse loading tasks per YEAR NA NA 0 NA NA
OEWM-LOAD-PEAK warehouse loading tasks per PEAK TIME NA NA NA 0 0

OBJECTS ITEMS % CHG % DISP MONTHS ST TIME END TIME

OEWM-GOODS-AVERAGE Outbound delivery documents per YEAR 0 0 NA NA
OEWM-GOODS-PEAK Outbound delivery documents per PEAK TIME 0 NA 0 0
© Copyright IBM Corp. April-2008
QUICKSIZER SIZING FOR SRM

What release of SRM are you implementing 5

What time does the AVERAGE workday start 9:00
What time does the AVERAGE workday end 18:00
What time does the PEAK load start 12:00
What time does the PEAK load end 13:00

NON-PRODUCTION SYSTEMS
System Landscape (required)
A system landscape consists of the systems and clients that are needed for non-production. Once the system landscape has been
defined, you may then create an implementation strategy for the setup and maintenance of the systems and clients within this landscape.
IBM and SAP strongly recommend having at least a three-system landscape. A three-system landscape is comprised of a development
system, a quality assurance system and a production system. This configuration ensures the proper management and testing of changes to
the system before applying them to the live production environment. If nothing is specified we will assume a Dev and Test system.

Type Default Size Storage Default

First non-production system Dev 100GB's
Second non-production system QA =prod
Third non-production system, if needed None None
Fourth non-production system, if needed None None
Fifth non-production system, if needed None None

Please specify any other additional information to help in sizing

USER BASED SIZING

LOW MEDIUM HIGH
CTRCT-USER-Users in Contract Management
PLAN-USER-Users in Plan-Driven Procurement
CLASSIC-USER-Users in Self-Service Classic Procurement
EXT-USER-Users in Extended Classic Procurement
SERVC-USER-Users in Service Procurement
SOURC-USER-Users in Strategic Sourcing
TOTAL CONCURRENT Peak users 0 0 0 0

THRUPUT SIZING FOR SRM

OBJECTS ITEMS % CHG % DISP MONTHS ST TIME END TIME
SRM-CNTRCT-AVERAGE Contract management contracts per YEAR 0 0 NA NA
SRM-CNTRCT-PEAK Contract management contracts per PEAK TIME 0 NA 0 0
SRM-PLAN-AVERAGE Plan-driven customer orders per YEAR 0 0 NA NA
SRM-PLAN-PEAK Plan-driven customer orders per PEAK TIME 0 NA 0 0
CLASSIC-AVERAGE Self-service orders per YEAR 0 0 NA NA
CLASSIC-PEAK Self-service orders per PEAK TIME 0 NA 0 0
EXTENDED-AVERAGE Extended orders per YEAR 0 0 NA NA
EXTENDED-PEAK Extended orders per PEAK TIME 0 NA 0 0
SRM-SERVICE-AVERAGE Services orders per YEAR 0 0 NA NA
SRM-SERVICE-PEAK Services orders per PEAK TIME 0 NA 0 0

Bid invit. ITEMS Resp % CHG % DISP MONTHS ST TIME

SOURCING-AVERAGE strategic sourcing customer orders per YEAR 0 0 NA
SOURCING-PEAK strategic sourcing customer orders per PEAK TIME 0 NA 0
END TIME

END TIME
NA
0
© Copyright IBM Corp. April-2008
QUICKSIZER SIZING FOR GTS

What release of GTS are you implementing 2005

What time does the AVERAGE workday start 9:00
What time does the AVERAGE workday end 18:00
What time does the PEAK load start 12:00
What time does the PEAK load end 13:00

NON-PRODUCTION SYSTEMS
System Landscape (required)
A system landscape consists of the systems and clients that are needed for non-production. Once the system landscape has been
defined, you may then create an implementation strategy for the setup and maintenance of the systems and clients within this landscape.
IBM and SAP strongly recommend having at least a three-system landscape. A three-system landscape is comprised of a development
system, a quality assurance system and a production system. This configuration ensures the proper management and testing of changes to
the system before applying them to the live production environment. If nothing is specified we will assume a Dev and Test system.

Type Default Size Storage Default

First non-production system Dev 100GB's
Second non-production system QA =prod
Third non-production system, if needed None None
Fourth non-production system, if needed None None
Fifth non-production system, if needed None None

Please specify any other additional information to help in sizing

THRUPUT SIZING FOR COMPLIANCE AND CUSTOM MANAGEMENT

OBJECTS ITEMS % CHG % DISP MONTHS ST TIME END TIME

GTS-CUMA-AVERAGE Customs management contracts per YEAR 0 0 NA NA
GTS-CUMA-PEAK Customs management contracts per PEAK TIME 0 NA 0 0
GTS-SLS-AVERAGE Compliance management per YEAR 0 0 NA NA
GTS-SLS-PEAK Plan-Compliance management per PEAK TIME 0 NA 0 0
GTS-FI-PR-AVERAGE Screenings of payment proposals per YEAR 0 0 NA NA
GTS-FI-PEAK Screening of payment run per PEAK TIME 0 NA 0 0

OBJECTS MONTHS ST TIME END TIME

GTS-BP-AVERAGE Business Partners per YEAR NA NA NA 0 NA NA
GTS-BP-PEAK Business Partners per PEAK TIME NA NA NA NA 0 0
GTS-MAT-AVERAGE GTS Materials per YEAR NA NA NA 0 NA NA
GTS-MAT-PEAK GTS Materials per PEAK TIME NA NA NA NA 0 0

Bus Partner Documents MONTHS ST TIME END TIME

GTS-SCREEN-AVERAGE Business Partner screenings per YEAR 0 NA NA 0 NA NA
GTS-SCREEN-PEAK Business Partner screenings per PEAK TIME 0 NA NA NA 0 0

THRUPUT SIZING FOR GLOBAL TRADE SERVICE RISK MANAGEMENT

OBJECTS ITEMS % CHG % DISP MONTHS ST TIME END TIME

GTS-RI-BOM-AVERAGE BOM transfers per YEAR 0 0 NA NA
GTS-RI-BOM-PEAK BOM transfers per PEAK TIME 0 NA 0 0
GTS-RI-INV-AVERAGE worklist based on SD Invoices per YEAR 0 0 NA NA
GTS-RI-INV-PEAK worklist based on SD Invoices per PEAK TIME 0 NA 0 0
GTS-RI-MM-AVERAGE worklist based on MM per YEAR 0 0 NA NA
GTS-RI-MM-PEAK worklist based on MM per PEAK TIME 0 NA 0 0
GTS-RI-PRD-AVERAGE BOM Preference determination per YEAR 0 0 NA NA
GTS-RI-PRD-PEAK BOM Preference determination per PEAK TIME 0 NA 0 0
GTS-RI-SO-AVERAGE SD/SO Preference determination per YEAR 0 0 NA NA
GTS-RI-SO-PEAK SD/SO Preference determination per PEAK TIME 0 NA 0 0

Customers Prod/cust % CHG MONTHS ST TIME END TIME

GTS-RI-ISS-AVERAGE vendor declarations per YEAR 0 NA 0 NA NA
GTS-RI-ISS-PEAK vendor declarations per PEAK TIME 0 NA NA 0 0

Vendors Prod/vend MONTHS ST TIME END TIME

GTS-RI-AGG-AVERAGE vendor declarations per YEAR 0 NA NA 0 NA NA
GTS-RI-AGG-PEAK vendor declarations per PEAK TIME 0 NA NA NA 0 0
GTS-RI-SOL-AVERAGE vendor solicitations per YEAR 0 NA NA 0 NA NA
GTS-RI-SOL-PEAK vendor solicitations per PEAK TIME 0 NA NA NA 0 0
© Copyright IBM Corp. April-2008
QUICKSIZER SIZING FOR Banking

What time does the AVERAGE workday start 9:00

What time does the AVERAGE workday end 18:00
What time does the PEAK load start 12:00
What time does the PEAK load end 13:00

NON-PRODUCTION SYSTEMS
System Landscape (required)
A system landscape consists of the systems and clients that are needed for non-production. Once the system landscape has been
defined, you may then create an implementation strategy for the setup and maintenance of the systems and clients within this landscape.
IBM and SAP strongly recommend having at least a three-system landscape. A three-system landscape is comprised of a development
system, a quality assurance system and a production system. This configuration ensures the proper management and testing of changes to
the system before applying them to the live production environment. If nothing is specified we will assume a Dev and Test system.

Type Default Size Storage Default

First non-production system Dev 100GB's
Second non-production system QA =prod
Third non-production system, if needed None None
Fourth non-production system, if needed None None
Fifth non-production system, if needed None None

Please specify any other additional information to help in sizing

THRUPUT SIZING FOR ANALYTICAL BANKING

OBJECTS ST TIME END TIME

FT/FI-PEAK Financial transactions per PEAK TIME NA NA NA NA 0 0
POSITION- PEAK Changed positions per PEAK TIME NA NA NA NA 0 0
REG-REPORT-PEAK Regulatory data per PEAK TIME NA NA NA NA 0 0

OBJECTS MONTHS
POSITION-AVERAGE Changed positions per YEAR NA NA NA 0

OBJECTS Collat/Claims Lines MONTHS Eff matur Cash flow ST TIME

CE-RUN-AVERAGE payments on cash flow per YEAR 0 0 0 NA NA NA
CE-RUN-PEAK payments on cash flow per PEAK TIME NA NA 0

OBJECTS Level 2 ST TIME END TIME

DR-RUN-PEAK Disclosure/reporting documents per PEAK TIME NA NA NA 0 0

THRUPUT SIZING FOR CORE BANKING

OBJECTS MONTHS
FS-BK-PST-AVERAGE Processing payments items per YEAR NA NA NA 0
FS-BK-SETT-AVERAGE Processing payments items per YEAR NA NA NA 0
FS-BK-CORR-AVERAGE Processing payments items per YEAR NA NA NA 0
FS-BK-ACCR-AVERAGE Processing payments items per YEAR NA NA NA 0

OBJECTS ST TIME END TIME

FS-BK-MPST-PEAK Processing payments items per PEAK TIME NA NA NA NA 0 0
FS-BK-SPST-PEAK Processing payments items per PEAK TIME NA NA NA NA 0 0
FS-BK-STAT-PEAK Processing payments items per PEAK TIME NA NA NA NA 0 0
FS-BK-SETT-PEAK Processing payments items per PEAK TIME NA NA NA NA 0 0
FS-BK-CORR-PEAK Processing payments items per PEAK TIME NA NA NA NA 0 0
FS-BK-ACCR-PEAK Processing payments items per PEAK TIME NA NA NA NA 0 0

Coll agree Loans ST TIME END TIME

FS-BK-CMS-PEAK Loans per PEAK TIME NA NA NA 0 0
END TIME
 END TIME
NA
0

END TIME

END TIME

END TIME
© Copyright IBM Corp. April-2008
QUICKSIZER SIZING FOR Insurance

What time does the AVERAGE workday start 9:00

What time does the AVERAGE workday end 18:00
What time does the PEAK load start 12:00
What time does the PEAK load end 13:00

NON-PRODUCTION SYSTEMS
System Landscape (required)
A system landscape consists of the systems and clients that are needed for non-production. Once the system landscape has been
defined, you may then create an implementation strategy for the setup and maintenance of the systems and clients within this landscape.
IBM and SAP strongly recommend having at least a three-system landscape. A three-system landscape is comprised of a development
system, a quality assurance system and a production system. This configuration ensures the proper management and testing of changes to
the system before applying them to the live production environment. If nothing is specified we will assume a Dev and Test system.

Type Default Size Storage Default

First non-production system Dev 100GB's
Second non-production system QA =prod
Third non-production system, if needed None None
Fourth non-production system, if needed None None
Fifth non-production system, if needed None None

Please specify any other additional information to help in sizing

OBJECTS Items ST TIME END TIME

ACC-STAT-PEAK Invoice/Account statements per PEAK TIME 0 NA NA NA 0 0
INS-INV-PEAK Insurance objects per PEAK TIME 0 NA NA NA 0 0

OBJECTS ST TIME END TIME

BROK-ITEM-PEAK Broker report items per PEAK TIME NA NA NA NA 0 0
PAY-EXE-PEAK payment plan executions per PEAK TIME NA NA NA NA 0 0
PAY-TRANS-PEAK Payment plan transfers per PEAK TIME NA NA NA NA 0 0
ACC-BAL-PEAK Account balance displays per PEAK TIME NA NA NA NA 0 0
 OBJECTS Items MONTHS
ACC-STAT-AVERAGE Invoice/Account statements per YEAR 0 NA NA NA 0
INS-INV-AVERAGE Insurance objects per YEAR 0 NA NA NA 0

OBJECTS MONTHS
BROK-ITEM-AVERAGE Broker report items per year NA NA NA NA 0
PAY-EXE-AVERAGE payment plan executions per year NA NA NA NA 0
PAY-TRANS-AVERAGE Payment plan transfers per year NA NA NA NA 0
© Copyright IBM Corp. April-2008
QUICKSIZER SIZING FOR Utilities

What time does the AVERAGE workday start 9:00

What time does the AVERAGE workday end 18:00
What time does the PEAK load start 12:00
What time does the PEAK load end 13:00

NON-PRODUCTION SYSTEMS
System Landscape (required)
A system landscape consists of the systems and clients that are needed for non-production. Once the system landscape has been
defined, you may then create an implementation strategy for the setup and maintenance of the systems and clients within this landscape.
IBM and SAP strongly recommend having at least a three-system landscape. A three-system landscape is comprised of a development
system, a quality assurance system and a production system. This configuration ensures the proper management and testing of changes to
the system before applying them to the live production environment. If nothing is specified we will assume a Dev and Test system.

Type Default Size Storage Default

First non-production system Dev 100GB's
Second non-production system QA =prod
Third non-production system, if needed None None
Fourth non-production system, if needed None None
Fifth non-production system, if needed None None

Please specify any other additional information to help in sizing

Billcycle Budget Partial P-items C-items Lines Contracts Tax ContAcc Meters
UTIL-01-AVERAGE billing documents per YEAR 0 0 0 0 0 0 0

BusPart Overdues Deposits Cust cont MONTHS

UTIL-02-AVERAGE billing documents per YEAR 0 0 0 NA 0

BusPart Days for batch ST TIME END TIME

UTIL-BP-PEAK Batch processing per PEAK TIME 0 0 NA NA NA 0 0

OBJECTS ST TIME END TIME

OVERVIEW-AVERAGE use of "Customer Overview" transaction per YEAR NA NA NA NA NA NA
OVERVIEW-PEAK use of "Customer Overview" transaction per PEAK TIME NA NA NA NA 0 0
CONTACT-AVERAGE Customer contacts per YEAR NA NA NA NA NA NA
CONTACT-PEAK Customer contacts per PEAK TIME NA NA NA NA 0 0
MOVE IN-AVERAGE customer move-ins per YEAR NA NA NA NA NA NA
MOVE IN-PEAK customer move-ins per PEAK TIME NA NA NA NA 0 0
MOVE-OUT-AVERAGE customer move-outs per YEAR NA NA NA NA NA NA
MOVE-OUT-PEAK customer move-outs per PEAK TIME NA NA NA NA 0 0
 NO
NO
NO

MONTHS
0
© Copyright IBM Corp. April-2008
T-SHIRT SIZING FOR SOLUTION MANAGER

What release of Solution Manager are you implementing? 4

NON-PRODUCTION SYSTEMS
System Landscape (required)
A system landscape consists of the systems and clients that are needed for non-production. Once the system landscape has been
defined, you may then create an implementation strategy for the setup and maintenance of the systems and clients within this landscape.
IBM and SAP strongly recommend having at least a three-system landscape. A three-system landscape is comprised of a development
system, a quality assurance system and a production system. This configuration ensures the proper management and testing of changes to
the system before applying them to the live production environment. If nothing is specified we will assume a Dev and Test system.

Type Default Size Storage Default

First non-production system Dev 100GB's
Second non-production system QA None
Third non-production system, if needed None None
Fourth non-production system, if needed None None
Fifth non-production system, if needed None None

Please specify any other additional information to help in sizing

Enter total CONCURRENT users during the PEAK hour--A user must NOT be counted twice
He is either one type of user or another--NOT both at the same time during the PEAK hour
OPTION 1--USER BASED SIZING Click for sizing white paper
LOW MEDIUM HIGH SAPS GB-Storage
Users in Implementation and Upgrade-PEAK PER HOUR 0 0
Users in Service Desk and Change Request-PEAK PER HOUR 0 0
Users in Collaboration-PEAK PER HOUR 0 0
Diagnostics--Choose the most appropriate system 0 0
Solution Monitoring--Choose the most appropriate system 0 0
TOTAL 0 0

OPTION 2--T-SHIRT SIZING System SAPS GB-Storage

All except diagnostics--Choose the most appropriate system 0 0
Diagnostics--Choose the most appropriate system 0 0.0
TOTAL 0 0.0

T-SHIRT SIZING FOR SYSTEM LANDSCAPE DIRECTORY

What release of SLD are you implementing? 7

NON-PRODUCTION SYSTEMS
System Landscape (required)
A system landscape consists of the systems and clients that are needed for non-production. Once the system landscape has been
defined, you may then create an implementation strategy for the setup and maintenance of the systems and clients within this landscape.
IBM and SAP strongly recommend having at least a three-system landscape. A three-system landscape is comprised of a development
system, a quality assurance system and a production system. This configuration ensures the proper management and testing of changes to
the system before applying them to the live production environment. If nothing is specified we will assume a Dev and Test system.

Type Default Size Storage Default

First non-production system Dev 100GB's
Second non-production system QA None
Third non-production system, if needed None None
Fourth non-production system, if needed None None
Fifth non-production system, if needed None None

Please specify any other additional information to help in sizing

T-SHIRT SIZING for SLD Click for sizing white paper-page 39
ABAP JAVA SAPS
PEAK-Number of systems connected during the PEAK hour NA 0
© Copyright IBM Corp. April-2008
T-SHIRT SIZING FOR PLM

NON-PRODUCTION SYSTEMS
System Landscape (required)
A system landscape consists of the systems and clients that are needed for non-production. Once the system landscape has been
defined, you may then create an implementation strategy for the setup and maintenance of the systems and clients within this landscape.
IBM and SAP strongly recommend having at least a three-system landscape. A three-system landscape is comprised of a development
system, a quality assurance system and a production system. This configuration ensures the proper management and testing of changes to
the system before applying them to the live production environment. If nothing is specified we will assume a Dev and Test system.

Type Default Size Storage Default

First non-production system Dev 100GB's
Second non-production system QA None
Third non-production system, if needed None None
Fourth non-production system, if needed None None
Fifth non-production system, if needed None None

Please specify any other additional information to help in sizing

Enter total CONCURRENT users during the PEAK hour--A user must NOT be counted twice
He is either one type of user or another--NOT both at the same time during the PEAK hour

cPROJECTS SIZING Click for sizing white paper

Objects Projects Results

CPU sizing based on number of objects and number of projects 0 SAPS
Disk sizing based on number of objects and number of projects 0 GB's

cFOLDERS SIZING
 # msgs msg size SAPS
CPU sizing for the download scenario 0
CPU sizing for the upload and copying scenario 0

# docs doc size GB's

Disk sizing based on number of documents and size of document 0

cRECORDS SIZING Click for sizing white paper

User Based Sizing
LOW MEDIUM HIGH SAPS
Users in Records and Case Management-PEAK PER HOUR 0

Thruput Based Sizing

CASES ST TIME END TIME SAPS
PEAK Cases created by a user per PEAK TIME NA NA NA NA 12 13 0

Elements ST TIME END TIME SAPS

TOTAL elements added to cases by a user per PEAK TIME NA NA NA NA 12 13 0

CASES ST TIME END TIME SAPS

PEAK Cases created by an interface per PEAK TIME NA NA NA NA 12 13 0

Elements ST TIME END TIME SAPS

TOTAL elements added to cases by an interface per PEAK TIME NA NA NA NA 12 13 0

# cases # elements GB's

Disk sizing based on cases and records 0

CONTENT SERVER SIZING Click for sizing white paper

User Based Sizing
Users SAPS GB's
PEAK PARALLEL Users accessing the Content database 0 0
© Copyright IBM Corp. April-2008
T-SHIRT SIZING FOR MDM-5.5

NON-PRODUCTION SYSTEMS
System Landscape (required)
A system landscape consists of the systems and clients that are needed for non-production. Once the system landscape has been
defined, you may then create an implementation strategy for the setup and maintenance of the systems and clients within this landscape.
IBM and SAP strongly recommend having at least a three-system landscape. A three-system landscape is comprised of a development
system, a quality assurance system and a production system. This configuration ensures the proper management and testing of changes to
the system before applying them to the live production environment. If nothing is specified we will assume a Dev and Test system.

Type Default Size Storage Default

First non-production system Dev 100GB's
Second non-production system QA None
Third non-production system, if needed None None
Fourth non-production system, if needed None None
Fifth non-production system, if needed None None

Please specify any other additional information to help in sizing

Enter total CONCURRENT users during the PEAK hour--A user must NOT be counted twice
He is either one type of user or another--NOT both at the same time during the PEAK hour

NetWeaver MDM Server-APP Server Click for sizing white paper

BP Materials Results
CPU sizing--number of records in the primary table NA 0 SAPS
Memory sizing 0.00 GB's
Accelerator size on disk 0.00 GB's

NetWeaver MDM Server-DBMS Server

 Users Results
CPU sizing--number of concurrent users NA NA 0 SAPS
Disk sizing--number of records in the primary table NA NA NA 0.00 GB's
Disk sizing--based on estimate of total storage NA NA 0.00 GB's

Results
Import, Syndication,Layout Server-Optional None 0 SAPS
© Copyright IBM Corp. April-2008
T-SHIRT SIZING FOR Miscellaneous Applications

NON-PRODUCTION SYSTEMS
System Landscape (required)
A system landscape consists of the systems and clients that are needed for non-production. Once the system landscape has been
defined, you may then create an implementation strategy for the setup and maintenance of the systems and clients within this landscape.
IBM and SAP strongly recommend having at least a three-system landscape. A three-system landscape is comprised of a development
system, a quality assurance system and a production system. This configuration ensures the proper management and testing of changes to
the system before applying them to the live production environment. If nothing is specified we will assume a Dev and Test system.

Type Default Size Storage Default

First non-production system Dev 100GB's
Second non-production system QA None
Third non-production system, if needed None None
Fourth non-production system, if needed None None
Fifth non-production system, if needed None None

Please specify any other additional information to help in sizing

Enter total CONCURRENT users during the PEAK hour--A user must NOT be counted twice
He is either one type of user or another--NOT both at the same time during the PEAK hour

Business Planning & Consolidation(BPC 7.0) Netweaver Server .NET Server

Users Requirements SAPS GB Memory cores GB Memory
Server sizing--number of PEAK users

OutlookSoft sizing Guidance Click for vendor information

Users Results
Server sizing--number of PEAK users

Enterprise Search Appliance sizing Guidance

# Files # Bus Obj Users SAPS # Blades GB's Mem
Server sizing--number of PEAK users 0 0 0

Adobe Document Services sizing Guidance Click for sizing white paper
Small Medium Large SAPS
ADS Server--# documents per hour 0
ADS Server--# documents per hour(batching) 0
SM Simple SM Complex Medium Large SAPS
ADS Server--# documents per hour(interactive) 0
ADS Server--Will ADS PDF cache be enabled? No
ADS Server--Will changes or printing be permitted? No
ADS Server--Will all form signatures be extracted? No
ADS Server--Will the form data be extracted after 2nd signature? No

Learning Solutions sizing Guidance

Users Activity Level Course Size SAPS
User based sizing guidance for Learning Solutions 0

e-Recruiting sizing Guidance Click for sizing white paper

Will you be using a distributed landscape? yes

How much data per application do you expect to store? 1.5 MB
How long will the data for each application stay resident? 24 Months
Number of work days per year? 240 Days
Number of work hours per day? 8 Hours
LOW MEDIUM HIGH
Number of recruiters-AVERAGE PER HOUR
Number of recruiters-PEAK PER HOUR
Average/yr Peak/hr Steps/proc
How many applications do you expect?
How many registrations do you expect?
How many searches do you expect?
SAPS Memory Disk-GB's
Results for Server A 2000 8 150
Results for Server B 2000 8 150

GRC-VIRSA sizing Guidance--Initial t-shirt sizing Click for sizing white paper
System SAPS GB-Storage
Compliance Calibrator(Risk analysis and remediation) NA NA 0 0
Access Enforcer(Compliant user provisioning) NA NA 0 0
Role Expert(Enterprise role management) NA NA 0 0
TOTAL 0 0

GRC-VIRSA sizing Guidance--Expert sizing Click for sizing white paper

Users Roles SOD Report SAPS GB-Storage
Compliance Calibrator(Risk analysis and remediation) NA 0
Initial Load Sizing per hour 0 NA
Daily Transactional Sizing per hour 0 NA
Daily Batch Sizing per hour 0 NA

Access Enforcer(Compliant user provisioning) NA 0

Initial Load Sizing per hour 0 NA
Daily Transactional Sizing per hour 0 NA

Role Expert(Enterprise role management) NA 0

Daily Transactional Sizing per hour 0 NA
Daily Batch Sizing per hour 0 NA
Total 0 NA

EH&S-Environment, Health and Safety--Initial t-shirt sizing Click for sizing white paper
System SAPS GB-Storage
Product Safety(PS) and dangerous goods(DG) sizing NA NA 0 0
LOW MEDIUM HIGH
Number of users--All other sub modules--PEAK PER HOUR 0

xEM-Emissions Management--sizing guidance

USERS SAPS GB-Storage
Compliance Management--Users-PEAK PER HOUR NA NA 0 0
Calculations
Emissions Management--Calculations per year--Average per year NA NA NA 0
Emissions Management--Calculations per hour--PEAK PER HOUR NA NA 0 NA

xRPM-Resource & Portfolio Mgmt--sizing guidance

DISPLAYS Items per EP SAPS RPM SAPS
User Displays-PEAK PER HOUR-JAVA based dashboard 0 0
User Displays-PEAK PER HOUR-ABAP based dashboard 0 0

ARIS BPM--Server sizing guidance Click for vendor information

Business Server DBMS Server
USERS SAPS GB-Memory SAPS GB-Memory
Concurrent users on the server--PEAK PER HOUR 0 0 0 0

SAP MOBILITY--three alternatives

SAP MOBILITY--CRM LOGONS SAPS GB-Storage

Users that will be synchronizing laptops-PEAK PER HOUR 0 0

SAP MOBILITY--Mobile Business

Web Application Server ECC Server
Syncs J2EE ABAP DB ABAP
Mobile Asset Management(MAM) Standard and Utilities 0 0 0 0
Mobile Asset Management for Utilities(MAU) 0 0 NA 0
Syncs CRM SAPS
Mobile Sales for Handheld with CRM 5.x 0
Web Application Server ECC Server
Visits To Handheld To Backend DB ABAP
Mobile Direct Store Delivery 0 0 NA 0
Web Application Server ECC Server
Syncs J2EE ABAP DB ABAP
Mobile Sales for Handheld with R/3 and ECC 0 0 NA 0
Mobile Time Sheet-single mode scenario-sync weekly NA 0 NA 0
Mobile Time Sheet-administration scenario-sync daily NA 0 NA 0
Mobile Travel Expenses-Daily Trip Scenario NA 0 NA 0
Mobile Travel Expenses-Weekly Trip Scenario NA 0 NA 0
Smart Sync Data Model NA 0 0 NA

SAP MOBILITY--NetWeaver Mobility

Web Application Server ECC Server
Profile J2EE ABAP DB ABAP
Back-end triggered delta load NA 0 NA NA

Web Application Server ECC Server

Syncs J2EE ABAP DB ABAP
Client Synchronizations NA 0 NA NA

Web Application Server ECC Server

Messages J2EE ABAP DB ABAP
Processing uploaded messages in an 8-hour window NA 0 NA NA

SAP NFe-electronic invoicing-Biller Direct Click for sizing white paper

 BC's J2EE AS DB
Using FI-AR(accounts receivable) as the backend 0 0 0
Using FI-CA(contract accounts) as the backend 0 0 0

NRX-Add-on to EP Click for vendor information

USERS Think time Java iViews URL iViews % KMC
NW-EP-PRT-PEAK 180 4 0 30

Duet
Users Duet Server Duet Memory
Time Management-Users on Duet Server--PEAK PER HOUR 0 0.0
Team Management-Users on Duet Server--PEAK PER HOUR 0 0.0
Reporting-Users on Duet Server--PEAK PER HOUR 0 0.0
Sales Management-Users on Duet Server--PEAK PER HOUR 0 0.0
Sales Management-Users on Duet Server--PEAK PER HOUR 0 0.0

T-SHIRT SIZING GUIDANCE FOR KNOWLEDGE MANAGEMENT AND COLLABORATION Click for sizing white paper
PORTAL DB Portal
Users SAPS SAPS Memory
KM-PEAK Concurrent users per PEAK TIME NA NA NA 0 0 0

NWDI or JDI Click for sizing SAP NOTE 737368

Developers SAPS GB-Memory
Scenario 1-Development in a team 0 0
Scenario 2-Development with components 0 0
Scenario 2+-Development with a Track 0 0
Scenario 3-Layered development 0 0

Web Dispatcher Click for sizing white paper

Messages SAPS
Scenario 1-Incoming=HTTP,Outgoing=HTTP 0
Scenario 2-Incoming=HTTPS,Outgoing=HTTPS-SSL passthrough 0
Scenario 3-Incoming=HTTPS,Outgoing=HTTPS-SSL termination 0
Scenario 4-Incoming=HTTPS,Outgoing=HTTPS-SSL re-encryption 0
TOTAL 0

Auto-ID Infrastructure-RFID Click for sizing white paper

Slap & Ship Scenario Print Req Tags Time SAPS Storage
Tag Commissioning 0 0.00
Pallets Cases Time
Packing 0 0.00
Pallets Cases Time
Loading 0 0.00

RFID-Enabled Returnable Transport Item-RTI Scenario Print Req Tags Time SAPS Storage
Tag Commissioning in All 0 0.00
Pallets Cases Time
Packing/Unpacking in All 0 0.00
Pallets Cases Time
Loading/Unloading in All 0 0.00

RFID-Enabled Returnable Transport Item-RTI Scenario Print Req Tags Time SAPS Storage
Tag Commissioning in SCM 0 0.00
Pallets Cases Time
Packing/Unpacking in SCM 0 0.00
Pallets Cases Time
Loading/Unloading in SCM 0 0.00

RFID-Integrated Delivery Processing Scenario Print Req Tags Time SAPS Storage
Tag Commissioning in All 0 0.00
Deliveries Items EPC Time Pieces Pallets
Packing/Unpacking in All 0 0.00
Deliveries Items EPC Time Pieces Pallets
Loading/Unloading in All with hierarchy 0 0.00
Deliveries Items EPC Time Pieces
Loading/Unloading in All without hierarchy 0 0.00
© Copyright IBM Corp. April-2008
INFORMATION ON DOING AN UPGRADE SIZING
Default
To what release of SAP are you upgrading? ECC 6.0
Will you be adding Unicode? Default is yes. yes
How many additional users will you be adding or specify growth factor(%) 0
What is your preferred hardware platform?

Upgrade Sizing information for System i

Upgrade Sizing information for System p

What AIX level are you running now? 5.2?, 5.3? Other? 5.3
If not 5.3, do you plan to upgrade to 5.3 with SMT? yes
If 5.3, are you running the SAP workload in a shared pool? no

Upgrade Sizing information for System x

Are you running the SAP workload in a VMware environment? no
Is hyperthreading enabled on your current SAP system? no

Upgrade Sizing information for System z

© Copyright IBM Corp. April-2008

INPUTS USER BASED THRUPUT BASED

Changed # of users SAPS Storage Changed ?
ERP NO 0 0 0 NO
CRM NO 0 0 0 NO
BI/SEM NO 0 NA NA NO
Portal NO 0 NA NA NO
PI NA NA NA NA NO
TREX NA 0 0 0 NO
SCM APO NA NA NA NA NO
SRM NO 0 NA NA NO
GTS NA NA NA NA NO
Banking NA NA NA NA NO
Insurance NA NA NA NA NO
Utilities NA NA NA NA NO
SM SLD NA 0 0 0 NO
PLM NA 0 0 0 NO
MDM NA 0 0 0 NO
MISC NA 0 0 0 NO
Upgrade NA NA NA NA NO
Totals 0 0 0