PRELIMIARY SIZING GUIDELINE

Sizing GRC PC Version 10.0 Beta

Release/Ramp-Up

Released to SAP Customers for Beta/Ramp-up

Document Version 1.0, December 2010
 Disclaimer

The information in this presentation/document is confidential and proprietary to SAP and

may not be disclosed without the permission of SAP. This presentation is not subject to
your license agreement or any other service or subscription agreement with SAP. SAP
has no obligation to pursue any course of business outlined in this document or any
related presentation, or to develop or release any functionality mentioned therein. This
document, or any related presentation about SAP’s strategy and possible future
developments, directions, and functionality of products and/or platforms, are all subject
to change and may be changed by SAP at any time for any reason without notice. The
information in this document is not a commitment, promise, or legal obligation to deliver
any material, code, or functionality. This document is provided without a warranty of any
kind, either express or implied, including but not limited to, the implied warranties of
merchantability, fitness for a particular purpose, or non-infringement. This document is
for informational purposes to provide guidance in preliminary sizing of hardware for beta
testing and may not be incorporated into a contract. SAP assumes no responsibility for
errors or omissions in this document, except if such damages were caused by SAP
intentionally or grossly negligent. Once SAP officially publishes sizing guideline at the
general availability of the product/solution, this preliminary guideline is not valid any
more.

© SAP 2008 / Page 2

 Agenda

1. Introduction
1.1. Functions and Requirements of SAP GRC Process Control
1.2. Architecture of SAP GRC Process Control
1.3. Factors that Influence the GRC Process Control Performance
2. Initial Sizing for GRC Process Control v 10
2.1. Assumptions
2.2. Sizing Guideline
3. Comments and Feedback
4. Sizing Fundamentals and Terminology

© SAP 2008 / Page 3

 Functions and Requirements of SAP GRC
Process Control – An Example

Example: PC 10.0

Scenario 01: Refresh Inbox

Click Work Inbox

Click Refresh Button

Scenario 02: My Process

Click My Process
Open Process
Navigation between the tabs.

Scenario 03: Organization

Maintenance
Click Organization.
Create Organization.
Save Organization.

© SAP 2008 / Page 4

Process Control 10.0 Architecture &
Landscape

optional
Front End Client
SAP NW Portal 7.01
SAP GUI GRC Portal Content
Web Browser
7.10 (Business Package)

optional
SAP NetWeaver BW
GRC BI Content
AC, PC & RM
(Add-On: GRCFND_A) SAP ERP (4.6C – 7.1)
NW Function Modules
(Plug-in: GRCPINW)

HR Function Modules
PC Automated Ctrls
(Plug-in: GRCPIERP)

SAP NetWeaver
optional AS ABAP 7.02
Identity Management optional
Solutions SAP BusinessObjects Non-SAP Business
(SAP or Non-SAP) Adapter
GRC Suite 2010 Applications
 Selected Factors That Influence the
Performance
Landscape
 Number and type (SAP, Non-SAP, IDM, etc.) of target/backend systems: for Refresh Work Inbox, My
Process.

Business Requirements
Total number of Work Items (users/roles/profiles) in each of the backend system for Refresh Work Inbox

 Total number of 500 Processes, 500 Controls, 80000 Local Controls for Creating Work Items.

 Total number of 500 Processes, Regulations , 500 Sub Process for My Process Scenario.

Number of average Processes per User and number of average systems associated per Work Item.

 Number of Refresh Inbox and My Process Navigation per hour or per working day and number of maximum
concurrent users.

Disk size depends on number of Processes , Controls , Sub Processes ; frequency of ad -hoc analysis, etc. It
will also depend on # of clients

© SAP 2008 / Page 6

 PRELIMINARY SIZING GUIDELINE FOR PC 10.0

Refresh Inbox
Category Peak Memory Consumption Minimum SAPS

Small 50 Users 16.525 MB 50*7 = 350 SAPS

Medium 200 Users 16.525 MB 200*7 = 1400 SAPS
Large 750 Users 24.709 MB 750*7 = 5250 SAPS

Category Peak Memory Consumption Minimum SAPS

01 Users 16.525 MB 1*7 = 7 SAPS

10 Users 16.525 MB 10*7 = 70 SAPS
100 Users 16.525 MB 100*7 = 700 SAPS

© SAP 2008 / Page 7

 PRELIMINARY SIZING GUIDELINE FOR PC 10.0

My Process
Category Peak Memory Consumption Minimum SAPS

Small 50 Users 24.709 MB 50*11 = 550 SAPS

Medium 100 Users 36.983 MB 100*11 = 1100 SAPS
Large 250 Users 36.983 MB 250*11 = 2750 SAPS

Category Peak Memory Consumption Minimum SAPS

01 Users 24.709 MB 1*11 = 11 SAPS

10 Users 24.709 MB 10*11 = 110 SAPS
100 Users 36.983 MB 100*11 = 1100 SAPS

© SAP 2008 / Page 8

 PRELIMINARY SIZING GUIDELINE FOR PC 10.0

Organization Maintenance
Category Peak Memory Consumption Minimum SAPS
Small 01 Users 28.64 MB 1*49 = 49 SAPS
Medium 05 Users 28.64 MB 5*49 = 245 SAPS
Large 10 Users 28.64 MB 10*49 = 490 SAPS

Category Peak Memory Consumption Minimum SAPS

01 Users 28.64 MB 1*49 = 49 SAPS

10 Users 28.64 MB 10*49 = 490 SAPS
100 Users 36.983 MB 100*49 = 4900 SAPS

© SAP 2008 / Page 9

 PRELIMINARY SIZING GUIDELINE FOR PC 10.0

Planner
Category Peak Memory Consumption Minimum SAPS
Small 01 Users 16.525 MB 1*94 = 94 SAPS
Medium 03 Users 24.709 MB 3*94 = 282 SAPS
Large 10 Users 24.709 MB 10*94 = 940 SAPS

Category Peak Memory Consumption Minimum SAPS

01 Users 16.525 MB 1*94 = 94 SAPS

10 Users 24.709 MB 10*94 = 940 SAPS
100 Users 36.702 MB 100*94 = 9400 SAPS

© SAP 2008 / Page 10

 PRELIMINARY SIZING GUIDELINE FOR PC 10.0

Policy Acknowledgement
Category Peak Memory Consumption Minimum SAPS
Small 01 Users 16.525 MB 1*172 = 172 SAPS
Medium 10 Users 16.525 MB 10*172 = 1720 SAPS
Large 100 Users 24.709 MB 100*172 = 17200 SAPS

Category Peak Memory Consumption Minimum SAPS

Small 01 Users 16.525 MB 1*172 = 172 SAPS

Medium 10 Users 16.525 MB 10*172 = 1720 SAPS
Large 100 Users 24.709 MB 100*172 = 17200 SAPS

© SAP 2008 / Page 11

 Sizing Fundamentals and Terminology

Sizing
Sizing means determining the hardware requirements of an SAP application, such as network bandwidth,
physical memory, CPU processing power, and I/O capacity

 Processing times of business transactions or tasks

CPU  Cost factor: Number and processing power of servers

 Data that resides on the database

 File read and write activity to storage
Disk size
 Cost factors
Disk I/O – Backup/recovery depends on size of database
– Storage capacity

 Allocated to a user or background process

Memory  Garbage collection, planning run
 Cost factor: Physical memory slots

Front-end  Transferred amount of data

Network  Network time and roundtrips
Load  Cost factor: Leasing bandwidth

© SAP 2008 / Page 12

 Sizing Fundamentals and Terminology

SAPS
The SAP Application Performance Standard (SAPS) is a hardware-independent unit that describes the
performance of a system configuration in the SAP environment.

S AP
A pplication
P erformance
S tandard

2,000 fully processed 100 SAPS

order line items per hour*

SD
Benchmark

* ^
= 6,000 dialog steps and 2,000 postings or 2,400 SAP transactions

© SAP 2008 / Page 13

 Sizing Fundamentals and Terminology

Initial and Expert Sizing

Initial Sizing refers to the sizing approach that provides statements about platform-independent requirements of the hardware
resources necessary for representative, standard delivery SAP applications.

Expert sizing refers to a sizing where customer-specific data is being analyzed and used to put more detail on the sizing result.

Hardware Budget Sizing
Smaller companies
 Very simple algorithms
 Assumptions, likelihoods
Advanced Sizing
Medium to large companies
 Throughput estimates
 Questionnaires, formulas
Go
Expert Sizing Live
Large or complex projects
 Additional guidelines
 Custom calculations

 Level setting of project  Usage of standard tools  Analysis of custom coding

 Risk identification  Focus on core business  Custom sizing guidelines
processes

Initial Sizings

Re-Sizing Delta Sizing Upgrade Sizing

All projects All projects All projects

 SAP system monitors  SAP system monitors  SAP system monitors

 Goal: Extend an existing  Goal: Extend an existing  SAP Notes
system by load system by functions  Goal: Upgrade SAP softw are
 E.g. by volume  By different functions,
100 additional users e.g. you are live w ith
w ho'll do the same as CRM and w ant to add
the current productive SCM
ones

Production Sizings – whenever there is a change in throughput, sizing must be done

© SAP 2008 / Page 14

 Sizing Fundamentals and Terminology

Configuration and System Landscaping

Hardware resource and optimal system configuration greatly depend on the requirements of the customer-
specific project. This includes the implementation of distribution, security, and high availability solutions by
different approaches using various third-party tools.

There are some "best practices" which may be valid for a specific combination of operating system and
database. To provide guidance, SAP created the NetWeaver configuration guides
(http://service.sap.com/instguides  SAP NetWeaver).

© SAP 2008 / Page 15

 Comments and Feedback

Please send your comments and feedback to SAP to be considered in the official
Process Control v 10.0 Sizing Guide.

Contact: Rajat Saluja, rajat.saluja@sap.com

© SAP 2008 / Page 16