formulário sun para sap sizing

SAP R/3 Rel 4.6B

Project Questionnaire

SAP - Sun Competence Center

Altrottstr. 31

69190 Walldorf / Germany

FAX: +49 6227 356 222

Copyright Sun Microsystems Inc. 2000

1. General Information

1.1 Customer Information

Company Name

Department

Street

CityPostal Code

Phone Fax

Business Segment

1.2 Technical Contact in this Project to Sun

NameSurname

Phone Fax

E-mail

1.3 Sun Sales Representative

NameSurname

Phone Fax

E-mail

1.4 Sun System Engineer

NameSurname

Phone Fax

E-mail

1.5 External SAP Service & Consultant Partner

Company Name

Department

Street

CityPostal Code

Phone Fax

2. SAP Project Information

2.1 Timeframe

Has your company already decided for SAP R/3 ? O Yes O No

If not, when will they decide ?

When do you want Sun to deliver the offer ?

When will the R/3 installation take place ?

When will the R/3 system go live ?

2.2 Development Systems

How many R/3 development systems will be installed?

Separate R/3 system?

O Yes O No

Planned SAP R/3 Release ? (example.: 4.5A )

When will the development system go live ?(Month/year)

2.3 Integration Systems

How many R/3 test- and integration systems will be installed?


O Yes O No

Planned SAP R/3 Release ? (example: 4.5A )

When should the test- and integration system go live ?(Month/year)

2.3 Productive Systems

How many R/3 Production systems will be installed?


O Yes O No

Planned SAP R/3 Release ? (example: 4.5A )

Database (e.g.: Oracle, Informix, Adabas)

When will the production system go live ?(Month/year)

Do you need a systm with higher availability (failover solution)O Yes O No

NOTE:

Sun and SAP recommend to install Development, Test (Integration, Pre-Production) and Production systems on separate systemsin order to increase availability and managebility.

3. Legacy ERP Environment & Migration Servics

3.1 Existing ERP Enviroment

Hardware Vendors

Operating Systems

Application/Programs

Networks

Please describe the existing system landscape

3.2 Migration/Integration Services

Do you require integration services ?O Yes O No

O

Non-SAP system to R/3

OR/2 to R/3 migration

OR/2 to R/3 transfer by batch

O R/2 to R/3 online connection (RFC)

OR/3 to R/3 link (ALE)

OR/3 to R/3 migration (platform migration)

Please describe, what kind of data migration/integration will be needed ?:

Who will provide the migration plan (Sun, partner, self) ?

When will this plan be delivered (DD.MM.YYYY) ?

4. R/3 Configuration Requirements

4.1 User Based Sizing

4.1.1 SAP User Activity Definitions - READ CAREFULLY

In order to size a SAP R/3 system Sun needs more information about the users that will work with the SAP R/3 application. In addition to the number of SAP user accounts (also called Named Users) you can provide us more detailed information on how users will work with SAP R/3.

Not all users that have an account in SAP R/3 are equally active. User activity has a major impact on the required CPUs, so SAP defines three categories of user activity:

LOW:

Occasional User/Relevant User

An Occasional User is logged-on to the system and consumes system resources. On average typically around 400 dialog steps (screen changes) are executed per week, equivalent to ten dialog steps an hour (assuming a work week of 40 hours) or one every six minutes. This user should be used if the user accesses the system from time to time. Typically this type of user definition fits for executives/controllers. Important : The memory volume is calculated assuming that these users are typically working during peak hours.

MEDIUM: Accountant / Clerk

A Medium User or Active User is logged-on to the system and consumes system resources. On average typically around 4800 dialog steps are executed per week. That is equivalent to 120 dialog steps an hour (assuming a work week of 40 hours) or one every 30 seconds. This user is accessing the system permanently and is working with the system on a regular base. This type of user definition fits for accountants, clerks or office personnel.

HIGH:

Datatypist / Telesales User / Power User

A High User or Power User is logged-on to the system and consumes system resources. On average typically around 14400 dialog steps are executed per week. That is equivalent to 360 dialog steps an hour (assuming a workweek of 40 hours) or one every 10 seconds. This user is accessing the system permanently and is intensively working with the system on a regular base. Typically, this type of user definition fits to users working in the telesales environment, datatypists or power users like application developers.

With information about those three types of SAP users Sun will determine the required CPU performance and memory requirements for your online business using SAP sizing guidelines and our experience from other SAP installations.

4.1.2 SAP Online Business Definitions - READ CAREFULLY

Before entering your data into the tables, it is necessary for you to identify your online peak hours. Online peak hours are the hours where the maximum number of logged-on R/3 users impose the maximum load to the R/3 System. The maximum number of logged on users have a critical impact on sizing main memory to achieve optimal online performance resulting in low response times.

You might run into problems identifying your peak online hours when your company operates in more than one timezone. We recommend that you analyze your processing time windows thoroughly, because you will face an extended online window which may overlap with your offline background processing activities.

Usually not all the users that have an account in a SAP R/3 System are logged on at the same time. So most likely the sum of the logged on users during peak hours per module will be smaller than the number of SAP user accounts per module. The total number of the logged-on users during peak hours should not exceed the total number of SAP user accounts per module.

In many cases, users work in more than one module, making it difficult to determine the correct number of SAP user accounts per module. In general a user will have only one SAP user account per SAP R/3 system. To avoid counting of users twice, count them only for those modules where they have their most activity.

Example: A user who works 70% in FI and 30% in CO should count as a FI user.

Sometimes you will not be able to tell how many users you will have in the various activity categories. In this case just enter the total number of logged on users during peak hours. We will assume that those users work as users with medium activity.

As mentioned in the SAP definitions the activity of a user depends on the number of dialog steps (Screen changes) performed. Within the SAP world a dialog step is the smallest unit that creates load in a SAP R/3 system. Dialog steps do not equal SAP business transactions. One SAP transaction usually consists out of many dialog steps.

In addition the number of dialog steps can vary between different SAP R/3 installations for the same SAP transaction, because the number of dialog steps in a SAP transaction in many cases depend on the customizing of the R/3 System to fulfill the specific requirements of the customer. So customizing has a large impact on the SAP R/3 system configuration. A sizing based on transaction numbers also includes an assumption about the dialog steps per SAP transaction which may not reflect reality.

A more accurate way to size a configuration is based on the number of SAP business object creations and accesses, also known as Quantity Based Sizing. For large configurations Sun and SAP recommends to use the Quantity Based Sizing methodology. For the same reason SAP uses this methodology in their own tools to determine throughput requirements. Sizing will be an iterative process throughout the project lifecycle. We recommend tp resize the configuration using Quantity Based sizing at least once before Production Go Live.

In general we will base our sizing on your data, our experience, and information we get from SAP's Performance & Benchmarking Group.

PLEASE COPY THIS PAGE AND USE SEPERATE FORMS FOR SEPERATE SYSTEMS !!

4.1.3 SAP User numbers / Standard modules

SAP R/3 SYSTEM TYPE:

O DEVELOPMENTO TESTO INTEGRATIONO PRODUCTION

PEAK ONLINE HOURS:BeginEnd

O MON O TUE O WED O THU O FRI O SAT O SUN

4.1.4 SAP User numbers / Industry Solutions





Industry solutions are Add Ons to the Standard SAP R/3 Application Modules and adapt the functionality of the Standard SAP R/3 Application Modules to the requirements of the specific industry sector. If you plan on using an Industry Solution, additional information about your business is required to determine the system configuration. Use the table below to give us information about the Industry solution you intend to use in the future.

We will contact you with more specific questions on the particular Industry Solution.


4.1.5 SAP Transaction Profile





In order to get a more complete picture of your system requirements, we need more information about your online transaction profile.The sizing will be based on the default values below. If you think that these values do not reflect your transaction profile, please change the values and give us a short explanation:

Time WindowDefaultYour Value

How many days in a month is the system active ?20 days

How many hours per day is the system

doing online processing ? 8 hours

How many hours per day is the system

doing batch processing ? Peak/off Peak4 hours

Do users reside in more than one timezone?NO, just 1 timezoneYES, ___ timezones

Please, give details:

In general SAP R/3 users working online perform different types of transactions that have a different impact on the system requirements of an SAP R/3 system. Experience from other SAP R/3 installations tells us that the following assumptions seem to reflect average R/3 online activity.

Transaction Type ProfileDefault (Total=100%)Your Value

(Total=100%)

Data Entry Transactions40%

Online Reporting30%

Background Jobs (ABAP/4 Reporting)20%

Other Transactions (example. Administration, etc...)10%



4.2 Quantity based Sizing





Sizing a SAP configuration based on the SAP object quantities will enable us to size the system more accurately than with the user based approach. In addition, we can use the transaction data to estimate SAP R/3 disk space requirements.

Dialog Processing

Dialog Processing means creating, displaying and changing objects using the standard SAP transactions. Use these input fields, nonregarding wether you use this functionality in dialog or unattended. The same sizing approach is valid here.

Number of working days

If not changed, we assume 200 working days per year. This leads to an equal distribution of all objects to be created, changed or displayed over these number of days. If you have different constellations, please change the number of days accordingly. A higher number of working days will lead to lower SAPS ratings. A reduced number of working days will lead to higher SAPS numbers.

Objects per year, retention period, no. of subobjects

Please enter the number of objects created per year and the average number of subobjects in the appropriate fields. This information will be used for the average SAPS calculation. Together with the retention time we are able to estimate the disk requirements. Please understand, that with a given retention period you define the point in time, when your archiving solution should be operational.

Average calculation

For the average SAPS calculation you can define the start and end time of the day. If you do not fill in the information we assume a working day of 8 hours, beginning at 8 am and ending at 4 pm. The average number of objects to be considered during these 8 hours will be calculated out of the objects created per year divided by the number of working days.

In some cases (i. e. monthly billing runs), dedicated peaks will create nearly all objects. In this case it makes no sense to calculate the number of objects per day. You are free to give us the information regarding your object creations per day. This will overwrite our default assumption.

Peak Calculation

In many cases you will experience dedicated peaks you want to consider. This could be either a higher workload during a small timeframe (i. e. higher workload between 10 am and 12 am) or data uploads, which might need some resources. Other reasons are also possible, so give us the information regarding start and end time as well as the number of objects your process in the given timeframe.

% of object changes

Please enter the percentage of how often the newly created object gets changed (average).

% of object display

Please enter the percentage of how often the newly created object gets displayed (average).


If you experience difficulties filling in the different fields, please refer to the SAP Quicksizer online help. Since this input sheet is completely built on the Quicksizer design, you can always use SAP's business information for this sizing approach. (https://sapnet.sap-ag.de/quicksizing)

Background Processing

To determine the required throughput, we need to know how many objects have to be processed in a given time window:

Objects per day

Please enter the maximum number of objects being fully processed in batch within the execution time. Additionally please give us the tine window for these batch runs (start and end time). For payroll, you should specify the average number of retrocalculations for each calculation.

MRP

Please fill in the MRP information, if required. For assistance, please refer to SAP's online help.





5. Backup Requirements

In order to propose a backup plan, we need to calculate resources based on the database size.

If you have an estimate of your disk size please enter it here.:

______GB

How often is a backup performed ?

O dailyO weekly

If other, please specify how often:___________________________________

During what hours/days should the backup be performed ?

______________________________________________________________

Are there any existing or planned products (example: Veritas Enterprise NetBackup) you plan to use for SAP system backup ?

If so, please name them: __________________________________________

Should other data than the SAP system be backed up?

OYesONo

If so, please give details:

______________________________________________________________

______________________________________________________________

Do you have any procedures to carry out a database recovery?

OYesONo

If so, please give details:

______________________________________________________________

______________________________________________________________

Will your IT staff need training in database backup/recovery in an UNIX environment?

OYesONo

5.1 Backup duration in hours

Note: A full backup means saving the R/3 database (offline) and the complete system configuration (e.g. root file- system, etc.).

Backup Type Min. Duration (hrs) Max. Duration (hrs)

Online (Full)

Offline (Full)

Online(DB only)

Offline (DB only)

5.2 Restore duration in hours

This is the time to get the tape backup restored to the timestamp of the last complete backup, additional time will be needed to roll forward logs, etc.

Backup Type Min. Duration (hrs) Max. Duration (hrs)

Full

Online

Offline

6. Print Spool Requirements

In addition to the system load generated by users, batch or background processing we need to learn more about your print spool requirements, because they can have a significant impact on the SAP R/3 system configuration.

Printer ClassPrinter SpeedProfileNumber

of

PrintersActivity

Online HoursActivity

Offline hours

Desktop10 - 20 pages

per minute1 to 2 users

connected to the desktop (SAPLPD)From:

To:From:

To:

Group or

departemental> 10 pages per minutemore than 2 SAP users will print via a spool serverFrom:

To:From:

To:

High

Volume> 50 pages

per minuteSAP will print via a separate spool server, mainly used for large volumesFrom:

To:

From:

To:

Does a separate server operate as printer spooler already ?

OYesONo

If so, what kind of printer spooler is it ? (Unix based?):

______________________________________________________________

Are there any existing printing solutions to be integrated?

OYesONo

If so, please give details:_____________________________________

______________________________________________________________

Are there any requirements for high volume printing ?

OYesONo


______________________________________________________________

Do you plan on using an Archiving/Imaging Solution with a

direct interface to SAP R/3 via SAP's ArchiveLink interface ?

OYesONo


______________________________________________________________

7. Network Requirements

7.1 Type and number of end user desktops (Presentation Layer):

TypeNumber of Desktops

Intel PC with Windows / Windows NT

Intel PC with OS/2

Apple MacIntosh

Unix Workstation

X - Terminals

Java - Stations

Other: _________________________________

Total number of end user desktops:

Total amount of printers connected to the end user desktops:

What kind of network product is installed on the desktop ?


Do you wish to install a CUA Server for SAP R/2?

OYesONo

7.2 Existing Network Enviroment

O 10 MBit EthernetO 100MBit EthernetO Token Ring (4M)O TokenRing(16M)

O FDDIO ATMO Other:_________O Other:_________

7.3 WAN Requirements

Specify the WAN connection that will be available?

O X.25

O ISDNO Frame RelayO Other:_________

How many of your company's subsideries/external departments should be connected via WAN to the R/3 system? ________________

8. System Availability Requirements

8.1 Unplanned Downtime Of The R/3 System

When would unplanned downtime be especially damaging to your business ?


Are there any particular seasonal, peak or other unusual requirements (e.g. end of fiscal year) when downtime would be especially damaging to your business ?


One hour of unplanned downtime for the R/3 system costs your company:

Can you afford not having the system available for a complete day (24 hours) ? OYesONo

8.2 Planned Downtime Of The R/3 System (e.g. Software Upgrades)

Planned Downtime affordable for your company's business in a week from Monday to Sunday in hours: ____________

If your company cannot afford planned downtime over the weekend please describe the reasons why below:

8.3 High Availability Requirements

Note: High Availability R/3 configurations (e.g. failover, takeover or disaster recovery) increase the complexity of your R/3 system design. This will require more training for your R/3 administrators and additional hardware components which will increase the system costs.

Besides the redundant hardware design of Sun's servers, do you think that your production R/3 system configuration requires the following additional HA levels?:

OManual failover

OAutomatic failover

In case of system takeover or failover how much of the work load of the production Database server should provided in %(0-100): _____________

For the failover system, we recommend using a pair of systems where one is the Database Server and the other is the Central Instance (CI). Other configurations are possible. Please indicate any special failover configuration:

______________________________________________________________

______________________________________________________________

What kind of disk technology for data consistency would you prefer?

ONone (not recommended)

ORAID 1 (mirroring)

O RAID 1+0 (mirroring and striping)

ORAID 5

OThree-way mirroring

OFour-way mirroring

Would you like further information about creating a disaster recovery plan?

______________________________________________________________

______________________________________________________________

EMBED Spreadsheet

EMBED Spreadsheet

EMBED Spreadsheet

EMBED Spreadsheet

SAP-Sun Competence Center

Sun Microsystems Inc. 2000

17 of 17V-4.6B-01-E

_11844800.unknown

_13092608.unknown

_12326376.unknown

_11808360.unknown

formulário sun para sap sizing

Documents

sap r3 system

sap r3 application

separate r3 system

r3 test

r3 or2

r3 transfer

r3 installation

r3 production systems