SAP Questionnaire 061510

Download as xls, pdf, or txt
Download as xls, pdf, or txt
You are on page 1of 55

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 North and South America IBM Contact IBM Americas Techline Solutions Sizing by E-mail / Fax [email protected] / +1 845-491-2372

IBMers raise a Techline Request through http://w3.ibm.com/support/emea/techline

Europe, Middle East, and Africa

BPs raise a Techline Request through http://www.ibm.com/partnerworld/techline For both : in case of attachment problems, send file [email protected] to

Asia, Pacific Others

IBM ASEAN/SA Techline(Singapore, Malaysia, Thailand, Philippines, Indonesia, Vietnam, India and Sri Lanka) GCG(China) Hong Kong Taiwan South Korea Japan Australia and New Zealand IBM SAP International Competence Center, ISICC, Walldorf

[email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected]

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 customers 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 customers 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 NumberREQUIRED QuickSizer customer number QuickSizer project name Company Name Street Address City, State/Province Zip/Postal Code, Country Customer Contact Title Phone Number e-mail address IBM Contact Phone Number e-mail address SAP Contact Phone Number e-mail address

Business Partner or SAP Value Added Reseller 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 Server System z System p System x System i Comments:

Application Server(s) System z System p System x System i System p System x System x System x

Preferred Disk Technology Sizing


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

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

Scalability Sizing
Scalability Questions How important is scalability in your hardware configuration? Answer Options 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 Is high availability technology, such as clustering or HACMP, on the database server required? If yes, where will failover be? App Server? Test Server? Idle Server? Other? Answer Options Default-no Default-App

Backup/Restore Sizing
Backup/Restore Question Do you want a backup device included in the proposed configuration? Answer Options 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 How many working days are in your business year? Answer Options 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 Questionnaire Answer Options

Copyright IBM Corp. April-2008

QUICKSIZER SIZING FOR ERP


What release of ERP are you implementing What time does the AVERAGE workday start What time does the AVERAGE workday end What time does the PEAK load start What time does the PEAK load end 6.0 9:00 18:00 12:00 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 First non-production system Second non-production system Third non-production system, if needed Fourth non-production system, if needed Fifth non-production system, if needed Please specify any other additional information to help in sizing Default Dev QA None None None Size Storage Default 100GB's =prod None None None

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

USER BASED SIZING


LOW MEDIUM HIGH Typically, high users are fewer than 20% of the total for any module. If in doubt put the concurrently active users in the medium category. 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 Approximate SAPS Approximate Storage If AFS is implemented add this uplift

0 0 Qser 0

users SAPS GB's SAPS

0 init SAPS Click for sizing white paper 0

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

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

NA

NA

ST TIME END TIME 0 0 ST TIME END TIME 0 0 0 0 0 0 0 0 ST TIME END TIME 0 0

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

NA NA NA NA

NA NA NA NA

NA NA NA NA

NA

NA

PAY-RUN-PEAK Payment Run CD-PL-PEAK Payment Lots CORR-PRINT-PEAK Correspondence Print DEF-POST-PEAK Deferred Postings EDRs EDR-UPL-AVERAGE Event Detail Record Upload OBJECTS PAY-RUN-AVERAGE Payment Run CD-PL-AVERAGE Payment Lots CORR-PRINT-AVERAGE Correspondent Print DEF-POST-AVERAGE Deferred Postings

NA NA NA NA AddFld

NA NA NA NA

NA NA NA NA

NA NA NA NA

0 0 0 0

0 0 0 0

NA

NA

MONTHS ST TIME END TIME 0 NA NA MONTHS ST TIME END TIME 0 NA NA 0 NA NA 0 NA NA 0 NA NA MONTHS ST TIME END TIME 0 NA NA 0 NA NA 0 NA NA 0 NA NA P itm 0 % credit MONTHS ST TIME END TIME 0 NA NA

NA NA NA NA OBJECTS ITEMS 0 0 0 0 Postings BP itm 0

NA NA NA NA

NA NA NA NA

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

NA NA NA NA GL itm 0

NA NA NA NA Payments 0

SUBLEDGER-AVERAGE Subledger Documents

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

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

MONTHS ST TIME END TIME 0 NA NA NA 0 0 0 NA NA NA 0 0

THRUPUT SIZING FOR E-Recruitment--If you complete this section, you must resolve all "ERROR" messages.
ERC-CA-REG-AVERAGE Candidate Registrations per YEAR ERC-CA-REG-PEAK Candidate Registrations per PEAK TIME OBJECTS ITEMS 0 0 % CHG % DISP DCS no no Attach NA Size NA MONTHS ST TIME END TIME 0 NA NA NA 0 0

ERC-APPL-PEAK Candidate Applications per PEAK TIME

OBJECTS ITEMS 0 OBJECTS ITEMS 0 OBJECTS

% CHG

% DISP

DCS no

ST TIME END TIME 0 0

% CHG

% DISP

ERC-REQ-PEAK Requisition creation per PEAK TIME

ST TIME END TIME 0 0 DCS no ST TIME END TIME 0 0

% CHG NA

% DISP

ERC-JOB-SE-PEAK Candidate Applications per PEAK TIME OBJECTS ERC-CA-LST-PEAK Requisition creation per PEAK TIME

% CHG NA

% DISP

ST TIME END TIME 0 0

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

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

NETW

REORD Non-REORHORIZON % CHG 0

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

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

NA NA

NA NA

NA NA

NA NA

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

ITEMS COM CON 0 0

NA NA

NA NA

NA NA

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

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

Copyright IBM Corp. April-2008

QUICKSIZER SIZING FOR CRM


What release of CRM are you implementing What time does the AVERAGE workday start What time does the AVERAGE workday end What time does the PEAK load start What time does the PEAK load end 2007 9:00 18:00 12:00 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 First non-production system Second non-production system Third non-production system, if needed Fourth non-production system, if needed Fifth non-production system, if needed Please specify any other additional information to help in sizing Default Dev QA None None None Size Storage Default 100GB's =prod None None None

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 ACC-USER-CRM Account Management-PEAK PER HOUR MEDIUM HIGH ext SAPS GB-Storage 0 Use Qser

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

USER-BASED SIZING FOR CRM SALES


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

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

% CHG

USER-BASED SIZING FOR CRM SERVICE


LOW MEDIUM HIGH ext SAPS GB-Storage

Users doing CRM Service Transactions-PEAK PER HOUR

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

% CHG

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

USER-BASED SIZING FOR CRM INTERACTION CENTER


LOW Total users in the Call Center(CIC)-PEAK PER HOUR MEDIUM HIGH ext SAPS GB-Storage 0 0

THRUPUT SIZING FOR CRM IC--If you complete this section, you must resolve all "ERROR" messages.
OBJECTS AVERAGE calls/emails in customer center per YEAR PEAK calls/emails in customer center per PEAK TIME NA NA % CHG % DISP MONTHS ST TIME END TIME 0 NA NA NA 0 0

USER-BASED SIZING FOR CRM MOBILE


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

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

Campaign Execution sizing Guidance


Profile for Campaign number one Profile for Campaign number two Profile for Campaign number three Profile for Campaign number four Profile for Campaign number five

Click for sizing white paper Bus Part Activities Int Objects e-mails

to BW

ST TIME END TIME ext SAPS 0 0 0 0 0

TPM-Trade Promotions Management


Promotions Products Periods Keyfigures Plng Cells Partners PR_REB Rec CDET Rec

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

ABAP SAPS DB SAPS GB's-Memory

0 0 0 0 0 0

0 0 0 0 0 0

SEM/BI
Rendering the planning layout Re-synchronizing with SAP NW BW(Saving the promotion) Total for SEM/BI

ABAP SAPS DB SAPS GB's-Memory GB Storage

0 0 0

0 0 0

Copyright IBM Corp. April-2008

QUICKSIZER SIZING FOR NetWeaver BW & SEM


What release of BI/SEM are you implementing What time does the AVERAGE workday start What time does the AVERAGE workday end What time does the PEAK load start What time does the PEAK load end 7 9:00 18:00 12:00 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 First non-production system Second non-production system Third non-production system, if needed Fourth non-production system, if needed Fifth non-production system, if needed Please specify any other additional information to help in sizing Default Dev QA None None None Size Storage Default 100GB's =prod None None None

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


Business Planning and Simulations Group 1-PEAK Business Planning and Simulations Group 2-PEAK Business Planning and Simulations Group 3-PEAK SEM Users STEPS 6 12 30 0 ChngRec Data/Step Data/User ST TIME END TIME 30000 60000 200000 12:00 13:00 15000 30000 100000 12:00 13:00 5000 10000 25000 12:00 13:00

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


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

ST TIME END TIME 0 0

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

DATASTORE OBJECTS
NUMFLD DS OBJECTS-DISK-Duplicate as needed TXTFLD Character WO no INITIAL PERIODIC PERIODS 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 First non-production system Second non-production system Third non-production system, if needed Fourth non-production system, if needed Fifth non-production system, if needed Please specify any other additional information to help in sizing Default Dev QA None None None Size Storage Default 100GB's =prod None None None

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
NW-EP-URL-PEAK NW-EP-INT-PEAK NW-EP-PCC-PEAK NW-EP-PRT-PEAK Total Users USERS Think time Java iViews 600 0 211 3 180 3 0 0 0 URL iViews 1 0 0 0

LOGONS Maximum number of logons per PEAK hour

NetWeaver Portal Knowledge Management and Collaboration


NW-KMC-Documents per TIME Period NW-KMC-PEAK Documents per PEAK TIME Acc Docs New Docs 0 0 Size 700 NA Rooms 4000 NA MONTHS ST TIME END TIME 0 NA NA NA 0 0

Co p yr ig h t IB M Co r p . Ap r il-2008

QUICKSIZER SIZING FOR PROCESS INTEGRATION


What release of PI are you implementing What time does the PEAK load start What time does the PEAK load end 7 12:00 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 First non-production system Second non-production system Third non-production system, if needed Fourth non-production system, if needed Fifth non-production system, if needed Please specify any other additional information to help in sizing Default Dev QA None None None Size Storage Default 100GB's =prod None None None

PI ADVANCED SIZING FOR INTEGRATION SERVER


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

PI NON-CENTRAL ADAPTER ENGINE


PI-ADAPTER-PEAK per PEAK TIME XML SIZE KB Messages Sync/Async Inbd adap Outb adap 0 Asynchronous None None Int.S. no ST TIME END TIME 0 0

Copyright IBM Corp. April-2008

QUICKSIZER SIZING FOR TREX


What release of TREX are you implementing What time does the PEAK load start What time does the PEAK load end 7 12:00 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 First non-production system Second non-production system Third non-production system, if needed Fourth non-production system, if needed Fifth non-production system, if needed Please specify any other additional information to help in sizing Default Dev QA None None None Size Storage Default 100GB's =prod None None None

THRUPUT SIZING FOR TREX


Searches Indexed data Delta Index TREX-SRCH-PEAK TREX Searches per PEAK TIME NA NA NA NA ST TIME END TIME 0 0

Copyright IBM Corp. April-2008

QUICKSIZER SIZING FOR Solution Manager


What release of Solution Manager are you implementing What time does the AVERAGE workday start What time does the AVERAGE workday end 7 12:00 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 First non-production system Second non-production system Third non-production system, if needed Fourth non-production system, if needed Fifth non-production system, if needed Please specify any other additional information to help in sizing Default Dev QA None None None Size Storage Default 100GB's =prod None None None

USER SIZING FOR Solution Manager


LOW MEDIUM HIGH Typically, high users are fewer than 20% of the total for any module. If in doubt put the concurrently active users in the medium category. SOLMAN-IMP-Users in SM Implementation-PEAK PER HOUR

Copyright IBM Corp. April-2008

QUICKSIZER SIZING FOR SCM What release of SCM are you implementing What time does the AVERAGE workday start What time does the AVERAGE workday end What time does the PEAK load start What time does the PEAK load end 5 9:00 18:00 12:00 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 First non-production system Second non-production system Third non-production system, if needed Fourth non-production system, if needed Fifth non-production system, if needed Please specify any other additional information to help in sizing Default Dev QA None None None Size Storage Default 100GB's =prod None None None

QuickSizer customer number QuickSizer project name THRUPUT SIZING FOR DEMAND PLANNING CharCom TIMESERIES-Planning Area Sizing for LiveCache memory CharCom DP-RUN-Planning Run Sizing for CPU NA NA NA KeyFig 0 Periods 0 Com Index Times 0 Time Buck Pl Vers 0

Time Buck ST TIME END TIME 0 0 0

APO Users DP-USER-Additional Users for CPU 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 PLANNEDORD-Planned orders Sizing for LiveCache memory SCM OBJ FORECAST-Forecast orders Sizing for LiveCache memory PURCHORD-Purchase orders Sizing for LiveCache memory SALES-Sales orders Sizing for LiveCache memory TRANSFER-Transfer orders Sizing for LiveCache memory SKUs SNP-RUN-Heuristic plan Sizing for CPU--PEAK APO User PP USER-Planning Board User Sizing for CPU--PEAK SNP USER-SNP User Sizing for CPU--PEAK THRUPUT SIZING FOR ORDER FULFILLMENT Loc prod ATP-MD-ATP Masterdata Sizing for LiveCache memory Requests ATP-SIMPLE-ATP simple checks Sizing for CPU--PEAK ATP-RULE-ATP rules based checks Sizing for CPU--PEAK ATP-CTP-ATP Capable to promise checks Sizing for CPU--PEAK THRUPUT SIZING FOR SERVICE PARTS PLANNING SKUs SPP-STK-Stocking--PEAK SPP-DESTK-Destocking--PEAK SPP-EOQ-Economic order quantity--PEAK NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA Components 0 SUB OBJ 0 0 0 0 OPER 0 NA NA NA NA

ST TIME END TIME 0 0

ACT/OP ALT/RES ParCap 0

Time Buck ST TIME END TIME 0 0 0 ST TIME END TIME 0 0 0 0

ST TIME END TIME 0 0 0 0 0 0

ST TIME END TIME 0 0 0 0 0 0

SPP-DPLY-Deployment--PEAK Period Based Planning SPP-FCST-Forecasting--PEAK DRP Run SPP-DRP-Distribution requirements planning--PEAK SNC-Purchase Order Collaboration Profile Initial Sizing--See whitepaper on the QuickSizer website SNC-Release Processing Profile Initial Sizing--See whitepaper on the QuickSizer website SNC-Supplier Managed Inventory-SNI Profile Initial Sizing--See whitepaper on the QuickSizer website SKUs

NA

NA

NA

NA

NA Matrices ROP Stk

NA PB Stk. M

NA Loc

Time Buck ST TIME END TIME 0 0 0 PoD 1 PoD 2 Hor1

SAPS 0

Storage 0

SAPS 0

Storage 0

SAPS 0

Storage 0

THRUPUT SIZING FOR INTEGRATION TO ECC SCM objects PI-PROD-PEAK Manufacturing Orders per PEAK TIME PI-SALES-PEAK Sales Orders per PEAK TIME PI-PURCH-PEAK Purchase Orders per PEAK TIME PI-STOCKL-PEAK Stock movements per PEAK TIME THRUPUT SIZING FOR EWM INBOUND OBJECTS IEWM-DLV-AVERAGE Inbound delivery documents per YEAR IEWM-DLV-PEAK Inbound delivery documents per PEAK TIME Ware tasks IEWM-UNTSK-AVERAGE creation of unloading tasks per YEAR IEWM-UNTSK-PEAK creation of unloading tasks per PEAK TIME IEWM-CONF-AVERAGE confirm of unloading tasks per YEAR IEWM-CONF-PEAK confirm of unloading tasks per PEAK TIME Ware tasks NA NA NA NA NA NA NA NA % DISP ITEMS 0 0 % CHG % DISP MONTHS ST TIME END TIME 0 NA NA NA 0 0 MONTHS ST TIME END TIME 0 NA NA NA 0 0 0 NA NA NA 0 0 MONTHS ST TIME END TIME Items 0 0 0 1 NA NA NA NA NA NA NA NA NA NA NA NA ST TIME END TIME 0 0 0 0 0 0 0 0

% DISP

IEWM-PATSK-AVERAGE creation of putaway tasks per YEAR IEWM-PATSK-PEAK creation of putaway tasks per PEAK TIME Ware tasks IEWM-PACON-AVERAGE confirm of putaway tasks per YEAR IEWM-PACON-PEAK confirm of putaway tasks per PEAK TIME Ware tasks IEWM-RESPA-AVERAGE chg/resource of putaway tasks per YEAR IEWM-RESPA-PEAK chg/resource of putaway tasks per PEAK TIME HU's IEWM-DECON-AVERAGE unpacking of putaway tasks per YEAR IEWM-DECON-PEAK unpacking of putaway tasks per PEAK TIME Ware tasks IEWM-MOVE-AVERAGE move warehouse tasks per YEAR IEWM-MOVE-PEAK move warehouse tasks per PEAK TIME Ware tasks IEWM-RESFI-AVERAGE chg/resource of packing tasks per YEAR IEWM-RESFI-PEAK chg/resource of packing tasks per PEAK TIME THRUPUT SIZING FOR EWM OUTBOUND OBJECTS OEWM-DLV-AVERAGE Outbound delivery documents per YEAR OEWM-DLV-PEAK Outbound delivery documents per PEAK TIME Ware tasks OEWM-PICK-AVERAGE creation of picking tasks per YEAR OEWM-PICK-PEAK creation of picking tasks per PEAK TIME Ware tasks OEWM-CONF-AVERAGE confirmation of picking tasks per YEAR OEWM-CONF-PEAK confirmation of picking tasks per PEAK TIME Ware tasks OEWM-DEST-AVERAGE move warehouse tasks per YEAR OEWM-DEST-PEAK move warehouse tasks per PEAK TIME

NA NA % RF

NA NA % DISP NA NA

0 NA

NA 0

NA 0

MONTHS ST TIME END TIME 0 NA NA NA 0 0 MONTHS ST TIME END TIME 0 NA NA NA 0 0 ST TIME END TIME NA NA 0 0

RsChg NA NA Put. It. 0 0 Unpk Items

% DISP

% DISP NA NA % DISP

NA NA RsChg 0 0

NA NA % DISP NA NA

MONTHS ST TIME END TIME 0 NA NA NA 0 0 MONTHS ST TIME END TIME 0 NA NA NA 0 0

ITEMS 0 0

% CHG

% DISP

MONTHS ST TIME END TIME 0 NA NA NA 0 0 MONTHS ST TIME END TIME 0 NA NA NA 0 0 MONTHS ST TIME END TIME 0 NA NA NA 0 0 MONTHS ST TIME END TIME 0 NA NA NA 0 0

% DISP NA NA % RF NA NA % DISP NA NA NA NA NA NA % DISP

Ware tasks OEWM-RESPI-AVERAGE chg/resource of picking tasks per YEAR OEWM-RESPI-PEAK chg/resource of picking tasks per PEAK TIME HU's OEWM-PACK-AVERAGE packing tasks per YEAR OEWM-PACK-PEAK packing tasks per PEAK TIME Ware tasks OEWM-STAGE-AVERAGE move warehouse tasks per YEAR OEWM-STAGE-PEAK move warehouse tasks per PEAK TIME Ware tasks OEWM-RESST-AVERAGE chg/resource tasks per YEAR OEWM-RESST-PEAK chg/resource tasks per PEAK TIME Ware tasks OEWM-LOAD-AVERAGE warehouse loading tasks per YEAR OEWM-LOAD-PEAK warehouse loading tasks per PEAK TIME OBJECTS OEWM-GOODS-AVERAGE Outbound delivery documents per YEAR OEWM-GOODS-PEAK Outbound delivery documents per PEAK TIME

RsChg 0 0 Pick It. 0 0

% DISP NA NA % DISP NA NA % DISP

MONTHS ST TIME END TIME 0 NA NA NA 0 0 ST TIME END TIME NA NA 0 0

NA NA

NA NA RsChg 0 0

NA NA % DISP NA NA % DISP

MONTHS ST TIME END TIME 0 NA NA NA 0 0 MONTHS ST TIME END TIME 0 NA NA NA 0 0 MONTHS ST TIME END TIME 0 NA NA NA 0 0 MONTHS ST TIME END TIME 0 NA NA NA 0 0

NA NA ITEMS 0 0

NA NA % CHG % DISP

Copyright IBM Corp. April-2008

QUICKSIZER SIZING FOR SRM


What release of SRM are you implementing What time does the AVERAGE workday start What time does the AVERAGE workday end What time does the PEAK load start What time does the PEAK load end 7 9:00 18:00 12:00 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 First non-production system Second non-production system Third non-production system, if needed Fourth non-production system, if needed Fifth non-production system, if needed Please specify any other additional information to help in sizing Default Dev QA None None None Size Storage Default 100GB's =prod None None None

Operational Purchasing
Active Users - Standard Sizing LOW SRM-PO-1U-Users in SRM(PO with few complex steps) SRM-PO-2U-Users in SRM(PO with many simple steps) SRM-OSC-U-Users in SRM Occasional Shopping Cart SRM-PSC-1U-Users in SRM shopping cart(few complex steps) SRM-PSC-2U-Users in SRM shopping cart(many simple steps) SRM-CONF-U-Users in SRM Confirmation MEDIUM HIGH

SRM-INV-U-Users in SRM Invoice TOTAL CONCURRENT Peak users THRUPUT - Standard Sizing

OBJECTS SRM-PO-1-SRM Purchase Order with few complex steps SRM-PO-1-SRM Purchase Order with few complex steps SRM-PO-2-SRM Purchase Order with many simple steps SRM-PO-2-SRM Purchase Order with many simple steps SRM-OSC-SRM Occasional Shopping Cart SRM-OSC-SRM Occasional Shopping Cart SRM-PSC-1-SRM Shopping Cart with few complex steps SRM-PSC-1-SRM Shopping Cart with few complex steps SRM-PSC-2-SRM Shopping Cart with many simple steps SRM-PSC-2-SRM Shopping Cart with many simple steps SRM-CONF-SRM Confirmation SRM-CONF-SRM Confirmation SRM-INV-SRM Invoice SRM-INV-SRM Invoice

ITEMS 0 0 0 0 0 0 0 0 0 0 0 0 0 0

% CHG

% DISP

MONTHS ST TIME END TIME 0 NA NA NA 0 0 0 NA NA NA 0 0 0 NA NA NA 0 0 0 NA NA NA 0 0 0 NA NA NA 0 0 0 NA NA NA 0 0 0 NA NA NA 0 0

Strategic Purchasing
Active Users - Standard Sizing LOW SRM-CTR-LU-Users in SRM Lean Contract Management SRM-CTR-EU-Users in SRM Extended Contract Management SRM-RFX-LU-Users in Lean SRM RFx SRM-RFX-EU-Users in Extended SRM RFx TOTAL CONCURRENT Peak users THRUPUT - Standard Sizing OBJECTS SRM-CTR-L-Lean Contract Management-Contract SRM-CTR-L-Lean Contract Management-Contract SRM-CTR-E-Extended Contract Management-Contract SRM-CTR-E-Extended Contract Management-Contract SRM-RFX-L-SRM Lean RFx SRM-RFX-L-SRM Lean RFx SRM-RFX-E-SRM Extended RFx SRM-RFX-E-SRM Extended RFx ITEMS 0 0 0 0 0 0 0 0 % CHG % DISP MONTHS ST TIME END TIME 0 NA NA NA 0 0 0 NA NA NA 0 0 0 NA NA NA 0 0 0 NA NA NA 0 0 MEDIUM HIGH

Copyright IBM Corp. April-2008

QUICKSIZER SIZING FOR GTS


What release of GTS are you implementing What time does the AVERAGE workday start What time does the AVERAGE workday end What time does the PEAK load start What time does the PEAK load end 2007 9:00 18:00 12:00 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 First non-production system Second non-production system Third non-production system, if needed Fourth non-production system, if needed Fifth non-production system, if needed Please specify any other additional information to help in sizing Default Dev QA None None None Size Storage Default 100GB's =prod None None None

THRUPUT SIZING FOR COMPLIANCE AND CUSTOM MANAGEMENT


OBJECTS GTS-CUMA-AVERAGE Customs management contracts per YEAR GTS-CUMA-PEAK Customs management contracts per PEAK TIME GTS-SLS-AVERAGE Compliance management per YEAR GTS-SLS-PEAK Plan-Compliance management per PEAK TIME ITEMS 0 0 0 0 % CHG % DISP MONTHS ST TIME END TIME 0 NA NA NA 0 0 0 NA NA NA 0 0

GTS-FI-PR-AVERAGE Screenings of payment proposals per YEAR GTS-FI-PEAK Screening of payment run per PEAK TIME OBJECTS GTS-BP-AVERAGE Business Partners per YEAR GTS-BP-PEAK Business Partners per PEAK TIME GTS-MAT-AVERAGE GTS Materials per YEAR GTS-MAT-PEAK GTS Materials per PEAK TIME

0 0

0 NA

NA 0

NA 0

NA NA NA NA Bus Partner Documents 0 0

NA NA NA NA

NA NA NA NA

MONTHS ST TIME END TIME 0 NA NA NA 0 0 0 NA NA NA 0 0 MONTHS ST TIME END TIME 0 NA NA NA 0 0

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

NA NA

NA NA

THRUPUT SIZING FOR GLOBAL TRADE SERVICE RISK MANAGEMENT


OBJECTS GTS-RI-BOM-AVERAGE BOM transfers per YEAR GTS-RI-BOM-PEAK BOM transfers per PEAK TIME GTS-RI-INV-AVERAGE worklist based on SD Invoices per YEAR GTS-RI-INV-PEAK worklist based on SD Invoices per PEAK TIME GTS-RI-MM-AVERAGE worklist based on MM per YEAR GTS-RI-MM-PEAK worklist based on MM per PEAK TIME GTS-RI-PRD-AVERAGE BOM Preference determination per YEAR GTS-RI-PRD-PEAK BOM Preference determination per PEAK TIME GTS-RI-SO-AVERAGE SD/SO Preference determination per YEAR GTS-RI-SO-PEAK SD/SO Preference determination per PEAK TIME Customers GTS-RI-ISS-AVERAGE vendor declarations per YEAR GTS-RI-ISS-PEAK vendor declarations per PEAK TIME Vendors GTS-RI-AGG-AVERAGE vendor declarations per YEAR GTS-RI-AGG-PEAK vendor declarations per PEAK TIME GTS-RI-SOL-AVERAGE vendor solicitations per YEAR GTS-RI-SOL-PEAK vendor solicitations per PEAK TIME ITEMS 0 0 0 0 0 0 0 0 0 0 Prod/cust 0 0 Prod/vend 0 0 0 0 % CHG % DISP MONTHS ST TIME END TIME 0 NA NA NA 0 0 0 NA NA NA 0 0 0 NA NA NA 0 0 0 NA NA NA 0 0 0 NA NA NA 0 0 MONTHS ST TIME END TIME 0 NA NA NA 0 0 MONTHS ST TIME END TIME 0 NA NA NA 0 0 0 NA NA NA 0 0

% CHG NA NA

NA NA NA NA

NA NA NA NA

Copyright IBM Corp. April-2008

QUICKSIZER SIZING FOR Banking


What time does the AVERAGE workday start What time does the AVERAGE workday end What time does the PEAK load start What time does the PEAK load end 9:00 18:00 12:00 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 First non-production system Second non-production system Third non-production system, if needed Fourth non-production system, if needed Fifth non-production system, if needed Please specify any other additional information to help in sizing Default Dev QA None None None Size Storage Default 100GB's =prod None None None

THRUPUT SIZING FOR ANALYTICAL BANKING


OBJECTS FT/FI-PEAK Financial transactions per PEAK TIME POSITION- PEAK Changed positions per PEAK TIME REG-REPORT-PEAK Regulatory data per PEAK TIME OBJECTS POSITION-AVERAGE Changed positions per YEAR NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA MONTHS 0 ST TIME END TIME 0 0 0 0 0 0

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

OBJECTS Collat/Claims 0

Lines 0 NA

MONTHS Eff matur Cash flow ST TIME END TIME 0 NA NA NA NA NA 0 0 ST TIME END TIME 0 0

OBJECTS DR-RUN-PEAK Disclosure/reporting documents per PEAK TIME

Level 2 NA NA NA

THRUPUT SIZING FOR CORE BANKING


OBJECTS FS-BK-PST-AVERAGE Processing payments items per YEAR FS-BK-SETT-AVERAGE Processing payments items per YEAR FS-BK-CORR-AVERAGE Processing payments items per YEAR FS-BK-ACCR-AVERAGE Processing payments items per YEAR OBJECTS FS-BK-MPST-PEAK Processing payments items per PEAK TIME FS-BK-SPST-PEAK Processing payments items per PEAK TIME FS-BK-STAT-PEAK Processing payments items per PEAK TIME FS-BK-SETT-PEAK Processing payments items per PEAK TIME FS-BK-CORR-PEAK Processing payments items per PEAK TIME FS-BK-ACCR-PEAK Processing payments items per PEAK TIME Coll agree FS-BK-CMS-PEAK Loans per PEAK TIME NA NA NA NA NA NA Loans NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA MONTHS 0 0 0 0 ST TIME END TIME 0 0 0 0 0 0 0 0 0 0 0 0 ST TIME END TIME 0 0

Copyright IBM Corp. April-2008

QUICKSIZER SIZING FOR Insurance


What time does the AVERAGE workday start What time does the AVERAGE workday end What time does the PEAK load start What time does the PEAK load end 9:00 18:00 12:00 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 First non-production system Second non-production system Third non-production system, if needed Fourth non-production system, if needed Fifth non-production system, if needed Please specify any other additional information to help in sizing Default Dev QA None None None Size Storage Default 100GB's =prod None None None

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

Items 0 0

NA NA

NA NA

NA NA

ST TIME END TIME 0 0 0 0 ST TIME END TIME 0 0 0 0 0 0 0 0 MONTHS

NA NA NA NA Items

NA NA NA NA

NA NA NA NA

NA NA NA NA

ACC-STAT-AVERAGE Invoice/Account statements per YEAR INS-INV-AVERAGE Insurance objects per YEAR OBJECTS BROK-ITEM-AVERAGE Broker report items per year PAY-EXE-AVERAGE payment plan executions per year PAY-TRANS-AVERAGE Payment plan transfers per year

0 0

NA NA

NA NA

NA NA

0 0 MONTHS 0 0 0

NA NA NA

NA NA NA

NA NA NA

NA NA NA

Copyright IBM Corp. April-2008

QUICKSIZER SIZING FOR Retail Forecasting and Replenishment


What time does the PEAK load start What time does the PEAK load end 12:00 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 First non-production system Second non-production system Third non-production system, if needed Fourth non-production system, if needed Fifth non-production system, if needed Please specify any other additional information to help in sizing Default Dev QA None None None Size Storage Default 100GB's =prod None None None

Loc Prod R-MDS Master Data Synchronization-SCM->FRP PEAK TIME OP Items R-ODS Order Data Synchronization-SCM->FRP PEAK TIME Loc Prod R-PCSD Processing Consumption (and stock) data PEAK TIME Loc Prod 0 NA Res time 0 SDT yes OP Items 0 NA NA NA WMD yes

ST TIME END TIME 0 0 ST TIME END TIME 0 0 ST TIME END TIME 0 0 ST TIME END TIME 0 0

NA Loc Prod 0

NA

NA

NA

R-FRP--FRP run

NA

NA

NA

Copyright IBM Corp. April-2008

QUICKSIZER SIZING FOR Utilities


What time does the AVERAGE workday start What time does the AVERAGE workday end What time does the PEAK load start What time does the PEAK load end 9:00 18:00 12:00 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 First non-production system Second non-production system Third non-production system, if needed Fourth non-production system, if needed Fifth non-production system, if needed Please specify any other additional information to help in sizing Default Dev QA None None None Size Storage Default 100GB's =prod None None None

Billcycle UTIL-01-AVERAGE billing documents per YEAR BusPart UTIL-02-AVERAGE billing documents per YEAR BusPart 0 OBJECTS OVERVIEW-AVERAGE use of "Customer Overview" transaction per YEAR OVERVIEW-PEAK use of "Customer Overview" transaction per PEAK TIME CONTACT-AVERAGE Customer contacts per YEAR CONTACT-PEAK Customer contacts per PEAK TIME MOVE IN-AVERAGE customer move-ins per YEAR MOVE IN-PEAK customer move-ins per PEAK TIME MOVE-OUT-AVERAGE customer move-outs per YEAR MOVE-OUT-PEAK customer move-outs per PEAK TIME

Budget 0 Overdues 0 Days for batch 0

Partial 0 Deposits 0

P-items 0 Cust cont 0

C-items 0

Lines 0 MONTHS 0

Contracts 0

Tax 0

ContAcc

Meters

MONTHS 0

NA

UTIL-BP-PEAK Batch processing per PEAK TIME

NA

NA

NA

ST TIME END TIME 0 0 ST TIME END TIME NA NA 0 0 NA NA 0 0 NA NA 0 0 NA NA 0 0

NA NA NA NA NA NA NA NA

NA NA NA NA NA NA NA NA

NA NA NA NA NA NA NA NA

NA NA NA NA NA NA NA NA

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 First non-production system Second non-production system Third non-production system, if needed Fourth non-production system, if needed Fifth non-production system, if needed Please specify any other additional information to help in sizing Default Dev QA None None None Size Storage Default 100GB's None None None None

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

PLM Core 7.0

Click for sizing white paper Users 0 SAPS 0

cPROJECTS SIZING

Click for sizing white paper Objects Projects Results 0

CPU sizing based on number of objects and number of projects

SAPS

Disk sizing based on number of objects and number of projects

GB's

cFOLDERS SIZING
# msgs CPU sizing for the download scenario CPU sizing for the upload and copying scenario # docs Disk sizing based on number of documents and size of document doc size msg size SAPS 0 0 GB's 0

cRECORDS SIZING User Based Sizing


Users in Records and Case Management-PEAK PER HOUR

Click for sizing white paper LOW MEDIUM HIGH SAPS 0

Thruput Based Sizing


CASES PEAK Cases created by a user per PEAK TIME Elements TOTAL elements added to cases by a user per PEAK TIME CASES PEAK Cases created by an interface per PEAK TIME Elements TOTAL elements added to cases by an interface per PEAK TIME NA # cases # elements Disk sizing based on cases and records NA NA GB's 0 NA NA NA NA NA NA NA NA NA NA NA NA NA ST TIME END TIME 12 13 ST TIME END TIME 12 13 ST TIME END TIME 12 13 ST TIME END TIME 12 13 SAPS 0 SAPS 0 SAPS 0 SAPS 0

CONTENT SERVER SIZING User Based Sizing


PEAK PARALLEL Users accessing the Content database

Click for sizing white paper Users SAPS 0 GB's 0

Copyright IBM Corp. April-2008

T-SHIRT SIZING FOR MDM-7.1 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 First non-production system Second non-production system Third non-production system, if needed Fourth non-production system, if needed Fifth non-production system, if needed Please specify any other additional information to help in sizing Default Dev QA None None None Size Storage Default 100GB's None None None None

Enter total CONCURRENT users during the PEAK hour--A user must NOT be counted twice

NetWeaver MDM Server-APP Server


CPU sizing--number of records in the primary table Memory sizing Accelerator size on disk

Click for sizing white paper Repository # Records # Users

Results SAPS GB's GB's

NetWeaver MDM Server-DBMS Server


CPU sizing Results 0 SAPS

Memory sizing Disk sizing--based on estimate of total storage

Data size

0 0 Results 0 0

GB's GB's

Import, Syndication,Layout Server-Optional


CPU sizing Memory sizing

SAPS GB's

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 First non-production system Second non-production system Third non-production system, if needed Fourth non-production system, if needed Fifth non-production system, if needed Please specify any other additional information to help in sizing Default Dev QA None None None Size Storage Default 100GB's None None None None

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 Obj Planning & Consolidation(BPC 7.5)


System Server--PEAK users-MS Windows version Users Server--PEAK users-NW version-simple requirements Server--PEAK users-NW version-Med Complexity requirements Server--PEAK users-NW version-Very Complex requirements Netweaver Tier SAPS GB Memory SQL/OLAP Server SAPS GB Memory IIS/.NET Server cores GB Memory Storage 200 min IIS/.NET Server cores GB Memory Storage See BW See BW See BW

OutlookSoft sizing Guidance

Click for vendor information Users

Results

Server sizing--number of PEAK users

Enterprise Search Appliance sizing Guidance


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

Adobe Document Services sizing Guidance


ADS Server--# documents per hour ADS Server--# documents per hour(batching)

Click for sizing white paper Small Medium

Large

SM Simple ADS Server--# documents per hour(interactive) ADS Server--Will ADS PDF cache be enabled? ADS Server--Will changes or printing be permitted? ADS Server--Will all form signatures be extracted? ADS Server--Will the form data be extracted after 2nd signature? No No No No

SM Complex

Medium

SAPS 0 0 Large

SAPS 0

Learning Solutions sizing Guidance


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

GRC-VIRSA sizing Guidance--Initial t-shirt sizing


Compliance Calibrator(Risk analysis and remediation) Access Enforcer(Compliant user provisioning) Role Expert(Enterprise role management) TOTAL

Click for sizing white paper System NA NA NA

SAPS NA NA NA 0 0 0 0

GB-Storage 0 0 0 0

GRC-VIRSA sizing Guidance--Expert sizing


Compliance Calibrator(Risk analysis and remediation) Initial Load Sizing per hour Daily Transactional Sizing per hour Daily Batch Sizing per hour Access Enforcer(Compliant user provisioning) Initial Load Sizing per hour Daily Transactional Sizing per hour Role Expert(Enterprise role management)

Click for sizing white paper Users Roles

SOD

Report

SAPS NA

GB-Storage 0 0 NA 0 NA 0 NA 0 0 0 NA NA 0

NA

NA

Daily Transactional Sizing per hour Daily Batch Sizing per hour Total

0 0 0 Click for sizing white paper NA MEDIUM NA HIGH SAPS 0 0 GB-Storage 0

NA NA NA

EH&S-Environment, Health and Safety--Initial t-shirt sizing


System Product Safety(PS) and dangerous goods(DG) sizing LOW Number of users--All other sub modules--PEAK PER HOUR

xEM-Emissions Management--sizing guidance


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

xRPM-Resource & Portfolio Mgmt--sizing guidance


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

ARIS BPM--Server sizing guidance

Concurrent users on the server--PEAK PER HOUR

Click for vendor information Business Server USERS SAPS GB-Memory 0 0

DBMS Server SAPS GB-Memory 0 0

SAP MOBILITY--three alternatives SAP MOBILITY--CRM


Users that will be synchronizing laptops-PEAK PER HOUR LOGONS SAPS 0 GB-Storage 0

SAP MOBILITY--Mobile Business


Syncs Mobile Asset Management(MAM) Standard and Utilities Mobile Asset Management for Utilities(MAU) Syncs Mobile Sales for Handheld with CRM 5.x Visits Web Application Server J2EE ABAP DB 0 0 0 0 0 NA CRM SAPS 0 Web Application Server To Handheld To Backend DB ECC Server ABAP 0 0

ECC Server ABAP

Mobile Direct Store Delivery Syncs Mobile Sales for Handheld with R/3 and ECC Mobile Time Sheet-single mode scenario-sync weekly Mobile Time Sheet-administration scenario-sync daily Mobile Travel Expenses-Daily Trip Scenario Mobile Travel Expenses-Weekly Trip Scenario Smart Sync Data Model

0 NA Web Application Server J2EE ABAP DB 0 0 NA NA 0 NA NA 0 NA NA 0 NA NA 0 NA NA 0 0

0 ECC Server ABAP 0 0 0 0 0 NA

SAP MOBILITY--NetWeaver Mobility


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

Syncs Client Synchronizations

Messages Processing uploaded messages in an 8-hour window

SAP NFe-electronic invoicing-Biller Direct


Using FI-AR(accounts receivable) as the backend Using FI-CA(contract accounts) as the backend

Click for sizing white paper BC's J2EE 0 0

AS 0 0

DB 0 0

NRX-Add-on to EP
NW-EP-PRT-PEAK

Click for vendor information USERS Think time 180 Java iViews URL iViews 4 0 % KMC 30

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

T-SHIRT SIZING GUIDANCE FOR KNOWLEDGE MANAGEMENT AND COLLABORATION


Users KM-PEAK Concurrent users per PEAK TIME NA NA NA PORTAL SAPS 0

Click for sizing white paper DB SAPS 0 Portal Memory 0

NWDI or JDI
Scenario 1-Development in a team Scenario 2-Development with components Scenario 2+-Development with a Track Scenario 3-Layered development

Click for sizing SAP NOTE 737368 Developers SAPS GB-Memory 0 0 0 0 0 0 0 0

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

Web Dispatcher

Auto-ID Infrastructure-RFID
Slap & Ship Scenario Tag Commissioning Packing

Click for sizing white paper Print Req Tags Pallets Pallets Cases Cases

Time Time

SAPS 0 0

Storage 0.00 0.00 0.00 Storage 0.00 0.00 0.00 Storage 0.00

Time 0

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

SAPS 0 0 0 SAPS 0

Packing/Unpacking in SCM Pallets Loading/Unloading in SCM RFID-Integrated Delivery Processing Scenario Tag Commissioning in All Packing/Unpacking in All Deliveries Loading/Unloading in All with hierarchy Deliveries Loading/Unloading in All without hierarchy Items EPC Time Pieces Items EPC Time Pieces Pallets Print Req Deliveries Tags Items Time EPC Time Pieces Pallets Cases Time

0 0 SAPS 0 0 0 0

0.00 0.00 Storage 0.00 0.00 0.00 0.00

Copyright IBM Corp. April-2008

INFORMATION ON DOING AN UPGRADE SIZING


To what release of SAP are you upgrading? Will you be adding Unicode? Default is yes. How many additional users will you be adding or specify growth factor(%) What is your preferred hardware platform? Default ECC 6.0 yes 0

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

Upgrade Sizing information for System x


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

Upgrade Sizing information for System z

Copyright IBM Corp. April-2008

INPUTS
ERP CRM BW/SEM Portal PI TREX SM SCM APO SRM GTS Banking Insurance Retail Utilities PLM MDM MISC Upgrade Totals Changed NO NO NO NO NA NA NA NA NO NA NA NA NA NA NA NA NA NA

USER BASED
# of users 0 0 0 0 NA 0 0 NA 0 NA NA NA NA NA 0 0 0 NA 0 SAPS 0 0 NA NA NA 0 NA NA NA NA NA NA NA NA 0 0 0 NA 0 Storage Qser 0 NA NA NA 0 NA NA NA NA NA NA NA NA 0 0 0 NA 0

THRUPUT BASED
Changed ? NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO

You might also like