SAP Questionnaire 061510

business solutions

IBM and SAP

IBM Sizing and Planning Questionnairefor SAP Solutions

© Copyright IBM Corp. April-2008

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

Europe, Middle East, and Africa

For more information about IBM SAP solutions go to http://www.ibm-sap.comFor online entry of data from this questionnaire go to http://service.sap.com/sizingFor access to the most recent version of this questionnaire go to http://www.ibm.com/erp/sizing

[email protected] / +1 845-491-2372IBMers raise a Techline Request through http://w3.ibm.com/support/emea/techline

BPs raise a Techline Request through

http://www.ibm.com/partnerworld/techline

For both : in case of attachment problems, send file to

[email protected]

http://service.sap.com/sizing

mailto:[email protected]

http://w3-5.ibm.com/support/emea/techline

Asia, Pacific

[email protected](China)Hong KongTaiwanSouth KoreaJapanAustralia and New Zealand

[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:

directly by the SAP QuickSizer. Other components in this questionnaire are estimated in this questionnaire tool by derivation fromwhite papers provided by SAP. Links to these white papers are provided within this questionnaire tool. You will need an OSS UserID and an SAP customer number which you can get from your local SAP representative.

will need an OSS User ID and an SAP customer number which you can get from your local SAP representative. Request sizing fromIBM 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.

IBM ASEAN/SA Techline(Singapore, Malaysia, Thailand, Philippines, Indonesia, Vietnam, India and Sri Lanka)

[email protected]@[email protected]@[email protected]@au1.ibm.com

OthersIBM SAP International Competence Center, ISICC, Walldorf

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

3. Return the questionnaire to IBM, or, enter the data directly into the SAP QuickSizer at web address: http://service.sap.com. You







http://service.sap.com/

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,

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 AssumptionsThis 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

and custom code. The degree of variability can range from small to very significant. Sizing the hardware requirements for each

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 InformationPlease fill in the information on the following contact points. If unknown or not applicable, leave blank.

QuickSizer customer number QuickSizer project name

Company Name SAP ContactStreet Address Phone Number

City, State/Province e-mail addressZip/Postal Code, Country

Customer Contact Business Partner or SAP Value Added ResellerTitle Contact

Phone Number Phone Numbere-mail address e-mail address

IBM ContactPhone Numbere-mail address

Opportunity Number-REQUIRED

A7

We highly recommend that you consider putting your answers in this questionnaire directly into the SAP QuickSizer. The QuickSizer may be found at http://service.sap.com/quicksizing. This site requires an SAP supplied username and password. You may use username s0001066187 and password a813i817 on a temporary basis. The QuickSizer also requires a customer number. You may use 12345 on a temporary basis. The project name is your choice. Please consider using something you remember with some sort of time or date reference in the name.

© Copyright IBM Corp. April-2008 General Sizing Questions for Initial Sizings – New Installation or new workloads

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 SolutionPlease specify if you plan to implement a specific industry solution or want to give any other additional information:

Planned Hardware Platform

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.

Application Server(s)

System z System z System p System xSystem p System p System xSystem x System xSystem i System i System x

Comments:

Preferred Disk Technology SizingDisk Technology Questions Answer OptionsPlease indicate your preferred disk technology? Default DS4300

In this section, we would like to know about your hardware and software requirements. Some of the subsections require responses; others are

Which IBM eServer would you like to consider for this sizing estimate? Specify a database server and one of its application server options. If

Database Server

A34

Enter the type of disk technology you plan to use. This could be DS4300, ESS, SCSI or some other type of disk technology.

Storage SizingStorage Capacity Questions Answer OptionsWhat RAID Technology will you use? Default-RAID5At what capacity do you run your storage subsystem? Default-80%What storage growth factor per year over how many years would you like us to use? Default-0%, 0 yearsWhat 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 SizingScalability Questions Answer OptionsHow important is scalability in your hardware configuration? Default-not important

High Availability SizingIBM 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 OptionsIs high availability technology, such as clustering or HACMP, on the database server required? Default-noIf yes, where will failover be? App Server? Test Server? Idle Server? Other? Default-App

Backup/Restore SizingBackup/Restore Question Answer OptionsDo you want a backup device included in the proposed configuration? Default-no

UNICODE SizingUNICODE 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 OptionsWill you be using UNICODE? Default-yes

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

A38

Enter the type of disk technology you plan to use. This could be RAID5 which is the default, RAID1 or any other RAID technology.

A39

Disks are not normally filled to 100% capacity because of fragmentation, free space, reserved space, etc. Enter the estimate of the percentage of the total storage capacity that will be normally filled.

A40

Enter the estimate of the percentage of annual growth you expect for storage capacity and over how many years you would like us to calculate this growth.

A41

There are various methods for compressing data to use storage capacity more efficiently. Enter the percentage of total storage that you expect to gain by using a compression solution. This defaults to 0% except for System z which defaults to 40% compression because of hardare data compression.

A42

We can provide an estimate for Tivoli Storage Manager buffer pools. If you plan to backup directly to tape, we add no additional disk storage for buffer pools. If you plan a full backup to disk, we assume 100% additional storage for buffer pools. If you plan to do incremental backups to disk, you can specify the percentage of total production disk that we should allocate for disk buffer pools. A reasonable percentage might be 10-15%.

L68

Enter the length of your business year in days. Defaults are 250 days for US and Latin America, 300 for Asia/Pacific and 200 for EMEA.

Project Phases and GrowthBy 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 SizingType of Sizing Questionnaire Answer Options

© Copyright IBM Corp. April-2008 QUICKSIZER SIZING FOR ERP

What release of ERP are you implementing 6.0What time does the AVERAGE workday start 9:00What time does the AVERAGE workday end 18:00What time does the PEAK load start 12:00 What time does the PEAK load end 13:00

NON-PRODUCTION SYSTEMSSystem Landscape (required)

defined, you may then create an implementation strategy for the setup and maintenance of the systems and clients within this landscape.

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 DefaultFirst non-production system Dev 100GB'sSecond non-production system QA =prodThird non-production system, if needed None NoneFourth non-production system, if needed None NoneFifth 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 twiceHe is either one type of concurrently active user or another--NOT both at the same time during the PEAK hourUSER BASED SIZING

LOW MEDIUM HIGHTypically, 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 HOURFI-Users in Financial Transactions-PEAK PER HOURPA-Users in Personnel Administration-PEAK PER HOURPD-Users in Personnel Development-PEAK PER HOURLE-Users in Logistics Execution-PEAK PER HOURALM/PM-Users in Asset Lifecycle Management-PEAK PER HOUR

A system landscape consists of the systems and clients that are needed for non-production. Once the system landscape has been

IBM and SAP strongly recommend having at least a three-system landscape. A three-system landscape is comprised of a development

B4

SAP Qser is currently sizing ERP 6.0

B5

Enter a time between 00:00 and 24:00.

B6


B7


B8


B19

This is used to specify the type or name of this non-production system. Please choose one of the specific types of systems or specify "other" and put the name of the "other" system in the comments box below.

D19

You may specify the size of this system using either expected number of concurrent peak users of this system or as a percentage of the size of production of this system. The next cell is used to specify whether you are using users or percentage.

F19

Specify the raw storage in GB's (before uplift for RAID, utilization, Unicode, growth, etc) for this non-production system.

B20


D20


F20


B21


D21


F21


B22


D22


F22


B23


D23


F23


B34

Low users change screens every 6 minutes during the peak hour. These users cause only a slight amount of workload so putting users in this category affects the sizing only slightly.

C34

Medium users change screens every 30 seconds during the peak hour. If you're not sure, you might put all of your users in the medium category.

D34

High users change screens every 10 seconds during the peak hour. Typically, high users are less than 20% of your total user count for any application.

MM-Users in Materials Management-PEAK PER HOURPP-Users in Production Planning-PEAK PER HOURPS-Users in Project Management-PEAK PER HOURQM-Users in Quality Management-PEAK PER HOURCS-Users in Customer Service-PEAK PER HOURSD-Users in Sales & Distribution-PEAK PER HOURBC-Users in Basis transactions-PEAK PER HOURTOTAL CONCURRENT PEAK users -PEAK PER HOUR 0 0 0 0 usersApproximate SAPS 0 SAPS 0 init SAPSApproximate Storage Qser GB'sIf AFS is implemented add this uplift 0 SAPS Click for sizing white paper

0OBJECTS ITEMS % CHG % DISP MONTHS ST TIME END TIME

CO-PA-BIL-AVERAGE Billing docs posted to CO per YEAR 0 0 NA NACO-PA-BIL-PEAK Billing docs posted to CO per PEAK TIME 0 NA 12:00 13:00CO-PA-FI-AVERAGE Financial docs posted to CO per YEAR 0 0 NA NACO-PA-FI-PEAK Financial docs posted to CO per PEAK TIME 0 NA 12:00 12:00CO-PA-SLS-AVERAGE Sales orders posted to CO per YEAR 0 0 NA NACO-PA-SLS-PEAK Sales orders posted to CO per PEAK TIME 0 NA 12:00 12:00CO-AVERAGE Controlling docs or postings per YEAR 0 0 NA NACO-PEAK Controlling docs or postings per PEAK TIME 0 NA 12:00 12:00EC-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:00FIN-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 TIMECO-OM-PEAK Sender-receiver relations for all cycles NA NA NA NA 0 0CO-OM-RAT-PEAK Orders/period with overhead rate NA NA NA NA 0 0CO-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 TIMELOAD-BILL-PEAK Load Billing 0 NA NA NA 0 0LOAD-INV-PEAK Load Invoicing 0 NA NA NA 0 0CONV-INV-PEAK Convergent Invoicing 0 NA NA NA 0 0DUNNING-PEAK Dunning 0 NA NA NA 0 0

THRUPUT SIZING FOR FINANCIALS--If you complete this section, you must resolve all "ERROR" messages.

https://websmp204.sap-ag.de/~sapdownload/011000358700000472452004E/SIZING_RULES_AFS.PDF

E50

These are the estimated SAPS if you are adding workload to an existing SAP ERP system.

G50

These are the estimated SAPS if this is a completely new installation. SAP recommends a minimum of 2000 SAPS for the initial install.

A52

Apparel and Footwear Solution is an add-on to core ERP. The uplift is 25% for MM, 30% for SD and 50% for PP. This has been included in this uplift. If categories are in use add 5% more. If split valuation is in use add 5% more.

G52

Sizing for this component or feature is provided by SAP thru the publication of a white paper. Access to this white paper requires an OSS User ID and SAP customer number which you can get from your local SAP representative.

B56

If you enter the number of OBJECTS you MUST enter ITEMS and MONTHS but NOT ST TIME and END TIME. These are the average number of OBJECTS per year. This is used to calculate disk and will be used to calculate CPU if you put nothing in the PEAK row.

C56

Enter number of line ITEMS PER OBJECT. NOT total line items.

D56

Enter the percentage of time that a typical object is changed before it is archived.

E56

Enter the percentage of time that a typical object is displayed before it is archived.

F56

Enter the number of months this data will remain online before being archived.

B57

If you enter the number of OBJECTS, you MUST enter ITEMS and ST TIME and END TIME but NOT MONTHS. These are the number of OBJECTS processed during the peak or highest time period; usually an hour or a couple of hours. You specify the time period that these peak OBJECTS are processed using the ST TIME and END TIME columns. This is used to calculate CPU requirements. This must be larger than the annual objects divided by the number of working days divided by the length of the average work day.

C57


D57

Enter the percentage of time that a typical OBJECT is changed before it is archived.

E57

Enter the percentage of time that a typical OBJECT is displayed before it is archived.

G57

Enter the time of day that the peak of these OBJECTS will start processing. Default for this is the overall Peak Start Time.

H57

Enter the time of day that the peak of these OBJECTS will end processing. Default for this is the overall Peak End Time.

B58


C58


D58


E58


F58


B59


C59


D59


E59


G59


H59


B60


C60


D60


E60


F60


B61


C61


D61


E61


G61


H61


B62


C62


D62


E62


F62


B63


C63


D63


E63


G63


H63


B64


C64


D64


E64


F64


B65


C65


D65


E65


G65


H65


B66


C66


D66


E66


F66


B67


C67


D67


E67


G67


H67


B70

If you enter the number of OBJECTS, you MUST enter ST TIME and END TIME. These are the number of OBJECTS processed during the peak or highest time period; usually an hour or a couple of hours. You specify the time period that these peak OBJECTS are processed using the ST TIME and END TIME columns. This is used to calculate CPU requirements.

G70


H70


B71


G71


H71


B72


G72


H72


B76

If you enter the number of OBJECTS, you MUST enter ITEMS, EDRs/bd and ST TIME and END TIME. These are the number of OBJECTS processed during the peak or highest time period; usually an hour or a couple of hours. You specify the time period that these peak OBJECTS are processed using the ST TIME and END TIME columns. This is used to calculate CPU requirements.

C76

Enter the number of business partner line items per posting. Not the total line items.

D76


G76


H76


B79

If you enter the number of OBJECTS, you MUST enter ITEMS and ST TIME and END TIME. These are the number of OBJECTS processed during the peak or highest time period; usually an hour or a couple of hours. You specify the time period that these peak OBJECTS are processed using the ST TIME and END TIME columns. This is used to calculate CPU requirements.

C79


G79


H79


B80


C80


G80


H80


B81


C81


G81


H81


B82


C82


G82


H82


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

EDRs AddFld MONTHS ST TIME END TIMEEDR-UPL-AVERAGE Event Detail Record Upload NA NA 0 NA NA

OBJECTS MONTHS ST TIME END TIMEPAY-RUN-AVERAGE Payment Run NA NA NA 0 NA NACD-PL-AVERAGE Payment Lots NA NA NA 0 NA NACORR-PRINT-AVERAGE Correspondent Print NA NA NA 0 NA NADEF-POST-AVERAGE Deferred Postings NA NA NA 0 NA NA

OBJECTS ITEMS MONTHS ST TIME END TIMEEDR-BILL-AVERAGE Event Detail Record Billing 0 NA NA 0 NA NALOAD-BILL-AVERAGE Load Billing 0 NA NA 0 NA NACONV-INV-AVERAGE Convergent Invoicing 0 NA NA 0 NA NADUNNING-AVERAGE Dunning 0 NA NA 0 NA NA

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

ESS/MSS workload Scenarios Steps ST TIME END TIMEESS-LEAVE 7 NA NA NA 0 0ESS-CATS 9 NA NA NA 0 0ESS-TRAVEL 18 NA NA NA 0 0MSS_COST 9 NA NA NA 0 0MSS-PERS 13 NA NA NA 0 0

OBJECTS MONTHS ST TIME END TIMEHCM-PT-AVERAGE Processed Time Pairs per YEAR NA NA NA 0 NA NAHCM-PT-PEAK Processed Time Pairs per PEAK TIME NA NA NA NA 0 0HCM-PY-AVERAGE Payroll periods incl retro calculations NA NA NA 0 NA NAHCM-PY-PEAK Payroll periods incl retro calculations NA NA NA NA 0 0

THRUPUT SIZING FOR HUMAN CAPITAL MANAGEMENT--If you complete this section, you must resolve all "ERROR" messages.

THRUPUT SIZING FOR E-Recruitment--If you complete this section, you must resolve all "ERROR" messages.

B85


G85


H85


B86


G86


H86


B87


G87


H87


B88


G88


H88


B89


G89


H89


B92

If you enter the number of EDR's, you MUST enter Addfld and MONTHS. These are the average number of EDR's uploaded during the year. You specify the time period that these peak EDR's are uploaded using the ST TIME and END TIME columns. This is used to calculate Disk requirements.

C92

Enter the length of the additional fields in the EDR table.

F92


B95

If you enter the number of OBJECTS, you MUST enter MONTHS. These are the average number of OBJECTS processed during the year. You specify the time period that these peak OBJECTS are storage on disk before being deleted or archived in the MONTHS column. This is used to calculate Disk requirements.

F95


B96


F96


B97


F97


B98


F98


B101

If you enter the number of OBJECTS, you MUST enter ITEMS and Months. These are the average number of OBJECTS processed during the year. You specify the time period that these OBJECTS remain in online storage before being either deleted or archived in the MONTHS field. This is used to calculate Disk requirements.

C101


F101


B102


C102


F102


B103


C103


F103


B104


C104


F104


B107

If you enter the number of Postings, you MUST enter BP itm, GL itm, Payments, P itm, % credit and MONTHS. These are the average number of Postings processed during the year. You specify the time period that these Postings are stored on disk before being deleted or archived in the MONTHS column. This is used to calculate Disk requirements.

C107


D107


E107


F107


G107

Enter the percentage of prepaid payments with credit card.

H107


A110

This allows you to estimate the workload from employees and managers accessing information and performing routine tasks.

B110

A scenario is a user session where the employee or manager accomplishes a specific task. This may entail a single dialog or usually multiple dialogs.

A111

Employee leave requests

B111

If you enter the number of Scenarios, you MUST enter ST TIME and END TIME. These are the number of LEAVE scenarios processed during the peak or highest time period; usually an hour or a couple of hours. You specify the time period that these peak Scenarios are processed using the ST TIME and END TIME columns. This is used to calculate CPU requirements.

C111

Enter the number of steps required for each scenario including navigation to the scenario entry. The defaults for each scenario are based on measurements of each specific scenario type and may be over-ridden.

G111

Enter the time of day that the peak of these Scenarios will start processing. Default for this is the overall Peak Start Time.

H111

Enter the time of day that the peak of these Scenarios will end processing. Default for this is the overall Peak End Time.

A112

Cross-Application Time Sheets or recording working time.

B112

If you enter the number of Scenarios, you MUST enter ST TIME and END TIME. These are the number of CATS scenarios processed during the peak or highest time period; usually an hour or a couple of hours. You specify the time period that these peak Scenarios are processed using the ST TIME and END TIME columns. This is used to calculate CPU requirements.

C112


G112


H112


A113

Travel expense recording

B113

If you enter the number of Scenarios, you MUST enter ST TIME and END TIME. These are the number of TRAVEL scenarios processed during the peak or highest time period; usually an hour or a couple of hours. You specify the time period that these peak Scenarios are processed using the ST TIME and END TIME columns. This is used to calculate CPU requirements.

C113


G113


H113


A114

Cost center monitoring

B114

If you enter the number of Scenarios, you MUST enter ST TIME and END TIME. These are the number of COST center monitoring scenarios processed during the peak or highest time period; usually an hour or a couple of hours. You specify the time period that these peak Scenarios are processed using the ST TIME and END TIME columns. This is used to calculate CPU requirements.

C114


G114


H114


A115

Personnel change requests

B115

If you enter the number of Scenarios, you MUST enter ST TIME and END TIME. These are the number of Personnel change request scenarios processed during the peak or highest time period; usually an hour or a couple of hours. You specify the time period that these peak Scenarios are processed using the ST TIME and END TIME columns. This is used to calculate CPU requirements.

C115


G115


H115


B118

If you enter the number of OBJECTS, you MUST enter MONTHS. These are the average number of clock-in/clock-out time pairs(OBJECTS) processed during the year. You specify the time period that these peak OBJECTS are stored on disk before being deleted or archived in the MONTHS column. This is used to calculate Disk requirements.

F118


B119

If you enter the number of OBJECTS, you MUST enter ST TIME and END TIME. These are the number of clock-in/clock-out time pairs(OBJECTS) processed during the peak or highest time period; usually a day or a couple of hours. You specify the time period that these peak OBJECTS are processed using the ST TIME and END TIME columns. This is used to calculate CPU requirements.

G119


H119


B120

If you enter the number of OBJECTS, you MUST enter MONTHS. These are the average number of retro calculations(OBJECTS) processed during the year. You specify the time period that these peak OBJECTS are stored on disk before being deleted or archived in the MONTHS column. This is used to calculate Disk requirements.

F120


B121

If you enter the number of OBJECTS, you MUST enter ST TIME and END TIME. A retro calculation calculates payroll from a previous payroll run to correct a change. Enter the (number of retro calculations PER EMPLOYEE PER PAYROLL Plus 1) times (the number of employees). You specify the time period that these peak OBJECTS are processed using the ST TIME and END TIME columns. This is used to calculate CPU requirements.

G121


H121


OBJECTS ITEMS % CHG % DISP DCS Attach Size MONTHS ST TIME END TIMEERC-CA-REG-AVERAGE Candidate Registrations per YEAR 0 no 0 NA NAERC-CA-REG-PEAK Candidate Registrations per PEAK TIME 0 no NA NA NA 0 0

OBJECTS ITEMS % CHG % DISP DCS ST TIME END TIMEERC-APPL-PEAK Candidate Applications per PEAK TIME 0 no 0 0

OBJECTS ITEMS % CHG % DISP ST TIME END TIMEERC-REQ-PEAK Requisition creation per PEAK TIME 0 0 0

OBJECTS % CHG % DISP DCS ST TIME END TIMEERC-JOB-SE-PEAK Candidate Applications per PEAK TIME NA no 0 0

OBJECTS % CHG % DISP ST TIME END TIMEERC-CA-LST-PEAK Requisition creation per PEAK TIME NA 0 0

OBJECTS ITEMS % CHG % DISP MONTHS ST TIME END TIMELE-WM-AVERAGE Transfer Orders per YEAR 0 0 NA NALE-WM-PEAK Transfer Orders per PEAK TIME 0 NA 0 0LE-SHP-AVERAGE Delivery notes and goods issue per YEAR 0 0 NA NALE-SHP-PEAK Delivery notes and goods issue per PEAK TIME 0 NA 0 0

OBJECTS ITEMS % CHG % DISP MONTHS ST TIME END TIMEALM-PM-AVERAGE Maintenance Orders per YEAR 0 0 NA NAALM-PM-PEAK Maintenance Orders per PEAK TIME 0 NA 0 0MM-IM-AVERAGE Material Movements per YEAR 0 0 NA NAMM-IM-PEAK Material Movements per PEAK TIME 0 NA 0 0MM-PUR-AVERAGE Purchase Orders per YEAR 0 0 NA NAMM-PUR-PEAK Purchase Orders per PEAK TIME 0 NA 0 0PP-CONF-AVERAGE Order Confirmations per YEAR 0 0 NA NAPP-CONF-PEAK Order Confirmations per PEAK TIME 0 NA 0 0PP-REM-AVERAGE Planned Orders per YEAR 0 0 NA NAPP-REM-PEAK Planned Orders per PEAK TIME 0 NA 0 0PP-SFC-AVERAGE Production Orders per YEAR 0 0 NA NAPP-SFC-PEAK Production Orders per PEAK TIME 0 NA 0 0QM-IM-AVERAGE Inspections in Quality Mgmt per YEAR 0 0 NA NAQM-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

THRUPUT SIZING FOR LOGISTICS EXECUTION--If you complete this section, you must resolve all "ERROR" messages.

THRUPUT SIZING FOR PRODUCT DEV AND EXECUTION--If you complete this section, you must resolve all "ERROR" messages.

B125


C125


D125


E125


F125

Distributed Candidate Scenario. Will you separate the user interaction function from the database access function?

G125

Enter the number of attachments per object.

H125

Enter the average size of one attachment in KB.

I125


B126

If you enter the number of OBJECTS, you MUST enter ITEMS and ST TIME and END TIME but NOT MONTHS. These are the number of OBJECTS processed during the peak or highest time period; usually an hour or a couple of hours. You specify the time period that these peak OBJECTS are processed using the ST TIME and END TIME columns. This is used to calculate CPU requirements.

C126


D126


E126


F126


J126


K126


B129


C129


D129


E129


F129


G129


H129


B132


C132


D132


E132


F132


G132


B135


D135


E135


F135


G135


H135


B138


D138


E138


F138


G138


B142


C142


D142


E142


F142


B143


C143


D143


E143


G143


H143


B144


C144


D144


E144


F144


B145


C145


D145


E145


G145


H145


B149


C149


D149


E149


F149


B150


C150


D150


E150


G150


H150


B151


C151


D151


E151


F151


B152


C152


D152


E152


G152


H152


B153


C153


D153


E153


F153


B154


C154


D154


E154


G154


H154


B155


C155


D155


E155


F155


B156


C156


D156


E156


G156


H156


B157


C157


D157


E157


F157


B158


C158


D158


E158


G158


H158


B159


C159


D159


E159


F159


B160


C160


D160


E160


G160


H160


B161


C161


D161


E161


F161


B162


C162


D162


E162


G162


H162


PS-AVERAGE Projects per YEAR 0 0 NA NAPS-PEAK Projects per PEAK TIME 0 NA 0 0

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

OBJECTS ITEMS % CHG % DISP MONTHS ST TIME END TIMECS-AG-AVERAGE Customer Service objects per YEAR 0 0 NA NACS-AG-PEAK Customer Service objects per PEAK TIME 0 NA 0 0SD-CUST-AVERAGE Customer Contacts per YEAR 0 0 NA NASD-CUST-PEAK Customer Contacts per PEAK TIME 0 NA 0 0SD-BIL-AVERAGE Billing Documents per YEAR 0 0 NA NASD-BIL-PEAK Billing Documents per PEAK TIME 0 NA 0 0SD-POS-AVERAGE Point of Sales objects for Retail per YEAR 0 0 NA NASD-POS-PEAK Point of Sales objects for Retail per PEAK TIME 0 NA 0 0SD-SLS-AVERAGE Sales Orders per YEAR 0 0 NA NASD-SLS-PEAK Sales Orders per PEAK TIME 0 NA 0 0

COM CAS REMC MONTHS ST TIME END TIMEICM-CASE-AVERAGE Customer Service cases per YEAR 0 NA NA 0 NA NAICM-CASE-PEAK Customer Service cases per PEAK TIME 0 NA NA NA 0 0

DOCU REMD MONTHS ST TIME END TIMEICM-DOC-AVERAGE Commission documents posted per YEAR 0 NA NA 0 NA NAICM-DOC-PEAK Commission documents posted per PEAK TIME 0 NA NA NA 0 0

ITEMS COM CON ST TIME END TIMEICM-SET-AVERAGE Settlement items per YEAR 0 NA NA NA NA NAICM-SET-PEAK Settlement items PEAK TIME 0 NA NA NA 0 0

OBJECTS ITEMS % CHG % DISP MONTHS ST TIME END TIMETV-RECEIPT-AVERAGE Travel Receipts per YEAR 0 0 NA NATV-RECEIPT-PEAK Travel Receipts per PEAK TIME 0 NA 0 0

OBJECTS % CHG % DISP MONTHS ST TIME END TIMEBC-PRINT-AVERAGE Print Pages per YEAR NA 0 NA NABC-PRINT-PEAK Print Pages per PEAK TIME NA NA 0 0

THRUPUT SIZING FOR SALES AND SERVICE--If you complete this section, you must resolve all "ERROR" messages.

THRUPUT SIZING FOR CORPORATE SERVICES--If you complete this section, you must resolve all "ERROR" messages.

THRUPUT SIZING FOR APPLICATION SERVER SERVICES--If you complete this section, you must resolve all "ERROR" messages.

B165

If you enter the number of Projects(OBJECTS), you MUST enter WBS and MONTHS but NOT ST TIME and END TIME. These are the average number of Projects(OBJECTS) per year. This is used to calculate disk and will be used to calculate CPU if you put nothing in the PEAK row.

C165

Enter the average number of work breakdown structure elements per project. Not the total WBS elements.

D165

Average # of network plans per project

E165

Enter the average number of activities per network.

F165


G165


H165


B166

If you enter the number of OBJECTS, you MUST enter WBS and ST TIME and END TIME but NOT MONTHS. These are the number of Projects(OBJECTS) processed during the peak or highest time period; usually an hour or a couple of hours. You specify the time period that these peak OBJECTS are processed using the ST TIME and END TIME columns. This is used to calculate CPU requirements.

C166

Enter the average number of work breakdown structure elements per project. Not the total WBS elements.

D166

Average # of network plans per project

E166

Enter the average number of activities per network.

F166


G166


I166


J166


C169

Enter number of line items PER order. NOT total line items.

D169

Enter the purchase requisitions for reorder- point driven materials

E169

Enter the purchase requisitions or schedule line items for non-reorder-point driven materials

F169


G169

Enter the % of BOM strcture changes per day

H169

Enter the percentage of BOM components with object dependencies (average).

I169

Enter the percentage of orders with Lead Time Scheduling

J169


K169


B173


C173


D173


E173


F173


B174

If you enter the number of OBJECTS you MUST enter ITEMS and ST TIME and END TIME but NOT MONTHS. These are the number of OBJECTS processed during the peak or highest time period; usually an hour or a couple of hours. You specify the time period that these peak OBJECTS are processed using the ST TIME and END TIME columns. This is used to calculate CPU requirements.

C174


D174


E174


G174


H174


B175


C175


D175


E175


F175


B176


C176


D176


E176


G176


H176


B177


C177


D177


E177


F177


B178


C178


D178


E178


G178


H178


B179


C179


D179


E179


F179


B180


C180


D180


E180


G180


H180


B181


C181


D181


E181


F181


B182


C182


D182


E182


G182


H182


B185

If you enter the number of COM CAS you MUST enter REMC and MONTHS but NOT ST TIME and END TIME. These are the average number of COM CAS per year multiplied by the number of processing steps. This is used to calculate disk and will be used to calculate CPU if you put nothing in the PEAK row.

C185

Enter the number of remunerations a document creates. In general this is the number of (direct and indirect) recipients per commission case.

F185


B186

If you enter the number of COM CAS, you MUST enter REMC and ST TIME and END TIME but NOT MONTHS. These are the number of COM CAS processed during the peak or highest time period usually an hour or a couple of hours multiplied by the number of processing steps. You specify the time period that these peak COM CAS are processed using the ST TIME and END TIME columns. This is used to calculate CPU requirements.

C186


G186


H186


B189

If you enter the number of DOCU, you MUST enter REMD and MONTHS but NOT ST TIME and END TIME. These are the average number of documents(DOCU) that are directly imported from the operational system(s) to ICM without using the commission case process per year. This is used to calculate disk and will be used to calculate CPU if you put nothing in the PEAK row.

C189


F189


B190

If you enter the number of DOCU, you MUST enter REMD and ST TIME and END TIME but NOT MONTHS. These are the number of documents(DOCU) directly imported from the operational systems(s) to ICM without using the commission case process that are processed during the peak or highest time period; usually an hour or a couple of hours. You specify the time period that these peak DOCU are processed using the ST TIME and END TIME columns. This is used to calculate CPU requirements.

C190


G190


H190


B193

If you enter the number of ITEMS, you MUST enter COM CON but NOT ST TIME and END TIME. This is the total of COM CAS and DOCU per year. This is used to calculate disk and will be used to calculate CPU if you put nothing in the PEAK row.

C193


B194

If you enter the number of ITEMS, you MUST enter COM CON and ST TIME and END TIME. This is the total of COM CAS and DOCU processed during the peak or highest time period; usually an hour or a couple of hours. You specify the time period that these peak ITEMS are processed using the ST TIME and END TIME columns. This is used to calculate CPU requirements.

C194


G194


H194


B198


C198


D198


E198


F198


B199

If you enter the number of OBJECTS you MUST enter ITEMS and ST TIME and END TIME but NOT MONTHS. These are the number of objects processed during the peak or highest time period; usually an hour or a couple of hours. You specify the time period that these peak OBJECTS are processed using the ST TIME and END TIME columns. This is used to calculate CPU requirements.

C199


D199


E199


G199


H199


B203

If you enter the number of OBJECTS you MUST enter MONTHS but NOT ST TIME and END TIME. These are the average number of print pages(OBJECTS) per year. This is used to calculate disk and will be used to calculate CPU if you put nothing in the PEAK row.

D203


E203


F203


B204

If you enter the number of OBJECTS you MUST enter ST TIME and END TIME but NOT MONTHS. These are the number of print pages(OBJECTS) processed during the peak or highest time period; usually an hour or a couple of hours. You specify the time period that these peak OBJECTS are processed using the ST TIME and END TIME columns. This is used to calculate CPU requirements.

D204


E204


G204


H204


© Copyright IBM Corp. April-2008 QUICKSIZER SIZING FOR CRM

What release of CRM are you implementing 2007What time does the AVERAGE workday start 9:00What time does the AVERAGE workday end 18:00What time does the PEAK load start 12:00 What time does the PEAK load end 13:00






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

USER-BASED SIZING FOR CRM MASTER DATALOW MEDIUM HIGH ext SAPS GB-Storage



B4

SAP Qser is currently sizing CRM 2007

B5


B6


B7


B8


B19


D19


F19


B20


D20


F20


B21


D21


F21


B22


D22


F22


B23


D23


F23


B35

Low users change screens every 6 minutes during the peak hour

C35

Medium users change screens every 30 seconds during the peak hour

D35

High users change screens every 10 seconds during the peak hour.

ACC-USER-CRM Account Management-PEAK PER HOUR 0 Use Qser

New Acct Chg Acct Dis Acct Tot Acct ST TIME END TIMECRM-CORACC-AVERAGE Corp Accounts per YEAR NA 0 NA NACRM-CORACC-PEAK Corp Accounts per PEAK TIME NA NA 0 0CRM-INDACC-AVERAGE Individual Accounts per YEAR NA 0 NA NACRM-INDACC-PEAK Individual Accounts per PEAK TIME NA NA 0 0

USER-BASED SIZING FOR CRM SALESLOW MEDIUM HIGH ext SAPS GB-Storage

Users doing CRM Activity Management-PEAK PER HOUR 0 0Users doing CRM Opportunity Management-PEAK PER HOUR 0 0Users doing CRM Sales Transactions-PEAK PER HOUR 0 0TOTAL CRM Sales-PEAK PER HOUR 0 0 0 0 0

OBJECTS ITEMS % CHG % DISP MONTHS ST TIME END TIMECRM-SLSQC-AVERAGE sales quotations per YEAR 0 0 NA NACRM-SLSQC-PEAK sales quotations per PEAK TIME 0 NA 0 0CRM-SLS-AVERAGE sales orders per YEAR 0 0 NA NACRM-SLS-PEAK sales orders per PEAK TIME 0 NA 0 0CRM-SLSCO-AVERAGE sales contracts per YEAR 0 0 NA NACRM-SLSCO-PEAK sales contracts per PEAK TIME 0 NA 0 0

OBJECTS % CHG % DISP MONTHS ST TIME END TIMECRM-LEAD-AVERAGE sales leads per YEAR NA 0 NA NACRM-LEAD-PEAK sales leads per PEAK TIME NA NA 0 0CRM-ACT-AVERAGE sales activities per YEAR NA 0 NA NACRM-ACT-PEAK sales activities per PEAK TIME NA NA 0 0CRM-APP-AVERAGE sales appointments per YEAR NA 0 NA NACRM-APP-PEAK sales appointments per PEAK TIME NA NA 0 0CRM-OPP-AVERAGE sales opportunities per YEAR NA 0 NA NACRM-OPP-PEAK sales opportunities per PEAK TIME NA NA 0 0

THRUPUT SIZING FOR CRM Acc for BP's--If you complete this section, you must resolve all "ERROR" messages.

THRUPUT SIZING FOR CRM SALES--If you complete this section, you must resolve all "ERROR" messages.

E36

These are the estimated SAPS if this workload is adding to an existing SAP CRM system. If this is a new installation, SAP recommends at least 2000 SAPS.

B40

These are the total number of new created accounts (individual or corporate) per year. This is used to calculate disk and will be used to calculate CPU if you put nothing in the PEAK row.

D40

These are the total number of changed accounts (individual or corporate) per year. This is used to calculate disk and will be used to calculate CPU if you put nothing in the PEAK row.

E40

These are the total number of displayed accounts (individual or corporate) per year. This is used to calculate disk and will be used to calculate CPU if you put nothing in the PEAK row.

F40

These are the total number of accounts accounts (individual or corporate) managed in the CRM system per year. This is used to calculate Disk.

B41

These are the total number of new created accounts (individual or corporate) per PEAK time period. This is used to calculate CPU.

D41

These are the total number of changed accounts (individual or corporate) per PEAK time period. This is used to calculate CPU.

E41

These are the total number of displayed accounts (individual or corporate) per PEAK time period. This is used to calculate CPU.

G41


H41


B42

These are the total number of new created accounts (individual or corporate) per year. This is used to calculate disk and will be used to calculate CPU if you put nothing in the PEAK row.

D42


E42


F42

These are the total number of accounts accounts (individual or corporate) managed in the CRM system per year. This is used to calculate Disk.

B43

These are the total number of new created accounts (individual or corporate) per PEAK time period. This is used to calculate CPU.

D43

These are the total number of changed accounts (individual or corporate) per PEAK time period. This is used to calculate CPU.

E43

These are the total number of displayed accounts (individual or corporate) per PEAK time period. This is used to calculate CPU.

G43


H43


B46


C46


D46


E46


A49

Enter customer orders that are entered thru CRM. This may be thru the call center or thru Internet self service or other ways.

B54

If you enter the number of OBJECTS you MUST enter ITEMS and MONTHS but NOT ST TIME and END TIME. These are the average number of sales quotations(OBJECTS) per year. This is used to calculate disk and will be used to calculate CPU if you put nothing in the PEAK row.

C54


D54


E54


F54

Enter the number of MONTHS this data(OBJECTS) will remain online before being archived.

B55

If you enter the number of OBJECTS, you MUST enter LINES and ST TIME and END TIME but NOT MONTHS. These are the number of sales quotations(OBJECTS) processed during the peak or highest time period; usually an hour or a couple of hours. You specify the time period that these peak OBJECTS are processed using the ST TIME and END TIME columns. This is used to calculate CPU requirements.

C55


D55


E55


G55


H55


B56

If you enter the number of OBJECTS you MUST enter ITEMS and MONTHS but NOT ST TIME and END TIME. These are the average number of sales orders(OBJECTS) per year. This is used to calculate disk and will be used to calculate CPU if you put nothing in the PEAK row.

C56


D56


E56


F56


B57

If you enter the number of OBJECTS, you MUST enter LINES and ST TIME and END TIME but NOT MONTHS. These are the number of sales orders(OBJECTS) processed during the peak or highest time period; usually an hour or a couple of hours. You specify the time period that these peak OBJECTS are processed using the ST TIME and END TIME columns. This is used to calculate CPU requirements.

C57


D57


E57


G57


H57


B58

If you enter the number of OBJECTS you MUST enter ITEMS and MONTHS but NOT ST TIME and END TIME. These are the average number of sales contracts(OBJECTS) per year. This is used to calculate disk and will be used to calculate CPU if you put nothing in the PEAK row.

C58


D58


E58


F58


B59

If you enter the number of OBJECTS, you MUST enter LINES and ST TIME and END TIME but NOT MONTHS. These are the number of sales contracts(OBJECTS) processed during the peak or highest time period; usually an hour or a couple of hours. You specify the time period that these peak OBJECTS are processed using the ST TIME and END TIME columns. This is used to calculate CPU requirements.

C59


D59


E59


G59


H59


B62

If you enter the number of OBJECTS you MUST enter ITEMS and MONTHS but NOT ST TIME and END TIME. These are the average number of sales leads(OBJECTS) per year. This is used to calculate disk and will be used to calculate CPU if you put nothing in the PEAK row.

D62


E62


F62


B63

If you enter the number of OBJECTS, you MUST enter LINES and ST TIME and END TIME but NOT MONTHS. These are the number of sales leads(OBJECTS) processed during the peak or highest time period; usually an hour or a couple of hours. You specify the time period that these peak OBJECTS are processed using the ST TIME and END TIME columns. This is used to calculate CPU requirements.

D63


E63


G63


H63


B64

If you enter the number of OBJECTS you MUST enter ITEMS and MONTHS but NOT ST TIME and END TIME. These are the average number of sales activities(OBJECTS) per year. This is used to calculate disk and will be used to calculate CPU if you put nothing in the PEAK row.

D64


E64


F64


B65

If you enter the number of OBJECTS, you MUST enter LINES and ST TIME and END TIME but NOT MONTHS. These are the number of sales activities(OBJECTS) processed during the peak or highest time period; usually an hour or a couple of hours. You specify the time period that these peak OBJECTS are processed using the ST TIME and END TIME columns. This is used to calculate CPU requirements.

D65


E65


G65


H65


B66

If you enter the number of OBJECTS you MUST enter ITEMS and MONTHS but NOT ST TIME and END TIME. These are the average number of sales appointments(OBJECTS) per year. This is used to calculate disk and will be used to calculate CPU if you put nothing in the PEAK row.

D66


E66


F66


B67

If you enter the number of OBJECTS, you MUST enter LINES and ST TIME and END TIME but NOT MONTHS. These are the number of sales appointments(OBJECTS) processed during the peak or highest time period; usually an hour or a couple of hours. You specify the time period that these peak OBJECTS are processed using the ST TIME and END TIME columns. This is used to calculate CPU requirements.

D67


E67


G67


H67


B68

If you enter the number of OBJECTS you MUST enter ITEMS and MONTHS but NOT ST TIME and END TIME. These are the average number of sales opportunities(OBJECTS) per year. This is used to calculate disk and will be used to calculate CPU if you put nothing in the PEAK row.

D68


E68


F68


B69

If you enter the number of OBJECTS, you MUST enter LINES and ST TIME and END TIME but NOT MONTHS. These are the number of sales opportunities(OBJECTS) processed during the peak or highest time period; usually an hour or a couple of hours. You specify the time period that these peak OBJECTS are processed using the ST TIME and END TIME columns. This is used to calculate CPU requirements.

D69


E69


G69


H69


USER-BASED SIZING FOR CRM SERVICELOW MEDIUM HIGH ext SAPS GB-Storage

Users doing CRM Service Transactions-PEAK PER HOUR 0 0

OBJECTS ITEMS % CHG % DISP MONTHS ST TIME END TIMECRM-SRVQC-AVERAGE service order quotes per YEAR 0 0 NA NACRM-SRVQC-PEAK service order quotes per PEAK TIME 0 NA 0 0CRM-SRV-AVERAGE service orders per YEAR 0 0 NA NACRM-SRV-PEAK service orders per PEAK TIME 0 NA 0 0CRM-SRVCC-AVERAGE service contracts/quotes per YEAR 0 0 NA NACRM-SRVCC-PEAK service contracts/quotes per PEAK TIME 0 NA 0 0CRM-CPLT-AVERAGE compliants/returns/repairs per YEAR 0 0 NA NACRM-CPLT-PEAK complaints/returns/repairs per PEAK TIME 0 NA 0 0CRM-WCL-AVERAGE warranty claims per YEAR 0 0 NA NACRM-WCL-PEAK warranty claims per PEAK TIME 0 NA 0 0

OBJECTS % CHG % DISP MONTHS ST TIME END TIMECRM-SRVAC-AVERAGE service activities per YEAR 0 NA NACRM-SRVAC-PEAK service activities per PEAK TIME NA 0 0CRM-CONF-AVERAGE service confirmations per YEAR 0 NA NACRM-CONF-PEAK service confirmations per PEAK TIME NA 0 0

VISITS % ORD ITEMS IPC MONTHS ST TIME END TIMEAVERAGE Internet sales orders and visits per YEAR NA 0 0 No 0 NA NAPEAK Internet sales orders and visits per PEAK TIME NA 0 0 No NA 0 0

USER-BASED SIZING FOR CRM INTERACTION CENTERLOW MEDIUM HIGH ext SAPS GB-Storage

Total users in the Call Center(CIC)-PEAK PER HOUR 0 0

OBJECTS % CHG % DISP MONTHS ST TIME END TIME

THRUPUT SIZING FOR CRM SERVICE--If you complete this section, you must resolve all "ERROR" messages.

THRUPUT SIZING FOR CRM E-COMMERCE--If you complete this section, you must resolve all "ERROR" messages.

THRUPUT SIZING FOR CRM IC--If you complete this section, you must resolve all "ERROR" messages.

B72


C72


D72


E72


B77

If you enter the number of OBJECTS you MUST enter ITEMS and MONTHS but NOT ST TIME and END TIME. These are the average number of service order quotes(OBJECTS) per year. This is used to calculate disk and will be used to calculate CPU if you put nothing in the PEAK row.

C77


D77


E77


F77


B78

If you enter the number of OBJECTS, you MUST enter LINES and ST TIME and END TIME but NOT MONTHS. These are the number of service order quotes(OBJECTS) processed during the peak or highest time period; usually an hour or a couple of hours. You specify the time period that these peak OBJECTS are processed using the ST TIME and END TIME columns. This is used to calculate CPU requirements.

C78


D78


E78


G78


H78


B79

If you enter the number of OBJECTS you MUST enter ITEMS and MONTHS but NOT ST TIME and END TIME. These are the average number of service orders(OBJECTS) per year. This is used to calculate disk and will be used to calculate CPU if you put nothing in the PEAK row.

C79


D79


E79


F79


B80

If you enter the number of OBJECTS, you MUST enter LINES and ST TIME and END TIME but NOT MONTHS. These are the number of service orders(OBJECTS) processed during the peak or highest time period; usually an hour or a couple of hours. You specify the time period that these peak OBJECTS are processed using the ST TIME and END TIME columns. This is used to calculate CPU requirements.

C80


D80


E80


G80


H80


B81

If you enter the number of OBJECTS you MUST enter ITEMS and MONTHS but NOT ST TIME and END TIME. These are the average number of service contracts and contract quotes(OBJECTS) per year. This is used to calculate disk and will be used to calculate CPU if you put nothing in the PEAK row.

C81


D81


E81


F81


B82

If you enter the number of OBJECTS, you MUST enter LINES and ST TIME and END TIME but NOT MONTHS. These are the number of service contracts and contract quotes(OBJECTS) processed during the peak or highest time period; usually an hour or a couple of hours. You specify the time period that these peak OBJECTS are processed using the ST TIME and END TIME columns. This is used to calculate CPU requirements.

C82


D82


E82


G82


H82


B83

If you enter the number of OBJECTS you MUST enter ITEMS and MONTHS but NOT ST TIME and END TIME. These are the average number of complaints, returns and inhouse repairs(OBJECTS) per year. This is used to calculate disk and will be used to calculate CPU if you put nothing in the PEAK row.

C83


D83


E83


F83


B84

If you enter the number of OBJECTS, you MUST enter LINES and ST TIME and END TIME but NOT MONTHS. These are the number of complaints, returns and inhouse repairs(OBJECTS) processed during the peak or highest time period; usually an hour or a couple of hours. You specify the time period that these peak OBJECTS are processed using the ST TIME and END TIME columns. This is used to calculate CPU requirements.

C84


D84


E84


G84


H84


B85

If you enter the number of OBJECTS you MUST enter ITEMS and MONTHS but NOT ST TIME and END TIME. These are the average number of warranty claims(OBJECTS) per year. This is used to calculate disk and will be used to calculate CPU if you put nothing in the PEAK row.

C85


D85


E85


F85


B86

If you enter the number of OBJECTS, you MUST enter LINES and ST TIME and END TIME but NOT MONTHS. These are the number of warranty claims(OBJECTS) processed during the peak or highest time period; usually an hour or a couple of hours. You specify the time period that these peak OBJECTS are processed using the ST TIME and END TIME columns. This is used to calculate CPU requirements.

C86


D86


E86


G86


H86


B89

If you enter the number of OBJECTS you MUST enter ITEMS and MONTHS but NOT ST TIME and END TIME. These are the average number of service activities(OBJECTS) per year. This is used to calculate disk and will be used to calculate CPU if you put nothing in the PEAK row.

D89


E89


F89


B90

If you enter the number of OBJECTS, you MUST enter LINES and ST TIME and END TIME but NOT MONTHS. These are the number of service activities(OBJECTS) processed during the peak or highest time period; usually an hour or a couple of hours. You specify the time period that these peak OBJECTS are processed using the ST TIME and END TIME columns. This is used to calculate CPU requirements.

D90


E90


G90


H90


B91

If you enter the number of OBJECTS you MUST enter ITEMS and MONTHS but NOT ST TIME and END TIME. These are the average number of service confirmations(OBJECTS) per year. This is used to calculate disk and will be used to calculate CPU if you put nothing in the PEAK row.

D91


E91


F91


B92

If you enter the number of OBJECTS, you MUST enter LINES and ST TIME and END TIME but NOT MONTHS. These are the number of service confirmations(OBJECTS) processed during the peak or highest time period; usually an hour or a couple of hours. You specify the time period that these peak OBJECTS are processed using the ST TIME and END TIME columns. This is used to calculate CPU requirements.

D92


E92


G92


H92


B96

If you enter VISITS you must also enter % ORD, ITEMS and MONTHS. Enter the number of VISITS to the internet website for the entire year.

D96

Enter the percentage of times that an Internet website visit results in a customer order.

E96


F96

No says that the Internet Price Configurator will NOT be used.

G96


B97

If you enter VISITS you must also enter % ORD, ITEMS ST TIME and END TIME. Enter the number of VISITS to the internet website during the peak or highest time period; usually an hour or a couple of hours. You specify the time period that these peak VISITS are processed using the ST TIME and END TIME columns. This is used to calculate CPU requirements.

D97

Enter the percentage of times that an Internet website visit results in a customer order.

E97


F97

No says that the Internet Price Configurator will NOT be used.

H97


I97


B100


C100


D100


E100


A101

For user-based sizing SAP assumes that the CIC creates additional load. Basic load is created by the business transactions called through CIC, such as Opportunity Management, Activity Management, Sales Transaction, and Service Transaction. Therefore SAP recommends you enter a CIC user in the line for CIC as well as in the line of the respective business transaction.

AVERAGE calls/emails in customer center per YEAR NA 0 NA NAPEAK calls/emails in customer center per PEAK TIME NA NA 0 0

USER-BASED SIZING FOR CRM MOBILELOGONS ext SAPS GB-Storage

MSA-USER--Users synchronizing laptops-PEAK PER HOUR 0 0

OBJECTS ITEMS % CHG % DISP MONTHS ST TIME END TIMEAVERAGE orders thru Mobile Sales and Service per YEAR 0 0 NA NAPEAK orders thru Mobile Sales and Service per PEAK TIME 0 NA 0 0

Campaign Execution sizing Guidance Click for sizing white paperBus Part Activities Int Objects e-mails to BW ST TIME END TIME ext SAPS

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

TPM-Trade Promotions ManagementPromotions Products Periods Keyfigures Plng Cells Partners PR_REB Rec CDET Rec

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

SEM/BI ABAP SAPS DB SAPS GB's-Memory GB StorageRendering the planning layout 0 0

THRUPUT SIZING FOR CRM MOBILE--If you complete this section, you must resolve all "ERROR" messages.

https://websmp204.sap-ag.de/~sapdownload/011000358700002188352004E/Sizing_Campaign_Exec_40.pdf

B105

If you enter OBJECTS you must also enter MONTHS. Enter all calls and emails(OBJECTS) handled by the customer interaction center for the entire year. This is used to size disk storage.

D105


E105


F105


B106

If you enter OBJECTS you must also enter ST TIME and END TIME. Enter all calls and emails(OBJECTS) handled by the customer interaction center during the peak or highest time period; usually an hour or a couple of hours. You specify the time period that these peak OBJECTS are processed using the ST TIME and END TIME columns. This is used to calculate CPU requirements.

D106


E106


G106


H106


E109


A110

Enter maximum # of logons per hour for synchronizing laptops only. If you want to size for handhelds or using NetWeaver Mobile please use the MISC tab in this questionnaire.

D110

Enter the maximum logons per hour for laptop synchronization with CRM

B114

If you enter the number of OBJECTS you MUST enter ITEMS and MONTHS but NOT ST TIME and END TIME. These are the average number of Mobile Sales and Service Orders(OBJECTS) per year. This is used to calculate disk and will be used to calculate CPU if you put nothing in the PEAK row.

C114


D114


E114


F114


B115

If you enter the number of OBJECTS, you MUST enter LINES and ST TIME and END TIME but NOT MONTHS. These are the number of Mobile Sales and Service Orders(OBJECTS) processed during the peak or highest time period; usually an hour or a couple of hours. You specify the time period that these peak OBJECTS are processed using the ST TIME and END TIME columns. This is used to calculate CPU requirements.

C115


D115


E115


G115


H115


A117

This provides you with control over the marketing campaign process, including design, execution, coordination and monitoring. This guidance is based on the SAP white paper dated 2004.

B117


I118


D119

Will you be creating interaction objects or interactive responses in this campaign?

A126

TPM is used to plan and coordinate temporary marketing activities with retailers. This includes Key Figure Planning with the Volumes/Trade Spends Tab and Condition Record Generation. It is based on the SAP Whitepaper dated December, 2008.

B128

Enter the total number of promotions during the peak hour of the year.

C128

Enter the number of products included in these promotions.

D128

Enter the number of time periods in weeks for these promotions.

E128

Enter the number if key figures in these promotions.

F128

Enter the number of price/rebate condition records. See white paper for determining this.

G128

Enter the number if key figures in these promotions.

H128

Enter the number of price/rebate condition records. See white paper for determining this.

I128

Enter the number of campaign determination condition records. See white paper for determining this.

A129

TPM has a component incorporated within CRM.

B129


C129


B130

This is the estimated number of SAPS of capacity requirement.

C130


B131


C131


B132


C132


B133


C133


B134


C134


A137

TPM relies on planning information from SEM.

B137


C137


B138

This is the estimated number of SAPS or capacity requirement.

C138


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

B139


C139


© Copyright IBM Corp. April-2008 QUICKSIZER SIZING FOR NetWeaver BW & SEM

What release of BI/SEM are you implementing 7What time does the AVERAGE workday start 9:00What time does the AVERAGE workday end 18:00What time does the PEAK load start 12:00 What time does the PEAK load end 13:00






Enter total CONCURRENT users during the peak hour--A user must NOT be counted twiceHe is either one type of user or another--NOT both at the same time during the peak hourSEM Business Planning

SEM Users STEPS ChngRec Data/Step Data/User ST TIME END TIMEBusiness 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:00Business Planning and Simulations Group 3-PEAK 30 5000 10000 25000 12:00 13:00



B4

SAP Qser is currently sizing BI 7.0

B5


B6


B7


B8


B19


D19


F19


B20


D20


F20


B21


D21


F21


B22


D22


F22


B23


D23


F23


B35

If you enter USERS all other columns must also be completed. Enter the maximum number of concurrent SEM planning users for this group. This is used to size CPU.

C35

Enter the number of planning STEPS per user. NOT the total STEPS. Default for this group is 6.

D35

Enter the average number of data records manipulated by one single planning STEP. Default for this group is 30000.

E35

Enter the maximum number of data records manipulated by one single planning step. Default for this group is 60000.

F35

Enter the maximum number of data records a user holds in memory simultaneously to change. This is used to estimate memory. Default for this group is 200000.

G35

Enter the time of day that the peak of these users will be starting their largest planning and simulation work. Default for this is the overall Peak Start Time.

H35

Enter the time of day that the peak of these users will be ending their largest planning and simulation work. Default for this group is the overall Peak End time.

B36


C36


D36


E36


F36


G36


H36


B37


C37


D37


E37


F37


G37


H37


0

BW(fill in the number of concurrently active BW users)BW Users % Report % OLAP % Explore Web IP BWA B.P ST TIME END TIME

BW-INFO-typically 71% of all BI users 80 20 0 yes no no 1 NA NABW-BUSIN-typically 26% of all BI users 50 50 0 yes no no 1 NA NABW-EXPERT-typically 3% of all BI users 0 0 100 yes no no 1 NA NA

0

RECORDS ST TIME END TIMEData record uploads NA NA NA NA 0 0

INFOCUBESDIMEN KEY FIG INITIAL PERIODIC PERIODS BWA % MD D Values % DVL % DV1

INFOCUBE-DISK-Duplicate as needed 0 no 10 7

DATASTORE OBJECTSNUMFLD TXTFLD Character WO INITIAL PERIODIC PERIODS

DS OBJECTS-DISK-Duplicate as needed no 0

C41

Enter the percentage of time these users will be viewing predefined, static reports. Default for BI-INFO users is 80%.

D41

Enter the percentage of time these users will be doing OLAP Analysis. Slicing and dicing, navigating in reports, using various aggregates. Default for BI-INFO users is 20%.

E41

Enter the percentage of time these users will be doing Data Exploration. Data mining, ad-hoc reports with unpreditable navigation paths, access of detail data, full table scans.. Default for BI-INFO users is 0%.

F41

In NetWeaver BI reporting can be done either through Excel based BEx Analyzer or through a Web browser which receives HTML documents from a JAVA engines. If these users are BEx enter no. If Web enter yes. If both, insert and copy an additional line for this user type. Default is yes.

G41

Another property of queries which has an impact on sizing is their input capability. Usually, queries used for Integrated Planning are ready for input. If a query can accept input, then you need to check the flag "IP". Like in the case above, you have to create separate lines in table 2 for users who use input queries and for those who don't. Default is no.

H41

If this user type is planning to use BWA enter yes.

I41

Enter the average number of basis providers (InfoCubes which are replicated to BWA) per query used in BWA. Default is 1.

B42

If you enter BI Users you must also enter all other columns or let them default. Enter the maximum number of concurrently active BI-INFO(1 navigation step or 9 SD dialog steps per hour) users during the overall PEAK time of BI activity. This is used to size CPU.

B43

If you enter BI Users you must also enter all other columns or let them default. Enter the maximum number of concurrently active BI-BUSIN(11 navigation steps or 99 SD dialog steps per hour) users during the overall PEAK time of BI activity. This is used to size CPU.

B44

If you enter BI Users you must also enter all other columns or let them default. Enter the maximum number of concurrently active BI-EXPERT(33 navigation steps or 297 SD dialog steps per hour) users during the overall PEAK time of BI activity. This is used to size CPU.

B48

If you enter RECORDS you must also enter ST TIME and END TIME. Enter the PEAK number of BI records that you will be uploading between the ST TIME and END TIME. This is used to calculate CPU requirements.

G48


H48


B53

If you enter DIMEN you must enter KEY FIG. You must also enter a value in either INITIAL OR PERIODIC/PERIODS OR both. Enter the number of dimensions(evaluation groups or characteristics) for this CUBE. Maximum is 13.

C53

If you enter KEY FIG you must enter DIMEN. You must also enter a value in either INITIAL OR PERIODIC/PERIODS OR both. Enter the number of key figures, that is--values or quantities, such as sales revenue, fixed costs, sales quantity, number of employees, etc.

D53

Enter the number of records you plan to load into the cube initially.

E53

If you enter a value in PERIODIC you MUST also enter a value in PERIODS. Enter the estimated number of records which you plan to load during your periodic upload process. This number of records will most likely grow over time so plan to enter an estimated average over your time period.

F53

If you enter a value in PERIODS you MUST enter a value in PERIODIC. Enter the total number of periodic uploads which will be kept in the InfoCube before being discarded or archived. For example, if you do a periodic upload weekly and want to keep two years of these uploads, you would enter 52*2 or 104.

G53

Enter yes if this InfoCube should be replicated to BW Accelerator. Default is no.

H53

Enter the percentage of master data on total InfoCube size. Data equals sum of MD and InfoCube data. If master data is shared enter 0 if already considered. Default is 10%.

I53

Enter the average number of different values over all key figure columns.

J53

Enter the percentage of key figures columns with very low number of distinct values (sparse).

K53

Enter the percentage of key figure columns with one distinct value (super spares).

B58

If you enter NUMFLD you must enter a value in either INITIAL OR PERIODIC/PERIODS OR both. Enter the number of numeric fields in the DataStore Object.

C58

If you enter TXTFLDS you must enter a value in either INITIAL OR PERIODIC/PERIODS OR both. Enter the number of text fields in the DataStore Object.

D58

Enter the average length of character fields in the DataStore Objects in Bytes.

E58

Is this Datastore write-optimized?

F58

Enter the number of records you plan to load into the cube initially.

G58

If you enter a value in PERIODIC you MUST enter a value in PERIODS. Enter the estimated number of records which you plan to load during your periodic upload process. This number of records will most likely grow over time so plan to enter an estimated average over your time period.

H58

If you enter a value in PERIODS you MUST enter a value in PERIODIC. Enter the total number of periodic uploads which will be kept in the InfoCube before being discarded or archived. For example, if you do a periodic upload weekly and want to keep two years of these uploads, you would enter 52*2 or 104.

© Copyright IBM Corp. April-2008 QUICKSIZER SIZING FOR PORTAL

What release of Enterprise Portal are you implementing 7






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

USERS Think time Java iViews URL iViewsNW-EP-URL-PEAK 600 0 1NW-EP-INT-PEAK 211 3 0NW-EP-PCC-PEAK 180 3 0NW-EP-PRT-PEAK 0 0 0Total Users 0



B4

SAP Qser is currently sizing EP 7.0

B15


D15


F15


B16


D16


F16


B17


D17


F17


B18


D18


F18


B19


D19


F19


A31

These users are simply using the portal to launch transactions in the back-end system. Portal pages typically contain a single URL iView (no Java iViews). This is an example of a lightweight portal application such as employee or manager self service.

B31

If you enter USERS you must also enter Think time and either Java iViews or URL iViews or both. Enter the maximum number of concurrent URL portal users during the peak hour. This is used to size CPU.

C31

Enter the elapsed time between two successive "clicks" of a user to the portal system. Default for this scenario is 600 seconds.

D31

Enter the number of Java iViews of a typical portal page for this scenario. A Java iView retrieves business content from back-end systems via Jco/RFC and renders the unformatted business content in HTML. Default for this scenario is 0.

E31

Enter the number of URL iViews of a typical portal page for this scenario. For a URL iView, the portal generates the URL and sends it to the browser. The browser then sends the URL to the back-end system and retrieves the HTML content. Default for this scenario is 1.

A32

These users use the portal as an Enterprise Information Portal. They typically read news, access documents, and occasionally launch transactions to OTHER business systems. This is an example of a medium-weight portal application.

B32

If you enter USERS you must also enter Think time and either Java iViews or URL iViews or both. Enter the maximum number of concurrent INT portal users during the peak hour. This is used to size CPU.

C32


D32


E32


A33

These users use the portal for People-Centric CRM type scenarios. They typically launch BSP-based CRM transactions, display overview information from CRM or BI. This is an example of a medium to heavy-weight portal application.

B33

If you enter USERS you must also enter Think time and either Java iViews or URL iViews or both. Enter the maximum number of concurrent PCC portal users during the peak hour. This is used to size CPU.

C33


D33


E33


A34

You should use this scenario to define custom scenarios for which you know detailed architecture information of the iViews.

B34

If you enter USERS you must also enter Think time and either Java iViews or URL iViews or both. Enter the maximum number of concurrent PRT portal users during the peak hour. This is used to size CPU.

C34

Enter the elapsed time between two successive "clicks" of a user to the portal system. There is no default for this scenario.

D34

Enter the number of Java iViews of a typical portal page for this scenario. A Java iView retrieves business content from back-end systems via Jco/RFC and renders the unformatted business content in HTML. There is no default for this scenario.

E34

Enter the number of URL iViews of a typical portal page for this scenario. For a URL iView, the portal generates the URL and sends it to the browser. The browser then sends the URL to the back-end system and retrieves the HTML content. There is no default for this scenario.

LOGONSMaximum number of logons per PEAK hour

NetWeaver Portal Knowledge Management and CollaborationAcc Docs New Docs Size Rooms MONTHS ST TIME END TIME

NW-KMC-Documents per TIME Period 0 700 4000 0 NA NANW-KMC-PEAK Documents per PEAK TIME 0 NA NA NA 0 0

B38

Enter the maximum number of users that will logon during the PEAK hour.

B42

Enter the number of documents that are accessed. Accessed means searching, sorting, opening folders, opening documents, viewing document properties, cut&paste, etc. Assumes 45% are accessed from collaboration rooms.

C42

Enter the number of documents created. This includes creation, uploading, copy&paste, create folder, etc. Assumes 45% of new documents are structured in collaboration rooms.

D42

Enter the average file size in KB. Default is 700 KB.

E42

Enter the number of collaboration rooms. 4000 is the default and is the biggest currently known installation.

A43

KM provides a central, role-specific point of entry to unstructured information from various data sources such as text, presentations or HTML files. This information is available thru file servers, intranets or Internets. Access is provided thru the portal. This data may be managed thru SAP Content Server, other content management solutions as well as thru KM facilities. KM uses the search capabilities of TREX. For storage; in addition to the space needed for all content, add 4 kB's for each document stored in KM facilities plus 1MB for each virtual room.

B43

If you enter the number of Accessed Documents you MUST enter New Docs, Size and MONTHS but NOT ST TIME and END TIME. These are the average number of Accessed Documents per time period. A year will usually be too big. This is used to calculate disk and will be used to calculate CPU if you put nothing in the PEAK row.

C43

Enter number of New Documents created.

D43

Enter the average sizing in KB of the file.

E43

Enter the number of collaboration rooms.

F43


A44


B44

If you enter the number of Accessed Documents you MUST enter New Docs, Size and ST TIME and END TIME But not MONTHS. These are the average number of Accessed Documents per peak time period. This is used to calculate CPU.

C44

Enter number of New Documents created.

G44

Enter the time of day that the peak of these Documents will start being accessed or created. Default for this is the overall Peak Start Time.

H44

Enter the time of day that the peak of these Documents will stop being accessed or created. Default for this is the overall Peak End Time.

© Copyright IBM Corp. April-2008 QUICKSIZER SIZING FOR PROCESS INTEGRATION

What release of PI are you implementing 7What time does the PEAK load start 12:00 What time does the PEAK load end 13:00






PI ADVANCED SIZING FOR INTEGRATION SERVERXML 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 ENGINEXML 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



B4

SAP Qser is currently sizing PI 7.0

B5


B6


B17


D17


F17


B18


D18


F18


B19


D19


F19


B20


D20


F20


B21


D21


F21


A29

PI ADVANCED is used when you know quite a bit about how you expect to use PI. You have developed the architecture for PI and understood how PI is going to be used. This requires more knowledge of the expected PI environment.

B31

If you enter XML SIZE KB you must enter Messages, ST TIME and END TIME. Enter the average size of messages for this scenario.

C31

Enter the PEAK number of outbound messages to be processed in a given timeframe for this scenario.

D31

Enter whether the sender application must wait for a successful delivery response from the receiver(synchronous) or whether the sender application does not have to wait(asynchronous). Default is asynchronous.

E31

Inbound adapters receive requests from sending applications. Enter the adapter type from the pull-down list. Default is none.

F31

Outbound adapters send requests to receiving applications. Enter the adapter type from the pull-down list. Default is none.

G31

Is this an integrated scenario? Default is no.

H31

Business Process Management(BPM) allows for specific business processes to be enacted for certain message types. Enter the BPM scenario from the drop-down list. Most BPM scenarios are asynchronous. Default for this is none.

I31


J31


A33

PI Non-Central is used to size for specific adapter engines which are separate from central PI. The non-central adapter engine runs on the J2EE engine.

B35

If you enter XML SIZE KB you must enter Messages, ST TIME and END TIME. Enter the average size of messages for this scenario.

C35

Enter the PEAK number of outbound messages to be processed in a given timeframe for this scenario.

D35

Enter whether the sender application must wait for a successful delivery response from the receiver(synchronous) or whether the sender application does not have to wait(asynchronous). Default is asynchronous.

E35

Inbound adapters receive requests from sending applications. Enter the adapter type from the pull-down list. Default is none.

F35

Outbound adapters send requests to receiving applications. Enter the adapter type from the pull-down list. Default is none.

G35

Is this an integrated scenario? Default is no.

H35


I35


© Copyright IBM Corp. April-2008 QUICKSIZER SIZING FOR TREX

What release of TREX are you implementing 7What time does the PEAK load start 12:00 What time does the PEAK load end 13:00






THRUPUT SIZING FOR TREXSearches Indexed data Delta Index NA NA ST TIME END TIME

TREX-SRCH-PEAK TREX Searches per PEAK TIME NA NA 0 0



B4

SAP Qser is currently sizing TREX 7.0. Be aware that as of TREX 7.1, the platform will be Intel (Windows and Linux) only per SAP Note 965097.

B5


B6


B17


D17


F17


B18


D18


F18


B19


D19


F19


B20


D20


F20


B21


D21


F21


B31

If you enter the number of Searches, you MUST enter ST TIME and END TIME. These are the number of TREX Searches processed during the peak or highest time period; usually an hour or a couple of hours. You specify the time period that these peak Searches are processed using the ST TIME and END TIME columns. This is used to calculate CPU requirements.

C31

Enter the number of GB's of storage for the indexed data volume on which the TREX search is performed.

D31

Enter the number of GB's of storage for the delta index run during this time period.

G31


H31


© Copyright IBM Corp. April-2008 QUICKSIZER SIZING FOR Solution Manager

What release of Solution Manager are you implementing 7What time does the AVERAGE workday start 12:00 What time does the AVERAGE workday end 13:00






USER SIZING FOR Solution ManagerLOW 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



B4

SAP Qser is currently sizing TREX 7.0. Be aware that as of TREX 7.1, the platform will be Intel (Windows and Linux) only per SAP Note 965097.

B5


B6


B17


D17


F17


B18


D18


F18


B19


D19


F19


B20


D20


F20


B21


D21


F21


B30

Low users change screens every 6 minutes during the peak hour. These users cause only a slight amount of workload so putting users in this category affects the sizing only slightly.

C30

Medium users change screens every 30 seconds during the peak hour. If you're not sure, you might put all of your users in the medium category.

D30

High users change screens every 10 seconds during the peak hour. Typically, high users are less than 20% of your total user count for any application.

© Copyright IBM Corp. April-2008 QUICKSIZER SIZING FOR SCM

What release of SCM are you implementing 5What time does the AVERAGE workday start 9:00What time does the AVERAGE workday end 18:00What time does the PEAK load start 12:00 What time does the PEAK load end 13:00






QuickSizer customer number QuickSizer project name

THRUPUT SIZING FOR DEMAND PLANNINGCharCom 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 TIMEDP-RUN-Planning Run Sizing for CPU NA NA NA 0 0 0



B4

SAP Qser is currently sizing SCM 5.0

B5


B6


B7


B8


B19


D19


F19


B20


D20


F20


B21


D21


F21


B22


D22


F22


B23


D23


F23


A31

SCM-APO is a highly specialized application requiring significant application knowledge. It is very important that an SAP SCM-APO specialist from either SAP or your implementation partner be involved in completing these SCM-APO questions. We highly recommend that you consider putting your answers in this SCM-APO tab directly into the SAP QuickSizer. The QuickSizer may be found at http://service.sap.com/quicksizing. This site requires an SAP supplied username and password which can be obtained from SAP.

B36

If you enter CharCom you MUST also enter KeyFig and Period. Characteristics are attributes that describe what is planned. Examples include item code, UPC, brand name, market segment, location and customer name. Enter the product of all the characteristics being planned.

C36

Key figures hold the data input and output quantities that are stored in a single fact table for each InfoCube. Examples include sales history, demand forecast and percent promotion increase. Enter the sum of the key figures used in planning.

D36

Periods is the count of time buckets used in planning. An annual forecast in weekly time buckets is 52. Annual forecast of 12 weeks followed by 8 months is 12+8*4=42 because all data is stored in the smallest time unit.

E36

Fill in either Com Index or Times/Periods but not both. Compression index. Enter the expected compression index. Default is 5.

F36

Fill in either Com Index or Times/Periods but not both. Percentage of compressed timeseries.

G36

Fill in either Com Index or Times/Periods but not both. Number of time buckets in compressed timeseries.

H36

Total number of planning versions stored in LiveCache.

B39

If you enter CharCom you MUST also enter Time Buck and ST TIME and END TIME. Characteristics are attributes that describe what is planned. Examples include item code, UPC, brand name, market segment, location and customer name. Enter the product of all the characteristics being planned.

F39

Number of time buckets used in planning.

G39


H39


APO Users ST TIME END TIMEDP-USER-Additional Users for CPU NA NA NA NA 0 0

THRUPUT SIZING FOR SUPPLY & PRODUCTION PLANNINGLOC PROD Resources

MASTERDAT-Master data Sizing for LiveCache memory

SCM OBJSTOCK-Warehouse Stocks Sizing for LiveCache memory

SCM OBJ Components OPER ACT/OP ALT/RES ParCapPLANNEDORD-Planned orders Sizing for LiveCache memory 0 0 0

SCM OBJ SUB OBJFORECAST-Forecast orders Sizing for LiveCache memory 0PURCHORD-Purchase orders Sizing for LiveCache memory 0SALES-Sales orders Sizing for LiveCache memory 0TRANSFER-Transfer orders Sizing for LiveCache memory 0

SKUs Time Buck ST TIME END TIMESNP-RUN-Heuristic plan Sizing for CPU--PEAK NA NA NA 0 0 0

APO User ST TIME END TIMEPP USER-Planning Board User Sizing for CPU--PEAK NA NA NA NA 0 0SNP USER-SNP User Sizing for CPU--PEAK NA NA NA NA 0 0

THRUPUT SIZING FOR ORDER FULFILLMENTLoc prod

ATP-MD-ATP Masterdata Sizing for LiveCache memory

Requests ST TIME END TIMEATP-SIMPLE-ATP simple checks Sizing for CPU--PEAK NA NA NA NA 0 0ATP-RULE-ATP rules based checks Sizing for CPU--PEAK NA NA NA NA 0 0ATP-CTP-ATP Capable to promise checks Sizing for CPU--PEAK NA NA NA NA 0 0

THRUPUT SIZING FOR SERVICE PARTS PLANNINGSKUs ST TIME END TIME

SPP-STK-Stocking--PEAK NA NA NA NA 0 0

B42

If you enter APO Users you MUST also enter ST TIME and END TIME. Enter the number of planners using interactive planning.

G42


H42


B46

Total number of product-location(LOC PROD) combinations. Enter the sum of all of the product locations being planned at each location.

C46

Resources used in APO can define work centers, or production lines and tools used in the manufacturing of products. Determine the number of resources used in APO planning for both Supply Network Planning and Detailed Scheduling. Enter the numbers of resources(work centers, production lines, tools) to be planned.

B49

Enter the count of the detailed warehouse stock locations (SCM OBJ) used in planning including any sub locations or batching.

B52

If SCM OBJ is entered you must enter Components, OPER and ACT/OP. Enter the average number of planning relevant planned orders.

C52

The average number of bill of material components per manufacturing order.

D52

Enter the average number of operations per manufacturing order.

E52

Enter the average number of operations steps or activities per operation used for planning.

F52

Enter the average number of alterative resources(production line, work center, etc) that can be used for each activity.

G52

Enter the average number of parallel capacity requirements or constraining resources per operation step/activity.

B55

IF SCM OBJ is entered then SUB OBJ must also be entered. Enter the number of forecast orders(SCM OBJ) used for planning. This is also the total number of product-location combinations.

C55

Enter the average number of schedule lines per forecast or the number of partitions made for each time bucket.

B56

IF SCM OBJ is entered then SUB OBJ must also be entered. Enter the number of purchase orders or purchase requisitions(SCM OBJ) used for planning.

C56

Enter the average number of delivery schedules or transports per purchase order.

B57

IF SCM OBJ is entered then SUB OBJ must also be entered. Enter the number of sales orders(SCM OBJ) used for planning.

C57

Enter the average number of delivery schedules or transports per sales order.

B58

IF SCM OBJ is entered then SUB OBJ must also be entered. Enter the number of internal stock transfer orders(SCM OBJ) used for planning.

C58

Enter the average number of products per transfer order.

B61

If you enter SKUs you MUST also enter Time Buck and ST TIME and END TIME. Enter the number of SKUs planned in this heuristic planning run.

F61


G61


H61


B64

If you enter APO Users you MUST also enter ST TIME and END TIME. Enter the number of planners using interactive Planning Board planning.

G64


H64


B65

If you enter APO Users you MUST also enter ST TIME and END TIME. Enter the number of planners using interactive Supply Network Planning.

G65


H65


A69

Global availability to check(ATP)

B69

Total number of locations for which an availability to promise check is possible.

B72

If you enter Requests you MUST also enter ST TIME and END TIME and Loc prod. The simple ATP check is carried out based on the ATP quantity (Available-To-Promise). The ATP quantity is calculated from stock, planned receipts (production orders, purchase orders, planned orders and so on), and planned requirements (sales orders, deliveries, reservations and so on). Enter the number of online searches that are done during this time period to ensure that your company can provide the requested product at the requested time in the requested quantity.

G72

Enter the time of day that the peak of these Requests will start processing. Default for this is the overall Peak Start Time.

H72

Enter the time of day that the peak of these Requests will end processing. Default for this is the overall Peak End Time.

B73

If you enter Requests you MUST also enter ST TIME and END TIME and Loc prod. The rules based ATP check is an iterative process, every check defines the next check according to the rules in the system. Enter the number of online searches that are done during this time period to ensure that your company can provide the requested product at the requested time in the requested quantity.

G73


H73


B74

If you enter Requests you MUST also enter ST TIME and END TIME and Loc prod. The Capable-to-Promise(CTP) allows you to create planned orders or purchase requisitions for missing products. Enter the number of online searches that are done during this time period to ensure that your company can provide the requested product at the requested time in the requested quantity.

G74


H74


B78

If you enter SKUs you MUST also enter ST TIME and END TIME. Enter the number of SKUs planned for all possible product locations.

G78


H78


SPP-DESTK-Destocking--PEAK NA NA NA NA 0 0SPP-EOQ-Economic order quantity--PEAK NA NA NA NA 0 0SPP-DPLY-Deployment--PEAK NA NA NA NA 0 0

Period Based Planning SKUs Time Buck ST TIME END TIMESPP-FCST-Forecasting--PEAK NA NA NA 0 0 0

DRP Run Matrices ROP Stk PB Stk. M Loc PoD 1 PoD 2 Hor1 SPP-DRP-Distribution requirements planning--PEAK

SNC-Purchase Order CollaborationProfile SAPS Storage

Initial Sizing--See whitepaper on the QuickSizer website 0 0

SNC-Release ProcessingProfile SAPS Storage


SNC-Supplier Managed Inventory-SNIProfile SAPS Storage


THRUPUT SIZING FOR INTEGRATION TO ECCSCM objects Items ST TIME END TIME

PI-PROD-PEAK Manufacturing Orders per PEAK TIME 0 NA NA NA 0 0PI-SALES-PEAK Sales Orders per PEAK TIME 0 NA NA NA 0 0PI-PURCH-PEAK Purchase Orders per PEAK TIME 0 NA NA NA 0 0PI-STOCKL-PEAK Stock movements per PEAK TIME 1 NA NA NA 0 0

THRUPUT SIZING FOR EWM INBOUNDOBJECTS ITEMS % CHG % DISP MONTHS ST TIME END TIME

IEWM-DLV-AVERAGE Inbound delivery documents per YEAR 0 0 NA NAIEWM-DLV-PEAK Inbound delivery documents per PEAK TIME 0 NA 0 0

Ware tasks % DISP MONTHS ST TIME END TIMEIEWM-UNTSK-AVERAGE creation of unloading tasks per YEAR NA NA 0 NA NAIEWM-UNTSK-PEAK creation of unloading tasks per PEAK TIME NA NA NA 0 0IEWM-CONF-AVERAGE confirm of unloading tasks per YEAR NA NA 0 NA NA

B79

If you enter SKUs you MUST also enter ST TIME and END TIME. Enter the number of SKUs planned for all possible product locations.

G79


H79


B80

If you enter SKUs you MUST also enter ST TIME and END TIME. Enter the number of SKUs planned for all stocked product locations.

G80


H80


B81

If you enter SKUs you MUST also enter ST TIME and END TIME. Enter the number of SKUs planned for all product locations along the bill of distribution.

G81


H81


B84

If you enter SKUs you MUST also enter Time Buck and ST TIME and END TIME. Enter the number of SKUs planned for historical and planning horizon in monthly or weekly buckets.

F84


G84


H84


B87

If you enter Matrices you MUST also enter Loc and ST TIME and END TIME. Enter the total number of Matrices both stocked and unstocked calculated by DRP.

C87

Number of reorder point based matrices which are stocked

D87

Number of period based matrices which are stocked

E87

Average number of locations in the BoD-subtree below an entry location including the entry location.

F87

PoD/EOQ days on entry location.

G87

PoD/EOQ days on entry location.

H87

Freeze Horizon in working days.

B91

Enter the appropriate profile: Small = Up to 10 concurrent users. Medium = Up to 50 concurrent users. Medium = Up to 100 concurrent users.

B95


B99


B104

If you enter the number of SCM objects you MUST enter Items and ST TIME and END TIME. These are the PEAK number of production orders transferred from/to the ECC system.

C104

Enter the average number of components in the production order(Items)

G104

Enter the time of day that the peak of these Messages will start processing. Default for this is the overall Peak Start Time.

H104

Enter the time of day that the peak of these Messages will end processing. Default for this is the overall Peak End Time.

B105

If you enter the number of SCM objects you MUST enter Items and ST TIME and END TIME. These are the PEAK number of sales orders transferred from/to the ECC system.

C105

Enter the average number of schedule lines in the sales order(Items)

G105


H105


B106

If you enter the number of SCM objects you MUST enter Items and ST TIME and END TIME. These are the PEAK number of purchase orders transferred from/to the ECC system.

C106

Enter the average number of schedule lines in the purchase order(Items)

G106


H106


B107

If you enter the number of SCM objects you MUST enter ST TIME and END TIME. These are the PEAK number of stock movements transferred from/to the ECC system. Items is set at 1.

C107

Enter the average number of stock movements(Items). This is always 1.

G107


H107


A111

Mandatory--Inbound Step--Creation of Inbound Delivery

B111

If you enter the number of OBJECTS you MUST enter ITEMS and MONTHS but NOT ST TIME and END TIME. These are the average number of delivery documents(OBJECTS) per year. This is used to calculate disk and will be used to calculate CPU if you put nothing in the PEAK row.

C111

Enter the average number of ITEMS per delivery. NOT total line items.

D111


E111


F111


A112

Mandatory--Inbound Step--Creation of Inbound Delivery

B112

If you enter the number of OBJECTS, you MUST enter ITEMS and ST TIME and END TIME but NOT MONTHS. These are the number of delivery documents(OBJECTS) processed during the peak or highest time period; usually an hour or a couple of hours. You specify the time period that these peak OBJECTS are processed using the ST TIME and END TIME columns. This is used to calculate CPU requirements.

C112


D112


E112


G112


H112


A115

Optional--Inbound Steps--Creation of Unloading Warehouse Tasks.

B115

If you enter the number of warehouse tasks(Ware tasks) you MUST enter MONTHS but NOT ST TIME and END TIME. These are the average number of creations of unloading warehouse tasks. These are assumed to be 100% RF. This is used to calculate disk and will be used to calculate CPU if you put nothing in the PEAK row.

E115


F115


A116

Optional--Inbound Steps--Creation of Unloading Warehouse Tasks.

B116

If you enter the number of warehouse tasks(Ware tasks), you MUST enter ST TIME and END TIME but NOT MONTHS. These are the number of creations of unloading warehouse tasks processed during the peak or highest time period; usually an hour or a couple of hours. These are assumed to be 100% RF. You specify the time period that these peak OBJECTS are processed using the ST TIME and END TIME columns. This is used to calculate CPU requirements.

E116


G116


H116


A117

Optional--Inbound Steps--Confirmation of Unloading Warehouse Tasks.

B117

If you enter the number of warehouse tasks(Ware tasks) you MUST enter MONTHS but NOT ST TIME and END TIME. These are the average number of confirmations of unloading warehouse tasks. These are assumed to be 100% RF. This is used to calculate disk and will be used to calculate CPU if you put nothing in the PEAK row.

E117


F117


IEWM-CONF-PEAK confirm of unloading tasks per PEAK TIME NA NA NA 0 0

Ware tasks % DISP MONTHS ST TIME END TIMEIEWM-PATSK-AVERAGE creation of putaway tasks per YEAR NA NA 0 NA NAIEWM-PATSK-PEAK creation of putaway tasks per PEAK TIME NA NA NA 0 0

Ware tasks % RF % DISP MONTHS ST TIME END TIMEIEWM-PACON-AVERAGE confirm of putaway tasks per YEAR NA 0 NA NAIEWM-PACON-PEAK confirm of putaway tasks per PEAK TIME NA NA 0 0

Ware tasks RsChg % DISP MONTHS ST TIME END TIMEIEWM-RESPA-AVERAGE chg/resource of putaway tasks per YEAR NA 0 NA NAIEWM-RESPA-PEAK chg/resource of putaway tasks per PEAK TIME NA NA 0 0

HU's Put. It. Unpk Items % DISP ST TIME END TIMEIEWM-DECON-AVERAGE unpacking of putaway tasks per YEAR 0 NA NA NAIEWM-DECON-PEAK unpacking of putaway tasks per PEAK TIME 0 NA 0 0

Ware tasks % DISP MONTHS ST TIME END TIMEIEWM-MOVE-AVERAGE move warehouse tasks per YEAR NA NA 0 NA NAIEWM-MOVE-PEAK move warehouse tasks per PEAK TIME NA NA NA 0 0

Ware tasks RsChg % DISP MONTHS ST TIME END TIMEIEWM-RESFI-AVERAGE chg/resource of packing tasks per YEAR 0 NA 0 NA NAIEWM-RESFI-PEAK chg/resource of packing tasks per PEAK TIME 0 NA NA 0 0

THRUPUT SIZING FOR EWM OUTBOUNDOBJECTS ITEMS % CHG % DISP MONTHS ST TIME END TIME

OEWM-DLV-AVERAGE Outbound delivery documents per YEAR 0 0 NA NAOEWM-DLV-PEAK Outbound delivery documents per PEAK TIME 0 NA 0 0

Ware tasks % DISP MONTHS ST TIME END TIMEOEWM-PICK-AVERAGE creation of picking tasks per YEAR NA NA 0 NA NAOEWM-PICK-PEAK creation of picking tasks per PEAK TIME NA NA NA 0 0

Ware tasks % RF % DISP MONTHS ST TIME END TIMEOEWM-CONF-AVERAGE confirmation of picking tasks per YEAR NA 0 NA NAOEWM-CONF-PEAK confirmation of picking tasks per PEAK TIME NA NA 0 0

A118

Optional--Inbound Steps--Confirmation of Unloading Warehouse Tasks.

B118

If you enter the number of warehouse tasks(Ware tasks), you MUST enter ST TIME and END TIME but NOT MONTHS. These are the number of confirmations of unloading warehouse tasks processed during the peak or highest time period; usually an hour or a couple of hours. These are assumed to be 100% RF. You specify the time period that these peak OBJECTS are processed using the ST TIME and END TIME columns. This is used to calculate CPU requirements.

E118


G118


H118


A121

Mandatory--Inbound Step--Creation of Putaway Warehouse Tasks (Without Preceding Unloading Task)

B121

If you enter the number of warehouse tasks(Ware tasks) you MUST enter MONTHS but NOT ST TIME and END TIME. These are the average number of putaway tasks without preceding unloading warehouse task. This is used to calculate disk and will be used to calculate CPU if you put nothing in the PEAK row.

E121


F121


A122

Mandatory--Inbound Step--Creation of Putaway Warehouse Tasks (Without Preceding Unloading Task)

B122

If you enter the number of warehouse tasks(Ware tasks), you MUST enter ST TIME and END TIME but NOT MONTHS. These are the number of putaway tasks without preceding unloading warehouse task during the peak or highest time period; usually an hour or a couple of hours. You specify the time period that these peak OBJECTS are processed using the ST TIME and END TIME columns. This is used to calculate CPU requirements.

E122


G122


H122


A125

Mandatory--Inbound Step--Confirmation of Putaway Warehouse Tasks.

B125

If you enter the number of warehouse tasks(Ware tasks) you MUST enter MONTHS but NOT ST TIME and END TIME. These are the average number of confirmation of putaway tasks. This is used to calculate disk and will be used to calculate CPU if you put nothing in the PEAK row.

C125

Enter the percentage of these Ware task confirmations that are RF based.

E125


F125


A126

Mandatory--Inbound Step--Confirmation of Putaway Warehouse Tasks.

B126

If you enter the number of warehouse tasks(Ware tasks), you MUST enter ST TIME and END TIME but NOT MONTHS. These are the number of confirmations of putaway tasks during the peak or highest time period; usually an hour or a couple of hours. You specify the time period that these peak OBJECTS are processed using the ST TIME and END TIME columns. This is used to calculate CPU requirements.

C126


E126


G126


H126


A129

Optional--Inbound Step--Change of Resource in Putaway Task.

B129

If you enter the number of warehouse tasks(Ware tasks) you MUST enter MONTHS but NOT ST TIME and END TIME. These are the number of warehouse tasks with resource changes per year. This is used to calculate disk and will be used to calculate CPU if you put nothing in the PEAK row.

C129

Enter the average number of resource changes per Ware task.

E129


F129


A130

Optional--Inbound Step--Change of Resource in Putaway Task.

B130

If you enter the number of warehouse tasks(Ware tasks), you MUST enter ST TIME and END TIME but NOT MONTHS. These are the number of warehouse tasks with resource changes during the peak or highest time period; usually an hour or a couple of hours. You specify the time period that these peak OBJECTS are processed using the ST TIME and END TIME columns. This is used to calculate CPU requirements.

C130


E130


G130


H130


A133

Optional--Inbound Step--Deconsolidation ((Un)Packing and Creation of Follow-Up Move Warehouse Task for Putaway)

B133

If you enter the number of highest-level handling units(HU's) after deconsolidation you MUST enter putaway items (Put. It.) but NOT ST TIME and END TIME. These are the average number of HU's per year. This is used to calculate disk and will be used to calculate CPU if you put nothing in the PEAK row.

C133


D133

Enter the number of unpacked items.

E133


A134

Optional--Inbound Step--Deconsolidation ((Un)Packing and Creation of Follow-Up Move Warehouse Task for Putaway)

B134

If you enter the number of highest-level handling units(HU's) you MUST enter putaway items (Put. It.) and ST TIME and END TIME. These are the number of HU's during the peak or highest time period; usually an hour or a couple of hours. You specify the time period that these peak OBJECTS are processed using the ST TIME and END TIME columns. This is used to calculate CPU requirements.

C134


D134

Enter the number of unpacked items.

E134


G134


H134


A137

Optional--Inbound Step--Move Warehouse Task (From Deconsolidation Station to Final Bin)

B137

If you enter the number of warehouse tasks(Ware tasks) you MUST enter MONTHS but NOT ST TIME and END TIME. These are the average number of warehouse tasks from deconsolidation station to final bin per year. 100% RF is assumed This is used to calculate disk and will be used to calculate CPU if you put nothing in the PEAK row.

E137


F137


A138

Optional--Inbound Step--Move Warehouse Task (From Deconsolidation Station to Final Bin)

B138

If you enter the number of warehouse tasks(Ware tasks), you MUST enter ST TIME and END TIME but NOT MONTHS. These are the number of move warehouse tasks from deconsolidation station to final bin during the peak or highest time period; usually an hour or a couple of hours. 100% RF is assumed. You specify the time period that these peak OBJECTS are processed using the ST TIME and END TIME columns. This is used to calculate CPU requirements.

E138


G138


H138


A141

Optional--Inbound Step--Change of Resource in Movement from Deconsolidation Packing to Final Bin.

B141

If you enter the number of warehouse tasks(Ware tasks) you MUST enter resource changes(RsChg) and MONTHS but NOT ST TIME and END TIME. These are the number of warehouse tasks with resource changes per year. This is used to calculate disk and will be used to calculate CPU if you put nothing in the PEAK row.

C141


E141


F141


A142

Optional--Inbound Step--Change of Resource in Movement from Deconsolidation Packing to Final Bin.

B142

If you enter the number of warehouse tasks(Ware tasks), you MUST enter resource changes (RsChg) and ST TIME and END TIME but NOT MONTHS. These are the number of warehouse tasks with resource changes during the peak or highest time period; usually an hour or a couple of hours. You specify the time period that these peak OBJECTS are processed using the ST TIME and END TIME columns. This is used to calculate CPU requirements.

C142


E142


G142


H142


A146

Mandatory--Outbound Step--Creation of Outbound Delivery Order

B146


C146


D146


E146


F146


A147

Mandatory--Outbound Step--Creation of Outbound Delivery Order

B147


C147


D147


E147


G147


H147


A150

Mandatory--Outbound Steps--Creation of Picking Warehouse Tasks.

B150

If you enter the number of warehouse tasks(Ware tasks) you MUST enter MONTHS but NOT ST TIME and END TIME. These are the average number of creations of unloading warehouse tasks. These are assumed to be 100% RF. This is used to calculate disk and will be used to calculate CPU if you put nothing in the PEAK row.

E150


F150


A151

Mandatory--Outbound Steps--Creation of Picking Warehouse Tasks.

B151

If you enter the number of warehouse tasks(Ware tasks), you MUST enter ST TIME and END TIME but NOT MONTHS. These are the number of creations of unloading warehouse tasks processed during the peak or highest time period; usually an hour or a couple of hours. These are assumed to be 100% RF. You specify the time period that these peak OBJECTS are processed using the ST TIME and END TIME columns. This is used to calculate CPU requirements.

E151


G151


H151


A154

Mandatory--Outbound Step--Confirmation of Picking Warehouse Tasks.

B154

If you enter the number of warehouse tasks(Ware tasks) you MUST enter MONTHS but NOT ST TIME and END TIME. These are the average number of putaway tasks without preceding unloading warehouse task. This is used to calculate disk and will be used to calculate CPU if you put nothing in the PEAK row.

C154


E154


F154


A155

Mandatory--Outbound Step--Confirmation of Picking Warehouse Tasks.

B155

If you enter the number of warehouse tasks(Ware tasks), you MUST enter ST TIME and END TIME but NOT MONTHS. These are the number of putaway tasks without preceding unloading warehouse task during the peak or highest time period; usually an hour or a couple of hours. You specify the time period that these peak OBJECTS are processed using the ST TIME and END TIME columns. This is used to calculate CPU requirements.

C155


E155


G155


H155


Ware tasks % DISP MONTHS ST TIME END TIMEOEWM-DEST-AVERAGE move warehouse tasks per YEAR NA NA 0 NA NAOEWM-DEST-PEAK move warehouse tasks per PEAK TIME NA NA NA 0 0

Ware tasks RsChg % DISP MONTHS ST TIME END TIMEOEWM-RESPI-AVERAGE chg/resource of picking tasks per YEAR 0 NA 0 NA NAOEWM-RESPI-PEAK chg/resource of picking tasks per PEAK TIME 0 NA NA 0 0

HU's Pick It. % DISP ST TIME END TIMEOEWM-PACK-AVERAGE packing tasks per YEAR 0 NA NA NA NAOEWM-PACK-PEAK packing tasks per PEAK TIME 0 NA NA 0 0

Ware tasks % DISP MONTHS ST TIME END TIMEOEWM-STAGE-AVERAGE move warehouse tasks per YEAR NA NA 0 NA NAOEWM-STAGE-PEAK move warehouse tasks per PEAK TIME NA NA NA 0 0

Ware tasks RsChg % DISP MONTHS ST TIME END TIMEOEWM-RESST-AVERAGE chg/resource tasks per YEAR 0 NA 0 NA NAOEWM-RESST-PEAK chg/resource tasks per PEAK TIME 0 NA NA 0 0

Ware tasks % DISP MONTHS ST TIME END TIMEOEWM-LOAD-AVERAGE warehouse loading tasks per YEAR NA NA 0 NA NAOEWM-LOAD-PEAK warehouse loading tasks per PEAK TIME NA NA NA 0 0

OBJECTS ITEMS % CHG % DISP MONTHS ST TIME END TIMEOEWM-GOODS-AVERAGE Outbound delivery documents per YEAR 0 0 NA NAOEWM-GOODS-PEAK Outbound delivery documents per PEAK TIME 0 NA 0 0

A158

Optional--Outbound Step--Move Warehouse Task (From Picking Resource to Picking Destination Bin)

B158

If you enter the number of warehouse tasks(Ware tasks) you MUST enter MONTHS but NOT ST TIME and END TIME. These are the average number of move warehouse tasks from resource to picking destination. This is used to calculate disk and will be used to calculate CPU if you put nothing in the PEAK row.

E158


F158


A159

Optional--Outbound Step--Move Warehouse Task (From Picking Resource to Picking Destination Bin)

B159

If you enter the number of warehouse tasks(Ware tasks), you MUST enter ST TIME and END TIME but NOT MONTHS. These are the number of move warehouse tasks from resource to picking destination during the peak or highest time period; usually an hour or a couple of hours. You specify the time period that these peak OBJECTS are processed using the ST TIME and END TIME columns. This is used to calculate CPU requirements.

E159


G159


H159


A162

Optional--Outbound Step--Change of Resource in Picking Task.

B162

If you enter the number of warehouse tasks(Ware tasks) you MUST enter RsChg and MONTHS but NOT ST TIME and END TIME. These are the number of warehouse tasks with resource changes per year. This is used to calculate disk and will be used to calculate CPU if you put nothing in the PEAK row. Assumed 100% RF.

C162


E162


F162


A163

Optional--Outbound Step--Change of Resource in Picking Task.

B163

If you enter the number of warehouse tasks(Ware tasks), you MUST enter RsChg and ST TIME and END TIME but NOT MONTHS. These are the number of warehouse tasks with resource changes during the peak or highest time period; usually an hour or a couple of hours. You specify the time period that these peak OBJECTS are processed using the ST TIME and END TIME columns. This is used to calculate CPU requirements. Assumed 100% RF

C163


E163


G163


H163


A166

Optional--Outbound Step--Packing and Creation of Follow-Up Move Warehouse Task.

B166

If you enter the number of highest-level handling units(HU's) you MUST enter putaway items (Put. It.) but NOT ST TIME and END TIME. These are the average number of HU's created in packing per year. This is used to calculate disk and will be used to calculate CPU if you put nothing in the PEAK row.

C166

Enter the average number of pick items packed per ship highest-level HU.

E166


A167

Optional--Outbound Step--Packing and Creation of Follow-Up Move Warehouse Task.

B167

If you enter the number of highest-level handling units(HU's) you MUST enter putaway items (Put. It.) and ST TIME and END TIME. These are the number of HU's created in packing during the peak or highest time period; usually an hour or a couple of hours. You specify the time period that these peak OBJECTS are processed using the ST TIME and END TIME columns. This is used to calculate CPU requirements.

C167

Enter the average number of pick items packed per ship highest-level HU.

E167


G167


H167


A170

Optional--Outbound Step--Move Warehouse Task (From Packing Station to Staging Areas)

B170

If you enter the number of warehouse tasks(Ware tasks) you MUST enter MONTHS but NOT ST TIME and END TIME. These are the average number of staging original warehouse tasks per year. 100% RF is assumed This is used to calculate disk and will be used to calculate CPU if you put nothing in the PEAK row.

E170


F170


A171

Optional--Outbound Step--Move Warehouse Task (From Packing Station to Staging Areas)

B171

If you enter the number of warehouse tasks(Ware tasks), you MUST enter ST TIME and END TIME but NOT MONTHS. These are the number of staging original warehouse tasks during the peak or highest time period; usually an hour or a couple of hours. 100% RF is assumed. You specify the time period that these peak OBJECTS are processed using the ST TIME and END TIME columns. This is used to calculate CPU requirements.

E171


G171


H171


A174

Optional--Outbound Step--Change of Resource in Staging.

B174

If you enter the number of warehouse tasks(Ware tasks) you MUST enter resource changes(RsChg) and MONTHS but NOT ST TIME and END TIME. These are the number of warehouse tasks with resource changes per year. This is used to calculate disk and will be used to calculate CPU if you put nothing in the PEAK row.

C174

Enter the average number of resource changes per Ware task. Assume 100% RF.

E174


F174


A175

Optional--Outbound Step--Change of Resource in Staging.

B175

If you enter the number of warehouse tasks(Ware tasks), you MUST enter resource changes (RsChg) and ST TIME and END TIME but NOT MONTHS. These are the number of warehouse tasks with resource changes during the peak or highest time period; usually an hour or a couple of hours. You specify the time period that these peak OBJECTS are processed using the ST TIME and END TIME columns. This is used to calculate CPU requirements.

C175

Enter the average number of resource changes per Ware task. Assume 100% RF

E175


G175


H175


A178

Optional--Outbound Step--Loading Warehouse Task.

B178

If you enter the number of warehouse tasks(Ware tasks) you MUST enter MONTHS but NOT ST TIME and END TIME. These are the number of loading warehouse tasks per year. This is used to calculate disk and will be used to calculate CPU if you put nothing in the PEAK row. Assume 100% RF.

E178


F178


A179

Optional--Outbound Step--Loading Warehouse Task.

B179

If you enter the number of warehouse tasks(Ware tasks), you MUST enter ST TIME and END TIME but NOT MONTHS. These are the number of loading warehouse tasks during the peak or highest time period; usually an hour or a couple of hours. You specify the time period that these peak OBJECTS are processed using the ST TIME and END TIME columns. This is used to calculate CPU requirements. Assume 100% RF.

E179


G179


H179


A182

Mandatory--Outbound Step--Delivery based Goods Issue.

B182


C182


D182


E182


F182


A183

Mandatory--Outbound Step--Delivery based Goods Issue.

B183


C183


D183


E183


G183


H183


© Copyright IBM Corp. April-2008 QUICKSIZER SIZING FOR SRM

What release of SRM are you implementing 7What time does the AVERAGE workday start 9:00What time does the AVERAGE workday end 18:00What time does the PEAK load start 12:00 What time does the PEAK load end 13:00






Operational PurchasingActive Users - Standard Sizing

LOW MEDIUM HIGHSRM-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 CartSRM-PSC-1U-Users in SRM shopping cart(few complex steps)SRM-PSC-2U-Users in SRM shopping cart(many simple steps)



B4

SAP Qser is currently sizing SRM 7

B5


B6


B7


B8


B19


D19


F19


B20


D20


F20


B21


D21


F21


B22


D22


F22


B23


D23


F23


B33


C33


D33


SRM-CONF-U-Users in SRM ConfirmationSRM-INV-U-Users in SRM InvoiceTOTAL CONCURRENT Peak users 0 0 0 0

THRUPUT - Standard SizingOBJECTS ITEMS % CHG % DISP MONTHS ST TIME END TIME

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

Strategic PurchasingActive Users - Standard Sizing

LOW MEDIUM HIGHSRM-CTR-LU-Users in SRM Lean Contract ManagementSRM-CTR-EU-Users in SRM Extended Contract ManagementSRM-RFX-LU-Users in Lean SRM RFxSRM-RFX-EU-Users in Extended SRM RFxTOTAL CONCURRENT Peak users 0 0 0 0

THRUPUT - Standard SizingOBJECTS ITEMS % CHG % DISP MONTHS ST TIME END TIME

SRM-CTR-L-Lean Contract Management-Contract 0 0 NA NASRM-CTR-L-Lean Contract Management-Contract 0 NA 0 0SRM-CTR-E-Extended Contract Management-Contract 0 0 NA NASRM-CTR-E-Extended Contract Management-Contract 0 NA 0 0SRM-RFX-L-SRM Lean RFx 0 0 NA NASRM-RFX-L-SRM Lean RFx 0 NA 0 0SRM-RFX-E-SRM Extended RFx 0 0 NA NA

B45

If you enter the number of OBJECTS you MUST enter ITEMS and MONTHS but NOT ST TIME and END TIME. These are the average number of contracts or agreements(GOA) (OBJECTS) per year. This is used to calculate disk and will be used to calculate CPU if you put nothing in the PEAK row.

C45


D45


E45


F45


B46

If you enter the number of OBJECTS, you MUST enter ITEMS and ST TIME and END TIME but NOT MONTHS. These are the number of contracts or agreements(GOA)(OBJECTS) processed during the peak or highest time period; usually an hour or a couple of hours. You specify the time period that these peak OBJECTS are processed using the ST TIME and END TIME columns. This is used to calculate CPU requirements.

C46


D46


E46


G46


H46


B47

If you enter the number of OBJECTS you MUST enter ITEMS and MONTHS but NOT ST TIME and END TIME. These are the average number of plan-driven customer orders (OBJECTS) per year. This is used to calculate disk and will be used to calculate CPU if you put nothing in the PEAK row.

C47


D47


E47


F47


B48

If you enter the number of OBJECTS, you MUST enter ITEMS and ST TIME and END TIME but NOT MONTHS. These are the number of plan-driven customer orders(OBJECTS) processed during the peak or highest time period; usually an hour or a couple of hours. You specify the time period that these peak OBJECTS are processed using the ST TIME and END TIME columns. This is used to calculate CPU requirements.

C48


D48


E48


G48


H48


B49

If you enter the number of OBJECTS you MUST enter ITEMS and MONTHS but NOT ST TIME and END TIME. These are the average number of self-service orders(OBJECTS) per year. This is used to calculate disk and will be used to calculate CPU if you put nothing in the PEAK row.

C49


D49


E49


F49


B50

If you enter the number of OBJECTS, you MUST enter ITEMS and ST TIME and END TIME but NOT MONTHS. These are the number of self-service orders(OBJECTS) processed during the peak or highest time period; usually an hour or a couple of hours. You specify the time period that these peak OBJECTS are processed using the ST TIME and END TIME columns. This is used to calculate CPU requirements.

C50


D50


E50


G50


H50


B51

If you enter the number of OBJECTS you MUST enter ITEMS and MONTHS but NOT ST TIME and END TIME. These are the average number of extended orers(OBJECTS) per year. This is used to calculate disk and will be used to calculate CPU if you put nothing in the PEAK row.

C51


D51


E51


F51


B52

If you enter the number of OBJECTS, you MUST enter ITEMS and ST TIME and END TIME but NOT MONTHS. These are the number of extended orders(OBJECTS) processed during the peak or highest time period; usually an hour or a couple of hours. You specify the time period that these peak OBJECTS are processed using the ST TIME and END TIME columns. This is used to calculate CPU requirements.

C52


D52


E52


G52


H52


B53

If you enter the number of OBJECTS you MUST enter ITEMS and MONTHS but NOT ST TIME and END TIME. These are the average number of services orders(OBJECTS) per year. This is used to calculate disk and will be used to calculate CPU if you put nothing in the PEAK row.

C53


D53


E53


F53


B54


C54


D54


E54


G54


H54


B55


C55


D55


E55


F55


B56


C56


D56


E56


G56


H56


B57


C57


D57


E57


F57


B58

If you enter the number of OBJECTS, you MUST enter ITEMS and ST TIME and END TIME but NOT MONTHS. These are the number of services orders(OBJECTS) processed during the peak or highest time period; usually an hour or a couple of hours. You specify the time period that these peak OBJECTS are processed using the ST TIME and END TIME columns. This is used to calculate CPU requirements.

C58


D58


E58


G58


H58


B62


C62


D62


B71

If you enter the number of OBJECTS you MUST enter ITEMS and MONTHS but NOT ST TIME and END TIME. These are the average number of contracts or agreements(GOA) (OBJECTS) per year. This is used to calculate disk and will be used to calculate CPU if you put nothing in the PEAK row.

C71


D71


E71


F71


B72

If you enter the number of OBJECTS, you MUST enter ITEMS and ST TIME and END TIME but NOT MONTHS. These are the number of contracts or agreements(GOA)(OBJECTS) processed during the peak or highest time period; usually an hour or a couple of hours. You specify the time period that these peak OBJECTS are processed using the ST TIME and END TIME columns. This is used to calculate CPU requirements.

C72


D72


E72


G72


H72


B73

If you enter the number of OBJECTS you MUST enter ITEMS and MONTHS but NOT ST TIME and END TIME. These are the average number of plan-driven customer orders (OBJECTS) per year. This is used to calculate disk and will be used to calculate CPU if you put nothing in the PEAK row.

C73


D73


E73


F73


B74

If you enter the number of OBJECTS, you MUST enter ITEMS and ST TIME and END TIME but NOT MONTHS. These are the number of plan-driven customer orders(OBJECTS) processed during the peak or highest time period; usually an hour or a couple of hours. You specify the time period that these peak OBJECTS are processed using the ST TIME and END TIME columns. This is used to calculate CPU requirements.

C74


D74


E74


G74


H74


B75

If you enter the number of OBJECTS you MUST enter ITEMS and MONTHS but NOT ST TIME and END TIME. These are the average number of self-service orders(OBJECTS) per year. This is used to calculate disk and will be used to calculate CPU if you put nothing in the PEAK row.

C75


D75


E75


F75


B76

If you enter the number of OBJECTS, you MUST enter ITEMS and ST TIME and END TIME but NOT MONTHS. These are the number of self-service orders(OBJECTS) processed during the peak or highest time period; usually an hour or a couple of hours. You specify the time period that these peak OBJECTS are processed using the ST TIME and END TIME columns. This is used to calculate CPU requirements.

C76


D76


E76


G76


H76


B77

If you enter the number of OBJECTS you MUST enter ITEMS and MONTHS but NOT ST TIME and END TIME. These are the average number of extended orers(OBJECTS) per year. This is used to calculate disk and will be used to calculate CPU if you put nothing in the PEAK row.

C77


D77


E77


F77


SRM-RFX-E-SRM Extended RFx 0 NA 0 0

B78


C78


D78


E78


G78


H78


END TIME

END TIME

© Copyright IBM Corp. April-2008 QUICKSIZER SIZING FOR GTS

What release of GTS are you implementing 2007What time does the AVERAGE workday start 9:00What time does the AVERAGE workday end 18:00What time does the PEAK load start 12:00 What time does the PEAK load end 13:00






THRUPUT SIZING FOR COMPLIANCE AND CUSTOM MANAGEMENT

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



B4

SAP Qser is currently sizing GTS 2007

B5


B6


B7


B8


B19


D19


F19


B20


D20


F20


B21


D21


F21


B22


D22


F22


B23


D23


F23


A34

GTS Customs Documents (Import/Export Customs Declarations and Customs Shipments, Transit Documents)

B34

If you enter the number of customs documents(OBJECTS) you MUST enter ITEMS and MONTHS but NOT ST TIME and END TIME. These are the average number of customs documents(OBJECTS) per year. This is used to calculate disk and will be used to calculate CPU if you put nothing in the PEAK row.

C34


D34


E34


F34


A35

GTS Customs Documents (Import/Export Customs Declarations and Customs Shipments, Transit Documents)

B35

If you enter the number of customs documents(OBJECTS), you MUST enter ITEMS and ST TIME and END TIME but NOT MONTHS. These are the number of customs documents(OBJECTS) processed during the peak or highest time period; usually an hour or a couple of hours. You specify the time period that these peak OBJECTS are processed using the ST TIME and END TIME columns. This is used to calculate CPU requirements.

C35


D35


E35


G35


H35


A36

GTS Compliance Documents (Sales Orders, Deliveries, Purchase Orders)

B36

If you enter the number of compliance documents(OBJECTS) you MUST enter ITEMS and MONTHS but NOT ST TIME and END TIME. These are the average number of compliance documents(OBJECTS) per year. This is used to calculate disk and will be used to calculate CPU if you put nothing in the PEAK row.

C36


D36


E36


F36


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

OBJECTS MONTHS ST TIME END TIMEGTS-BP-AVERAGE Business Partners per YEAR NA NA NA 0 NA NAGTS-BP-PEAK Business Partners per PEAK TIME NA NA NA NA 0 0GTS-MAT-AVERAGE GTS Materials per YEAR NA NA NA 0 NA NAGTS-MAT-PEAK GTS Materials per PEAK TIME NA NA NA NA 0 0

Bus Partner Documents MONTHS ST TIME END TIMEGTS-SCREEN-AVERAGE Business Partner screenings per YEAR 0 NA NA 0 NA NAGTS-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 TIMEGTS-RI-BOM-AVERAGE BOM transfers per YEAR 0 0 NA NAGTS-RI-BOM-PEAK BOM transfers per PEAK TIME 0 NA 0 0GTS-RI-INV-AVERAGE worklist based on SD Invoices per YEAR 0 0 NA NAGTS-RI-INV-PEAK worklist based on SD Invoices per PEAK TIME 0 NA 0 0GTS-RI-MM-AVERAGE worklist based on MM per YEAR 0 0 NA NAGTS-RI-MM-PEAK worklist based on MM per PEAK TIME 0 NA 0 0GTS-RI-PRD-AVERAGE BOM Preference determination per YEAR 0 0 NA NAGTS-RI-PRD-PEAK BOM Preference determination per PEAK TIME 0 NA 0 0GTS-RI-SO-AVERAGE SD/SO Preference determination per YEAR 0 0 NA NAGTS-RI-SO-PEAK SD/SO Preference determination per PEAK TIME 0 NA 0 0

Customers Prod/cust % CHG MONTHS ST TIME END TIMEGTS-RI-ISS-AVERAGE vendor declarations per YEAR 0 NA 0 NA NAGTS-RI-ISS-PEAK vendor declarations per PEAK TIME 0 NA NA 0 0

Vendors Prod/vend MONTHS ST TIME END TIMEGTS-RI-AGG-AVERAGE vendor declarations per YEAR 0 NA NA 0 NA NAGTS-RI-AGG-PEAK vendor declarations per PEAK TIME 0 NA NA NA 0 0GTS-RI-SOL-AVERAGE vendor solicitations per YEAR 0 NA NA 0 NA NA

A37

GTS Compliance Documents (Sales Orders, Deliveries, Purchase Orders)

B37

If you enter the number of compliance documents(OBJECTS), you MUST enter ITEMS and ST TIME and END TIME but NOT MONTHS. These are the number of compliance documents(OBJECTS) processed during the peak or highest time period; usually an hour or a couple of hours. You specify the time period that these peak OBJECTS are processed using the ST TIME and END TIME columns. This is used to calculate CPU requirements.

C37


D37


E37


G37


H37


A38

Screening of payment proposals(Sanctioned Party List Screening for Financial Accounting)

B38

If you enter the number of screening of payment proposal documents(OBJECTS) you MUST enter ITEMS and MONTHS but NOT ST TIME and END TIME. These are the average number of screening of payments proposal documents(OBJECTS) per year. This is used to calculate disk and will be used to calculate CPU if you put nothing in the PEAK row.

C38


D38


E38


F38


A39

Screening of payment run.

B39

If you enter the number of screening of payment documents(OBJECTS), you MUST enter ITEMS and ST TIME and END TIME but NOT MONTHS. These are the number of screening of payments documents(OBJECTS) processed during the peak or highest time period; usually an hour or a couple of hours. You specify the time period that these peak OBJECTS are processed using the ST TIME and END TIME columns. This is used to calculate CPU requirements.

C39


D39


E39


G39


H39


A42

GTS Business Partners Master data (Vendors, Customers, Employees, etc)

B42

If you enter the number of business partners(OBJECTS) you MUST enter MONTHS but NOT ST TIME and END TIME. These are the average number of business partners(OBJECTS) per year. This is used to calculate disk and will be used to calculate CPU if you put nothing in the PEAK row.

F42


A43

GTS Business Partners Master data (Vendors, Customers, Employees, etc)

B43

If you enter the number of business partners(OBJECTS), you MUST enter ST TIME and END TIME but NOT MONTHS. These are the number of business partners(OBJECTS) processed during the peak or highest time period; usually an hour or a couple of hours. You specify the time period that these peak OBJECTS are processed using the ST TIME and END TIME columns. This is used to calculate CPU requirements.

G43


H43


B44

If you enter the number of GTS materials(OBJECTS) you MUST enter MONTHS but NOT ST TIME and END TIME. These are the average number of GTS Materials(OBJECTS) per year. This is used to calculate disk and will be used to calculate CPU if you put nothing in the PEAK row.

F44


B45

If you enter the number of GTS Materials(OBJECTS), you MUST enter ST TIME and END TIME but NOT MONTHS. These are the number of GTS materials(OBJECTS) processed during the peak or highest time period; usually an hour or a couple of hours. You specify the time period that these peak OBJECTS are processed using the ST TIME and END TIME columns. This is used to calculate CPU requirements.

G45


H45


A48

GTS Sanctioned Party list screening. Asynchronous or Delta screening of business partners.

B48

If you enter the number of business partners(Bus Partner) you MUST enter Documents and MONTHS but NOT ST TIME and END TIME. These are the average number of business partners(Bus Partner) per year. This is used to calculate disk and will be used to calculate CPU if you put nothing in the PEAK row.

C48

Enter number of documents PER Bus Partner. NOT total documents

F48


A49

GTS Sanctioned Party list screening. Asynchronous or Delta screening of business partners.

B49

If you enter the number of business partners(Bus Partner), you MUST enter Documents and ST TIME and END TIME but NOT MONTHS. These are the number of business partners(Bus Partner) processed during the peak or highest time period; usually an hour or a couple of hours. You specify the time period that these peak OBJECTS are processed using the ST TIME and END TIME columns. This is used to calculate CPU requirements.

C49


G49


H49


A54

For transferring Bills of Materials.

B54

If you enter the number of BOMs transfers(OBJECTS) you MUST enter ITEMS and MONTHS but NOT ST TIME and END TIME. These are the average number of BOM transfers(OBJECTS) per year. This is used to calculate disk and will be used to calculate CPU if you put nothing in the PEAK row.

C54


D54


E54


F54


A55

For transferring Bills of Materials.

B55

If you enter the number of BOM transfers(OBJECTS), you MUST enter ITEMS and ST TIME and END TIME but NOT MONTHS. These are the number of BOM transfers(OBJECTS) processed during the peak or highest time period; usually an hour or a couple of hours. You specify the time period that these peak OBJECTS are processed using the ST TIME and END TIME columns. This is used to calculate CPU requirements.

C55


D55


E55


G55


H55


A56

Worklist for issuing long-term vendor declarations based on SD Invoices. For Invoice Documents being sent to GTS. In case the Invoice Documents are also to be processed within SAP GTS Customs, you should make a separate entry in GTS-CUM.

B56

If you enter the number of worklists(OBJECTS) you MUST enter ITEMS and MONTHS but NOT ST TIME and END TIME. These are the average number of worklists for issuing long-term vendor declarations based on SD Invoices(OBJECTS) per year. This is used to calculate disk and will be used to calculate CPU if you put nothing in the PEAK row.

C56


D56


E56


F56


A57

Worklist for issuing long-term vendor declarations based on SD Invoices. For Invoice Documents being sent to GTS. In case the Invoice Documents are also to be processed within SAP GTS Customs, you should make a separate entry in GTS-CUM.

B57

If you enter the number of worklists(OBJECTS), you MUST enter ITEMS and ST TIME and END TIME but NOT MONTHS. These are the number of worklists for issuing long-term vendor declarations based on SD Invoices.(OBJECTS) processed during the peak or highest time period; usually an hour or a couple of hours. You specify the time period that these peak OBJECTS are processed using the ST TIME and END TIME columns. This is used to calculate CPU requirements.

C57


D57


E57


G57


H57


A58

Worklist for requesting long-term vendor declarations based on MM Purchase Orders and MM Goods Receipts . For MM Documents (Purchase Orders and Goods Receipts) being sent to GTS. In case the Purchase Orders are also to be screened with SAP GTS Compliance, you should make a separate entry in GTS-SLS.

B58

If you enter the number of worklists(OBJECTS) you MUST enter ITEMS and MONTHS but NOT ST TIME and END TIME. These are the average number of worklists for requesting long-term vendor declarations based on MM Purchase Orders and MM Goods Receipts.(OBJECTS) per year. This is used to calculate disk and will be used to calculate CPU if you put nothing in the PEAK row.

C58


D58


E58


F58


A59

Worklist for requesting long-term vendor declarations based on MM Purchase Orders and MM Goods Receipts . For MM Documents (Purchase Orders and Goods Receipts) being sent to GTS. In case the Purchase Orders are also to be screened with SAP GTS Compliance, you should make a separate entry in GTS-SLS.

B59

If you enter the number of worklists(OBJECTS), you MUST enter ITEMS and ST TIME and END TIME but NOT MONTHS. These are the number of worklists for requesting long-term vendor declarations based on MM Purchase Orders and MM Goods Receipts.(OBJECTS) processed during the peak or highest time period; usually an hour or a couple of hours. You specify the time period that these peak OBJECTS are processed using the ST TIME and END TIME columns. This is used to calculate CPU requirements.

C59


D59


E59


G59


H59


A60

For the preference determination of in house production according to Bills of Materials (BOMs).

B60

If you enter the number of (OBJECTS) you MUST enter ITEMS and MONTHS but NOT ST TIME and END TIME. These are the average number of preference determination of bills of material(OBJECTS) per year. This is used to calculate disk and will be used to calculate CPU if you put nothing in the PEAK row.

C60


D60


E60


F60


A61

For the preference determination of in house production according to Bills of Materials (BOMs).

B61

If you enter the number of (OBJECTS), you MUST enter ITEMS and ST TIME and END TIME but NOT MONTHS. These are the number of preference determination of bills of material(OBJECTS) processed during the peak or highest time period; usually an hour or a couple of hours. You specify the time period that these peak OBJECTS are processed using the ST TIME and END TIME columns. This is used to calculate CPU requirements.

C61


D61


E61


G61


H61


A62

For Sales Orders Documents being sent to GTS. In case the Sales Orders are also to be screened with SAP GTS Compliance, you should make a seprate entry in GTS-SLS.

B62

If you enter the number of (OBJECTS) you MUST enter ITEMS and MONTHS but NOT ST TIME and END TIME. These are the average number of preference status determination in the sales process (SD SO)(OBJECTS) per year. This is used to calculate disk and will be used to calculate CPU if you put nothing in the PEAK row.

C62


D62


E62


F62


A63

For Sales Orders Documents being sent to GTS. In case the Sales Orders are also to be screened with SAP GTS Compliance, you should make a seprate entry in GTS-SLS.

B63

If you enter the number of (OBJECTS), you MUST enter ITEMS and ST TIME and END TIME but NOT MONTHS. These are the number of preference status determination in the sales process (SD SO)(OBJECTS) processed during the peak or highest time period; usually an hour or a couple of hours. You specify the time period that these peak OBJECTS are processed using the ST TIME and END TIME columns. This is used to calculate CPU requirements.

C63


D63


E63


G63


H63


A66

For issuing and revocation of long-term vendor declarations.

B66

If you enter the number of customers(Customers) you MUST enter Prod/cust and MONTHS but NOT ST TIME and END TIME. These are the average number of customers(Customers) per year. This is used to calculate disk and will be used to calculate CPU if you put nothing in the PEAK row.

C66

Enter number of products per customer. NOT total products.

D66


F66


A67

For issuing and revocation of long-term vendor declarations.

B67

If you enter the number of customers(Customers), you MUST enter Prod/cust and ST TIME and END TIME but NOT MONTHS. These are the number of customers(Customers) processed during the peak or highest time period; usually an hour or a couple of hours. You specify the time period that these peak Customers are processed using the ST TIME and END TIME columns. This is used to calculate CPU requirements.

C67


D67


G67


H67


A70

Aggregation of long-term vendor declarations. For the preference status aggregation into the GTS product master based on long-term vendor declarations.

B70

If you enter the number of vendors(Vendors) you MUST enter Prod/vend and MONTHS but NOT ST TIME and END TIME. These are the average number of customers(Customers) per year. This is used to calculate disk and will be used to calculate CPU if you put nothing in the PEAK row.

C70

Enter number of products per vendor. NOT total products.

F70


A71

Aggregation of long-term vendor declarations. For the preference status aggregation into the GTS product master based on long-term vendor declarations.

B71

If you enter the number of vendors(Vendors), you MUST enter Prod/vend and ST TIME and END TIME but NOT MONTHS. These are the number of vendors(Vendors) processed during the peak or highest time period; usually an hour or a couple of hours. You specify the time period that these peak Vendors are processed using the ST TIME and END TIME columns. This is used to calculate CPU requirements.

C71


G71


H71


A72

Request of long-term vendor declaration. For the solicitation of long-term vendor declarations.

B72

If you enter the number of vendors(Vendors) you MUST enter Prod/vend and MONTHS but NOT ST TIME and END TIME. These are the average number of vendors(Vendors) per year. This is used to calculate disk and will be used to calculate CPU if you put nothing in the PEAK row.

C72

Enter number of products per vendor. NOT total products.

F72


GTS-RI-SOL-PEAK vendor solicitations per PEAK TIME 0 NA NA NA 0 0

A73

Request of long-term vendor declaration. For the solicitation of long-term vendor declarations.

B73

If you enter the number of vendors(Vendors), you MUST enter Prod/vend and ST TIME and END TIME but NOT MONTHS. These are the number of vendors (Vendors) processed during the peak or highest time period; usually an hour or a couple of hours. You specify the time period that these peak Vendors are processed using the ST TIME and END TIME columns. This is used to calculate CPU requirements.

C73


G73


H73


© Copyright IBM Corp. April-2008 QUICKSIZER SIZING FOR Banking

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






THRUPUT SIZING FOR ANALYTICAL BANKING

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

OBJECTS MONTHSPOSITION-AVERAGE Changed positions per YEAR NA NA NA 0



B4


B5


B6


B7


B18


D18


F18


B19


D19


F19


B20


D20


F20


B21


D21


F21


B22


D22


F22


A33

Upload of the financial data from the front office systems to the source data layer (SDL): For the calculation of the risk weighted assets.

B33

If you enter the number of transactions(OBJECTS), you MUST enter ST TIME and END TIME. These are the number of new or changed business transactions or instruments(OBJECTS) processed during the peak or highest time period; usually an hour or a couple of hours. You specify the time period that these peak OBJECTS are processed using the ST TIME and END TIME columns. This is used to calculate CPU requirements.

G33


H33


A34


B34

If you enter the number of changed positions(OBJECTS), you MUST enter ST TIME and END TIME. These are the number of changed positions(OBJECTS) processed during the peak or highest time period; usually an hour or a couple of hours. You specify the time period that these peak OBJECTS are processed using the ST TIME and END TIME columns. This is used to calculate CPU requirements.

G34


H34


A35

Regulatory reporting consists of writing the enriched data to the cluster and creating a file on the file system. Only the writing of the enriched data is considered in this sizing.

B35

If you enter the regulatory data (OBJECTS), you MUST enter ST TIME and END TIME. These are the number of regulatory documents(OBJECTS) processed during the peak or highest time period; usually an hour or a couple of hours. You specify the time period that these peak OBJECTS are processed using the ST TIME and END TIME columns. This is used to calculate CPU requirements.

G35


H35


A38


B38

If you enter the number of positions(OBJECTS) you MUST enter MONTHS but NOT ST TIME and END TIME. These are the average number of changed positions(OBJECTS) per year. This is used to calculate disk and will be used to calculate CPU if you put nothing in the PEAK row.

F38


OBJECTS Collat/Claims Lines MONTHS Eff matur Cash flow ST TIMECE-RUN-AVERAGE payments on cash flow per YEAR 0 0 0 NA NA NACE-RUN-PEAK payments on cash flow per PEAK TIME NA NA 0

OBJECTS Level 2 ST TIME END TIMEDR-RUN-PEAK Disclosure/reporting documents per PEAK TIME NA NA NA 0 0

THRUPUT SIZING FOR CORE BANKING

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

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

Coll agree Loans ST TIME END TIMEFS-BK-CMS-PEAK Loans per PEAK TIME NA NA NA 0 0

A41

For calculating the risk weighted assets (RWA) in accordance with the Basel II paper and meets the requirements for regulatory reporting.

B41

If you enter the number of payments(OBJECTS) you MUST also enter Collat/Claims, Lines, MONTHS but NOT Eff matur, Cash flow, ST TIME and END TIME. These are the average number of financial transactions or instruments, and objects that are relevant for effective maturity(OBJECTS) per year. This is used to calculate disk and will be used to calculate CPU if you put nothing in the PEAK row.

C41

Enter number of collaterals and claims to be processed.

D41

Enter the number of free lines.

E41


A42

For calculating the risk weighted assets (RWA) in accordance with the Basel II paper and meets the requirements for regulatory reporting.

B42

These are the number of payments(OBJECTS) processed during the peak or highest time period; usually an hour or a couple of hours. You specify the time period that these peak OBJECTS are processed using the ST TIME and END TIME columns. This is used to calculate CPU requirements.

C42

Enter number of collaterals and claims to be processed during this peak time period.

F42

Enter the number of documents that are relevant for effective maturity to be processed during this peak time period.

G42

Enter the number of cash flow documents to be processed during this peak time period.

H42


A45

Data from SDL plus results of the calculation process stored in the RDL and other SAP or non-SAP systems is extracted into BI for reporting.

B45

If you enter the data(OBJECTS), you MUST enter ST TIME and END TIME. These are the number of objects (OBJECTS)extracted for D&R reporting during the peak or highest time period; usually an hour or a couple of hours. You specify the time period that these peak OBJECTS are processed using the ST TIME and END TIME columns. This is used to calculate CPU requirements.

C45

Enter the number of level 2 results.

G45


H45


A50

This is the processing of payment items which includes the validation of the payment items, the posting to the dedicated account, and subsequently the update of balances for the account.

B50

If you enter the number of payment items(OBJECTS) you MUST enter MONTHS. These are the average number of payments items(OBJECTS) per year. This is used to calculate disk and will be used to calculate CPU if you put nothing in the PEAK row.

F50


A51

The settlement process embraces the calculation of interest and period charges for an account and the posting of the results to the settled or a deviate account.

B51

If you enter the number of accounts(OBJECTS) you MUST enter MONTHS. These are the average number of accounts to be settled(OBJECTS) per year. This is used to calculate disk and will be used to calculate CPU if you put nothing in the PEAK row.

F51


A52

The correspondence process embraces the creation of all types of customer correspondences (bank statements, correspondences for contract changes, correspondences for special posting events. This is started asynchronously daily.

B52

If you enter the number of documents(OBJECTS) you MUST enter MONTHS. These are the average number of created correspondence documents(OBJECTS) per year. This is used to calculate disk and will be used to calculate CPU if you put nothing in the PEAK row.

F52


A53

The accrual process embraces the calculation of interest and periodic charges for an account.

B53

If you enter the number of positions(OBJECTS) you MUST enter MONTHS but NOT ST TIME and END TIME. These are the average number of changed positions(OBJECTS) per year. This is used to calculate disk and will be used to calculate CPU if you put nothing in the PEAK row.

F53


A56


B56

If you enter the number of payments(OBJECTS), you MUST enter ST TIME and END TIME. These are the number of mass posting payments(OBJECTS) processed during the peak or highest time period; usually an hour or a couple of hours. You specify the time period that these peak OBJECTS are processed using the ST TIME and END TIME columns. This is used to calculate CPU requirements.

G56


H56


A57


B57

If you enter the number of payments(OBJECTS), you MUST enter ST TIME and END TIME. These are the number of single posting payments(OBJECTS) processed during the peak or highest time period; usually an hour or a couple of hours. You specify the time period that these peak OBJECTS are processed using the ST TIME and END TIME columns. This is used to calculate CPU requirements.

G57


H57


A58


B58

If you enter the number of statements(OBJECTS), you MUST enter ST TIME and END TIME. These are the number of on request bank statements(OBJECTS) processed during the peak or highest time period; usually an hour or a couple of hours. You specify the time period that these peak OBJECTS are processed using the ST TIME and END TIME columns. This is used to calculate CPU requirements.

G58


H58


A59


B59

If you enter the number of accounts(OBJECTS), you MUST enter ST TIME and END TIME. These are the number of accounts to be settled(OBJECTS) processed during the peak or highest time period; usually an hour or a couple of hours. You specify the time period that these peak OBJECTS are processed using the ST TIME and END TIME columns. This is used to calculate CPU requirements.

G59


H59


A60


B60

If you enter the number of correspondences(OBJECTS), you MUST enter ST TIME and END TIME. These are the number of created correspondences(OBJECTS) processed during the peak or highest time period; usually an hour or a couple of hours. You specify the time period that these peak OBJECTS are processed using the ST TIME and END TIME columns. This is used to calculate CPU requirements.

G60


H60


A61


B61

If you enter the number of accounts(OBJECTS), you MUST enter ST TIME and END TIME. These are the number of accounts to be accrued(OBJECTS) processed during the peak or highest time period; usually an hour or a couple of hours. You specify the time period that these peak OBJECTS are processed using the ST TIME and END TIME columns. This is used to calculate CPU requirements.

G61


H61


A64

Collateral management monitoring run.

B64

If you enter the collateral agreements(Coll agree), you MUST enter ST TIME and END TIME. These are the number of collateral agreements(OBJECTS) processed during the peak or highest time period; usually an hour or a couple of hours. You specify the time period that these peak OBJECTS are processed using the ST TIME and END TIME columns. This is used to calculate CPU requirements.

C64

Enter the number of loans processed during this peak period.

G64


H64


END TIME

END TIMENA0

END TIME

END TIME

END TIME

I42


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







OBJECTS Items ST TIME END TIMEACC-STAT-PEAK Invoice/Account statements per PEAK TIME 0 NA NA NA 0 0INS-INV-PEAK Insurance objects per PEAK TIME 0 NA NA NA 0 0

OBJECTS ST TIME END TIMEBROK-ITEM-PEAK Broker report items per PEAK TIME NA NA NA NA 0 0PAY-EXE-PEAK payment plan executions per PEAK TIME NA NA NA NA 0 0PAY-TRANS-PEAK Payment plan transfers per PEAK TIME NA NA NA NA 0 0ACC-BAL-PEAK Account balance displays per PEAK TIME NA NA NA NA 0 0



B4


B5


B6


B7


B18


D18


F18


B19


D19


F19


B20


D20


F20


B21


D21


F21


B22


D22


F22


B31

If you enter the number of invoice/account statments(OBJECTS), you MUST enter Items and ST TIME and END TIME. These are the number of invoices and accounts statements (OBJECTS) processed and printed during the peak or highest time period; usually an hour or a couple of hours. You specify the time period that these peak OBJECTS are processed using the ST TIME and END TIME columns. This is used to calculate CPU requirements.

C31

Enter the number of items(Items) per invoice/account statement(OBJECT). Not the total items.

G31


H31


A32

There are several different kinds of insurance objects. The principal objects used are contract accounts and claims. You can assign several insurance objects to a contract account.

B32

If you enter the number of insurance objects(OBJECTS), you MUST enter Items and ST TIME and END TIME. These are the number of insurance objects(OBJECTS) processed during the peak or highest time period; usually an hour or a couple of hours. You specify the time period that these peak OBJECTS are processed using the ST TIME and END TIME columns. This is used to calculate CPU requirements.

C32

Enter the number of items(Items) per insurance objects(OBJECT). Not the total items.

G32


H32


A35

This is the number of broker report items(reported premiums, claims, commission and cost items) reported by all brokers or intermediaries during the period.

B35

If you enter the number of broker report items(OBJECTS), you MUST enter ST TIME and END TIME. These are the number of broker report items(OBJECTS) reported during the peak or highest time period; usually an hour or a couple of hours. You specify the time period that these peak OBJECTS are processed using the ST TIME and END TIME columns. This is used to calculate CPU requirements.

G35


H35


B36

If you enter the number of payment plan executions(OBJECTS), you MUST enter ST TIME and END TIME. These are the number of payment plan executions(OBJECTS) processed during the peak or highest time period; usually an hour or a couple of hours. You specify the time period that these peak OBJECTS are processed using the ST TIME and END TIME columns. This is used to calculate CPU requirements. The number of open items is relevant for sizing.

G36


H36


B37

If you enter the number of payment plan transfers(OBJECTS), you MUST enter ST TIME and END TIME. These are the number of payment plan transfers(OBJECTS) processed during the peak or highest time period; usually an hour or a couple of hours. You specify the time period that these peak OBJECTS are processed using the ST TIME and END TIME columns. This is used to calculate CPU requirements. The number of open items is relevant for sizing.

G37


H37


B38

If you enter the number of account balance displays(OBJECTS), you MUST enter ST TIME and END TIME. These are the highest number of account balance displays(OBJECTS) that occur during the peak or highest time period; usually an hour or a couple of hours. You specify the time period that these peak OBJECTS are processed using the ST TIME and END TIME columns. This is used to calculate CPU requirements.

G38


H38


OBJECTS Items MONTHSACC-STAT-AVERAGE Invoice/Account statements per YEAR 0 NA NA NA 0INS-INV-AVERAGE Insurance objects per YEAR 0 NA NA NA 0

OBJECTS MONTHSBROK-ITEM-AVERAGE Broker report items per year NA NA NA NA 0PAY-EXE-AVERAGE payment plan executions per year NA NA NA NA 0PAY-TRANS-AVERAGE Payment plan transfers per year NA NA NA NA 0

B41

If you enter the number of invoice/account statements(OBJECTS) you MUST also enter Items and MONTHS. These are the average number of invoice/account statements(OBJECTS) processed per year. This is used to calculate disk and will be used to calculate CPU if you put nothing in the PEAK row.

C41

Enter number of line items(Items) per invoice/account statement(OBJECTS) processed per year.

G41


A42

There are several different kinds of insurance objects. The principal objects used are contract accounts and claims. You can assign several insurance objects to a contract account.

B42

If you enter the number of insurance objects(OBJECTS) you MUST also enter Items and MONTHS. These are the average number of insurance objects(OBJECTS) processed per year. This is used to calculate disk and will be used to calculate CPU if you put nothing in the PEAK row.

C42

Enter number of line items(Items) per insurance object(OBJECTS) processed per year.

G42


A45

This is the number of broker report items(reported premiums, claims, commission and cost items) reported by all brokers or intermediaries during the period.

B45

If you enter the number of broker report items(OBJECTS) you MUST also enter MONTHS. These are the average number of broker report items(OBJECTS) processed per year. This is used to calculate disk and will be used to calculate CPU if you put nothing in the PEAK row.

G45


B46

If you enter the number of payment plan executions(OBJECTS) you MUST also enter MONTHS. These are the average number of payment plan executions(OBJECTS) processed per year. This is used to calculate disk and will be used to calculate CPU if you put nothing in the PEAK row.

G46


B47

If you enter the number of payment plan transfers(OBJECTS) you MUST also enter MONTHS. These are the average number of payment plan transfers(OBJECTS) processed per year. This is used to calculate disk and will be used to calculate CPU if you put nothing in the PEAK row.

G47


© Copyright IBM Corp. April-2008 QUICKSIZER SIZING FOR Retail Forecasting and Replenishment

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






Loc Prod ST TIME END TIMER-MDS Master Data Synchronization-SCM->FRP PEAK TIME NA NA NA NA 0 0

OP Items Res time WMD ST TIME END TIMER-ODS Order Data Synchronization-SCM->FRP PEAK TIME 0 NA NA yes 0 0

Loc Prod SDT Loc Prod ST TIME END TIMER-PCSD Processing Consumption (and stock) data PEAK TIME yes 0 NA NA 0 0

Loc Prod OP Items ST TIME END TIMER-FRP--FRP run 0 0 NA NA NA 0 0



B4


B5


B16


D16


F16


B17


D17


F17


B18


D18


F18


B19


D19


F19


B20


D20


F20


B29

If you enter the number of location products(Loc Prod), you MUST enter ST TIME and END TIME. These are the number of all location product combinations which are relevant for F&R, i.e. for which replenishment is performed with F&R You specify the time frame in which location products is executed.

G29


H29


B32

If you enter the number of order proposal items(OP Items) you MUST also enter Res time and start time and end time. These are the average number of order proposal items created by F&R per day.

C32

Enter the order proposal residence time in days for the order proposal items. This is usually the time between the creation of an order and the complete delivery.

F32

Choose yes if the R-ODS step is processed with the R-MDS step.

G32


H32


B35

If you enter the number of location products(Loc Prod) you MUST also enter start time and end time. These are the peak number of location products processed per peak time period.

C35

SDT--has stock data already been processed beforehand, i.e. outside the process steps considered for this sizing.

D35

Non entry field. This is the value of the location products field of the R-MDS entry.

G35


H35


B38

Non entry field. This is the value of the location products field of the R-MDS entry.

C38

Non entry field. This is the value of the OP items field of the R-ODS entry.

G38


H38


© Copyright IBM Corp. April-2008 QUICKSIZER SIZING FOR Utilities







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

BusPart Overdues Deposits Cust cont MONTHSUTIL-02-AVERAGE billing documents per YEAR 0 0 0 NA 0

BusPart Days for batch ST TIME END TIMEUTIL-BP-PEAK Batch processing per PEAK TIME 0 0 NA NA NA 0 0

OBJECTS ST TIME END TIMEOVERVIEW-AVERAGE use of "Customer Overview" transaction per YEAR NA NA NA NA NA NAOVERVIEW-PEAK use of "Customer Overview" transaction per PEAK TIME NA NA NA NA 0 0CONTACT-AVERAGE Customer contacts per YEAR NA NA NA NA NA NACONTACT-PEAK Customer contacts per PEAK TIME NA NA NA NA 0 0MOVE IN-AVERAGE customer move-ins per YEAR NA NA NA NA NA NAMOVE IN-PEAK customer move-ins per PEAK TIME NA NA NA NA 0 0MOVE-OUT-AVERAGE customer move-outs per YEAR NA NA NA NA NA NAMOVE-OUT-PEAK customer move-outs per PEAK TIME NA NA NA NA 0 0



B4


B5


B6


B7


B18


D18


F18


B19


D19


F19


B20


D20


F20


B21


D21


F21


B22


D22


F22


A32

Master Data and Transactional Data for Disk Sizing-Part I.

B32

These are the number of bills sent to a customer each year. Typical values here are 1(yearly), 2(bi-yearly), 4(quarterly), 6(bi-monthly) 12(monthly. This is used to calculate disk.

C32

Enter the average number of budget bills per business partner per year. Budget bills are not posting relevant.

D32

Enter number of customer bills that are based on partial amounts not actual meter reading consumption. Partial bills are legally declared as earnings of the company.

E32

Enter the number of post relevant line items on each partial or budget bill. This should be the average of number of lines for each bill that contain monetary information that is passed to general ledger. If no partial or budget bill line items are passed to GL this should be 0.

F32

If C-items is entered then Contracts, ContAcc, Meters and MONTHS must be entered. Enter the number of post relevant line items on each consumption bill. This should be the average of the number of lines for each bill that contain monetary information that is passed to general ledger.

G32

Enter the number of additional information lines on each consumption bill. This might be a line for consumption or for control readings.

H32

If Contracts is entered C-items, Cont/Acc Meters and MONTHS must also be entered. Enter the number of contracts between the utility company and the business partner(customer). A single business partner might have a contract for electricity and a second contract for gas.

I32

Enter the number of different taxes to be paid on each contract.

J32

If ContAcc is entered then C-items, Contracts, Meters and MONTHS must also be entered. Enter the number of accounts in which posting data for contracts or contract items are processed for which the same collection/payment agreements apply.

K32

Enter the number of meters to be read. Meters in stock are not counted. However, a single meter with multiple registers should be counted as the number of registers.

A35

Master Data and Transactional Data for Disk Sizing-Part 2.

B35

If you enter the number of business partners(BusPart) you MUST also enter Overdues, Deposits, Cust Cont and MONTHS. These are the number of customers, organizations or groups in which the utility company has a business interest(OBJECTS) processed per year. This is used to calculate disk and will be used to calculate CPU if you put nothing in the PEAK row.

C35

Enter the number of overdue notices(Overdues) to be sent per year. This is usually between 5 and 10% of the total number of billing documents.

D35

Enter number of total number of cash security deposits(Deposits) which are accepted per year.

E35

Enter number of customer contacts (Cust cont) per year. If you customer contacts are completely handled in the CRM system, this should be 0.

G35


B38

This is forced to be the same as BusPart in UTIL-02. If you enter the number of business partners(BusPart) you MUST also enter Overdues, Deposits, Cust Cont and MONTHS. These are the number of customers, organizations or groups in which the utility company has a business interest(OBJECTS) processed per year. This is used to calculate disk and will be used to calculate CPU if you put nothing in the PEAK row.

C38

Enter the minimum number of days available for one complete billing cycle.

G38


H38


B41

These are the average number of use of the "Customer Overview" transaction per year. This is used to calculate disk and will be used to calculate CPU if you put nothing in the PEAK row.

B42

If you enter OBJECTS you must enter ST TIME and END TIME. This is the number of use of the "Customer Overview" transaction during the peak or highest time period; usually an hour or a couple of hours. You specify the time period that these peak OBJECTS are processed using the ST TIME and END TIME columns. This is used to calculate CPU requirements.

G42


H42


B43

These are the average number of customer contacts per year. This is used to calculate disk and will be used to calculate CPU if you put nothing in the PEAK row. If customer contacts are recorded in the CRM system, this should be 0.

B44

If you enter OBJECTS you must enter ST TIME and END TIME. This is the number of customer contacts during the peak or highest time period; usually an hour or a couple of hours. You specify the time period that these peak OBJECTS are processed using the ST TIME and END TIME columns. This is used to calculate CPU requirements. If customer contacts are recorded in the CRM system, this should be 0.

G44


H44


B45

These are the average number of customer registraction for utility servers per year. This is used to calculate disk and will be used to calculate CPU if you put nothing in the PEAK row.

B46

If you enter OBJECTS you must enter ST TIME and END TIME. This is the number of customer registration for utility service during the peak or highest time period; usually an hour or a couple of hours. You specify the time period that these peak OBJECTS are processed using the ST TIME and END TIME columns. This is used to calculate CPU requirements.

G46


H46


B47

These are the average number of cancellations of utility service per year. This is used to calculate disk and will be used to calculate CPU if you put nothing in the PEAK row.

B48

If you enter OBJECTS you must enter ST TIME and END TIME. This is the number of customer cancellation of utility service during the peak or highest time period; usually an hour or a couple of hours. You specify the time period that these peak OBJECTS are processed using the ST TIME and END TIME columns. This is used to calculate CPU requirements.

G48


H48


NONONO

MONTHS0

L32

If MONTHS is entered then C-items, Contracts, ContAcc and Meters must be entered. Enter the number of months this data will remain online before being archived.

© Copyright IBM Corp. April-2008 T-SHIRT SIZING FOR PLM




Type Default Size Storage DefaultFirst non-production system Dev 100GB'sSecond non-production system QA NoneThird non-production system, if needed None NoneFourth non-production system, if needed None NoneFifth non-production system, if needed None None


Enter total CONCURRENT users during the PEAK hour--A user must NOT be counted twiceHe 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 SAPS0 0

cPROJECTS SIZING Click for sizing white paper

Objects Projects Results



https://websmp107.sap-ag.de/~sapdownload/011000358700000917082009E/PLMCore_7.pdf

https://websmp204.sap-ag.de/~sapdownload/011000358700006329312006E/Sizing_cProjects_45_V14.pdf

B13


D13


F13


B14


D14


F14


B15


D15


F15


B16


D16


F16


B17


D17


F17


A28

Provides a Web User Interface (Web UI) to manage the master data objects for PLM. It requires a search engine and a portal engine which must be sized separately. It also continues to need the base PLM applications below.

B28


B31

Enter the number of concurrent users expected.

B33


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

cFOLDERS SIZING

# msgs msg size SAPSCPU sizing for the download scenario 0CPU sizing for the upload and copying scenario 0

# docs doc size GB'sDisk sizing based on number of documents and size of document 0

cRECORDS SIZING Click for sizing white paperUser Based Sizing

LOW MEDIUM HIGH SAPSUsers in Records and Case Management-PEAK PER HOUR 0

Thruput Based SizingCASES ST TIME END TIME

PEAK Cases created by a user per PEAK TIME NA NA NA NA 12 13

Elements ST TIME END TIMETOTAL elements added to cases by a user per PEAK TIME NA NA NA NA 12 13

CASES ST TIME END TIMEPEAK Cases created by an interface per PEAK TIME NA NA NA NA 12 13

Elements ST TIME END TIMETOTAL elements added to cases by an interface per PEAK TIME NA NA NA NA 12 13

# cases # elements GB'sDisk sizing based on cases and records 0

CONTENT SERVER SIZING Click for sizing white paperUser Based Sizing

https://websmp204.sap-ag.de/~sapdownload/011000358700001407132004E/SIZING_REC_CASE_MGMT_1_0.PDF

https://websmp204.sap-ag.de/~sapdownload/011000358700006713092002E/Kpro_march_2006.pdf

B36

Enter the average number of objects per project. This is the sum of all phases, checklists, checklist items, tasks, and subtasks in each project. Choose the number which most closely represents your estimated requirements.

C36

Enter the number of projects you plan to have per year.

B37

Enter the average number of objects per project. This is the sum of all phases, checklists, checklist items, tasks, and subtasks in each project. Choose the number which most closely represents your estimated requirements.

C37

Enter the number of projects you plan to have per year.

A39

This is based on the SAP White paper dated September 2008.

B42

Enter the maximum number of downloads per hour that you expect to occur during the peak hour.

C42

Enter the average size for each of the download messages.

B43

Enter the maximum number of uploads plus copys that you expect to occur during the peak hour.

C43

Enter the average size for each of the upload and copy messages.

B46

Enter the number of documents you plan to store in your PLM database.

C46

Enter the average size of these documents in MB's.

B48


B50


C50


D50


A51

This is based on SAP white paper dated March 2004.

A55

To reflect the creation of a case or a record (empty without any elements) by a user, enter the number of records created by users per the peak time period.

B55

If you enter the number of CASES you MUST enter ST TIME and END TIME but NOT MONTHS. These are the number of empty cases or records created by a user per peak time period; usually an hour or a couple of hours. You specify the time period that these peak CASES are processed using the ST TIME and END TIME columns. This is used to calculate CPU requirements.

G55


H55


A58

To reflect the creation of a case or a record (empty without any elements) by a user, enter the number of records created by users per the peak time period.

B58

If you enter the number of CASES you MUST enter ST TIME and END TIME but NOT MONTHS. These are the total number of elements, such as a document to a case or a record created by a user per peak time period; usually an hour or a couple of hours. You specify the time period that these peak CASES are processed using the ST TIME and END TIME columns. This is used to calculate CPU requirements.

G58


H58


A61

To reflect the creation of a case or a record (empty without any elements) by a API (BAPI) call, enter the number of records created by users per the peak time period.

B61

If you enter the number of CASES you MUST enter ST TIME and END TIME but NOT MONTHS. These are the number of empty cases or records created by a API (BAPI) call per peak time period; usually an hour or a couple of hours. You specify the time period that these peak CASES are processed using the ST TIME and END TIME columns. This is used to calculate CPU requirements.

G61


H61


A64

To reflect the creation of a case or a record (empty without any elements) by a API (BAPI) call, enter the number of records created by users per the peak time period.

B64

If you enter the number of CASES you MUST enter ST TIME and END TIME but NOT MONTHS. These are the total number of elements, such as a document to a case or a record created by a API (BAPI) call per peak time period; usually an hour or a couple of hours. You specify the time period that these peak CASES are processed using the ST TIME and END TIME columns. This is used to calculate CPU requirements.

G64


H64


B67

Enter the number of cases or records you expect to store in your PLM database.

C67

Enter the average number of elements in each case.

A69

This guidance is based on the SAP whitepaper dated June 2006.

B69


Users SAPS GB'sPEAK PARALLEL Users accessing the Content database 0 0

A72

Because documents are changed on the user's PC, CPU power has not been a bottleneck so far. Enter the number of concurrent parallel users who access the database at the same time. Parallel users are much lower than concurrent users because parallel users may be working on a document in their PC which requires no file server workload. They will only access the database when they request a document or replace a document.

SAPS0

SAPS0

SAPS0

SAPS0

© Copyright IBM Corp. April-2008 T-SHIRT SIZING FOR MDM-7.1






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

NetWeaver MDM Server-APP Server Click for sizing white paperRepository # Records # Users Results

CPU sizing--number of records in the primary table SAPSMemory sizing GB'sAccelerator size on disk GB's

NetWeaver MDM Server-DBMS ServerResults



https://websmp109.sap-ag.de/~sapidb/011000358700001921872008E

B13


D13


F13


B14


D14


F14


B15


D15


F15


B16


D16


F16


B17


D17


F17


A28

MDM Server--Mandatory--Manages access through the DBMS to one or more MDM repositories containing master data. The MDM Server passes this information to various client components across a network. These repositories may be unique to your implementation or you may used predefined MDM Business Content repositories. Material(for ERP), Vendor(for ERP), Customer(for ERP), Employee(for ERP), Article(for SAP Retail), Product/Material(for CRM/SRM, ERP), Business Partner/Vendor/Customer(for CRM/SRM,ERP)

B28


B30

Enter the type of repository BP Std=12 tables, 39 total fields & 11 lookup fields in primary table and 32 total fiels in sub tables. BP Ext=39 tables, 79 total fields & 23 lookup fields in primary table and 158 total fiels in sub tables. SRM Cat=19 tables, 29 total fields & 16 lookup fields in primary table and 54 total fiels in sub tables.

C30

Enter the number of records in the primary table in the repository.

D30

Enter the number of concurrent peak users.

CPU sizing 0 SAPSMemory sizing Data size 0 GB'sDisk sizing--based on estimate of total storage 0 GB's

Import, Syndication,Layout Server-Optional ResultsCPU sizing 0 SAPSMemory sizing 0 GB's

E36

1600 SAPs is recommended

E37


A38

This should be used for disk sizing since it allows you to actually specify the amount of storage you need.

B38

Enter the total size of all stored data and objects (PDF's, JPG's, etc.)

A40

Import Server-- Optional--Allows you to import data automatically in conjunction with predefined inbound ports and import maps. Syndication Server--Optional--Allows you to export data automatically in conjunction with predefined outbound ports and syndicator maps. Layout Server--Optional--Supports the publishing capabilities of MDM.

E41


E42


© Copyright IBM Corp. April-2008 T-SHIRT SIZING FOR Miscellaneous Applications






Enter total CONCURRENT users during the PEAK hour--A user must NOT be counted twiceHe 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)SQL/OLAP Server IIS/.NET Server

System SAPS GB Memory cores GB Memory StorageServer--PEAK users-MS Windows version 200 min

Netweaver Tier IIS/.NET ServerUsers SAPS GB Memory cores GB Memory Storage

Server--PEAK users-NW version-simple requirements See BWServer--PEAK users-NW version-Med Complexity requirements See BWServer--PEAK users-NW version-Very Complex requirements See BW



B13


D13


F13


B14


D14


F14


B15


D15


F15


B16


D16


F16


B17


D17


F17


A31

Windows version uses SQL as the BPC storage repository and IIS/.NET as the application layer.

B31

SMALL = Up to 100 named/20concurrent users doing simple calculations, lightweight consolidations, simple input, light default logic, and limited MDX based formulas. Midsize =Up to 500 named/100concurrent users doing simple calculations, lightweight consolidations, simple input, light default logic, and limited MDX based formulas. LARGE = Up to 100 named/200concurrent users doing simple calculations, lightweight consolidations, simple input, light default logic, and limited MDX based formulas.

A34

Netweaver version uses SAP BW as the BPC storage repository, Netweaver as the application layer and IIS/.NET as an additional application layer. This is for simple calculations, simple input, light default logic and limited MDX based formulas.

B34

Enter the number of users.

I34

Since BPC storage is on BW, the storage for BPC can be approximated by using the BW QuickSizer.

A35

Netweaver version uses SAP BW as the BPC storage repository, Netweaver as the application layer and IIS/.NET as an additional application layer. This is for medium complexity calculations, default logic, limited MDX based formulas, light consolidation operations and medium complexity planning logic.

B35


I35

IBM_USER:Since BPC storage is on BW, the storage for BPC can be approximated by using the BW QuickSizer.

A36

Netweaver version uses SAP BW as the BPC storage repository, Netweaver as the application layer and IIS/.NET as an additional application layer. This is for complex calculations, very detailed default logic, limited MDX based formulas and complex planning logic.

B36


I36

Since BPC storage is on BW, the storage for BPC can be approximated by using the BW QuickSizer.

OutlookSoft sizing Guidance Click for vendor informationUsers 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 paperSmall Medium Large SAPS

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

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

Learning Solutions sizing GuidanceUsers Activity Level Course Size SAPS

User based sizing guidance for Learning Solutions 0

GRC-VIRSA sizing Guidance--Initial t-shirt sizing Click for sizing white paperSystem SAPS GB-Storage

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

GRC-VIRSA sizing Guidance--Expert sizing Click for sizing white paperUsers 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

http://www.outlooksoft.com/

https://websmp204.sap-ag.de/~sapdownload/011000358700002950932006E/ADS_SizingNW2004sV2_1.pdf

https://websmp204.sap-ag.de/~sapdownload/011000358700000435122007E/Sizing_AccessControl_2_0.pdf

https://websmp204.sap-ag.de/~sapdownload/011000358700000435122007E/Sizing_AccessControl_2_0.pdf

B39


B41

Enter the number of concurrent users active on the system at the same time during the peak hour.

A45

This guidance is based on the SAP white paper dated November 2008 .

B47

Enter the number of files exclusive of business objects processed on the system at the same time during the peak hour.

C47

Enter the number of business objects exclusive of files processed on the system at the same time during the peak hour.

D47

Enter the number of concurrent user sessions active on the system at the same time during the peak hour.

A49

Adobe document services render PDF, PCL, PostScript and other output formats from form designs created using the Adobe LiveCycle Designer. SAP recommends adding 10% to the total SAPS as a security measure. This version of the t-shirt sizing is based on 2004s. Since it runs in NetWeaver, it is supported on all NetWeaver platforms. This guidance is based on the SAP whitepaper dated 2006.

B49


A51

In this scenario, the ADS server is asked to render and print documents in a random mode.

B51

Enter the number of small documents printed. A small document is equivalent to 1 page of average amount of data.

C51

Enter the number of medium documents printed. A small document is equivalent to 10 pages of average amount of data.

D51

Enter the number of large documents printed. A small document is equivalent to 100 pages of average amount of data.

A52

In this scenario, the ADS server is asked to render and print documents where the documents are accumulated and presented in a homogeneous batch of 50 documents.

B52

Enter the number of small documents printed. A small document is equivalent to 1 page of average amount of data.

C52

Enter the number of medium documents printed. A small document is equivalent to 2 pages of average amount of data.

D52

Enter the number of large documents printed. A small document is equivalent to 4 pages of average amount of data.

A54

Enter the number of documents per hour in each of the document size categories.

B54

Enter the number of small simple interactive forms processed. A small simple form type is 1 page with mostly static form elements.

C54

Enter the number of small complex interactive forms processed. A small complex form type is 1 page with some interactive form elements.

D54

Enter the number of medium interactive forms processed. A medium form type is 2 pages with some interactive form elements.

E54

Enter the number of large interactive forms processed. A large form type is 4 pages with some interactive form elements.

A55

Form Generation--During the form processing workflow, you may ask ADS to cache the form. This allows for better performance and response time. Default is No. This is test A and B.

A56

Application of Security Settings--During the form review process specify whether changes or printing will be permitted. Default is No. This is test C.

A57

Digital Signatures--When ADS receives a signed form, a list of signatures is typically retrieved and each signature is validated to ensure the form is in good standing. Default is No. This is test D.

A58

Digital Signatures--After the form's standing is established, a request is send to ADS to retrieve the form state when a given signature was applied. This is done to compare certain values of the form for validity and authentication. Normally this is done after the 2nd signature. Default is No. This is test E.

A60

This guidance is based on the SAP whitepaper dated 2004.

B62

Enter the number of users per hour. This is not the number of courses which are requested per hour. If the duration for executing a course is expected to be a half an hour, the number of concurrent users is half the number of requested courses per hour.

C62

Enter the average activity level of these users. A slow user is characterized as doing about 30 steps per hour. Medium about 60 steps per hour. Fast about 120 steps per hour.

D62

Enter the average course size. A small course is characterized as consisting of about 20 steps. Medium is about 50 steps. Big is about 100 steps.

A64

Using T-shirt model for GRC Access Controls, customers can size the necessary products accordingly. This method is not as accurate as transactional sizing but gives you a rough estimate before you are able to do a more in-depth approach. Make sure that this is done for the peak hour of the year. All the components reside on SAP NetWeaver. Pre-requisites include J2EE and IGS. This guidance is based on the SAP whitepaper dated October 2007.

B64


B66

SMALL = Up to 10,000 named users, 5000 roles and 10,000 violations per hour. MEDIUM = Up to 25,000 named users, 10,000 roles and 50,000 violations per hour. LARGE = Up to 50,000 named users, 25,000 roles and 100,000 violations per hour.

B67

SMALL - Up to 5000 roles and 10 requests per hour MEDIUM = Up to 10000 roles and 25 requests per hour LARGE = Up to 25000 roles and 50 requests per hour

B68

SMALL - Up to 100 simple roles, 200 derived roles and 500 roles in mass generation per hour MEDIUM = Up to 250 simple roles, 500 derived roles and 1000 roles in mass generation per hour LARGE = Up to 500 simple roles, 1000 derived roles and 2500 roles in mass generation per hour

A71

Using expert sizing requires more product knowledge. The sizing approach for GRC Access Control includes the most popular scenarios needed for sizing of all the three components. Make sure that this is done for the peak hour of the year. All the components reside on SAP NetWeaver. Pre-requisites include J2EE and IGS. This guidance is based on the SAP whitepaper dated October 2007.

B71


B73

Enter the approximate number of total named SAP Users (User Sync)

C73

Enter the approximate number of total Roles (Role Sync)

D73

Enter the approximate number of SoD (segregation of duties) Violations during risk analysis.

E73

Will you be processing management reports?

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 NATotal 0 NA

EH&S-Environment, Health and Safety--Initial t-shirt sizing Click for sizing white paperSystem SAPS GB-Storage

Product Safety(PS) and dangerous goods(DG) sizing NA NA 0 0LOW MEDIUM HIGH

Number of users--All other sub modules--PEAK PER HOUR 0

xEM-Emissions Management--sizing guidanceUSERS SAPS GB-Storage

Compliance Management--Users-PEAK PER HOUR NA NA 0 0Calculations

Emissions Management--Calculations per year--Average per year NA NA NA 0Emissions Management--Calculations per hour--PEAK PER HOUR NA NA 0 NA

xRPM-Resource & Portfolio Mgmt--sizing guidanceDISPLAYS Items per EP SAPS RPM SAPS

User Displays-PEAK PER HOUR-JAVA based dashboard 0 0User Displays-PEAK PER HOUR-ABAP based dashboard 0 0

ARIS BPM--Server sizing guidance Click for vendor informationBusiness Server DBMS Server

USERS SAPS GB-Memory SAPS GB-MemoryConcurrent users on the server--PEAK PER HOUR 0 0 0 0

SAP MOBILITY--three alternatives

SAP MOBILITY--CRM LOGONS SAPS GB-StorageUsers that will be synchronizing laptops-PEAK PER HOUR 0 0

SAP MOBILITY--Mobile BusinessWeb Application Server ECC Server

Syncs J2EE ABAP DB ABAPMobile Asset Management(MAM) Standard and Utilities 0 0 0 0

https://websmp204.sap-ag.de/~sapdownload/011000358700006131352006E/Sizing_EHS.pdf

http://www.ids-scheer.com/en/ARIS_Software_Software/3730.html

A87

Using T-shirt model, customers can size the necessary products accordingly. This method is not as accurate as transactional sizing but gives you a rough estimate before you are able to do a more in-depth approach. Make sure that this is done for the peak hour of the year. This guidance is based on the SAP whitepaper dated 2006.

C87


A89

EH&S is dominated by product safety and dangerous goods concerning system load. Other sub modules are estimated in the next line. It is assumed that this workload occurs fairly evenly throughout the year.

B89

SMALL = Up to 5,000 listed substances, 10,000 real substances, 20,000 MSDS, 50,000 TREM Cards, 10 languages/countries and 250,000 shipped reports/year. MEDIUM = Up to 10,000 listed substances, 50,000 real substances, 100,000 MSDS, 500,000 TREM Cards, 30 languages/countries and 500,000 shipped reports/year. LARGE = Up to 20,000 listed substances, 100,000 real substances, 500,000 MSDS, 2,000,000 TREM Cards, 30 languages/countries and 2,000,000 shipped reports/year. Extra-LARGE = Greater than 20,000 listed substances, 100,000 real substances, 500,000 MSDS, 2,000,000 TREM Cards, 30 languages/countries and 2,000,000 shipped reports/year.

B90


C90


D90


A91

Enter the number of users of sub modules other than PS and DG. These include EH&S modules such as IH, OH, WA, etc

A93

xEM is a compliance and emissions management application to ensure and prove regulatory compliance. xEM integrates with core ECC. Using T-shirt model, customers can size the necessary products accordingly. This method is not as accurate as transactional sizing but gives you a rough estimate before you are able to do a more in-depth approach. Make sure that this is done for the peak hour of the year. This guidance is based on the SAP whitepaper dated September 2006.

B95

Enter the total number of concurrent users doing compliance tracking. This is for the peak hour of the year.

B97

Enter the number of calculations processed for the entire year. This assumes that each record requires 4kB and that each calculation has an average of 5 emission records. If you have 1000 daily records and 500 monthly records and 100 annual records, you would put (1000*365 + 500*12 + 100) 371100.

B98

Enter the maximum number of calculations processed during the peak hour. If you have 100 daily, 10 monthy and 5000 annual calculations that will be processed in the peak hour you would enter 5110.

A100

xRPM unifies project management, time tracking, financial data, and employee skills information in a portfolio management and governance mode. Make sure that this is done for the peak hour of the year. This guidance is based on the SAP whitepaper dated February 2008.

B102

Enter the total number of concurrent xRPM dashboard displays per peak hour. This can be estimated by multiplying the total number of peak concurrent users by the average number of displays per user during the peak hour.

C102

Enter the number of portfolio items per largest portfolio.

D102

These are the estimated SAPS for the Portal part of xRPM workload.

E102

These are the estimated SAPS for the Core RPM JAVA server.

B103

Enter the total number of concurrent xRPM dashboard displays per peak hour. This can be estimated by multiplying the total number of peak concurrent users by the average number of displays per user during the peak hour.

C103

Enter the number of portfolio items per largest portfolio.

D103

These are the estimated SAPS for the Portal part of xRPM workload.

E103

These are the estimated SAPS for the Core RPM ABAP server.

A105

ARIS is a Business Process Management suite of products. It includes functions such asarchitect, optimizer, publisher, simulator, rules designer and balanced scorecard. It is fully integrated with SAP Netweaver and SAP Solution Manager for business functions as well as SAP software installation and upgrade processes. It requires a single Business server with a DBMS. The Oracle or SQL Server DBMS can be on a separate server. Make sure that this is done for the peak hour of the year. This guidance is based on the ARIS whitepaper dated October 2006.

B105


C106

This is a Wintel platform only. The DBMS may run in this server as well but is not recommended for more than 50 users.

E106

This is the DBMS server. It may be included in the Business Server for fewer than 50 users. This server is any platform on which MS SQL or Oracle is support.

B108

Enter the total number of concurrent users with access to the Business Server. This is for the peak hour of the year.

A110

There are currently three Mobility sizing alternatives 1. Sizing for synchronizing laptops--Use the QuickSizer for CRM Mobility 2. Sizing for Mobile Business using non-laptop handheld pre-built applications 3. Sizing for NetWeaver Mobile using application development tools for hand-held devices

A112

This is the same sizing as asked in the CRM QuickSizer for mobility.

D113

Enter maximum # of logons per hour for synchronizing laptops only.

A115

This is based on an SAP white paper dated September August 2008

A118

MAM is a full offline mobile application that helps field service and maintenance technicians perform their daily activities at their customer sites. This sizes the backend server functions and not the client requirements. See the white paper for details on the specifics of the scenario sized.

B118

Enter the total number of synchronizations per hour expected during the peak hour of the year.

Mobile Asset Management for Utilities(MAU) 0 0 NA 0Syncs CRM SAPS

Mobile Sales for Handheld with CRM 5.x 0Web Application Server ECC Server

Visits To Handheld To Backend DB ABAPMobile Direct Store Delivery 0 0 NA 0

Web Application Server ECC ServerSyncs J2EE ABAP DB ABAP

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

SAP MOBILITY--NetWeaver MobilityWeb Application Server ECC Server

Profile J2EE ABAP DB ABAPBack-end triggered delta load NA 0 NA NA

Web Application Server ECC ServerSyncs J2EE ABAP DB ABAP

Client Synchronizations NA 0 NA NA

Web Application Server ECC ServerMessages 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 paperBC's J2EE AS DB

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

NRX-Add-on to EP Click for vendor informationUSERS Think time Java iViews URL iViews % KMC

NW-EP-PRT-PEAK 180 4 0 30

DuetUsers Duet Server Duet Memory

https://websmp204.sap-ag.de/~sapdownload/011000358700005273352003E/Sizingbillerdirect60_1.pdf

http://www.nrx.com/

A119

MAU integrates the mobile proceses with SAP for Utilities and Enterprise Asset Management. It is based on MAM. See the white paper for details on the specifics of the scenario sized.

B119


A121

Mobile Sales for Handheld is one of a number of applications, such as Direct Store Delivery, Mobile Service for Handheld, Mobile Procurement or Time and Travel which allows the sales representative to carry out their daily work in offline mode. See the white paper for details on the specifics of the scenario sized.

B121

Enter the total number of synchronizations per hour expected during the peak hour of the year. Mid-size data sets assumed.

C121

These are the number of SAPS that are to be added to the CRM server.

A124

DSD addresses the needs of drivers and van sellers in direct-store-delivery situations. The sizing assumes 1000 synchronizations per hour. See the white paper for specifics on the sizing scenarios.

B124

Enter the total number of customers/visits per hour expected during the peak hour of the year.

A127

See the white paper for specifics on the sizing scenarios.

B127


A128


B128


A129


B129


A130


B130


A131


B131


A132

See the white paper for specifics on the sizing scenarios. This is based on measurement for MI 7.0 SPS05.

B132


A134

This allows you to develop mobile applications that can be deployed on mobile devices. This sizes the backend server functions and not the client requirements. See the white paper for details on the specifics of the scenario sized. This is based on an SAP white paper dated July 2008.

B137

Enter the appropriate profile: Small = Up to 10000 data objects per hour and up to 94000 DB rows per hour. Medium = Up to 50000 data objects per hour and up to 470000 DB rows per hour. Medium = Up to 100000 data objects per hour and up to 940000 DB rows per hour.

B141


B145

Enter the total number of uploaded messages that are processed during an eight hour processing window during the peak time of the year.

A147

This allows you to electronically send bills to their customers and share account information with them. See the white paper for details on the specifics of the scenario sized. This is based on an SAP white paper dated August 2005.

B147


B149

Enter the peak number of business cases per hour based on FI-AR as the ECC backend. This is the peak per hour. A business case is a typical scenario of an electronic payment process. The benchmark scenario consists of logging on, displaying three bills, paying one of the bills, displaying the payment status, backing out the payment of this bill, displaying the status, displaying the status of the last 12 months of bills paid and then logs off. Please see the white paper for a complete description of the business case.

B150

Enter the peak number of business cases per hour based on FI-CA as the ECC backend. This is the peak per hour. A business case is a typical scenario of an electronic payment process. The benchmark scenario consists of logging on, displaying three bills, paying one of the bills, displaying the payment status, backing out the payment of this bill, displaying the status, displaying the status of the last 12 months of bills paid and then logs off. Please see the white paper for a complete description of the business case.

A153

NRX is a master data management add-on to SAP. It is made of the Asset Center which has minimal impact on sizing the SAP server and VIP. VIP is sized as an EP application. Use the Custom line of EP in the QuickSizer. Recommended defaults are Number of concurrent users are commonly 10% of the total user population. 180 seconds is a reasonable think time. 6 Java iViews is a reasonable workload 30% KMC is reasonable. As this is an EP application, the resulting SAPS should be added to the EP footprint.

B153


A155

These users are simply using the portal to launch transactions in the back-end system. Portal pages typically contain a single URL iView (no Java iViews). This is an example of a custom portal application and as such can be described per your specific application requirements.

B155

If you enter USERS you must also enter Think time and either Java iViews or URL iViews or both. Enter the maximum number of concurrent VIP users during the peak hour. This is used to size CPU.

C155

Enter the elapsed time between two successive "clicks" of a user to the portal system. Default for VIP is 180 seconds.

D155

Enter the number of Java iViews of a typical VIP page for this scenario. A Java iView retrieves business content from back-end systems via Jco/RFC and renders the unformatted business content in HTML. Default for VIP is 4 .

E155

Enter the number of URL iViews of a typical VIP portal page for this scenario. For a URL iView, the portal generates the URL and sends it to the browser. The browser then sends the URL to the back-end system and retrieves the HTML content. Default for this scenario is 0.

F155

Enter the percentage of "clicks" access Knowledge Management Content. Default for this scenario is 30.

A158

Duet software presents selected business practices and information such as time management and budget monitoring, from SAP through MS Office. It is comprised of the Duet Client(Wintel only desktop add-on to MS Office), the Duet Server(.Net Wintel only Java server) and the NetWeaver add-on(Any Netweaver Java platform). It is assumed that this Duet infrastructure will access an already in place SAP Netweaver set of components. This sizing is based on the SAP White Paper dated December 2008.

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

T-SHIRT SIZING GUIDANCE FOR KNOWLEDGE MANAGEMENT AND COLLABORATION Click for sizing white paperPORTAL DB Portal

Users SAPS SAPS MemoryKM-PEAK Concurrent users per PEAK TIME NA NA NA 0 0 0

NWDI or JDI Click for sizing SAP NOTE 737368Developers SAPS GB-Memory

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

Web Dispatcher Click for sizing white paperMessages SAPS

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

Auto-ID Infrastructure-RFID Click for sizing white paperSlap & Ship Scenario Print Req Tags Time SAPS StorageTag Commissioning 0 0.00

Pallets Cases TimePacking 0 0.00

Pallets Cases TimeLoading 0 0.00

RFID-Enabled Returnable Transport Item-RTI Scenario Print Req Tags Time SAPS StorageTag Commissioning in All 0 0.00

Pallets Cases Time

https://websmp204.sap-ag.de/~sapdownload/011000358700000289152007E/SIZING_KMC_1_1_SP13.pdf

http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=DISPL_TXT&_NNUM=0737368&

https://websmp204.sap-ag.de/~sapdownload/011000358700001869252005E/Sizing_Web_Dispatch_640.pdf

https://websmp209.sap-ag.de/~sapdownload/011000358700000328372005E/Sizing_AutoID_v3_0.pdf

B160

Enter the total number of concurrent active sales management users during the peak hour of the year.

C160

These are the incremental SAPS for the Duet Server.

D160

GB's of memory recommended for the Duet Server. It is estimated from the number of J2EE nodes required at 3 GB's per node.

B161


C161


D161


B162


C162


D162


B163


C163


D163


B164

Enter the total number of concurrent active users for all other Duet applications during the peak hour of the year.

C164


D164


G167


A170


B170

Enter the number of concurrent users (30 seconds average think time) accessing the KM functions during the peak or highest time period; usually an hour or a couple of hours. This is used to calculate CPU requirements.

A173

The NWDI or JDI consists of the following components: DTR-Design Time Repository CBS-Component Build Service CMS-Change Management Service All three are always installed together on NetWeaver but they can be used separately and distributed depending on the scenario and the workload.

B173

Sizing for this component or feature is provided by SAP thru the publication of a SAP NOTE. Access to this NOTE requires an OSS User ID and SAP customer number which you can get from your local SAP representative.

A175

Only the Design Time Repository(DTR), which is installed on a J2EE server, is used. For testing with 1-5 developers recommend 500-1500 SAPS and 1 GB of memory.

B175

Enter the total number of concurrent active developers during the peak hour of the year.

C175


D175

This is the recommended amount of memory for the production server.

A176

This is the same as Scenario 1 except you may optionally use the SLD. SLD may already be present in your landscape or may be added to the DTR server. For testing with 1-5 developers recommend 500-1500 SAPS and 1 GB of memory.

B176


C176


D176


A177

All JDI components and the SLD are required. For testing with 1-5 developers, all JDI and the SLD are installed on a J2EE server. Recommended to be 500-1500 SAPS and 2 GB's of memory. See SAP Note 737368 for more architecture recommendations.

B177


C177


D177


A178

This is the same as scenario 2+ but requires distribution because of workload or performance problems. CBS should be transferred to a separate server.

B178

Enter the size of system: small=Up to 50 developers and up to 10,000 development components(DCs) medium=50-150 developers and 10,000-40,000 development components(DCs) large=More than 150 developers and more than 40,000 development components(DCs)

C178


D178


B181


A183

Incoming protocol is HTTP and outgoing protocol is HTTP.

B183

Enter the total number of messages per second during the peak hour of the year. Assumed message size is 16 KB.

C183


A184

Incoming protocol is HTTPS and outgoing protocol is HTTPS-Pass through of end-to-end SSL.

B184


C184


A185

Incoming protocol is HTTPS and outgoing protocol is HTTPS-SSL termination.

B185


C185


A186

Incoming protocol is HTTPS and outgoing protocol is HTTPS-SSL termination and re-encryption.

B186


C186


A190

Auto-ID Infrastructure(All 4.0) is the SAP software component for RFID integration. There is a scenario for standalone shipping of goods, a second scenario for registering returns of goods and a third scenario for a completely integrated RFID solution into ERP.

B190


A191

This is the standalone system for creating labels, print records and tags for shipping goods. There are three main functions; tag commissioning, Packing and Loading. Each step in Slap & Ship prepares some records for BI which are uploaded in batch.

A192

Warehouse worker requests and prints labels for labeling cases.

B192

Enter the number of print requests per peak time period for labels. Do not divide by 1000.

C192

Enter the number of RFID labels per print request during this peak time period.

D192

Enter the processing time for this peak time period in hours.

A194

All receives all EPC information for one packed pallet

B194

Enter the number of packed pallets processed per peak time period. Do not divide by 1000.

C194

Enter the number of cases per pallet during this peak time period.

D194


A196

Pallets leave the warehouse and goods issue is registered.

B196

Enter the number of loaded pallets per peak time period. Do not divide by 1000.

C196


D196


A198

This is the system for creating labels, print records and tags for shipping goods. There are three main functions; tag commissioning, Packing/Unpacking and Loading/Unloading. Each step in RTI prepares some records for BI which are uploaded in batch. This group is for the sizing for the All system.

A199

Warehouse worker requests and prints labels for labeling cases. This information is replicated to SCM.

B199


C199


D199


Packing/Unpacking in All 0 0.00Pallets Cases Time

Loading/Unloading in All 0 0.00

RFID-Enabled Returnable Transport Item-RTI Scenario Print Req Tags Time SAPS StorageTag Commissioning in SCM 0 0.00

Pallets Cases TimePacking/Unpacking in SCM 0 0.00

Pallets Cases TimeLoading/Unloading in SCM 0 0.00

RFID-Integrated Delivery Processing Scenario Print Req Tags Time SAPS StorageTag Commissioning in All 0 0.00

Deliveries Items EPC Time Pieces PalletsPacking/Unpacking in All 0 0.00

Deliveries Items EPC Time Pieces PalletsLoading/Unloading in All with hierarchy 0 0.00

Deliveries Items EPC Time PiecesLoading/Unloading in All without hierarchy 0 0.00

A201

All receives all EPC information for one packed pallet

B201


C201


D201


A203

Pallets leave/enter the warehouse and goods issue /receipt is registered.

B203


C203


D203


A205

This is the system for creating labels, print records and tags for shipping goods. There are three main functions; tag commissioning, Packing/Unpacking and Loading/Unloading. Each step in RTI prepares some records for BI which are uploaded in batch. This group is for the sizing for the SCM Event handlers. See the white paper for information on sizing the BI workload.

A206


B206


C206


D206


A208

All receives all EPC information for one packed pallet. This information is replicated to SCM.

B208


C208


D208


A210

Pallets leave/enter the warehouse and goods issue /receipt is registered. This information is replicated to SCM.

B210


C210


D210


A212

This is the system for creating labels, print records and tags for shipping goods. There are three main functions; tag commissioning, Packing/Unpacking and Loading/Unloading. Each step in Integrated Delivery prepares some records for BI which are uploaded in batch. This scenario also receives documents from ERP and data is transferred back to ERP using PI. This group is for the sizing for the SCM Event handlers.

A213


B213


C213


D213


A215

All receives all EPC information for one packed pallet. This information is replicated to SCM. This sizing is only valid for <= 100 EPC's per delivery.

B215

Enter the number of deliveries processed per peak time period. Do not divide by 100.

C215

Enter the number of line items per delivery during this peak time period.

D215

Enter the number of EPC-Tags per delivery for this peak time period.

E215


F215

Enter the number of pieces per line item for this peak time.

G215

Enter the number of pallets per delivery for this peak time period.

A217

Pallets leave/enter the warehouse and goods issue /receipt is registered. This information is replicated to SCM. This sizing is only valid for <= 100 EPC's per delivery.

B217


C217


D217


E217


F217


G217

Enter the number of pallets per delivery for this peak time period.

A219

Pallets leave/enter the warehouse and goods issue /receipt is registered. This information is replicated to SCM. This sizing is only valid for <= 100 EPC's per delivery.

B219


C219


D219


E219


F219


© Copyright IBM Corp. April-2008 INFORMATION ON DOING AN UPGRADE SIZING

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

Upgrade Sizing information for System i

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

Upgrade Sizing information for System xAre you running the SAP workload in a VMware environment? noIs hyperthreading enabled on your current SAP system? no

Upgrade Sizing information for System z

A2

To size your current workload use the Insight tool to capture the 2-3 day period of your peak workload. Download Insight at: http://www-03.ibm.com/support/techdocs/atsmastr.nsf/PubAllNum/PRS381 If SAP is running on System z or System i please read the respective section below. If SAP is running in a shared processor pool on system p read the System p section below. IF SAP is running in a VMware type of shared environment read the System x section below.

A9

a) Select an appropriate timeframe (usually a peak) based on the customer’s workload or business schedule. b) Determine if the SAP system to be measured runs in its own LPAR or shares the LPAR with other non-SAP work. c) If it runs in its own LPAR, request an i5/OS Performance Tool (or other similar tool) report. For Performance Tool request a run during the peak 2-3 day period. Request an interval of 60 seconds. The report will specify the CPU utilization of the assigned processors. This may exceed 100% in cases where the LPAR exceeded its assigned number of processors. The resulting report should be analyzed and the 95th percentile used to calculate the CPU utilization for sizing purposes. d) If it runs in the same LPAR with other work then the customer needs to estimate the amount of the reported CPU utilization that should be attributed to the SAP workload.

A11

a) Select an appropriate timeframe (usually a peak) based on the customer’s workload or business schedule. b) Determine if the SAP system to be measured runs in its own LPAR or shares the LPAR with other non-SAP work. c) If it runs in its own LPAR, request a Nigel’s Monitor (NMON, or other similar tool) report. See techdocs PRS 3754. For NMON, request a run during the peak 2-3 day period. Request an interval of 60 seconds. This would be something like -s 60 -c 4320 The resulting report should be analyzed to calculate the CPU utilization for sizing purposes. d) If it runs in the same LPAR with other work then the customer needs to estimate the amount of the reported CPU utilization that should be attributed to the SAP workload.

A13

Using simultaneous multi threading(SMT) provides about a 30% capacity advantage over previously releases of AIX.

A14

If SAP is running in an LPAR which is part of a pool of LPARs that shares CPU's, then a tool such as NMON is needed to provide an accurate estimate of the current workload.

A16

a) Select an appropriate timeframe (usually a peak) based on the customer’s workload or business schedule. b) Determine if the SAP system to be measured runs in its own virtual machine (VM) or shares the VM with other non-SAP work. c) If it runs in its own VM, request a VMware esxtop (or other similar tool) report. Obtain the VM’s id (VMID) from the ESX server management tool called Virtual Center. For esxtop request a run during the peak 2-3 day period. Request an interval of 60 seconds. The report will specify the CPU utilization of the assigned processors. The esxtop tool runs from the ESX Server command line and you can obtain help by typing 'man esxtop'. The resulting report should be analyzed and the 95th percentile used to calculate the CPU utilization for sizing purposes. d) If it runs in the same VM with other work then the customer needs to estimate the amount of the reported CPU utilization that should be attributed to the SAP workload.

A17

If SAP is running in a virtual machine which is part of a pool of virtual machines that shares CPU's, then a tool such as esxtop is needed to provide an accurate estimate of the current workload.

A20

a) Select an appropriate timeframe (usually a peak) based on the customer’s workload or business schedule. b) Determine if the SAP system to be measured runs in its own LPAR or shares the LPAR with other non-SAP work. c) If it runs in its own LPAR, request a Resource Measurement Facility (RMF) CPU Summary Report and CPU Activity Report for that LPAR in no more than 15 minute intervals (if the timeframe is short, for example only a few hours, then 5 minute intervals may be more appropriate). The Summary Report displays the LPAR’s logical CPU utilization for that interval. To determine the number of logical engines you must look at the CPU Activity Report - Partition Data Report. One of the columns displays the number of logical engines assigned to that LPAR. This data can then be used in a spreadsheet to calculate the required metric..e.g. 90 percentile value. d) If it runs in the same LPAR with other work then the customer must provide a copy of their WLM Service Policy or provide a list of the WLM Service or Report Classes corresponding to the specific work to be measured. You must then request an RMF WLM Report - Goal Mode. For each service or report class to include there will be a field called ‘APPL%’ - this is the measurement for that interval of the work consumed by that service or report class based on a single CPU engine. So, for example, if the value is 123% for a 15 minute interval then the service class used the equivalent of 1.23 engines during that timeframe on average. All of the service or report classes must be summed for that interval in order to determine the utilization of that specific workload. 4b. What is the recommended process for System p? a) Select an appropriate timeframe (usually a peak) based on the customer’s workload or business schedule. b) Determine if the SAP system to be measured runs in its own LPAR or shares the LPAR with other non-SAP work. c) If it runs in its own LPAR, request a Nigel’s Monitor (NMON, or other similar tool) report. For NMON, request a run during the peak 2-3 day period. Request an interval of 60 seconds. This would be something like -s 60 -c 4320 The resulting report should be analyzed and the 95th percentile used to calculate the CPU utilization for sizing purposes. d) If it runs in the same LPAR with other work then the customer needs to estimate the amount of the reported CPU utilization that should be attributed to the SAP workload.

© Copyright IBM Corp. April-2008

INPUTS USER BASED THRUPUT BASEDChanged # of users SAPS Storage Changed ?

ERP NO 0 0 Qser NOCRM NO 0 0 0 NOBW/SEM NO 0 NA NA NOPortal NO 0 NA NA NOPI NA NA NA NA NOTREX NA 0 0 0 NOSM NA 0 NA NA NOSCM APO NA NA NA NA NOSRM NO 0 NA NA NOGTS NA NA NA NA NOBanking NA NA NA NA NOInsurance NA NA NA NA NORetail NA NA NA NA NOUtilities NA NA NA NA NOPLM NA 0 0 0 NOMDM NA 0 0 0 NOMISC NA 0 0 0 NOUpgrade NA NA NA NA NOTotals 0 0 0

SAP Questionnaire 061510

Documents

average vendor

average workday

average workday

srm shopping

virsa sizing

average sales

peak vendor

local sap