Professional Documents
Culture Documents
SAP Questionnaire 061510
SAP Questionnaire 061510
Send completed questionnaire and SAP sizing questions to either your local IBM contact or:
Region North and South America IBM Contact IBM Americas Techline Solutions Sizing by E-mail / Fax [email protected] / +1 845-491-2372
BPs raise a Techline Request through http://www.ibm.com/partnerworld/techline For both : in case of attachment problems, send file [email protected] to
IBM ASEAN/SA Techline(Singapore, Malaysia, Thailand, Philippines, Indonesia, Vietnam, India and Sri Lanka) GCG(China) Hong Kong Taiwan South Korea Japan Australia and New Zealand IBM SAP International Competence Center, ISICC, Walldorf
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.
What has to be Sized? SAP architectures have evolved from a client-server model to a Web-enabled front-end environment. The front-end device and network elements are shared across IT applications and a dedicated server infrastructure for SAP application and database server is required. The server infrastructure includes a hardware server plus operating system platform, a relational database and the application itself. To obtain satisfactory end-user response times for any application, the technical specification for the client device, network and the server infrastructure must be sized and specified. The purpose of this questionnaire is to collect information that will be used to estimate the IBM hardware resources required to run the SAP application suite on IBM eServers including System z, System i, System p, System x or mixed environments. The sizing estimate results will include recommendations for CPU(s), memory, and disk for the server infrastructure. In addition, information from the sizing questionnaire may be used by an IBM sales representative or business partner to develop an IBM infrastructure proposal including additional hardware and software e.g. for systems management to support the SAP applications. A sizing estimate is an approximation of the hardware resources required to support an SAP solution or component implementation. It is a pre-sales effort based on information available at a point in time, providing an entry into understanding the customers hardware requirements. Customers actual experiences will vary from the sizing estimate for many reasons, including batch and reporting workloads, and custom code. The degree of variability can range from small to very significant. Sizing the hardware requirements for each customers SAP implementation is an iterative process, which may be refined and repeated a number of times. We recommend checking the sizing input data and estimations during the implementation project. It is important to understand that the sizing estimate is a pre-installation effort mainly based on standard assumptions and benchmark performance data; it can not replace capacity planning for installed systems. The IBM/SAP sizing methodology is continually reviewed and revised to provide the best possible estimate of the IBM hardware resources required to run SAP. Guidelines for sizing SAP solutions come from a number of sources, including SAP, SAP benchmarks, and customer feedback. Based on this information and your completed sizing questionnaire, we will analyze your requirements and recommend an IBM hardware configuration. Sizing Assumptions This sizing will estimate the resources required to support your SAP activity with default values for CPU utilization, batch, spool, and reporting. The default values have been determined as a result of our experience with many SAP projects and sizings. This sizing estimation includes a workload from a provider other than IBM. IBM is not responsible for the accuracy of the data contained in such a workload. Any reliance by you on the third party workload is at your sole risk and will not create any liability or obligation for IBM. If you have any questions or are unsatisfied with the third party workload information, you should contact the third party provider. The system resources quoted to you in any sizing related communications are sufficient only for the workload(s) estimated. Other factors may require additional resources (e.g. additional non-estimated workloads, minimum configurations for RAID, allowance for growth, workspace, etc). The information provided to you in any sizing related communications are provided by International Business Machines Corporation (IBM) as a service to you and may be used for informational purposes only. Use of any sizing related communications is restricted to the purpose of helping you predict a possible IBM eServer model processor, memory and disk resources for a given workload. All representations of processor utilization, throughput, response time, memory, disk, and other performance data in the sizing
communications are estimates and averages based on certain assumptions and conditions. No representation is made that these throughputs and their corresponding response times or other performance data will be accurate or achieved in any given IBM eServer installation environment. They are based on specific configurations and run time environments. Customer results will vary. Any configuration recommended by the sizing information communicated should be tested and verified. By accepting this information or using the sizing details you agree to the terms and conditions contained herein. If you do not agree with such terms and conditions, please do not review or use the provided materials and return the materials to IBM. Customer results may vary, and IBM assumes no liability for actual results that differ from the sizing estimate.
Contact Information
Please fill in the information on the following contact points. If unknown or not applicable, leave blank. Opportunity NumberREQUIRED QuickSizer customer number QuickSizer project name Company Name Street Address City, State/Province Zip/Postal Code, Country Customer Contact Title Phone Number e-mail address IBM Contact Phone Number e-mail address SAP Contact Phone Number e-mail address
Business Partner or SAP Value Added Reseller Contact Phone Number e-mail address
General Sizing Questions for Initial Sizings New Installation or new workloads
In this section, we would like to know about your hardware and software requirements. Some of the subsections require responses; others are optional. This section is intended for new SAP implementations. If you already have installed SAP components and you want to expand your installation by adding new modules or additional users or new components or solutions, you should select Upgrade Sizing when generating this questionnaire. Industry Solution Please specify if you plan to implement a specific industry solution or want to give any other additional information:
Application Server(s) System z System p System x System i System p System x System x System x
Storage Sizing
Storage Capacity Questions What RAID Technology will you use? At what capacity do you run your storage subsystem? What storage growth factor per year over how many years would you like us to use? What storage compression factor would you like us to use? Will you be backing up data directly to tape? Full backup to disk? Incremental backup to disk? Answer Options Default-RAID5 Default-80% Default-0%, 0 years Default-0% Default-to tape
Scalability Sizing
Scalability Questions How important is scalability in your hardware configuration? Answer Options Default-not important
Backup/Restore Sizing
Backup/Restore Question Do you want a backup device included in the proposed configuration? Answer Options Default-no
UNICODE Sizing
UNICODE is an international character set standard which allows you to process and store virtually all the languages and scripts in the world. UNICODE Question Answer Options Will you be using UNICODE? Default-yes
questionnaire. If desired, you can use this section to request sizing estimates for specific project phases. A project phase may be the implementation of one or more SAP business applications, growth in terms of additional users, or growth in business volumes. If you plan to implement in different phases, please copy the respective tabs of the questionnaire and submit together.
Type of Sizing
Type of Sizing Questionnaire Answer Options
NON-PRODUCTION SYSTEMS
System Landscape (required) A system landscape consists of the systems and clients that are needed for non-production. Once the system landscape has been defined, you may then create an implementation strategy for the setup and maintenance of the systems and clients within this landscape. IBM and SAP strongly recommend having at least a three-system landscape. A three-system landscape is comprised of a development system, a quality assurance system and a production system. This configuration ensures the proper management and testing of changes to the system before applying them to the live production environment. If nothing is specified we will assume a Dev and Test system. Type First non-production system Second non-production system Third non-production system, if needed Fourth non-production system, if needed Fifth non-production system, if needed Please specify any other additional information to help in sizing Default Dev QA None None None Size Storage Default 100GB's =prod None None None
Enter total CONCURRENT users during the PEAK hour--A user must NOT be counted twice He is either one type of concurrently active user or another--NOT both at the same time during the PEAK hour
PP-Users in Production Planning-PEAK PER HOUR PS-Users in Project Management-PEAK PER HOUR QM-Users in Quality Management-PEAK PER HOUR CS-Users in Customer Service-PEAK PER HOUR SD-Users in Sales & Distribution-PEAK PER HOUR BC-Users in Basis transactions-PEAK PER HOUR TOTAL CONCURRENT PEAK users -PEAK PER HOUR Approximate SAPS Approximate Storage If AFS is implemented add this uplift
0 0 Qser 0
THRUPUT SIZING FOR FINANCIALS--If you complete this section, you must resolve all "ERROR" messages.
CO-PA-BIL-AVERAGE Billing docs posted to CO per YEAR CO-PA-BIL-PEAK Billing docs posted to CO per PEAK TIME CO-PA-FI-AVERAGE Financial docs posted to CO per YEAR CO-PA-FI-PEAK Financial docs posted to CO per PEAK TIME CO-PA-SLS-AVERAGE Sales orders posted to CO per YEAR CO-PA-SLS-PEAK Sales orders posted to CO per PEAK TIME CO-AVERAGE Controlling docs or postings per YEAR CO-PEAK Controlling docs or postings per PEAK TIME EC-PCA-AVERAGE Profit center charged off docs per YEAR EC-PCA-PEAK Profit center charged off docs per PEAK TIME FIN-BAC-AVERAGE Business Accounting docs per YEAR FIN-BAC-PEAK Business Accounting docs per PEAK TIME OBJECTS ITEMS 0 0 0 0 0 0 0 0 0 0 0 0 OBJECTS CO-OM-PEAK Sender-receiver relations for all cycles CO-OM-RAT-PEAK Orders/period with overhead rate CO-OM-SET-PEAK Orders allocated/period NA NA NA NA NA NA NA NA NA NA NA NA % CHG % DISP MONTHS ST TIME END TIME 0 NA NA NA 12:00 13:00 0 NA NA NA 12:00 12:00 0 NA NA NA 12:00 12:00 0 NA NA NA 12:00 12:00 0 NA NA NA 12:00 12:00 0 NA NA NA 12:00 12:00 ST TIME END TIME 0 0 0 0 0 0
Contract Accounting--If you complete this section, you must resolve all "ERROR" messages. OBJECTS ITEMS EDRs/bd EDR-BILL-PEAK Event Detail Record 0 0 OBJECTS ITEMS 0 0 0 0 OBJECTS EDR-UPL-PEAK EDR Upload NA NA
NA
NA
LOAD-BILL-PEAK Load Billing LOAD-INV-PEAK Load Invoicing CONV-INV-PEAK Convergent Invoicing DUNNING-PEAK Dunning
NA NA NA NA
NA NA NA NA
NA NA NA NA
NA
NA
PAY-RUN-PEAK Payment Run CD-PL-PEAK Payment Lots CORR-PRINT-PEAK Correspondence Print DEF-POST-PEAK Deferred Postings EDRs EDR-UPL-AVERAGE Event Detail Record Upload OBJECTS PAY-RUN-AVERAGE Payment Run CD-PL-AVERAGE Payment Lots CORR-PRINT-AVERAGE Correspondent Print DEF-POST-AVERAGE Deferred Postings
NA NA NA NA AddFld
NA NA NA NA
NA NA NA NA
NA NA NA NA
0 0 0 0
0 0 0 0
NA
NA
MONTHS ST TIME END TIME 0 NA NA MONTHS ST TIME END TIME 0 NA NA 0 NA NA 0 NA NA 0 NA NA MONTHS ST TIME END TIME 0 NA NA 0 NA NA 0 NA NA 0 NA NA P itm 0 % credit MONTHS ST TIME END TIME 0 NA NA
NA NA NA NA
NA NA NA NA
EDR-BILL-AVERAGE Event Detail Record Billing LOAD-BILL-AVERAGE Load Billing CONV-INV-AVERAGE Convergent Invoicing DUNNING-AVERAGE Dunning
NA NA NA NA GL itm 0
NA NA NA NA Payments 0
THRUPUT SIZING FOR HUMAN CAPITAL MANAGEMENT--If you complete this section, you must resolve all "ERROR" messages.
ESS/MSS workload ESS-LEAVE ESS-CATS ESS-TRAVEL MSS_COST MSS-PERS Scenarios Steps 7 9 18 9 13 NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA ST TIME END TIME 0 0 0 0 0 0 0 0 0 0
OBJECTS HCM-PT-AVERAGE Processed Time Pairs per YEAR HCM-PT-PEAK Processed Time Pairs per PEAK TIME HCM-PY-AVERAGE Payroll periods incl retro calculations HCM-PY-PEAK Payroll periods incl retro calculations NA NA NA NA NA NA NA NA NA NA NA NA
THRUPUT SIZING FOR E-Recruitment--If you complete this section, you must resolve all "ERROR" messages.
ERC-CA-REG-AVERAGE Candidate Registrations per YEAR ERC-CA-REG-PEAK Candidate Registrations per PEAK TIME OBJECTS ITEMS 0 0 % CHG % DISP DCS no no Attach NA Size NA MONTHS ST TIME END TIME 0 NA NA NA 0 0
% CHG
% DISP
DCS no
% CHG
% DISP
% CHG NA
% DISP
ERC-JOB-SE-PEAK Candidate Applications per PEAK TIME OBJECTS ERC-CA-LST-PEAK Requisition creation per PEAK TIME
% CHG NA
% DISP
THRUPUT SIZING FOR LOGISTICS EXECUTION--If you complete this section, you must resolve all "ERROR" messages.
LE-WM-AVERAGE Transfer Orders per YEAR LE-WM-PEAK Transfer Orders per PEAK TIME LE-SHP-AVERAGE Delivery notes and goods issue per YEAR LE-SHP-PEAK Delivery notes and goods issue per PEAK TIME OBJECTS ITEMS 0 0 0 0 % CHG % DISP MONTHS ST TIME END TIME 0 NA NA NA 0 0 0 NA NA NA 0 0
THRUPUT SIZING FOR PRODUCT DEV AND EXECUTION--If you complete this section, you must resolve all "ERROR" messages.
ALM-PM-AVERAGE Maintenance Orders per YEAR ALM-PM-PEAK Maintenance Orders per PEAK TIME MM-IM-AVERAGE Material Movements per YEAR MM-IM-PEAK Material Movements per PEAK TIME MM-PUR-AVERAGE Purchase Orders per YEAR MM-PUR-PEAK Purchase Orders per PEAK TIME PP-CONF-AVERAGE Order Confirmations per YEAR PP-CONF-PEAK Order Confirmations per PEAK TIME PP-REM-AVERAGE Planned Orders per YEAR PP-REM-PEAK Planned Orders per PEAK TIME PP-SFC-AVERAGE Production Orders per YEAR PP-SFC-PEAK Production Orders per PEAK TIME QM-IM-AVERAGE Inspections in Quality Mgmt per YEAR QM-IM-PEAK Inspections in Quality Mgmt per PEAK TIME OBJECTS ITEMS 0 0 0 0 0 0 0 0 0 0 0 0 0 0 OBJECTS PS-AVERAGE Projects per YEAR PS-PEAK Projects per PEAK TIME PLAN OR MRP RUN WBS 0 0 COMP 0 % CHG % DISP MONTHS ST TIME END TIME 0 NA NA NA 0 0 0 NA NA NA 0 0 0 NA NA NA 0 0 0 NA NA NA 0 0 0 NA NA NA 0 0 0 NA NA NA 0 0 0 NA NA NA 0 0 Act/Net % CHG % DISP MONTHS ST TIME END TIME 0 NA NA NA 0 0 % DISP % LTS ST TIME END TIME 0 0
NETW
THRUPUT SIZING FOR SALES AND SERVICE--If you complete this section, you must resolve all "ERROR" messages.
CS-AG-AVERAGE Customer Service objects per YEAR CS-AG-PEAK Customer Service objects per PEAK TIME SD-CUST-AVERAGE Customer Contacts per YEAR SD-CUST-PEAK Customer Contacts per PEAK TIME SD-BIL-AVERAGE Billing Documents per YEAR SD-BIL-PEAK Billing Documents per PEAK TIME SD-POS-AVERAGE Point of Sales objects for Retail per YEAR SD-POS-PEAK Point of Sales objects for Retail per PEAK TIME SD-SLS-AVERAGE Sales Orders per YEAR SD-SLS-PEAK Sales Orders per PEAK TIME OBJECTS ITEMS 0 0 0 0 0 0 0 0 0 0 COM CAS REMC 0 0 DOCU ICM-DOC-AVERAGE Commission documents posted per YEAR ICM-DOC-PEAK Commission documents posted per PEAK TIME REMD 0 0 % CHG % DISP MONTHS ST TIME END TIME 0 NA NA NA 0 0 0 NA NA NA 0 0 0 NA NA NA 0 0 0 NA NA NA 0 0 0 NA NA NA 0 0 MONTHS ST TIME END TIME 0 NA NA NA 0 0 MONTHS ST TIME END TIME 0 NA NA NA 0 0 ST TIME END TIME NA NA 0 0
ICM-CASE-AVERAGE Customer Service cases per YEAR ICM-CASE-PEAK Customer Service cases per PEAK TIME
NA NA
NA NA
NA NA
NA NA
ICM-SET-AVERAGE Settlement items per YEAR ICM-SET-PEAK Settlement items PEAK TIME
NA NA
NA NA
NA NA
THRUPUT SIZING FOR CORPORATE SERVICES--If you complete this section, you must resolve all "ERROR" messages.
TV-RECEIPT-AVERAGE Travel Receipts per YEAR TV-RECEIPT-PEAK Travel Receipts per PEAK TIME OBJECTS ITEMS 0 0 % CHG % DISP MONTHS ST TIME END TIME 0 NA NA NA 0 0
THRUPUT SIZING FOR APPLICATION SERVER SERVICES--If you complete this section, you must resolve all "ERROR" messages.
OBJECTS BC-PRINT-AVERAGE Print Pages per YEAR BC-PRINT-PEAK Print Pages per PEAK TIME NA NA % CHG % DISP MONTHS ST TIME END TIME 0 NA NA NA 0 0
NON-PRODUCTION SYSTEMS
System Landscape (required) A system landscape consists of the systems and clients that are needed for non-production. Once the system landscape has been defined, you may then create an implementation strategy for the setup and maintenance of the systems and clients within this landscape. IBM and SAP strongly recommend having at least a three-system landscape. A three-system landscape is comprised of a development system, a quality assurance system and a production system. This configuration ensures the proper management and testing of changes to the system before applying them to the live production environment. If nothing is specified we will assume a Dev and Test system. Type First non-production system Second non-production system Third non-production system, if needed Fourth non-production system, if needed Fifth non-production system, if needed Please specify any other additional information to help in sizing Default Dev QA None None None Size Storage Default 100GB's =prod None None None
Enter total CONCURRENT users during the peak hour--A user must NOT be counted twice He is either one type of user or another--NOT both at the same time during the PEAK hour
THRUPUT SIZING FOR CRM Acc for BP's--If you complete this section, you must resolve all "ERROR" messages.
New Acct CRM-CORACC-AVERAGE Corp Accounts per YEAR CRM-CORACC-PEAK Corp Accounts per PEAK TIME CRM-INDACC-AVERAGE Individual Accounts per YEAR CRM-INDACC-PEAK Individual Accounts per PEAK TIME NA NA NA NA Chg Acct Dis Acct Tot Acct 0 NA 0 NA ST TIME END TIME NA NA 0 0 NA NA 0 0
THRUPUT SIZING FOR CRM SALES--If you complete this section, you must resolve all "ERROR" messages.
CRM-SLSQC-AVERAGE sales quotations per YEAR CRM-SLSQC-PEAK sales quotations per PEAK TIME CRM-SLS-AVERAGE sales orders per YEAR CRM-SLS-PEAK sales orders per PEAK TIME CRM-SLSCO-AVERAGE sales contracts per YEAR CRM-SLSCO-PEAK sales contracts per PEAK TIME OBJECTS ITEMS 0 0 0 0 0 0 OBJECTS CRM-LEAD-AVERAGE sales leads per YEAR CRM-LEAD-PEAK sales leads per PEAK TIME CRM-ACT-AVERAGE sales activities per YEAR CRM-ACT-PEAK sales activities per PEAK TIME CRM-APP-AVERAGE sales appointments per YEAR CRM-APP-PEAK sales appointments per PEAK TIME CRM-OPP-AVERAGE sales opportunities per YEAR CRM-OPP-PEAK sales opportunities per PEAK TIME NA NA NA NA NA NA NA NA % CHG % DISP MONTHS ST TIME END TIME 0 NA NA NA 0 0 0 NA NA NA 0 0 0 NA NA NA 0 0 % DISP MONTHS ST TIME END TIME 0 NA NA NA 0 0 0 NA NA NA 0 0 0 NA NA NA 0 0 0 NA NA NA 0 0
% CHG
THRUPUT SIZING FOR CRM SERVICE--If you complete this section, you must resolve all "ERROR" messages.
CRM-SRVQC-AVERAGE service order quotes per YEAR CRM-SRVQC-PEAK service order quotes per PEAK TIME CRM-SRV-AVERAGE service orders per YEAR CRM-SRV-PEAK service orders per PEAK TIME CRM-SRVCC-AVERAGE service contracts/quotes per YEAR CRM-SRVCC-PEAK service contracts/quotes per PEAK TIME CRM-CPLT-AVERAGE compliants/returns/repairs per YEAR CRM-CPLT-PEAK complaints/returns/repairs per PEAK TIME CRM-WCL-AVERAGE warranty claims per YEAR CRM-WCL-PEAK warranty claims per PEAK TIME OBJECTS ITEMS 0 0 0 0 0 0 0 0 0 0 OBJECTS CRM-SRVAC-AVERAGE service activities per YEAR CRM-SRVAC-PEAK service activities per PEAK TIME CRM-CONF-AVERAGE service confirmations per YEAR CRM-CONF-PEAK service confirmations per PEAK TIME % CHG % DISP MONTHS ST TIME END TIME 0 NA NA NA 0 0 0 NA NA NA 0 0 0 NA NA NA 0 0 0 NA NA NA 0 0 0 NA NA NA 0 0 % DISP MONTHS ST TIME END TIME 0 NA NA NA 0 0 0 NA NA NA 0 0
% CHG
THRUPUT SIZING FOR CRM E-COMMERCE--If you complete this section, you must resolve all "ERROR" messages.
VISITS AVERAGE Internet sales orders and visits per YEAR PEAK Internet sales orders and visits per PEAK TIME NA NA % ORD 0 0 ITEMS 0 0 IPC No No MONTHS ST TIME END TIME 0 NA NA NA 0 0
THRUPUT SIZING FOR CRM IC--If you complete this section, you must resolve all "ERROR" messages.
OBJECTS AVERAGE calls/emails in customer center per YEAR PEAK calls/emails in customer center per PEAK TIME NA NA % CHG % DISP MONTHS ST TIME END TIME 0 NA NA NA 0 0
THRUPUT SIZING FOR CRM MOBILE--If you complete this section, you must resolve all "ERROR" messages.
AVERAGE orders thru Mobile Sales and Service per YEAR PEAK orders thru Mobile Sales and Service per PEAK TIME OBJECTS ITEMS 0 0 % CHG % DISP MONTHS ST TIME END TIME 0 NA NA NA 0 0
Click for sizing white paper Bus Part Activities Int Objects e-mails
to BW
CRM
Core TPM process(adding products) Generation of price/rebate condition records process Generation of campaign determination condition records process Rendering the planning layout Re-synchronizing with SAP NW BW(Saving the promotion) Total for CRM
0 0 0 0 0 0
0 0 0 0 0 0
SEM/BI
Rendering the planning layout Re-synchronizing with SAP NW BW(Saving the promotion) Total for SEM/BI
0 0 0
0 0 0
NON-PRODUCTION SYSTEMS
System Landscape (required) A system landscape consists of the systems and clients that are needed for non-production. Once the system landscape has been defined, you may then create an implementation strategy for the setup and maintenance of the systems and clients within this landscape. IBM and SAP strongly recommend having at least a three-system landscape. A three-system landscape is comprised of a development system, a quality assurance system and a production system. This configuration ensures the proper management and testing of changes to the system before applying them to the live production environment. If nothing is specified we will assume a Dev and Test system. Type First non-production system Second non-production system Third non-production system, if needed Fourth non-production system, if needed Fifth non-production system, if needed Please specify any other additional information to help in sizing Default Dev QA None None None Size Storage Default 100GB's =prod None None None
Enter total CONCURRENT users during the peak hour--A user must NOT be counted twice He is either one type of user or another--NOT both at the same time during the peak hour
INFOCUBES
DIMEN INFOCUBE-DISK-Duplicate as needed KEY FIG INITIAL PERIODIC PERIODS 0 BWA no % MD 10 D Values % DVL 7 % DV1
DATASTORE OBJECTS
NUMFLD DS OBJECTS-DISK-Duplicate as needed TXTFLD Character WO no INITIAL PERIODIC PERIODS 0
NON-PRODUCTION SYSTEMS
System Landscape (required) A system landscape consists of the systems and clients that are needed for non-production. Once the system landscape has been defined, you may then create an implementation strategy for the setup and maintenance of the systems and clients within this landscape. IBM and SAP strongly recommend having at least a three-system landscape. A three-system landscape is comprised of a development system, a quality assurance system and a production system. This configuration ensures the proper management and testing of changes to the system before applying them to the live production environment. If nothing is specified we will assume a Dev and Test system. Type First non-production system Second non-production system Third non-production system, if needed Fourth non-production system, if needed Fifth non-production system, if needed Please specify any other additional information to help in sizing Default Dev QA None None None Size Storage Default 100GB's =prod None None None
Enter total CONCURRENT users during the peak hour--A user must NOT be counted twice He is either one type of user or another--NOT both at the same time during the peak hour
Enterprise Portal
NW-EP-URL-PEAK NW-EP-INT-PEAK NW-EP-PCC-PEAK NW-EP-PRT-PEAK Total Users USERS Think time Java iViews 600 0 211 3 180 3 0 0 0 URL iViews 1 0 0 0
Co p yr ig h t IB M Co r p . Ap r il-2008
NON-PRODUCTION SYSTEMS
System Landscape (required) A system landscape consists of the systems and clients that are needed for non-production. Once the system landscape has been defined, you may then create an implementation strategy for the setup and maintenance of the systems and clients within this landscape. IBM and SAP strongly recommend having at least a three-system landscape. A three-system landscape is comprised of a development system, a quality assurance system and a production system. This configuration ensures the proper management and testing of changes to the system before applying them to the live production environment. If nothing is specified we will assume a Dev and Test system. Type First non-production system Second non-production system Third non-production system, if needed Fourth non-production system, if needed Fifth non-production system, if needed Please specify any other additional information to help in sizing Default Dev QA None None None Size Storage Default 100GB's =prod None None None
NON-PRODUCTION SYSTEMS
System Landscape (required) A system landscape consists of the systems and clients that are needed for non-production. Once the system landscape has been defined, you may then create an implementation strategy for the setup and maintenance of the systems and clients within this landscape. IBM and SAP strongly recommend having at least a three-system landscape. A three-system landscape is comprised of a development system, a quality assurance system and a production system. This configuration ensures the proper management and testing of changes to the system before applying them to the live production environment. If nothing is specified we will assume a Dev and Test system. Type First non-production system Second non-production system Third non-production system, if needed Fourth non-production system, if needed Fifth non-production system, if needed Please specify any other additional information to help in sizing Default Dev QA None None None Size Storage Default 100GB's =prod None None None
NON-PRODUCTION SYSTEMS
System Landscape (required) A system landscape consists of the systems and clients that are needed for non-production. Once the system landscape has been defined, you may then create an implementation strategy for the setup and maintenance of the systems and clients within this landscape. IBM and SAP strongly recommend having at least a three-system landscape. A three-system landscape is comprised of a development system, a quality assurance system and a production system. This configuration ensures the proper management and testing of changes to the system before applying them to the live production environment. If nothing is specified we will assume a Dev and Test system. Type First non-production system Second non-production system Third non-production system, if needed Fourth non-production system, if needed Fifth non-production system, if needed Please specify any other additional information to help in sizing Default Dev QA None None None Size Storage Default 100GB's =prod None None None
QUICKSIZER SIZING FOR SCM What release of SCM are you implementing What time does the AVERAGE workday start What time does the AVERAGE workday end What time does the PEAK load start What time does the PEAK load end 5 9:00 18:00 12:00 13:00
NON-PRODUCTION SYSTEMS System Landscape (required) A system landscape consists of the systems and clients that are needed for non-production. Once the system landscape has been defined, you may then create an implementation strategy for the setup and maintenance of the systems and clients within this landscape. IBM and SAP strongly recommend having at least a three-system landscape. A three-system landscape is comprised of a development system, a quality assurance system and a production system. This configuration ensures the proper management and testing of changes to the system before applying them to the live production environment. If nothing is specified we will assume a Dev and Test system. Type First non-production system Second non-production system Third non-production system, if needed Fourth non-production system, if needed Fifth non-production system, if needed Please specify any other additional information to help in sizing Default Dev QA None None None Size Storage Default 100GB's =prod None None None
QuickSizer customer number QuickSizer project name THRUPUT SIZING FOR DEMAND PLANNING CharCom TIMESERIES-Planning Area Sizing for LiveCache memory CharCom DP-RUN-Planning Run Sizing for CPU NA NA NA KeyFig 0 Periods 0 Com Index Times 0 Time Buck Pl Vers 0
APO Users DP-USER-Additional Users for CPU THRUPUT SIZING FOR SUPPLY & PRODUCTION PLANNING LOC PROD Resources MASTERDAT-Master data Sizing for LiveCache memory SCM OBJ STOCK-Warehouse Stocks Sizing for LiveCache memory SCM OBJ PLANNEDORD-Planned orders Sizing for LiveCache memory SCM OBJ FORECAST-Forecast orders Sizing for LiveCache memory PURCHORD-Purchase orders Sizing for LiveCache memory SALES-Sales orders Sizing for LiveCache memory TRANSFER-Transfer orders Sizing for LiveCache memory SKUs SNP-RUN-Heuristic plan Sizing for CPU--PEAK APO User PP USER-Planning Board User Sizing for CPU--PEAK SNP USER-SNP User Sizing for CPU--PEAK THRUPUT SIZING FOR ORDER FULFILLMENT Loc prod ATP-MD-ATP Masterdata Sizing for LiveCache memory Requests ATP-SIMPLE-ATP simple checks Sizing for CPU--PEAK ATP-RULE-ATP rules based checks Sizing for CPU--PEAK ATP-CTP-ATP Capable to promise checks Sizing for CPU--PEAK THRUPUT SIZING FOR SERVICE PARTS PLANNING SKUs SPP-STK-Stocking--PEAK SPP-DESTK-Destocking--PEAK SPP-EOQ-Economic order quantity--PEAK NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA Components 0 SUB OBJ 0 0 0 0 OPER 0 NA NA NA NA
SPP-DPLY-Deployment--PEAK Period Based Planning SPP-FCST-Forecasting--PEAK DRP Run SPP-DRP-Distribution requirements planning--PEAK SNC-Purchase Order Collaboration Profile Initial Sizing--See whitepaper on the QuickSizer website SNC-Release Processing Profile Initial Sizing--See whitepaper on the QuickSizer website SNC-Supplier Managed Inventory-SNI Profile Initial Sizing--See whitepaper on the QuickSizer website SKUs
NA
NA
NA
NA
NA PB Stk. M
NA Loc
SAPS 0
Storage 0
SAPS 0
Storage 0
SAPS 0
Storage 0
THRUPUT SIZING FOR INTEGRATION TO ECC SCM objects PI-PROD-PEAK Manufacturing Orders per PEAK TIME PI-SALES-PEAK Sales Orders per PEAK TIME PI-PURCH-PEAK Purchase Orders per PEAK TIME PI-STOCKL-PEAK Stock movements per PEAK TIME THRUPUT SIZING FOR EWM INBOUND OBJECTS IEWM-DLV-AVERAGE Inbound delivery documents per YEAR IEWM-DLV-PEAK Inbound delivery documents per PEAK TIME Ware tasks IEWM-UNTSK-AVERAGE creation of unloading tasks per YEAR IEWM-UNTSK-PEAK creation of unloading tasks per PEAK TIME IEWM-CONF-AVERAGE confirm of unloading tasks per YEAR IEWM-CONF-PEAK confirm of unloading tasks per PEAK TIME Ware tasks NA NA NA NA NA NA NA NA % DISP ITEMS 0 0 % CHG % DISP MONTHS ST TIME END TIME 0 NA NA NA 0 0 MONTHS ST TIME END TIME 0 NA NA NA 0 0 0 NA NA NA 0 0 MONTHS ST TIME END TIME Items 0 0 0 1 NA NA NA NA NA NA NA NA NA NA NA NA ST TIME END TIME 0 0 0 0 0 0 0 0
% DISP
IEWM-PATSK-AVERAGE creation of putaway tasks per YEAR IEWM-PATSK-PEAK creation of putaway tasks per PEAK TIME Ware tasks IEWM-PACON-AVERAGE confirm of putaway tasks per YEAR IEWM-PACON-PEAK confirm of putaway tasks per PEAK TIME Ware tasks IEWM-RESPA-AVERAGE chg/resource of putaway tasks per YEAR IEWM-RESPA-PEAK chg/resource of putaway tasks per PEAK TIME HU's IEWM-DECON-AVERAGE unpacking of putaway tasks per YEAR IEWM-DECON-PEAK unpacking of putaway tasks per PEAK TIME Ware tasks IEWM-MOVE-AVERAGE move warehouse tasks per YEAR IEWM-MOVE-PEAK move warehouse tasks per PEAK TIME Ware tasks IEWM-RESFI-AVERAGE chg/resource of packing tasks per YEAR IEWM-RESFI-PEAK chg/resource of packing tasks per PEAK TIME THRUPUT SIZING FOR EWM OUTBOUND OBJECTS OEWM-DLV-AVERAGE Outbound delivery documents per YEAR OEWM-DLV-PEAK Outbound delivery documents per PEAK TIME Ware tasks OEWM-PICK-AVERAGE creation of picking tasks per YEAR OEWM-PICK-PEAK creation of picking tasks per PEAK TIME Ware tasks OEWM-CONF-AVERAGE confirmation of picking tasks per YEAR OEWM-CONF-PEAK confirmation of picking tasks per PEAK TIME Ware tasks OEWM-DEST-AVERAGE move warehouse tasks per YEAR OEWM-DEST-PEAK move warehouse tasks per PEAK TIME
NA NA % RF
NA NA % DISP NA NA
0 NA
NA 0
NA 0
MONTHS ST TIME END TIME 0 NA NA NA 0 0 MONTHS ST TIME END TIME 0 NA NA NA 0 0 ST TIME END TIME NA NA 0 0
% DISP
% DISP NA NA % DISP
NA NA RsChg 0 0
NA NA % DISP NA NA
ITEMS 0 0
% CHG
% DISP
MONTHS ST TIME END TIME 0 NA NA NA 0 0 MONTHS ST TIME END TIME 0 NA NA NA 0 0 MONTHS ST TIME END TIME 0 NA NA NA 0 0 MONTHS ST TIME END TIME 0 NA NA NA 0 0
Ware tasks OEWM-RESPI-AVERAGE chg/resource of picking tasks per YEAR OEWM-RESPI-PEAK chg/resource of picking tasks per PEAK TIME HU's OEWM-PACK-AVERAGE packing tasks per YEAR OEWM-PACK-PEAK packing tasks per PEAK TIME Ware tasks OEWM-STAGE-AVERAGE move warehouse tasks per YEAR OEWM-STAGE-PEAK move warehouse tasks per PEAK TIME Ware tasks OEWM-RESST-AVERAGE chg/resource tasks per YEAR OEWM-RESST-PEAK chg/resource tasks per PEAK TIME Ware tasks OEWM-LOAD-AVERAGE warehouse loading tasks per YEAR OEWM-LOAD-PEAK warehouse loading tasks per PEAK TIME OBJECTS OEWM-GOODS-AVERAGE Outbound delivery documents per YEAR OEWM-GOODS-PEAK Outbound delivery documents per PEAK TIME
NA NA
NA NA RsChg 0 0
NA NA % DISP NA NA % DISP
MONTHS ST TIME END TIME 0 NA NA NA 0 0 MONTHS ST TIME END TIME 0 NA NA NA 0 0 MONTHS ST TIME END TIME 0 NA NA NA 0 0 MONTHS ST TIME END TIME 0 NA NA NA 0 0
NA NA ITEMS 0 0
NA NA % CHG % DISP
NON-PRODUCTION SYSTEMS
System Landscape (required) A system landscape consists of the systems and clients that are needed for non-production. Once the system landscape has been defined, you may then create an implementation strategy for the setup and maintenance of the systems and clients within this landscape. IBM and SAP strongly recommend having at least a three-system landscape. A three-system landscape is comprised of a development system, a quality assurance system and a production system. This configuration ensures the proper management and testing of changes to the system before applying them to the live production environment. If nothing is specified we will assume a Dev and Test system. Type First non-production system Second non-production system Third non-production system, if needed Fourth non-production system, if needed Fifth non-production system, if needed Please specify any other additional information to help in sizing Default Dev QA None None None Size Storage Default 100GB's =prod None None None
Operational Purchasing
Active Users - Standard Sizing LOW SRM-PO-1U-Users in SRM(PO with few complex steps) SRM-PO-2U-Users in SRM(PO with many simple steps) SRM-OSC-U-Users in SRM Occasional Shopping Cart SRM-PSC-1U-Users in SRM shopping cart(few complex steps) SRM-PSC-2U-Users in SRM shopping cart(many simple steps) SRM-CONF-U-Users in SRM Confirmation MEDIUM HIGH
SRM-INV-U-Users in SRM Invoice TOTAL CONCURRENT Peak users THRUPUT - Standard Sizing
OBJECTS SRM-PO-1-SRM Purchase Order with few complex steps SRM-PO-1-SRM Purchase Order with few complex steps SRM-PO-2-SRM Purchase Order with many simple steps SRM-PO-2-SRM Purchase Order with many simple steps SRM-OSC-SRM Occasional Shopping Cart SRM-OSC-SRM Occasional Shopping Cart SRM-PSC-1-SRM Shopping Cart with few complex steps SRM-PSC-1-SRM Shopping Cart with few complex steps SRM-PSC-2-SRM Shopping Cart with many simple steps SRM-PSC-2-SRM Shopping Cart with many simple steps SRM-CONF-SRM Confirmation SRM-CONF-SRM Confirmation SRM-INV-SRM Invoice SRM-INV-SRM Invoice
ITEMS 0 0 0 0 0 0 0 0 0 0 0 0 0 0
% CHG
% DISP
Strategic Purchasing
Active Users - Standard Sizing LOW SRM-CTR-LU-Users in SRM Lean Contract Management SRM-CTR-EU-Users in SRM Extended Contract Management SRM-RFX-LU-Users in Lean SRM RFx SRM-RFX-EU-Users in Extended SRM RFx TOTAL CONCURRENT Peak users THRUPUT - Standard Sizing OBJECTS SRM-CTR-L-Lean Contract Management-Contract SRM-CTR-L-Lean Contract Management-Contract SRM-CTR-E-Extended Contract Management-Contract SRM-CTR-E-Extended Contract Management-Contract SRM-RFX-L-SRM Lean RFx SRM-RFX-L-SRM Lean RFx SRM-RFX-E-SRM Extended RFx SRM-RFX-E-SRM Extended RFx ITEMS 0 0 0 0 0 0 0 0 % CHG % DISP MONTHS ST TIME END TIME 0 NA NA NA 0 0 0 NA NA NA 0 0 0 NA NA NA 0 0 0 NA NA NA 0 0 MEDIUM HIGH
NON-PRODUCTION SYSTEMS
System Landscape (required) A system landscape consists of the systems and clients that are needed for non-production. Once the system landscape has been defined, you may then create an implementation strategy for the setup and maintenance of the systems and clients within this landscape. IBM and SAP strongly recommend having at least a three-system landscape. A three-system landscape is comprised of a development system, a quality assurance system and a production system. This configuration ensures the proper management and testing of changes to the system before applying them to the live production environment. If nothing is specified we will assume a Dev and Test system. Type First non-production system Second non-production system Third non-production system, if needed Fourth non-production system, if needed Fifth non-production system, if needed Please specify any other additional information to help in sizing Default Dev QA None None None Size Storage Default 100GB's =prod None None None
GTS-FI-PR-AVERAGE Screenings of payment proposals per YEAR GTS-FI-PEAK Screening of payment run per PEAK TIME OBJECTS GTS-BP-AVERAGE Business Partners per YEAR GTS-BP-PEAK Business Partners per PEAK TIME GTS-MAT-AVERAGE GTS Materials per YEAR GTS-MAT-PEAK GTS Materials per PEAK TIME
0 0
0 NA
NA 0
NA 0
NA NA NA NA
NA NA NA NA
GTS-SCREEN-AVERAGE Business Partner screenings per YEAR GTS-SCREEN-PEAK Business Partner screenings per PEAK TIME
NA NA
NA NA
% CHG NA NA
NA NA NA NA
NA NA NA NA
NON-PRODUCTION SYSTEMS
System Landscape (required) A system landscape consists of the systems and clients that are needed for non-production. Once the system landscape has been defined, you may then create an implementation strategy for the setup and maintenance of the systems and clients within this landscape. IBM and SAP strongly recommend having at least a three-system landscape. A three-system landscape is comprised of a development system, a quality assurance system and a production system. This configuration ensures the proper management and testing of changes to the system before applying them to the live production environment. If nothing is specified we will assume a Dev and Test system. Type First non-production system Second non-production system Third non-production system, if needed Fourth non-production system, if needed Fifth non-production system, if needed Please specify any other additional information to help in sizing Default Dev QA None None None Size Storage Default 100GB's =prod None None None
CE-RUN-AVERAGE payments on cash flow per YEAR CE-RUN-PEAK payments on cash flow per PEAK TIME
OBJECTS Collat/Claims 0
Lines 0 NA
MONTHS Eff matur Cash flow ST TIME END TIME 0 NA NA NA NA NA 0 0 ST TIME END TIME 0 0
Level 2 NA NA NA
NON-PRODUCTION SYSTEMS
System Landscape (required) A system landscape consists of the systems and clients that are needed for non-production. Once the system landscape has been defined, you may then create an implementation strategy for the setup and maintenance of the systems and clients within this landscape. IBM and SAP strongly recommend having at least a three-system landscape. A three-system landscape is comprised of a development system, a quality assurance system and a production system. This configuration ensures the proper management and testing of changes to the system before applying them to the live production environment. If nothing is specified we will assume a Dev and Test system. Type First non-production system Second non-production system Third non-production system, if needed Fourth non-production system, if needed Fifth non-production system, if needed Please specify any other additional information to help in sizing Default Dev QA None None None Size Storage Default 100GB's =prod None None None
OBJECTS ACC-STAT-PEAK Invoice/Account statements per PEAK TIME INS-INV-PEAK Insurance objects per PEAK TIME OBJECTS BROK-ITEM-PEAK Broker report items per PEAK TIME PAY-EXE-PEAK payment plan executions per PEAK TIME PAY-TRANS-PEAK Payment plan transfers per PEAK TIME ACC-BAL-PEAK Account balance displays per PEAK TIME OBJECTS
Items 0 0
NA NA
NA NA
NA NA
NA NA NA NA Items
NA NA NA NA
NA NA NA NA
NA NA NA NA
ACC-STAT-AVERAGE Invoice/Account statements per YEAR INS-INV-AVERAGE Insurance objects per YEAR OBJECTS BROK-ITEM-AVERAGE Broker report items per year PAY-EXE-AVERAGE payment plan executions per year PAY-TRANS-AVERAGE Payment plan transfers per year
0 0
NA NA
NA NA
NA NA
0 0 MONTHS 0 0 0
NA NA NA
NA NA NA
NA NA NA
NA NA NA
NON-PRODUCTION SYSTEMS
System Landscape (required) A system landscape consists of the systems and clients that are needed for non-production. Once the system landscape has been defined, you may then create an implementation strategy for the setup and maintenance of the systems and clients within this landscape. IBM and SAP strongly recommend having at least a three-system landscape. A three-system landscape is comprised of a development system, a quality assurance system and a production system. This configuration ensures the proper management and testing of changes to the system before applying them to the live production environment. If nothing is specified we will assume a Dev and Test system. Type First non-production system Second non-production system Third non-production system, if needed Fourth non-production system, if needed Fifth non-production system, if needed Please specify any other additional information to help in sizing Default Dev QA None None None Size Storage Default 100GB's =prod None None None
Loc Prod R-MDS Master Data Synchronization-SCM->FRP PEAK TIME OP Items R-ODS Order Data Synchronization-SCM->FRP PEAK TIME Loc Prod R-PCSD Processing Consumption (and stock) data PEAK TIME Loc Prod 0 NA Res time 0 SDT yes OP Items 0 NA NA NA WMD yes
ST TIME END TIME 0 0 ST TIME END TIME 0 0 ST TIME END TIME 0 0 ST TIME END TIME 0 0
NA Loc Prod 0
NA
NA
NA
R-FRP--FRP run
NA
NA
NA
NON-PRODUCTION SYSTEMS
System Landscape (required) A system landscape consists of the systems and clients that are needed for non-production. Once the system landscape has been defined, you may then create an implementation strategy for the setup and maintenance of the systems and clients within this landscape. IBM and SAP strongly recommend having at least a three-system landscape. A three-system landscape is comprised of a development system, a quality assurance system and a production system. This configuration ensures the proper management and testing of changes to the system before applying them to the live production environment. If nothing is specified we will assume a Dev and Test system. Type First non-production system Second non-production system Third non-production system, if needed Fourth non-production system, if needed Fifth non-production system, if needed Please specify any other additional information to help in sizing Default Dev QA None None None Size Storage Default 100GB's =prod None None None
Billcycle UTIL-01-AVERAGE billing documents per YEAR BusPart UTIL-02-AVERAGE billing documents per YEAR BusPart 0 OBJECTS OVERVIEW-AVERAGE use of "Customer Overview" transaction per YEAR OVERVIEW-PEAK use of "Customer Overview" transaction per PEAK TIME CONTACT-AVERAGE Customer contacts per YEAR CONTACT-PEAK Customer contacts per PEAK TIME MOVE IN-AVERAGE customer move-ins per YEAR MOVE IN-PEAK customer move-ins per PEAK TIME MOVE-OUT-AVERAGE customer move-outs per YEAR MOVE-OUT-PEAK customer move-outs per PEAK TIME
Partial 0 Deposits 0
C-items 0
Lines 0 MONTHS 0
Contracts 0
Tax 0
ContAcc
Meters
MONTHS 0
NA
NA
NA
NA
NA NA NA NA NA NA NA NA
NA NA NA NA NA NA NA NA
NA NA NA NA NA NA NA NA
NA NA NA NA NA NA NA NA
Enter total CONCURRENT users during the PEAK hour--A user must NOT be counted twice He is either one type of user or another--NOT both at the same time during the PEAK hour
cPROJECTS SIZING
SAPS
GB's
cFOLDERS SIZING
# msgs CPU sizing for the download scenario CPU sizing for the upload and copying scenario # docs Disk sizing based on number of documents and size of document doc size msg size SAPS 0 0 GB's 0
Enter total CONCURRENT users during the PEAK hour--A user must NOT be counted twice
Data size
0 0 Results 0 0
GB's GB's
SAPS GB's
Enter total CONCURRENT users during the PEAK hour--A user must NOT be counted twice He is either one type of user or another--NOT both at the same time during the PEAK hour
Results
Large
SM Simple ADS Server--# documents per hour(interactive) ADS Server--Will ADS PDF cache be enabled? ADS Server--Will changes or printing be permitted? ADS Server--Will all form signatures be extracted? ADS Server--Will the form data be extracted after 2nd signature? No No No No
SM Complex
Medium
SAPS 0 0 Large
SAPS 0
SAPS NA NA NA 0 0 0 0
GB-Storage 0 0 0 0
SOD
Report
SAPS NA
GB-Storage 0 0 NA 0 NA 0 NA 0 0 0 NA NA 0
NA
NA
Daily Transactional Sizing per hour Daily Batch Sizing per hour Total
NA NA NA
Mobile Direct Store Delivery Syncs Mobile Sales for Handheld with R/3 and ECC Mobile Time Sheet-single mode scenario-sync weekly Mobile Time Sheet-administration scenario-sync daily Mobile Travel Expenses-Daily Trip Scenario Mobile Travel Expenses-Weekly Trip Scenario Smart Sync Data Model
AS 0 0
DB 0 0
NRX-Add-on to EP
NW-EP-PRT-PEAK
Click for vendor information USERS Think time 180 Java iViews URL iViews 4 0 % KMC 30
Duet
Users Time Management-Users on Duet Server--PEAK PER HOUR Team Management-Users on Duet Server--PEAK PER HOUR Reporting-Users on Duet Server--PEAK PER HOUR Sales Management-Users on Duet Server--PEAK PER HOUR Sales Management-Users on Duet Server--PEAK PER HOUR Duet Server Duet Memory 0 0.0 0 0.0 0 0.0 0 0.0 0 0.0
NWDI or JDI
Scenario 1-Development in a team Scenario 2-Development with components Scenario 2+-Development with a Track Scenario 3-Layered development
Click for sizing white paper Messages SAPS Scenario 1-Incoming=HTTP,Outgoing=HTTP 0 Scenario 2-Incoming=HTTPS,Outgoing=HTTPS-SSL passthrough 0 Scenario 3-Incoming=HTTPS,Outgoing=HTTPS-SSL termination 0 Scenario 4-Incoming=HTTPS,Outgoing=HTTPS-SSL re-encryption 0 TOTAL 0
Web Dispatcher
Auto-ID Infrastructure-RFID
Slap & Ship Scenario Tag Commissioning Packing
Click for sizing white paper Print Req Tags Pallets Pallets Cases Cases
Time Time
SAPS 0 0
Storage 0.00 0.00 0.00 Storage 0.00 0.00 0.00 Storage 0.00
Time 0
Loading RFID-Enabled Returnable Transport Item-RTI Scenario Tag Commissioning in All Packing/Unpacking in All Pallets Loading/Unloading in All RFID-Enabled Returnable Transport Item-RTI Scenario Tag Commissioning in SCM Print Req Pallets Tags Cases Time Time Cases Time Print Req Pallets Tags Cases Time Time
SAPS 0 0 0 SAPS 0
Packing/Unpacking in SCM Pallets Loading/Unloading in SCM RFID-Integrated Delivery Processing Scenario Tag Commissioning in All Packing/Unpacking in All Deliveries Loading/Unloading in All with hierarchy Deliveries Loading/Unloading in All without hierarchy Items EPC Time Pieces Items EPC Time Pieces Pallets Print Req Deliveries Tags Items Time EPC Time Pieces Pallets Cases Time
0 0 SAPS 0 0 0 0
Upgrade Sizing information for System i Upgrade Sizing information for System p
What AIX level are you running now? 5.2?, 5.3? Other? If not 5.3, do you plan to upgrade to 5.3 with SMT? If 5.3, are you running the SAP workload in a shared pool? 5.3 yes no
INPUTS
ERP CRM BW/SEM Portal PI TREX SM SCM APO SRM GTS Banking Insurance Retail Utilities PLM MDM MISC Upgrade Totals Changed NO NO NO NO NA NA NA NA NO NA NA NA NA NA NA NA NA NA
USER BASED
# of users 0 0 0 0 NA 0 0 NA 0 NA NA NA NA NA 0 0 0 NA 0 SAPS 0 0 NA NA NA 0 NA NA NA NA NA NA NA NA 0 0 0 NA 0 Storage Qser 0 NA NA NA 0 NA NA NA NA NA NA NA NA 0 0 0 NA 0
THRUPUT BASED
Changed ? NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO