Dell|SAP project sizing information where to get help If you need help understanding this form please email sap_sizin where to send thisOnce you have completed the form please email it to sap_sizing@ This form is designed to reflect SAP's Quick Sizer tool as of March 2006. Version 4 (3/20/06) The aim of this sizing form is to provide a structure for entry of the information required to size the required hardware for an SAP project. The form is based off SAP's Quick Sizer, as are most of the help texts - the text of these are reproduced from Quick Sizer with permission of SAP. No sizing calculations are generated as part of the form, SAP's Quick Sizer is used to generate the sizing in SAPS, their standarised load base. The form being provided Sizing the architecture for a SAP implementation is vital to the success of a SAP implementation. Sizing is an iterative process and should be revisited as you make discoveries through the phases of your implementation. There are two types of sizing that can be performed - a User-Based Sizing or a Transactional-Based sizing. It is best to provide both user information as well as transactional information to get the most accurate sizing result. A user-Based sizing is typical in the beginning of a project, with the mix and usage of modules and users. Although a user-based sizing can be reflective of what will be seen by production go-live, it is best to re-visit the sizing with any updated information to verify that the original planned architecture is still valid. Once transaction information and other particulars are discovered through the various phases of the implementation, the sizing should be checked to determine if any of these discoveries require any changes in the architecture design. In areas such as BW's InfoCubes and ODS objects, where more object descriptor lines might be need than are provided, insert new lines in the appropriate section of the
39
Embed
[XLS]Dell SAP sizing form - Dell United States Official Site | Dell ... SAP sizing... · Web viewTitle Dell SAP sizing form Author Dell Inc. Last modified by Dell Inc. Created Date
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Dell|SAP project sizing information
where to get help If you need help understanding this form please email [email protected]
where to send this Once you have completed the form please email it to [email protected]
This form is designed to reflect SAP's Quick Sizer tool as of March 2006.
Version 4 (3/20/06)
The aim of this sizing form is to provide a structure for entry of the information required to size the required hardware for an SAP project. The form is based off SAP's Quick Sizer, as are most of the help texts - the text of these are reproduced from Quick Sizer with permission of SAP. No sizing calculations are generated as part of the form, SAP's Quick Sizer is used to generate the sizing in SAPS, their standarised load base. The form being provided as a convenience to enter the required input. SAP might make changes to their Quick Sizer tool that are not reflected in this form. SAP's service marketplace should be seen as the authoritive place for sizing information and notes.
Sizing the architecture for a SAP implementation is vital to the success of a SAP implementation. Sizing is an iterative process and should be revisited as you make discoveries through the phases of your implementation.
There are two types of sizing that can be performed - a User-Based Sizing or a Transactional-Based sizing. It is best to provide both user information as well as transactional information to get the most accurate sizing result.
A user-Based sizing is typical in the beginning of a project, with the mix and usage of modules and users. Although a user-based sizing can be reflective of what will be seen by production go-live, it is best to re-visit the sizing with any updated information to verify that the original planned architecture is still valid. Once transaction information and other particulars are discovered through the various phases of the implementation, the sizing should be checked to determine if any of these discoveries require any changes in the architecture design.
The sizing information requested in this document is based on the most current SAP sizing methodology. Customers that require a sizing for any other solution based on solutions not covered in this SAP Sizing Request Form should contact their Dell representative or send an email to [email protected] to get further information.
In areas such as BW's InfoCubes and ODS objects, where more object descriptor lines might be need than are provided, insert new lines in the appropriate section of the worksheet.
Start Stop HoursAverage workday 8 17 9 Workdays per year 250Peak hours 10 12 2
User Based sizing
Users of: Low Medium High Highest number of concurrently active usersActivity ManagementOppurtunity ManagementSales Transactions Service Transactions
Should be less than or equal to the total of the first four lines
Mobile#Users who synchronise/hour
Internet Browse Catalog Shop/Use basket#users in Internet Sales
Throughput - Standard sizing
Average #orders per year Number Line items %change %view Retention (months)Internet Sales 60Mobile sales & service 0Customer Orders 0Service Orders 0
Peak period orders Number Line items %change %view Retention (months) Start End HoursInternet Sales 0Mobile sales & service 0 0Customer Orders 0 0Service Orders 0
Number %change %view Retention (months)ActivitiesCalls & EmailsOpportunities
Number %change %view Retention (months) Start End HoursActivities 0Calls & Emails 0Opportunities 0
%change The percentage of objects that will be changed during their retention period
%viewRetention For how many months the objects will remain in the databaseLow users Instigate SAP server activity every two minutesMedium users Instigate SAP server activity every thirty secondsHigh users Instigate SAP server activity every ten seconds
Interaction Center activity (per year)
Peak period Interaction Center activity
The percentage of objects that will be viewed during their retention period. If each object were viewed two times then that would be 200%