Service Availability Management – Reporting
In the last blog we talked about outages. Here we will discuss on how the outages can be processed.
Outages can have statuses like:
New – indicates newly created outages
In Process – being worked up on by an IT employee who is enriching or adjusting the outage details
To be reviewed – once the data is enriched, data is verified before it is confirmed
Confirmed – these outages are part of availability reporting
Rejected – not considered for reporting
Service Availability is a result of all outages which happened during the related reporting period until current day of current reporting period, but occurred outside the agreed Contractual maintenance period.
How Service Availability is measured
TA Technical Availability
DH Total of all downtimes measured in hours per month.
SDH Total of all agreed and scheduled downtimes, plus any downtimes outside the control of SAP, measured in hours per month
TH Total hours per month
Here is an example to illustrate the calculation :
Contractual Maintenance Period(not SLA relevant):
- a) „Maintenance Weekend“ on 3.16 time 08:00 – 18:00 ie., 600 -> = 600min
- b) „Regular Contractual Maintenance period“: on 8.3.16 time 07:00 – 11:00 -> 240 min
Unplanned outage(SLA relevant)
- c) „ABAP System Availability“ 02.3.2016 6:42 – 8:57 = 135 min
DH = Total of all Downtimes 975 Min (a+b+c)
SDH = 840 Min (a+b)
TH = March = 31 days = 744h (=44640Min)
TA= (1- (975min-840min)/44640min) = 99,69% for the system in march
Here is a typical system availability chart :
With that we come to a close of this series. Now you can try out the Service Availability Management in your landscape to benefit from transparent reporting.
I could indicate your email, to enable SAM in my solution manager 7.2.
I have some questions that I hope you can help me to clarify.
Thanks for putting this together.
Would it be possible to show an outage report that shows, planned outage with time/duration, description of the outage, along with the ticket number?
I want to look at something like.
Date SID Outage type(planned vs unplanned separately) Outage duration ( planned vs unplanned separately) Ticket associated with this outage incident/for tracking purposes.
Appreciate if you could throw some light with some options.
Also, could you please upload the process in defining such reports,. or automate them ?
Thanks in advance,
in the standard report provided in the tool, you cannot get the incident details. Could you please elaborate? or feel free to write to me.
Sorry for the delay in response.
Simple question Resmi.
How does one know if the outage is planned or unplanned?
Note: the SLA's are taken into consideration only for unplanned outages and not for any planned activity / outage.
So, based on this how does the system know if its a planned or an unplanned.
I see a room for improvement here, where we can check if the system was set in "MM" mode, and if so, it could be treated as planned activity/outage, and if not, its an unplanned, where the SLA count comes into picture.
Do let me know if you have such an option today, to identify planned vs unplanned outage.
Can you please go through this blog for questions on outage types?
I am really interested in SAM and i have set up everything.
I would like now to get all the information provided by SAM to put them into an SLR Dahsboard.
Is there any simple way to do this?
Is there any cubes containing SAM data or just tables?
THanks a lot for your answer on this subject,