INITIAL SIZEUP REPORT VERIFICATION

Your business decisions will lead you to the sizing, but it’s not easy to translate it into the sizing forms, and even be sure everything was covered, that’s why you have to understand every business requirement, peak times, user behavior, number of transactions executed by them and most important of all, re-visit this requirements at every decision project step.Īll your interpretations and decisions related to the business requirements must be made accordingly.

INITIAL SIZEUP REPORT VERIFICATION

The sizing procedure helps customers to determine the correct resources required by an application within customer’s business context.įrom the customer perspective, sizing is the translation of business requirements into hardware requirements, but from the development point of view, sizing refers to the creation of a sizing model for the product functionality with a reasonable number of input parameters and assumptions.Ĭonsidering this behavior can be changed during project, we cannot forget to re-visit this planning if any change is made on landscape requirements even from customer or development point of view, this can change the actual requirements and impact on overall solution performance.Īlso, depending on the scope, this may also include a detailed analysis of the systems to be migrated and/or verification of the sizing assumptions made on-premise or cloud. There are many perspectives that we need to consider when doing this planning.

This Blog was made to help customers prepare the SAP S/4HANA landscape conversion considering the sizing relevant KPI’s for the key performance indicators.

Initial sizeup report