KPI Calculation
Maximum number of active users
This KPI is the maximum number of end users with high or medium activity recorded by the system during the service level report reporting period. The system ignores end users with low activity.
The Service Level Report is generated weekly with period „2“.
■ EWA values of the 1st week:
Users with medium activity + 40 users with high activity = 60 active users
■ EWA values of the 2nd week:
Users with medium activity + 70 users with high activity = 80 active users
Result: max(60;80) = 80
Average system availability per week
The KPI gives the average availability value of all EWA reports in a week.
The Service Level Report is generated weekly with period „3“.
|
EWA values of the 1st week: |
EWA values of the 2nd week: |
EWA values of the 3rd week: |
Average system availability per week |
100% |
50% |
75% |
Result: (100% + 50% + 75%) / 3 weeks = 75%.
Average response times at times of high dialog load
This KPI is the average value of the dialog response times in the hours with the highest number of dialog steps.
The Service Level Report is generated weekly with period „3“.
|
EWA values of the 1st week: |
EWA values of the 2nd week: |
EWA values of the 3rd week: |
Hours with the highest number of dialog steps |
10:00 – 11:00 |
09:00 – 10:00 |
10:00 – 11:00 |
Average response time of type DIA for the time interval |
1250ms |
2500ms |
1000ms |
Number of dialog steps per week for the time interval |
7500 |
9800 |
5000 |
Result: (1250ms * 7500 steps) + (2500ms * 9800 steps) + (1000ms * 5000 steps) / (7500 steps+ 9800 steps+ 5000 steps) = 1743ms.
Average response times in dialog
This KPI is the average dialog response time per week.
The Service Level Report is generated weekly with period „3“.
|
EWA values of the 1st week: |
EWA values of the 2nd week: |
EWA values of the 3rd week: |
Average response times of type DIA |
1200ms |
1600ms |
1140ms |
Number of dialog steps of type DIA |
68000 |
51000 |
72000 |
Result: (1200ms * 68000 steps) + (1600ms * 51000 steps) + (1140ms * 72000 steps) / (68000 steps+ 51000 steps+ 72000 steps) = 1284ms.
Maximum number of dialog steps per hour
This KPI is the maximum number of dialog steps per hour for the type DIA
The Service Level Report is generated weekly with period „3“.
|
EWA values of the 1st week: |
EWA values of the 2nd week: |
EWA values of the 3rd week: |
Hours with the highest number of steps |
17:00 |
11:00 |
18:00 |
Maximum number of dialog steps per hour |
2090 |
3100 |
2800 |
Result: max(2090;3100;2800) = 3100.
Average database access times in dialog
This KPI is the average value of the database accesss times in the average dialog response times.
The Service Level Report is generated weekly with period „3“.
|
EWA values of the 1st week: |
EWA values of the 2nd week: |
EWA values of the 3rd week: |
Average response times of type DIA |
1200ms |
1600ms |
1140ms |
Average database response times in the average response time |
390ms |
480ms |
370ms |
Number of dialog steps of type DIA |
68000 |
51000 |
7200 |
Result: (390ms * 68000 steps) + (480ms * 51000 steps) + (370ms * 72000 steps) / (68000 steps+ 51000 steps+ 72000 steps) = 406ms.
Average database access times in an update
This KPI is the average database access times during the average update response times per week from the EWA reports of the selected reporting period.
In EWA, the KPI “Avg. DB Request Time in Update Task” is the average database load in the average response times for the type UPDATE in all dialog transactions in the week.
The Service Level Report is generated weekly with period „3“.
|
EWA values of the 1st week: |
EWA values of the 2nd week: |
EWA values of the 3rd week: |
Average response times of type UPD |
800ms |
950ms |
740ms |
Average database response times in the average response time |
290ms |
580ms |
370ms |
Number of dialog steps of type UPD |
5500 |
4100 |
4700 |
Result: (290ms * 5500 steps) + (580ms * 4100 steps) + (370ms * 4700 steps) / (5500 steps+ 4100 steps+ 4700 steps) = 399ms.
This KPI is not displayed for SAP BW and SAP SEM.
Database size
This KPI is the current database size.
The Service Level Report is generated weekly with period „2“.
|
EWA values of the 1st week: |
EWA values of the 2nd week: |
Database size at the end of the week |
52GB |
56GB |
Result: The system shows the last value: 56GB.
Database growth
This KPI is the delta value between the current database size and the database size in the previous Service Level Report.
The Service Level Report is generated weekly with period „2“.
■ Database size two weeks ago = 56GB
■ Current database size: 58GB
Result: 2GB
Maximum CPU load on database server
This KPI is the maximum CPU load measured on the database server.
The Service Level Report is generated weekly with period „2“.
|
EWA values of the 1st week: |
EWA values of the 2nd week: |
Highest hourly maximum CPU load measurement |
78% |
85% |
Result: max(78%;85%) = 85%.
Maximum CPU load on application server
This KPI is the maximum CPU load measured on the application server.
The Service Level Report is generated weekly with period „2“.
|
EWA values of the 1st week: |
EWA values of the 2nd week: |
Highest daily maximum CPU load measurement |
44% |
57% |
Result: max(44%;57%) = 57%.
Average BW query run-time
This KPI is the average run-time of BW queries.
The Service Level Report is generated weekly with period „3“.
|
EWA values of the 1st week: |
EWA values of the 2nd week: |
EWA values of the 3rd week: |
Average BW query run-time |
80s |
66s |
83s |
Number of navigation steps |
7400 |
5200 |
7500 |
Result: (80s * 7400 steps) + (66s * 5200 steps) + (83s * 7500 steps) / (7400 steps+ 5200 steps+ 7500 steps) = 77,5s.
Average BW query database run-time
This KPI is the average database access time during the average runtime of BW queries per week, from the EWA reports in the reporting period.
The Service Level Report is generated weekly with period „3“.
|
EWA values of the 1st week: |
EWA values of the 2nd week: |
EWA values of the 3rd week: |
Average BW query run-time |
22s |
34s |
40s |
Number of navigation steps |
7400 |
5200 |
7500 |
Result: (22s * 7400 steps) + (34s * 5200 steps) + (40s * 7500 steps) / (7400 steps+ 5200 steps+ 7500 steps) = 31,8s.